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/03 11:55] – mithat | qt:eclipse_qt_integration_for_c [2011/04/07 18:46] (current) – mithat | ||
---|---|---|---|
Line 18: | Line 18: | ||
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. | 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.1301831720.txt.gz · Last modified: 2011/04/03 11:55 by mithat