Lets point it out from the view of this certain developer: You need to study eclipse API so
in the endeffect you know the eclipse API better afterwards (+), but that takes time (-). He will
get a application to code faster, which is good for the person (+) but also good for any other
developer in flash(++ VS -). But you need to distribute it (and even worse: write documentation) (-)
No other one (as with the example of ASDT and HXDT) will contribute something, which tends to
be flash-alike, so you are forced to encurage the development es well.
So from the view of this developer it would take a bunch less work and a lot more afford if he just writes
it by himself for himself, unless there is some community that is able to support his work (by documentation,
handling bug reports, creating tutorials, what so ever). So what great perspective are you talking about.
I have heard a lot of times "I want to support that" but the common and usual praxis is that this
wont happen. In the end the developer who programmed this gets out with a minus and just because people
think programming it once is the only problem.
In order to make someone doing it I suggest to make(if youre really willing to get it) a fond of Money (real life value)
that is kept for people that can contribute code to this project and can be given to them when they made something
outstanding. And make some community deal to handle things like (as mentioned before) documentation that is
compulsive to that people that confirm to help.
Its kinda hard point of view but only having "hey do it for the community" is just not a very big opportunity, especially for this kind of topic.
yours
Martin.
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
