23. August 2012

IntelliJ Idea – How to enable zoom of text by CTRL + Mouse wheel

You can zoom-in or out text in editor window of IntelliJ idea (PyCharm) by CTRL + Mouse wheel.

The only problem is that this feature is disabled by default. You have to turn it on.

Press CTRL + Alt + S (Settings) and type: “change font size” into text search field. Select: Editor and check option “Change font size (Zoom) with Ctrl+Mouse Wheel”

21. June 2011

Writing Python scripts for Blender with Intellij IDEA

Blender is powerful 3D modelling tool. What makes it really powerful is support for Python.

I was playing little bit with configuration of Intellij IDEA and I found out that it is possible to use Intellij IDEA for developing Python scripts for Blender.

Here is video tutorial:

Update 23.06.2011: Video tutorial was recorded for Blender 2.57. There is small change in Blende 2.58 – scripts are located in Program Files directory, like: C:\Program Files\Blender Foundation\Blender\2.58\scripts\modules

Some useful links:

6. June 2011

IntelliJ – new Flex project – error #2032

IntelliJ Idea Ultimate has great support for Flex projects.

There are few gotchas that you have to deal with.

When you set up project, compile it and open it in browser you can get very common error #2032 in Flash Player.

This indicates that you have some problem with RSL libraries. I already wrote some posts about RSL troubleshooting.

In case of Intellij Idea just add following line to Additional compiler settings (Modules – Flex – Flex Compiler Settings):


This option causes that compiler links RSL into final SWF. The file is bigger, but you can be sure that it will work without #2032.

This option could help you for the time being.


17. May 2011

IntelliJ IDEA 10.5 with improved Flex/AIR support is here

Hooray! 🙂

New features in IntelliJ IDEA Ultimate for Flex developers:

  • Move inner ActionScipt class to Package refactoring.
  • Introduce variable/field refactorings improvements.
  • Full cycle of Mobile AIR applications development support.


17. May 2011

Quality in Flex/ActionScript development

Sergei Sokolov wrote article about Using automated tools across the lifecycle to develop higher quality Flex applications.

He explained some tools and approaches how to build better Flex based software.

I’d like to add some of my notes to this topic:

1. The key factor for reaching good quality of Flex products is learning. Flex is platform and it is evolving. Therefore it is imperative to learn new approaches to solve some problems.

2. Automation is very important. Flash Builder is bundled with support for Ant. That is not enough. Continuous integration should be implemented via tools like Maven using FlexMojos. Without this point everything is useless, because you’ll end up with mixing different versions of Flex SDK with your framework. Thanks to Jenkins and FlexMojos you reach stability in SW production. We already launched Jenkins CI for open source ActionScript projects – you can find some details at corlan.org.

Here is small example how to use FlexMojos.

3. Teach developers how to use FlexUnit. Companies tend to buy cheaper version of Flash Builder which has no support for FlexUnit. Investing few more bucks could give them very handy tool. See lynda.com or tv.adobe.com for lecture about FlexUnit. There are also other helpful tools like FlexMonkey, etc.

4. Different tools. Flash Builder is great, but real development power comes with combination of Flash Builder with IntelliJ Idea Ultimate. Those two tools together could speed up development and improve code quality. Also test automation has good implementation in IntelliJ Idea.

5. Flex PMD. This could help team which deals with new developers. Often it is hard to guess level of skill of new developer in the team. Using Flex PMD could help with measuring and detecting anomalies in his code style

6. Get rid of Not Invented Here Syndrome. There are many small useful frameworks which could help to improve Flex productivity, like Swiz, RobotLegs. Knowing those frameworks could save hundreds of development hours. So give a space to developers to learn new approaches.

I prefer small frameworks with less singletons inside. Some Flex frameworks are overflowing with singletons. Do not use sw with too much singletons, it will bite you and maintainability of your Flex product will drop to zero. Just a friendly warning at the end 🙂

In my opinion this is the core of producing real good and stable Flex software.