> MTASC was written is a testimony to this. However this has its own pros > and cons. If more than one person was working on MTASC I believe it > would have many more features than it currently does, and there would be > a much greater dialog between the authors and the community. The choice > of OCAML retricted this (though so did Nicolas' choice not to open up > the development tree). Other than Ralf's work with HamTASC, there have > been no other user contributions to MTASC (this may also be so that > MTASC can be dual-licensed?).
Hi Alex, I'm of course aware that OCaml is somehow restricting the number of people that can contribute, but I started MTASC alone, there was not so much Open Source community at this time, and no team willing to contribute. In that case, choosing the best tool I know and handle to get it done was obvious choice (and for the people that have been at OFLA, remember that MTASC and the SWF Library comes from MotionTypes which was itself written in OCaml ). I didn't write any documentation on MTASC sources but I don't think they're really difficult to understand, they're actually quite small (120 KB in 8 files !) so of course if peole want contribute I expect them to make the effort of learning OCaml . Ralf did really great work on HamTasc and the reason theses features haven't been merged is because I wanted to keep mtasc easy to use and do not offer too many rarely used features since they make difficult to maintain the whole for a long time. I'm accepting patches and nobody ever bought mtasc for relicensing (actually the "paid support" & relicensing paragraphs have been removed from the mtasc website a long time ago). Nicolas _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
