From: Pascal <pb...@oi...> - 2001-01-11 15:13:50
|
My widgets might work okay, but they need some changes to make them work correctly with onprecreate events instead of oncreate events, and the eventlisteners must be attached to the constructors, and not the prototypes of the widgets (problem with all old widgets) The precreation code will speed up the creation (and make netscape more stable) of layers with many child layers. All child layers are now created into one string (using the <div> tags and style properties) and that string is then written into the parent layer.. then the parent layer is added to the document, automatically creating ALL child layers and itself in one single document write. because of some browser checking for the precreation (to make the correct strings) in the dynlayer, the browser file must be included before the dynlayer. l8r, Pascal Bestebroer (pb...@oi...) Software ontwikkelaar Oberon Informatiesystemen b.v. http://www.oibv.com > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Richard :o > Verzonden: donderdag 11 januari 2001 15:14 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] CVS updated > > > Ok, i tried the latest snapshot with your two altered files > from the cvs, > it's basically ok, but: > * Buttons are ok now regarding text/events, but if you double-click a > text-button it selects bits of the caption, so it needs a > cover layer after > all. > * The list widget still doesn't mouse-over > * Mouse-over doesn't seem to occur for a layer with image. > > I'm afraid it seems this whole precreation thing has somewhat > passed me by, > probably it happened when I was offline over Christmas, so > I'll check the > archives for relevant info. What I don't understand though is > why Pascal > keeps saying that his widgets will be obsolete under the new > DynAPI, while > they all work perfectly alright under the latest snapshot, with latest > events + dynlayer files. Is it a question of not working ok > under DOM maybe? > The only widget I could not get working without altering was you're > scrollbar, which gives out of stack error in scrollbar.js, > line 137 which is > a setSize(w,null) call. > > * Now browser.js has to be included in your page before > dynlayer.js or error > "is undefined dynlayer.js line 265", this was not the case a > while ago. I > guess that's due to the precreation changes. > > Keep up the war, > > Richard :o > > ma...@ri... > www.richardinfo.com > (Everything running on, and ported to the 19/12/2000 snapshot > of DynAPI2) > > ----- Original Message ----- > From: "Jordi 'IlMaestro' Ministral" <jmi...@or...> > To: <dyn...@li...> > Sent: Thursday, January 11, 2001 1:12 PM > Subject: Re: [Dynapi-Dev] CVS updated > > > > I'm missing events... did I screw something ? First I > thought but then > going back to the latest code ( > > before my modifications ) I am missing those same events. > Ohh please just > a little luck from time to > > time !!!!! > > > > In NS you can apply the same "for (each image in doc) > img.lyrobj = myself" > event trick to the links > > array. > > > > > > Jordi 'IlMaestro' Ministral wrote: > > > > > I have updated CVS with a new events.js that should fix IEs event > problems. All the example files > > > worked fine. This is what happened ( at least this is > something I found, > maybe there are still > > > other issues ): > > > > > > - All browser events in DynAPI are captured and passed to the same > EventMethod. This eventMethod > > > identifyes the physical layer, cancels browser event, > searches for the > appropiate DynmLayer object > > > and invokes its event. > > > > > > - In IE, in order to access the DynLayer object we use the lyrobj > property of the DIV itself. This > > > property is set when creating a layer so from code > executed within the > DIV's scope we can still get > > > to our DynLayer obj. The problem with our contents was that when > clicking on a text, most of the > > > times the srcElement of the event was not the DIV but a > FONT, TD, TR, > TABLE, UL,... element. That > > > element did not have a pointer to the dynlayer and thus > the API could > not route the event properly. > > > > > > - This issue was partially solved for images by doing: > > > > > > if (is.ie) for (i in dlyr.elm.all.tags("img")) > dlyr.elm.all.tags("img")[i].lyrobj=dlyr; > > > > > > So images had a pointer to the layer aswell. This we > would have needed > to do to all elements in our > > > content, somethig really painful. Instead, I added this > line inside > eventmethod. > > > > > > for(;is.ie && !realsrc.lyrobj && realsrc.parentElement && > > > realsrc.parentElement!=realsrc;realsrc=realsrc.parentElement); > > > > > > Which actually makes realsrc travel IE's object hierarchy > until we find > the lyrobj reference. By > > > doing so I fixed events in IE5 and 5.5. I'm not that sure > everything is > fine now, but it is an > > > improvement. > > > > > > There are several lines in that method such as that > > > > > > if (e.type=="mouseover" || e.type=="mouseout") return false; > > > > > > just before the bubbleEvent() call that I don't > understand but I prefer > not to touch them. > > > > > > By the way, it seems that when clicking on a selectable > text, NS does > not fire a click event. > > > Mousedown and mouseup are fired, but click isn't. We could fire it > manually but then when clicking > > > outside a text we would get two onclicks. > > > > > > Tell me if I broke something. Sure I did. > > > > > > Cya > > > > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > ____________________________________________________________ > > Get your free domain name and domain-based e-mail from > > Namezero.com. New! Namezero Plus domains now available. > > Find out more at: http://www.namezero.com > > > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |