[Dynapi-Dev] DynDuo now pointing to SourceForge

[Dan S. <dy...@fu...>]

Sorry I've been out of the loop for a while there.  I've put a new notice on DynDuo about DynAPI 2 and SourceForge.  So you can probably expect some more visitors your way.  Actually the notice on the DynAPI site has been there for a while - that's how you've been getting new visitors (primarily developers who likely followed the Freshmeat link).

For right now I've pointed Dynduo directly at the SourceForge project page, but this is not ideal.  One thing I could suggest is reworking IMaestro's site to link back with SourceForge more obviously, or move it to the http://dynapi.sourceforge.net location altogether.  Have a common download area, and some kind of explaination of what files people need in order to have a working DynAPI 2 - even to me it wasn't entirely clear.  The documentation is fantastic, and the changes you've been making are great.

Pascal has some of the code I was working on a while back.  The loadpanel worked great, and (with all due respects to IMaestro) you will most likely want to use my ScrollBar/Window implementation, it's some very solid code.  Some significant changes must be done to dynapi.js in order to accomidate the way I was building my widgets.  The biggest being the removal of the "onCreate" handler altogether, and using only listeners for create and resize in the widgets.  This is what we do in WebOS because it's the only real way to implement inheritance properly with code like this.  Take a look at my ViewPort/ScrollPane files to see how it can be done in a good manner.

I've noticed none of you guys really know what to do with that ServerTask thing I wrote :)  So what I'd like to do is remove that from the DynAPI directly - I'll maintain that code separately because I was primarily using it as the serverside communication scheme in my app-that-never-gets-finished, the portal thing.  I haven't worked on it in a month, but what I'd like to do is sync it up with the latest DynAPI 2, so that I can continue working on it without forking my JS code so much from yours.

Anyways, I'll be keeping in tune, probably not actively developing much directly with DynAPI but using it and making suggestions along the way.

BTW: dy...@fu... will be my email-address for messages to this list, you can still reach me at my primary mail da...@da...

Dan Steinman