Hi Stephan, My English is not good enough to polemize with you, I just want to clarify my point of view:
Generally the motivation of open project staff is to have the maximum of people that use their product. Furthermore behind the open source idea there is the idea that software are to be distributed spreadly to improve them. I only pointed at that for my opinion a poor documented software leads people to a lot of frustration in trails-errors loop and dissuades them to go ahead with it. I didn't say that users shouldn't go deeper in the software, but that the documentation should help people to go into the code and understand it, again if you look at dynamic duo tutorial, you will see that all concepts are exposed and then it is easy to understand the code . Effectively Dynapi is complex but a long time ago when I was at school I learned that nothing is complex with good explanation. Be careful to not fall in a common developer syndrome: you will not show to all other that you are the best hacker of the universe by putting some obscucated piece of code on the web and proclaiming that nobody is good enough to understand it ! At the opposite you will be more regarded if you give to the software community something that helps in software quality improvement. If you look at Apache that is the most popular open project now more used than other commercial web server like Microsoft IIS and co, you will see that the documentation is very abundant and comprehensible. And I'm sure the good user documentation participates to its success. Dynapi is a really good initiative that can bring a lot to web development and can lead to promote open software and standard software toward proprietary initiative like Macromedia flash or Microsoft stuff. But before the project must become more "open" to the web developer community ! Eric. _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-help
