As the developer of a "clone", I don't agree wth your contention that the existance of such variations are taking away from the main project. It is in my own interest to make the dynapi as bug-free as humanly possible.
I disagree with your use of the word "clone". Each of the alternate disributions that have been released recently have all been enhancements of the DynAPI. If I purchased a new stereo, I see no reason for me to stop upgrading the individual components. To use the same analogy, just because the latest component wasn't made by the original manufacturer of my stereo, I see no reason to avoid installing it.
It is the conbination of ideas that has enabled the DynAPI to grow. I have recently required a new feature and it resulted in a loss of compatability. In my instance, I did not require Mac compatability and as such I did not have any problems. I do not expect all DynAPI users to drop mac support just because I have included a feature that they may never need.
Also, regarding your comments on what should or should not be dicussed on this board, you are posting to the wrong list. Your post appears to be directed at those who are developers and as such would be best posted to the DynAPI-Dev list.
This list, DynAPI-Help, is designed to help those who are using the DynAPI. If I come across a solution to someone's problems, why shouldn't I post my comments. Even if such comments may be related to my experience with my own development.
I closing, if your main argument is that not enough focus is being given to the main project, then I think that annoying the active developer and accusing them of not being dedicated can only lead to more developers focusing on other projects.
David Steele wrote:
I dont want to seem arrogant, but all i see is people posting about their--
"own" api which from all i can see is just a hacked version of the DynAPI
while the original "real" api just gathers dust in the CVS with only the
core member(s) making updates, all these clones can only add to peoples
confusion about which version to use ,compatibility, bugs, blah blahMaybe people are getting bored, i dunno but it seems like no-one is
interested in getting the DynAPI up and problem free, and more interested in
doing their own version or IDE's etc as people have allready pointed out in
the comments in the news section.Come on people lets stop trying to mess about with imitations or alternative
versions, this is the DynAPI project , the same one that is in the top 20 of
project activities in sourceforge ! if you want to do your own thing or
version then fine start your own project at sourceforge and start your own
list groups etc, as the title says this is the DYNAPI list, so please lets
concentrate on getting this up and bug free first and fix the bugs that
exist in the bug library instead of trying to claim all the glory with your
own clone(s).it would be a shame to give up at this stage after so many people put so
much effort into this (no names dp,rw)
major developers have allready left this project (i wonder why?)too many cooks spoil the broth
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
_______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-help
