I think I know what the answer would be and that it isn't what you'd expect.
The number of active developers vary a lot. Robert and Jordi being the most devoted active developers on the current 2.5.x version and Dan on the 2.9.x branch towards a DynAPI 3.x release. BUT the strenght of the dynapi project is that there are lots of other people doing development in a multiude of different ways, making it hard to define what 'AN' active developer is. What needs to be worked on isn't always the focus in this project. The developers are for the most part thinking in what they would use which may be different from what other users would need. Currently though the most sought for feature is documentation (although I personally feel that there's a lot more whining about this than lacking). The second most sought for feature is a wider scope of compability. Roadmap is kinda diversed and induvidual. I think you might rather talk of a philosophy in which keeping backwards compability is the strongest aim (can't say I'm totally sure on this, cause its very diffuse) Actiually I think that Pascal might be right about DynAPI being hold back, mainly because of keeping Netscape 4.x compability. Dropping support for this browser, would loosen up on many restrictions in the API and is also what probably could first be dropped, because of its minimal market-share. However, the questions is if that should be done in favor of support for currently unsupported or only partly suported browser/systems. Linux and Mac as platforms are still having lot's of issues and maybe that should be considerd for efforts. But also for that, there's need to join up some developers who are working on those platforms and intrested in delving into adapting DynAPI features for those platforms. Linux and MacOSX are after all at least heading for a future which Netscape 4.X isn't. Basicly DynAPI is at its core aiming for development towards the widest possible mainstream of internet users to enjoy DHTML features. Its legacy being native and FREE browser supported dynamicity in webpages for 4.x browsers and up. Rivals is mostly closed-code development platforms like Macromedia Flash in the lead. Wheter DynAPI actually could match up to Flash I'm doubting, but it has something that still makes it worth considering - pro-java syntax. While Flash is forcing on its own scripting language, DynAPI is a good tool if you considering moving up from simple javascripting to the Java language. What it lacks that competitiors doesn't is documentation and a tool for development. Documentation - even if somewhat outdated - was done by Pascal and a series in 6 parts essay on using the DynAPI on ZDnet. Also a couple of few developers - including myself - are working on another SourceForge project for a IDE to DynAPI and dynamic webpage development in general (see http://dynapyide.sf.net). Also a couple of other projects have been announced even if I'm unsure of their current status. So things are moving even if not as directed as you were probing for. Now anybody fill in and correct me if I'm errorous on some points, but I think I have fairly good insight into the project, been monitoring it for almost 2 years. Henrik V�glin [ [EMAIL PROTECTED] ] PS I think this only belongs in the developers list. Cross-posting is not apprieated in most cases, so I only post here. DS --- Mark Proctor <[EMAIL PROTECTED]> skrev: > I contacted Pascal to ask about what's happening > with DomLib, thought I > forward his reply to the list - hoping to maybe > spark up a little > discussion on his comment of DynAPI being held back > and talk about what's > happening in the future. I'm new to the project but > I want to get involved > as a I see DynAPI being a tremendous help in my > projects, so having an idea > of a roadmap and some of the obstacles DynAPI is > facing would be fantastic > - I would be more than happy, with your help, to > compile this document if > nothing is available at the moment. > > How many active developers does DynAPI have? > Do we know who is working on what? > What needs to be worked on, but doesn't have a > current owner? > What are DynAPI's current obstacles, and what are > the proposals - and what > roadmap is proposed? > Whats being done about taking advantages of new > technology and standards, > but giving some backwards compatibility - maybe a > two tier system? > > Mark _____________________________________________________ Hitta sn�rapporter... fr�n 500 olika skidorter i Europa p� http://se.snow.yahoo.com _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
