Thanks a lot Héctor !
Frédéric THOMAS
> From: neverbi...@gmail.com
> Date: Fri, 8 May 2015 16:34:40 +0200
> Subject: Re: [FlexJS] Reaching out to IDE developers to support FlexJS
> To: dev@flex.apache.org
>
> >
> > One question for the Flash Develop guys though, how are the intelli-sense
> > / refactoring / code navigation / hints and other IDE facilities including
> > maven integration compared to IntelliJ, do we have a comparative table ?
> >
>
> I can't compare to IntelliJ as I haven't used it for Flex/Flash (although I
> have a license for it).
>
> AFAIK we don't have Maven integration... it's something I'd like to look
> some day, but I barely know about it actually.
>
> Regarding some other aspects:
>
> - I'm sure their MXML autocompletion and refactoring is better than ours.
> In some exceptional cases ours is better than the one if Flash Builder tho.
> We do not currently support code completion inside binding expressions nor
> event handlers as attributes in MXML, also, Flex CSS isn't supported
> either. Refactoring like renaming doesn't update MXML code.
>
> - Code navigation: It's mostly implemented, only missing navigating to
> attribute values (event handlers, skin classes and the like), but it could
> be easily added I think.
>
> - Hints: fully supported, although the displayed help would need some love,
> support for some tags is missing, but again, hints are fully supported, and
> improving the displayed text is high on my to-do list.
>
> - Namespace resolution: It's fully dynamic, we detect custom manifest files
> used in the compiler arguments or in build files as well.
>
> - Wizards: One generic wizard to create MXML files. This is the most recent
> addition to MXML support, if there are enough interest more specific
> wizards for things like components, skins or applications could be created.
>
> MXML has always been a second-class (more third than second...) citizen in
> FlashDevelop, and I work on it, but my spare time has been lately pretty
> scarce, plus I also work on other features, also, since have to work on
> several features at the same time some of them are only implemented up to
> the point they are requested, for example, the code navigation, I wasn't
> requested things like navigating to attribute values, but I always try to
> provide more features than requested, or CSS support hasn't turned up by
> anyone yet either, but I also improved a bit of it compared to current
> stable FD versions.
> .
> Another important point to take into account: most MXML features are not
> currently added in the official FD branch because I have a couple of
> important changes not fully finished that have been so far of low priority.
> But I can post builds to anyone that wants them.
