sharing code between kjs and khtml

[George Staikos]

On Monday 25 July 2005 13:19, Darin Adler wrote:
> On Jul 24, 2005, at 6:35 PM, Maciej Stachowiak wrote:
> > I can think of three basic options for code sharing:
> >
> > 1) Cut and paste the relevant files, use in both places. This sucks
> > because any fixes or improvements would have to be made in two
> > places, and history shows that people will usually forget to update
> > other copies of the code.
> >
> > 2) Dump in kjs and export for use in khtml, even though this stuff
> > has basically nothing to do with a JavaScript API.
> >
> > 3) Make a new module that both kjs and khtml depend on ("kxmlcore"?
> > "kxmlbase"? something like that...).
>
> I like both (2) and (3) and don't have a strong preference between them.
>
> But then again I usually agree with Maciej on things, so that's no
> big surprise.

  I also like 3.  2 could be annoying since we use KJS in areas where we don't 
use KHTML and which has nothing to do with KHTML or related technology.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/