Sorry, I didn't mean to scare anyone, and you have a good point.

I guess a better way would be to create core structure where the only
separate libraries are those that handle functions and objects that are
specific to the browsers.

Like having a moveto function for the layer object which is something that
more or less exists in all the browsers now, but may need to be implemented
differently.  You wouldn't want to change the functionality of this
function, it should always do the same thing.

Some of the other features that may contain additional functionality may be
able to use these code libraries(browser specific), and be a single entity
that is not browser specific(i.e. it uses the libraries pulled in for that
browser to perform it's functions).  Some of these extended functions may
not be available for all platforms.



|-----Original Message-----
|From: Matthew A. Shirey [mailto:[EMAIL PROTECTED]]
|Sent: Tuesday, February 27, 2001 4:36 PM
|To: [EMAIL PROTECTED]
|Subject: RE: [Dynapi-Dev] not so sure about this anymore
|
|
|Frankly the idea of maintaining a codebase like that scares the shit
|outa me.  What happens when you want to change something that is
|actually common to all of the browsers?  Do you have to go into each
|subdir and change?  Possibly introducing bugs in one or more of the
|directories doing so?  I am sorry I cannot even type, I am still
|twitching at the idea.
|
|

_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to