Hi Nicolas,
As said, a good IDE will be a first start for haXe adoption. I'd like that it'll be hxdt as eclipse is becoming my everyday tool now. For the framework request, I remember the old flash days where as2lib where at his early stage. No one were complaining for the lack of framework. I think this point is important as I don't see haXe as a competitor of Flex. To be precise, a competitor of Flex component set. If one day, someone port one as2 GUI toolset to haXe it will be nice. But I think there won't be so much work as haXe is a direct successor of MTASC with which actionStep and aSwing are build (for example). One of my major trouble with haXe is the adoption. I don't imagine for now giving an haXe project to an another team. They will be completely lost. When one thinks about his technology of choice, he tries to pick the one that will be extendable. If someone tell me to develop a new product, I'll definitively think of this aspect first. So IMO, I'll choose haXe for a development product only if I am sure I'll be the only developper. It's a big constraint but investors and society need a kind of perinnity for their product. I won't take that risk for now, as I'll put my responsability on that type of choice. BTW, I really believe in the potentialities of haXe. I'll try to put some efforts on its grow, as it could be a good alternative to work with. So the last point is, as nobody never take mtasc further (mainly because ocaml seems not to be appealing), the continuation of haXe, eventhough Nicolas said is motiontwin will continue on it. It's IMO a great risk that it is a one maintainer only project. Everyone knows mtasc is in a very stable and efficient status. But haXe is another deal… Greetings. ----------- erixtekila http://blog.v-i-a.net/ _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
