Hi,

> what i see is a "dynAPI help" list , now in my eyes that means help on the
> dynAPI, so how does this Afro thing help people who are trying to get help
> with the dynAPI ?
>From day1 all developers have had their own versions of dynAPI, if you
don't, you can't experiment with code without breaking the snapshot
versions. Some of these were put online, like Pascal's DynaCore, or Jordi's
distro. These were always available as an alternative to the official
distro, and never threatened it's existence, although at one point it was
agreed that Jordi's version would be used as the official version, as no-one
had access to update Sourceforge then.

You're probably right that a reply to a help-request about dynapi, refering
to Afroapi code , is only helpfull if the question asker has the know-how to
apply the fix to their Dynapi code, and thus not so newbee friendly, but
then, it's probably better than no help at all, which might often be the
case.

> Why cant we work together and get this dynAPI project fixed and bug free
> instead of pissing about with clones, surely many hands make light work
> instead of too many cooks spoil the broth.
So what do you call Dan's new revised DynAPI version he posted about a few
days back. I can assure it's a lot different than the current release (more
so for the developers than for the users).
What about Jordi's dynAPIX? once it was a clone, now it's the code you are
using.

> why try and decrease the dynAPI userbase ? , seems
> like he is merely using this list to meet his own objectives.
A little competition never hurt anyone, as long as credit is given where
due. Especially when a real effort is made to help the DynAPI by submitting
bugs and patches.

> now flame on or not i dont give a fuck, but i give a fuck about loyalty to
a ...
At this point I wonder about the sincerity of your post.

Richard.



_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dynapi-help

Reply via email to