Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Dan Willemsen
On Mon, 2003-03-10 at 21:24, Raymond Irving wrote: > Ok, the majority is for the common-base solution. I'll > work on this and create a dynlayer_common.js and a > mouse_common.js file. > > IMO only the above two groups should require common > base solutions. > > As for the overwriting of function

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Raymond Irving
Ok, the majority is for the common-base solution. I'll work on this and create a dynlayer_common.js and a mouse_common.js file. IMO only the above two groups should require common base solutions. As for the overwriting of functions that are browser specific, I would suggested that we branch the

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Kevin
I agree with Doug's idea below, though Raymond mentioned: > 3) The library class > currently does not support common-base files (but this > can be added). I'm not sure? Are dynapi.api.* common files and then we add dynapi.api.ext.whatever for an extension. The dynapi pseudo-library system is clev

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Dan Willemsen
I hate these replay to all things I agree with everything he said. On Mon, 2003-03-10 at 21:20, Doug Melvin wrote: > > Let's hear the views of the other developers: > > > > 1) Should we implement a common-base file system for > > dynlayers? > > Yes. > > > > 2) Do you think it will be easier to

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Doug Melvin
> Let's hear the views of the other developers: > > 1) Should we implement a common-base file system for > dynlayers? Yes. > 2) Do you think it will be easier to maintain a > common-base dynlayer file? Yes. Clarification. While having to export a function once you have a browser specific fix i

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Raymond Irving
> To: "Dynapi-Dev" <[EMAIL PROTECTED]> > Sent: Monday, March 10, 2003 3:02 PM > Subject: Re: [Dynapi-Dev] New functions for DynLayer > > > > > > --- Kevin <[EMAIL PROTECTED]> wrote: > > > I prefer extending DynLayer in one file only. > >

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Raymond Irving
--- Benoit Marchant <[EMAIL PROTECTED]> wrote: > I think these should be added to dynlayer main > files. There's something > inconvenient with the split of all the dynlayer > files for different > browsers. There's no common file for apis that don't > have anything > browser related but rely on

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Doug Melvin
lt;[EMAIL PROTECTED]> Sent: Monday, March 10, 2003 3:02 PM Subject: Re: [Dynapi-Dev] New functions for DynLayer > > --- Kevin <[EMAIL PROTECTED]> wrote: > > I prefer extending DynLayer in one file only. > > So are you for the DynLayerXtension library? > > > Wi

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Raymond Irving
--- Kevin <[EMAIL PROTECTED]> wrote: > I prefer extending DynLayer in one file only. So are you for the DynLayerXtension library? > Will setFocus raise z-index on a layer to be the > highest? > Or did you mean something else? Yes, it will place the layer as the top but it also does a few other

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Benoit Marchant
I think these should be added to dynlayer main files. There's something inconvenient with the split of all the dynlayer files for different browsers. There's no common file for apis that don't have anything browser related but rely on existing dynapi api, which I guess is the case for something lik

Re: [Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Kevin
Raymond Irving <[EMAIL PROTECTED]> wrote: > Hello Everyone, > > Some time ago I started creating a new type of Layer > that would improved on DynLayer's features, but now > I've scrapped that idea to just fully support and > improve DynLayer as a low level layer for the api. > Below you'll find a

[Dynapi-Dev] New functions for DynLayer

2003-03-10 Thread Raymond Irving
Hello Everyone, Some time ago I started creating a new type of Layer that would improved on DynLayer's features, but now I've scrapped that idea to just fully support and improve DynLayer as a low level layer for the api. Below you'll find a few functions I had in mind. I'm wondering if I should