Hi --- In [email protected], Marcelo de Moraes Serpa <celose...@...> wrote: > > However, I'm no longer a Eclipse guy, I don't like bloated software anymore > and learned to love the Ruby/Rails way of doing things. In this time I was > away from Flex, I was doing exclusivelly Rails/Ajax apps and some generic > Ruby work, and it was great. Now I want to mix this knowledge with Flash and > create the product I have in mind. >
I share the same feeling about Eclipse but for me changing IDE is not an easy task, even if there are alternatives like the latest IntelliJ IDEA Ultimate Edition which has Flex support, provided you don't need the design view - which by the way IMHO is unusable besides building very simple prototypes, something for which I'd rather use Catalyst now. > Well, introductions aside, what I'd like to know is, how many less-is-more > emacsers/textmaters we have around here? Here's what I'd like to do: > > 1) Best case scenario: Setup a complete Flash/Flex3 dev env with emacs and > CLI tools. No Flex Builder whatsoever; > 2) Good case scneario: Setup a complete Flash/Flex de env with Textmate and > CLI tools. No Flex Builder whatsoever; > 3) Worst case/won'thappen scenario: Buy Flex Builder or (ouch) FDT3. > > (When I put Flash/Flex is because eventually I will be using Flash without > the Flex3/4 gorilla's framwork). You can setup your own CLI build using Ant with the ant tasks included in the Flex OSS SDK or better yet use Maven with flexmojos, which downloads the Flex SDK jars/swc for you, as explained in this online book: http://www.sonatype.com/books/maven-book/reference/flex-dev.html with lots of example on the project svn: http://svn.sonatype.org/flexmojos/tags/flexmojos-3.4.2/flexmojos-testing/flexmojos-test-harness/projects/concept/ The latter approach is the one I use for the headless builds triggered by my continuous integration server of choice, Hudson. You can also add to your build the excellent static code analysis tools built by Adobe Consulting with the FlexPMD project: http://opensource.adobe.com/wiki/display/flexpmd/FlexPMD Then you have to choose your editor, jEdit has some support for AS3, don't know about Textmate. For MXML you can always use an XML editor with XSD support and the schema provided by the AXDT project: http://axdt.org/browser/org.axdt.mxml/data/flex3.xsd http://axdt.org/browser/org.axdt.mxml/data/flex-config.xsd If you just want a Flash project without Flex I guess you have to use only ActionScript and don't reference any Flex class, the mxmlc compiler is smart enough not to include any class extracted from the Flex SWC. The biggest unresolved problem for me is having FLA source files around, because they don't fit in any headless build scenario, I try to avoid them as possible but as that is the output from the designers, I would really be happy if someone prove me wrong... i.e. building a maven plugin to drive the Flash Professional compiler in headless mode, even remotely from an external or virtualized Mac/Windows host. --m
