One major feature I like is the 'Terminal' in most cases I deal with Linux bash, so I enjoy having a terminal window that opens in the project directory and uses bash instead of the WIndows CLI. Pros: I had used WebStorm prior to using IntelliJ, so, many of the perks are the same between those two products which also seems to pleasantly true about all of the JetBrains development products across the board. The only workaround I have been able to find was to rename the SDK, add it as a new SDK, and remove the older one. 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.
#Intellij code with me 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. 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. I very much dislike pretty everything, but the worst are: But this review is ONLY about using IJ for AS3 / Flex / AIR development. 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)
