IJ maintains some long-life caching of file listings in every SDK you throw at it this makes it practically impossible to alter an existing SDK and have the changes reflected. My favorite features of IntelliJ include debugging, auto-filling, auto-correcting, navigation features, refactoring, plugins, dark mode, etc.
#Intellij ultimate features Patch#
SDK handling: as any Flex/AIR developer knows, AIR SDKs have to be overlaid on FLEX SDKs and this alone is a source for countless problems add on top that SDKs are often shipped in incomplete form (*.jar and *.swc files have to be salvaged from older SDKs) and you understand how being able to quickly patch / swap / tinker with an AIR/Flex SDK and test it's in working condition could save the day.
#Intellij ultimate features code#
the build process: IJ does not do any work to ease SWC dependencies management in a world where there are tools that analyze your code for imports and class instantiations and automatically match them against projects and libraries in your workspace (I build myself such a tool, it's name is SIRIUS and will be soon out on GitHub), IJ still wants you to add by hand 25+ dependencies. In 2002 In Swing) and it was feature-packed. Its always been polished (it had transparent UI panels. I very much dislike pretty everything, but the worst are: I used IntelliJ IDEA and havent looked back.
Im a Java developer, so, I use IntelliJ to write Java, 99 of the time. But this review is ONLY about using IJ for AS3 / Flex / AIR development. chances are you have access to an Ultimate version, so, we can improve our workflow by leveraging some tricks besides the simpler ones. I did use IJ for developing some Node.js applications, and experience was a little better. I do not know whether its subpar behavior is rooted in those dedicated plugins. Cons: I want to make it crystal clear that I mainly use IJ for AS3 / Flex / AIR development.
0 kommentar(er)
