RE: [Dynapi-Dev] Next Generation part II

[Pascal <pb...@oi...>]

Why not use a simple image tag for a simple image? why use a complete
dynlayer?

An object that can delete itself effectively is indeed something that we
need, but my main concern on that topic is the fact of where this bug
exists? The DynAPI or the browsers?  Anyway, if a problem of the DynAPI it
should also be possible to fix in the current code and is no need for a full
change on the dynapi.

The current dynlayer might be possible to make smaller, but that means no
controll over dynlayers at all (no setsize, moveto, etc) so you could just
as easy use normal html tags for that (it's not dynamic anyway).

So, what extra functionality (which is not possible with the current model)
could we achieve by changing to a new structure ?

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Doug Melvin
> Verzonden: dinsdag 30 januari 2001 19:21
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] Next Generation part II
>
>
> I vote for a 'modified' 'object model.
> My main concern is for an object that can delete itself effectively.
> Also, the base Layer Object should be just that,
> BASIC. A small and simple as possible.
> An icon in the top left corner of you web page.
> Which does nothing more than just sit at the top left corner
> of your webpage
> uses a very small fraction of the functionality currently
> built into the
> DynLayer object.
>
> ----- Original Message -----
> From: "Eytan Heidingsfeld" <ey...@tr...>
> To: <dyn...@li...>
> Sent: Tuesday, January 30, 2001 12:31 AM
> Subject: [Dynapi-Dev] Next Generation part II
>
>
> > Ok, so now we have all discussed and recommended and
> finished throwing
> > stones. After we all got in-depth about OO and prototypes
> and classes
> where
> > are we going. My recommendation of how to act is as such:
> > * Create a DynLayer(mayber change it's name) that is
> totally seprate and
> > stand alone. It includes only methods to affect the layer
> and events that
> > are triggered from the outside(mouse and keyboard events).
> > * Create the basic objects: Application, Object, Component
> > Application:
> > Manages the DynLayers focus and events
> > Object:
> > Basic object with create and destroy
> > Component:
> > Basic object with dynlayer.
> >
> > I'd be glad to change the model if anyone has new and
> improved ideas.
> >
> > Now except for the actual model I want to know if we have
> enough ppl who
> > want a next generation to continue.
> >
> > 8an
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>