qt:eclipse_qt_integration_for_c
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
qt:eclipse_qt_integration_for_c [2011/04/02 17:30] – mithat | qt:eclipse_qt_integration_for_c [2011/04/07 18:46] (current) – mithat | ||
---|---|---|---|
Line 7: | Line 7: | ||
I've tried Eclipse for Java development a few times in the past, and each time I've walked away from it. It uses SWT, so it integrates look and feel wise fine into any supported platform. Mostly. However, one of the problems I had with this version of Eclipse is that one or more of it's many splendored panes seemed to disappear at will. I'm not talking about it changing " | I've tried Eclipse for Java development a few times in the past, and each time I've walked away from it. It uses SWT, so it integrates look and feel wise fine into any supported platform. Mostly. However, one of the problems I had with this version of Eclipse is that one or more of it's many splendored panes seemed to disappear at will. I'm not talking about it changing " | ||
- | A problem that I've had with Eclipse in the past regards its approach to UI design. It seems to want to assert it powerfulness by showing you its mind-boggling power all the time. I have found the UI too distracting, | + | A problem that I've had with Eclipse in the past regards its approach to UI design. It seems to want to assert it powerfulness by showing you its mind-boggling power all the time. I have found the UI too distracting, |
- | Let's try to put these concerns behind us and move on to the Qt integration. I set up a simple project without any signal/slot connections and tried a debug. It generated a cryptic warning and then rendered my window. Success, I think. Regarding the user experience of the Eclipse plugin, it integrates the equivalent of Qt Designer into the Eclipse UI. But while all of the features available in the standalone seem to be present in the plugin version, accessing the features isn't as convenient. For example, when you want to open signal/slot editing mode, you must do so from the menu bar because there' | + | Things aren't looking good. |
+ | |||
+ | Ok ... let's try to put these concerns behind us and move on to the Qt integration. I set up a simple project without any signal/slot connections and tried a debug. It generated a cryptic warning and then rendered my window. Success, I think. Regarding the user experience of the Eclipse plugin, it integrates the equivalent of Qt Designer into the Eclipse UI. But while all of the features available in the standalone seem to be present in the plugin version, accessing the features isn't as convenient. For example, when you want to open signal/slot editing mode, you must do so from the menu bar because there' | ||
This ended my investigation into Eclipse as an option for Qt development. | This ended my investigation into Eclipse as an option for Qt development. | ||
+ | |||
+ | ''< | ||
+ | |||
+ | I think I've been too tough on Eclipse. I just gave it another go and it seems to be behaving a little less unpredictably. I'm not nearly sold on the idea though, just that I'm not totally in a veto state over it. | ||
+ | |||
+ | ===== Pros ===== | ||
+ | * " | ||
+ | * Qt support is (semi)official | ||
+ | * The Qt templates are good | ||
+ | * Support for PyQt through PyDev as well | ||
+ | ===== Cons ===== | ||
+ | * Quirky, often frustrating UI | ||
+ | * Closing a project leaves it visible in the workspace. | ||
+ | * Opening a new workspace resets everything | ||
+ | * Changes in " | ||
+ | * There' | ||
+ | * It's easy to change/ | ||
+ | * The integrated Qt Designer has usability issues. You can set the IDE to use the " | ||
+ | * The debugger stops at at '' | ||
+ | * You need to manually switch back to your editing perspective after debugging. | ||
+ | * PyDev is totally WTF. | ||
+ | |||
+ | ===== Thoughts ===== | ||
+ | If one or more of the problems above is solved (e.g., getting the debugger to stop breaking unless you explicitly add breakpoints) it may be an alternative. But given PyDev' |
qt/eclipse_qt_integration_for_c.1301765446.txt.gz · Last modified: 2011/04/02 17:30 by mithat