DomLib is Pascal's beast. He used to be a developer on the DynAPI, but has long since stopped working on this project. In fact I'm not sure if he works on domlib anymore either. Checkout domlib at http://www.dynamic-core.net/projects/domlib/index.php.
There are some other alternatives to the domlib that work in dom only browsers: http://www.domapi.com http://judelib.sourceforge.net DynAPI3 is still in development. However, you should see some updates for it real soon (hint hint :)). -- Robert Rainwater [EMAIL PROTECTED] Saturday, March 23, 2002, 10:05:43 PM, Mark wrote: > Just read about his DomLib - he says that it has all the core functionality > of DynApi2 - what's the road map here - is there a DynApi3 or is DomLib > going to replace this? > I like the fact that DomLib is forgetting backwards compatibility - I'm > going to take a further look at this - maybe I should be targeting my > development towards this. > Mark > At 13:07 24/03/2002 +1100, Michael Pemberton wrote: >>Mark Proctor wrote: >> >>>some of my own thoughts: >>>currently the "drop" event must be defined for every object you might >>>drop the source onto. This means that you don't have a drop event that >>>tells you the targeting layer, if one hasn't been setup. So I think an >>>event needs to be in place for the source that can tell you what the >>>target is whether the target has a onDrop listener on not - anyone have >>>any ideas for a good way of doing this? >> >>Here's a copy of a drop event listener I just pulled from some old >>DynaCore code (now there's a blast from the past): >> >> myDrop.ondrop=function(e) { >> me=e.getTarget() >> source=DynAPI.document.dragobject >> me.addChild(source) >> } >> >>The listener is then attached to the required dropzone. >> >>However, if you look into how to implement "simple" events, you could >>attach the above method to the DynLayer.prototype and you will end up with >>a method that is used across ALL dynlayers. >> >>>I think grouping would be nice too. While I might setup my ondrop event I >>>may only want it to fire for certain layers - or have different onDrop >>>events for different targets. So I think it would be nice to an array >>>that holds other layers that would fire the event. you can either hold >>>layers, or hold groups which contain layers Does this make sense? Anyone >>>got any good ideas on how to implement this? >> >>It is possible to attach the same EventListener to more than one layer. >>Look into this to see how to implement your desired setup. >> >>>Another great project would be pixel level detection - although I won't >>>be working on this. I think if a bitmap mask (an array of 1,0 for each >>>pixel in the layer) is specified for the source and target it should try >>>to pixel level collision detection - this would be great for games - any >>>takers? >> >>You should check out ww.dynacore.net >> >>Pascal has done some amazing this with the DynAPI and DHTML in general. >> >>-- >>Michael Pemberton >>[EMAIL PROTECTED] >>ICQ: 12107010 >> >> >> >> >> >> >>_______________________________________________ >>Dynapi-Dev mailing list >>[EMAIL PROTECTED] >>http://www.mail-archive.com/[email protected]/ > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/[email protected]/ _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
