History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: IDEADEV-14365
Type: Meta Issue Meta Issue
Status: Resolved Resolved
Resolution: Fixed
Priority: Normal Normal
Assignee: Maxim Mossienko
Reporter: Michael Klishin
Votes: 78
Watchers: 47
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

Flex 2 (ActionScript + MXML) support in IDEA

Created: 12 Feb 07 22:03   Updated: 02 Oct 08 14:43
Component/s: XML editing
Fix Version/s: Diana M1

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Mac OS, Linux, Windows
Issue Links:
Depend
This issue depends on:
IDEADEV-27104 Line marker pass to work in injected ... Major Resolved
IDEADEV-11399 JavaScript E4X syntax support Normal Resolved
IDEADEV-19542 Ability to run flex application from ... Normal Resolved
IDEADEV-19543 Would nice to have implement/override... Normal Resolved
IDEADEV-19544 Nice to have source folders for flex ... Normal Resolved
IDEADEV-20242 Support for mxml files Normal Resolved
IDEADEV-20266 Ability to navigate to an overriden m... Normal Resolved
IDEADEV-20307 Package name completion after package... Normal Resolved
IDEADEV-20308 Generation of getters/setters and con... Normal Resolved
IDEADEV-20309 Show as warnings unused imports in AS... Normal Resolved
IDEADEV-20311 Optimize imports for AS3 Normal Resolved
IDEADEV-20312 Highlight fields and static fields wi... Normal Resolved
IDEADEV-20571 Namespace name completion Normal Resolved
IDEADEV-23502 Should be able to create ECMAscript o... Normal Resolved
IDEADEV-25106 Support ActionScript in inline XML Normal Resolved
IDEADEV-24424 Suggest event type when completing in... Normal Resolved
IDEADEV-24425 Automatic adding xml namespace when e... Normal Resolved
IDEADEV-24426 Automatic adding <![CDATA[ ]]> when a... Normal Resolved
IDEADEV-24481 Build should copy resources (assets a... Normal Resolved
IDEADEV-24482 Class fields / methods should be comp... Normal Resolved
IDEADEV-24483 Automatic creation of html-wrapper du... Normal Resolved
IDEADEV-24513 Add component icons to Flex mxml file... Normal Resolved
IDEADEV-24626 MXML components metadata Normal Resolved
IDEADEV-24676 IDEA wrongly highlights public proper... Normal Resolved
IDEADEV-24839 Action script should be supported in ... Normal Resolved
IDEADEV-24840 Action script should be supported in ... Normal Resolved
IDEADEV-24842 ActionScript code in event listener c... Normal Resolved
IDEADEV-25133 Parameter info should work over 'supe... Normal Resolved
IDEADEV-25134 super keyword in ActionScript should ... Normal Resolved
IDEADEV-25296 JavaScript formatter settings is needed Normal Resolved
IDEADEV-25385 Provide import class intention in act... Normal Resolved
IDEADEV-27103 TODO highlighting inside injected doc... Normal Resolved
IDEADEV-20320 Override and implement with control+O... Normal Resolved
IDEADEV-26968 "Introduce Constant" for Flex/ActionS... Normal Resolved
IDEADEV-28544 Introduce Field Normal Resolved
IDEADEV-24491 In mxml files tags from flash namespa... Normal Resolved
IDEADEV-24515 Go declaration, complete, ctrl+Q in ... Normal Resolved
This issue is required for:
IDEADEV-24492 Most of mxml attributes can be presen... Normal Resolved
Duplicate
 
This issue is duplicated by:
IDEA-11504 Flex Support Resolved
IDEA-11505 ActionScript 3 and MXML Resolved
IDEA-11513 Flex Support Resolved
Relates
 
This issue is related to:
IDEADEV-28341 MXML outline view "search for" Normal Resolved

Build: 6,148
Fixed in build: 8,856
Severity: High

Sub-Tasks:   All   Open   
 Sub-Task Progress: 
1.
 ActionScript parsing Sub-task Resolved Resolved Maxim Mossienko  
2.
 Built-in MXML schema should be provided Sub-task Resolved Resolved Maxim Mossienko  
3.
 ActionScript should be injected into appropriate places of MXML documents Sub-task Resolved Resolved Maxim Mossienko  
4.
 CSS should be injected into appropriate places of MXML documents Sub-task Resolved Resolved Maxim Mossienko  
5.
 JavaScript completion should be aware of variable / function types Sub-task Resolved Resolved Maxim Mossienko  
6.
 Validation should check explicit types Sub-task Resolved Resolved Maxim Mossienko  
7.
 There should be navigation from include literal to files Sub-task Resolved Resolved Maxim Mossienko  
8.
 Flash std classes/func stubs are needed Sub-task Resolved Resolved Maxim Mossienko  
9.
 Safe delete should work for class Sub-task Resolved Resolved Maxim Mossienko  
10.
 Introduce var should add type information for created variable Sub-task Resolved Resolved Maxim Mossienko  
11.
 There should be intention to add type to var declaration Sub-task Resolved Resolved Maxim Mossienko  
12.
 Structure view should show inherited members for classes Sub-task Resolved Resolved Maxim Mossienko  
13.
 File references for [Embed] attribute in ActionScript Sub-task Resolved Resolved Maxim Mossienko  
14.
 Indexing of Flex SDK ActionScript sources to resolve import statements in ActionScript Sub-task Resolved Resolved Maxim Mossienko  
15.
 Completion after this should suggest only class members Sub-task Resolved Resolved Maxim Mossienko  
16.
 Flex facet is needed Sub-task Resolved Resolved Maxim Mossienko  
17.
 Context documentation should show class documentation over class name Sub-task Resolved Resolved Maxim Mossienko  
18.
 Context documentation should have navigatable links for @see tags Sub-task Resolved Resolved Maxim Mossienko  
19.
 Provide 'Add framework support page' for Flex in new module dialog Sub-task Resolved Resolved Maxim Mossienko  
20.
 Collapse file headers by default Sub-task Resolved Resolved Maxim Mossienko  
21.
 Provide type references in [Event / Style] type attribute value Sub-task Resolved Resolved Maxim Mossienko  
22.
 Mxml structure view should have css -styles- and -javascript- functions Sub-task Resolved Resolved Maxim Mossienko  
23.
 Control + N should navigate to ECMAScript class Sub-task Resolved Resolved Maxim Mossienko  
24.
 Control + shift + N should navigate to Flex source files Sub-task Resolved Resolved Maxim Mossienko  
25.
 Validate duplicated ids in mxml file Sub-task Resolved Resolved Maxim Mossienko  
26.
 File name completion and highlighting in source attribute of Style / Script tags Sub-task Resolved Resolved Maxim Mossienko  
27.
 Mxml can reference any not annotated public property or field Sub-task Resolved Resolved Maxim Mossienko  
28.
 Support 'enumerated' values of annotation (e.g. Style) in completion / validation Sub-task Resolved Resolved Maxim Mossienko  
29.
 Debugger is needed Sub-task Resolved Resolved Maxim Mossienko  
30.
 Provide checks for public class/function to be in correct file name + package name in correct path Sub-task Resolved Resolved Maxim Mossienko  
31.
 Check interface members does not have access modifiers Sub-task Resolved Resolved Maxim Mossienko  

 Description  « Hide
Given the fact IDEA has great Java/JavaScript/XML support, it is easy to implement ActionScript 3 (with strict typing) and MXML (actually subset of XML) support in IDEA.

Flex community is growing rapidly (MXNA weblogs aggregator now has more than 1000 blogs), Flex became the best cross-plaform choice for RIAs when Ajax limits in media and complex interfaces are no longer enough for developers ideas. Web video is driven by Flash platform, Adobe Apollo project that will bring web technologies to the desktop support Ajax and Flex.

Flex 2 was voted technology of the year by infoWorld and Java Developers Journal, AS3 is very close to Java in syntax and ideoms so Java devs adopt Flex easily.

With added Flex 2 support in IDEA it would become top choice in both server-side (Java/Ruby) and client-side (Ajax/Flex) cross-platform development.

 All   Comments   Work Log   Change History      Sort Order:
[ Permlink | « Hide ]
Taras Tielkes - 07 Mar 07 21:45
Maxim, are you planning to create a separate module type for this (with Flash SDK / libraries)?

[ Permlink | « Hide ]
Maxim Mossienko - 07 Mar 07 21:49
Eventually

[ Permlink | « Hide ]
Stuart Goldberg - 14 Jun 07 20:45
When do you think this will be ready? Go Maxim, Go!!!!

[ Permlink | « Hide ]
Pavel Tcholakov - 18 Jun 07 20:02
The ActionScript support in Selena (M1) looks excellent, keep it up! A Flex project nature together with the ability to define SDKs and some basic MXML support would be an awesome next step (no need for WYSIWYG in the short term, just support for package-imports-as-namespaces and scripts inside CDATA nodes).

[ Permlink | « Hide ]
Carl Byström - 02 Dec 07 20:03
I'd really like to see the Flex plugin available as open source. Just like the Groovy and Ruby plugin. I don't know what your plans are regarding accepting community contributions, but some more good and solid code examples of plugins are needed.

[ Permlink | « Hide ]
Dmitry Jemerov - 03 Dec 07 12:43
Carl,

Flex is not a separate plugin, but rather a part of the JavaScript plugin. You can find its source code in the Plugin Development Package.


[ Permlink | « Hide ]
Carl Byström - 03 Dec 07 22:13
Thanks for the quick reply!
Ah, must have misinterpreted it (Found the Flex facet now aswell).

But I still wonder, what is your policy regarding community contributions? I know that both the Groovy plugin and the Ruby plugin are stored in your public repository.
I've seen some plugins available at http://svn.jetbrains.org/idea/Trunk/bundled/ but I miss GWT and JavaScript for example.


[ Permlink | « Hide ]
Dmitry Jemerov - 04 Dec 07 10:36
Carl,

We are always happy to accept patches from community contributors. To send us a patch, just create a JIRA issue with the .patch file attached. A JetBrains developer will review it and commit if no problems are found.

For historical reasons, GWT and JavaScript are not stored in our public Subversion repository, but they are available under the same license as the rest of the open-source plugins. You can hack on the code which is available in the plugin development kit and send us patches built against that version.


[ Permlink | « Hide ]
Mike Berg - 14 Mar 08 05:46
So, are there any plans to provide the new project nature, the Flex project nature? Attaching my Flex projects which are in fact more complicated and numerous than my Java projects as facets, that really does not make any sense to me.

[ Permlink | « Hide ]
Per Olesen - 14 Mar 08 10:56
@Mike:

It is already there. Take the 7.0.3 version, create a project and add a flex facet to a module, point it to the flex sdk and you are ready.


[ Permlink | « Hide ]
Mike Berg - 14 Mar 08 18:46
Per, it's not there yet: as I said, a facet is not enough, I should not be forced to pick a Java project to attach my Flex projects to. But per discussion on the IDEADEV-19374 issue, per Maxim Mossienko, there will be Flex module feature in Diana (Idea 8 as it looks like), from what I understand that would give me Flex-only (no Java) projects which I am hoping for. That's good for me because I'll be saving on Flexbuilder licenses, that's good for JetBrains who will be getting Flex developers defecting from Adobe FlexBuilder to JetBrains Idea...

[ Permlink | « Hide ]
Per Olesen - 14 Mar 08 19:00
@Mike: Sorry, I misunderstood. You are of course right.

BTW: If you are using charting components, advanceddatagrid, ... in flex3, you will not be able to save on the flexbuilder licensing, cause it is only sold through flexbuilder pro now
But that is another problem


[ Permlink | « Hide ]
Dmitry Jemerov - 02 Oct 08 14:43
The support is there; separate issues need to be filed for additional requested features or bugs.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.10-#260) - Bug/feature request - Contact Administrators