IDE Factory

The following features are currently on the drawing board for future releases of the Enterprise IDE Plugin:

• PureMVC framework support
• Flex Code coverage explorer
• Code templates
• VisualFlexUnit framework support
• Prana framework support
• Form editors for Flex config files
• Ant tasks for project metrics gathering, code formating

If there are other features not listed here you would like to see in the Enterprise IDE, please feel free to post a request here or enter a New Feature issue in the IDE Factory bugtracker. You can also add feedback to existing New Feature issues in the bugtracker.

Feeback provided by the users will be take in consideration for effects of planning and further development of the Enterprise IDE Plugin. Thank you for your support!

Luis Lejter

As you consider PureMVC support, I would really like to be able to take advantage of the multi-core implementation of PureMVC for code generation of modular applications.

Also it would be cool if you could interface with the Manifold Project to be able to pull down AS3 utility packages directly to the libs folder.

Thank you for the suggestions, we will definitely look into multi-core PureMVC and Manifolds. I am planning to have PureMVC support in place by the end of the year.

Luis

Some sort of editor for the HTML template would be nice too. One where you have simple access to the various placeholders you can use in the template.
If what I'm saying sounds like gibberish, these are the things I'm talking about:

http://www.morearty.com/blog/2007/01/24 ... ate-files/

I have no idea what a userfriendly implementation would look like, but its maybe something you can think about a little. So far the Enterprise IDE is looking very promising, my main issues with it so far is that its not very responsive yet, it usually takes quite a while for dialogs to show up etc, but you're in beta so I'm not bitching about that

keep up the great work,

cheers,

Roland

i haven't seen if it's already included or not. But it would be nice to have the Code Documentation visible in the ide just like FDT handles it. That you see the Doc information when you hover over a method name or start typing it. Hope you guys know what i mean.

Cairngorm wizard is cool. But is there any chance to make my own wizard by extending some xml data in plugin directory ?- for ex. wizard for framework that's not supported in enterprise ide.

Extensible class creation wizards are definitely feasible, we will look into implementing them in a future release.

Great but - consider that deeply - even before implementing puremvc , prana or spicefactory. Some frameworks are pernamently evolving/changing- so how often plugin can updated by this cause?. If wizards are hardcoded - fixing them it is little bit waste of time. Implementing some sort of user xml driven dynamic wizard - not externalizing just extension points is better way to achieve success with all mvc frameworks support.

There are two key features that I find Flex Builder is sorely lacking.

First is code formatting for both the MXML and AS code. The visual studio model is the most intuitive to me (live reformatting by context area), but I would settle for just having a shortcut key that would format the current file.

Second is bookmarks. For the best implementation I have ever seen check out CodeRush for Visual Studio.
http://www.devexpress.com/Products/Visu ... gation.xml

I mentioned both of these requests at the end of my blog post on Flex Builder shortcuts:
http://allyourflex.wordpress.com/2008/0 ... shortcuts/

pet wrote:Great but - consider that deeply - even before implementing puremvc , prana or spicefactory. Some frameworks are pernamently evolving/changing- so how often plugin can updated by this cause?. If wizards are hardcoded - fixing them it is little bit waste of time. Implementing some sort of user xml driven dynamic wizard - not externalizing just extension points is better way to achieve success with all mvc frameworks support.

I totally agree that an editable XML-based dynamic wizard with class templates would be ideal. That way if there is a framework that Luis does not currently support, the community could *relatively* easily add support for the framework. Additionally, as the frameworks are updated, so then can the templates and wizards be.