salut, article intéressant ici
Should the developer community fork the Flex project ? http://www.arpitonline.com/blog/?p=160 ma réponse (qui pour le blog est du spam :p): ---------- Hi, as you say forking Flex is a huge process but even if it possible in term of license (yes the MPL allow you to fork it) I'm not sure how well it would work in the flash/flex community look at some open source AS3 3D framework Papervision3D, Away3D, Sandy, etc. instead of regrouping different devs around 1 project with same goals, you can see split of devs on different projects too bad as 1 well organized project would be stronger, but well it's like that now to fork something like Flex, people would really need to gather around a set of common goals and stick together because 2 or 3 devs not gonna cut it, for something this big even if you can start with a small team the goals should bring more devs into the same project instead of generating more forks and splits something healthy: 2/3 devs start to fork Flex, more devs come to help, you end up with a dozen dedicated devs to the fork etc. the project can grow something more likely to happen: 2/3 devs start to fork Flex, 2/3 other devs start their own fork, etc. none ofthe forks really go anywhere that's the math, for something as big as Flex you need a big team involved and that's why the goals and reasons to fork should be very clear the main problem I see with Flex (the framework) is that it combine 2 things that should be separated: an application framework and a UI/ Component framework. So one way to fork would be to focus only on one of those - either fork only an application framework - or either fork only a UI framework personally as a dev who want to be able to switch from a Flex project to an AS3 project, either compile it with Flash or mxmlc or asc there is no way I gonna reuse the Base64Decoder from Flex, so going the route of an AS3 application framework is appealing (either if I have to reimplement a Base64Decoder etc.) and we kind of started that with http://code.google.com/p/maashaack/ and to illustrate look at system.data.collections.ArrayCollection vs mx.collections.ArrayCollection our ArrayCollection is not tied to a UI framework, you can use it with the Flash CS3 components if you want or any other UI framework/components. Also because we focus on AS3 the language, the maashaack framework (that we consider as an application framework, and far from being finished) can be reused in places where AS3 can run, and recently we focused on the command-line because we think to be able to reuse or write AS3 for the command-line is also useful. So for that we have worked on Tamarin and extended it with another project http://code.google.com/p/redtamarin/ and from that, we had maashaack compiling and working in redtamarin, but also another project ASTUce (yeah another unit tests framework) http://code.google.com/p/astuce/ and because we did that: focus on AS3 without any dependencies on a UI framework, the same ASTUce AS3 framework now compile as an exe that can run on the command line, and that give us unit tests running on the command-line and working in our Ant builds. Ok I pimp some projects ;), but I also try to illustrate a point, to focus only on AS3 the language is good, it gives you portable code, libraries, frameworks, etc. that can virtually work anywhere (Flex, Flash, Tamarin, etc.). so if Gumbo tells us we can only run unit tests for Flex projects, we can answer "nah we ran our unit tests for AS3 projects and it also work on the command-line" =) But I don't blame Adobe nor Flex, I understand why they are doing it this way, and without tools like mxmlc or Tamarin we could have not done half of what we do we our own project but apparently they are a whole bunch of people that still care about AS3 projects (no Flex, no MXML) and maybe they should help or plan on that. For example, if the Flex framework had its UI/components parts and application framework parts splitted clearly they could avoid forks and have more people contributing to the Flex project itself just some thoughts ---------- zwetan --~--~---------~--~----~------------~-------~--~----~ Vous avez reçu ce message, car vous êtes abonné au groupe Groupe "FCNG" de Google Groupes. Pour transmettre des messages à ce groupe, envoyez un e-mail à l'adresse [email protected] Pour résilier votre abonnement à ce groupe, envoyez un e-mail à l'adresse [email protected] Pour afficher d'autres options, visitez ce groupe à l'adresse http://groups.google.com/group/FCNG?hl=fr -~----------~----~----~----~------~----~------~--~---
