--- 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 existing dynapi api,
> which I guess is the 
> case for something like setMinimumSize 

Juho had suggested that we grouped all non-browser
specific functions into what was called a common file.
As I mentioned before 1) a common file IMO would be
much harder to work with. 2) If a specific function
was changed in the future to fix a browser specific
bug, etc this would require us to move the function
into the various _xxx.js files. 3) The library class
currently does not support common-base files (but this
can be added).

Let's hear the views of the other developers:

1) Should we implement a common-base file system for
dynlayers? 

2) Do you think it will be easier to maintain a
common-base dynlayer file?

(please voice your opinion on this matter as it's very
important for future enhancements. Note: These changes
will _not_ affect the api)


>(what about
> setMaximumSize ? I 
> use this in the upcoming dragevent additions).

Sounds good to me

--
Raymond Irving

> 
> For example, now, p.setX=function(x)
> {this.setLocation(x,null)} is 
> defined in all the dynlayer_ the same way, which is
> bad.
> So if it is the occasion to create such a file,
> let's do it ! And have 
> that shared file included all the time, that way we
> can move to it 
> whatever is currently duplicated.
> 
> Does it make sense ?
> 
> Benoit
> 
> 
> On Monday, March 10, 2003, at 12:57  PM, Raymond
> Irving 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 few functions I had in mind.
> >
> > I'm wondering if I should add these functions to
> > dynlayer_xxx.js files as the average user will
> most
> > likely use them on a regular basis, or should I
> add
> > them to a separate class library (e.g.
> > DynLayerXtender)?
> >
> > setAutoSize(b) - set the size of the layer
> whenever
> > content changes
> >
> > setMinimumSize(w,h) - prevents the layer from
> being
> > sized below the specified. This is useful when
> > creating widgets that should not be set below a
> > certain size.
> >
> > setDragMode(b,boundry) - enable/disable dragging.
> > Easier than DragEvents.enabledDragEvents, etc
> >
> > setEnabled(b) - disable/enable a layer
> >
> > setBorder(w,c)  - Set a border on the layer. w=int
> or
> > {top,right,bottom,left},  c = string or
> > {top,right,bottom,left}
> >
> > setFocus(b) - sets the focus of a layer.
> >
> > setToolTip(text) - set's a tool tipe for the
> layer.
> > this will cause tool tip to appear when the mouse
> is
> > moved over the layer.
> >
> > What do you think?
> >
> > --
> > Raymond Irving
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Tax Center - forms, calculators, tips, more
> > http://taxes.yahoo.com/
> >
> >
> >
>
-------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> >
>
http://www.mail-archive.com/[EMAIL PROTECTED]/
> >
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/[EMAIL PROTECTED]/

Reply via email to