Well, there are two branches of DynAPI, the 2.5.x that is going obsolete as of the other, new 2.9 branch. I'm just guessing you're working with the 2.5.x branch, right?
I think Illmaestro is the one to contact about 2.5.x and you should try and reach Dan Steinman if you should be working with the new 2.9 branch. But most of all I'd recommend you showcase the codes as widgets or extensions if possible. If not, try put together a quick distribution based on the current dynapi distribution and put it out for download. You can then announce it on the official website at http://dynapi.sourceforge.net/ I know it may seem a bit tad way to go around it, but thing is that is how most of the new code made it there, besides of course beeing that implemented directly by active developers attached to the SourceForge project. Henrik V�glin [ [EMAIL PROTECTED] ] PS I must add that though I'm co-editing the official DynAPI website, I have no access to the projects administration. I have though once contributed some code (the original DynAPI2 keyevents), so there's where I've got my experience on the issue --- Seamus Malone <[EMAIL PROTECTED]> skrev: > I've talked with some of your about this project > before. I'm nearing final > approval for conributing the code back to the > project and think I can go > ahead and start trying to finalize and sync this > code with other peoples > efforts... I'm unsure how exactly to figure out > who's working on similar > projects and what conventions and design patterns > have been established... > anyways, below is a brief description of the > project... I've been using it > to create a UI layer on top of a JSP/tag-lib based > application, though I'm > sure it has a lot of other applications... it seems > to solve several key > problems with complex multi-widget pages. Please > contact me if this is > interesting to you or you've been working on similar > extensions of the > framework. > DynContainer > Allows the nesting of containers and widgets. This > allows page layout to > occur in a modular way with a parent-child > hierarchy. This includes > clam-shell type behaviors where parent objects are > in either an open or > closed state. When they are open they reveal their > children when they are > closed they hide them and appear in a 'collapsed' > mode. Containers arrange > themselves in a predictable modular fashion with > parent elements at the top > and child-elements aligning themselves in order > below the parent object. > When several dyncontainers are nested complex yet > dynamic page layouts can > be achieved. > DynForm > DynForm contains a DynForm class and a DynInput > class. It creates a > DynApi-compatible way of representing forms. It also > provides additional > functionality on input elements, simple > cross-browser getters and setters > for form-input fields. This was developed to > facitlitate the retrieval and > formatting of information from the form segments > that are created by the > dynContainer framework. Previous to DynForm it was > impossible to gather and > submit form information distributed through various > layers in a context > agnostic method. > > Seamus Malone > User Interface Architect > CascadeWorks, Inc. > [EMAIL PROTECTED] > office: 415.402.8194 > cell: 415.317.2922 > > > > > > ------------------------------------------------------- > 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]/ _____________________________________________________ Gratis e-mail resten av livet p� www.yahoo.se/mail Busenkelt! ------------------------------------------------------- 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]/
