[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] CDT and Qt Creator
|
Instead of talking in generalities, I'd prefer to talk with specifics. Saying Carbide is hard to learn, what exactly about it is it hard to learn? Is it things in the CDT or Eclipse platform or things Carbide has added on top? Is it creating projects? Is it setting up builds? Is it launching debug sessions? Is it creating files? Is it too many choices? Would adding wizards in strategic places make the CDT easier to learn?
Most of the complaints on usability with Eclipse I've heard are really complaints from users who find IDEs complex in general. Is Qt Creator really that less complex than the CDT? What about Qt Creator makes it easier to learn. And why don't we invest in the CDT to make it equivalent?
Doug.
On Fri, Dec 11, 2009 at 4:47 PM, Pawel Piech
<pawel.piech@xxxxxxxxxxxxx> wrote:
All we've done so far is rather vendor-specific. What we would like to
see in CDT is the ability to isolate and turn off various features
using capabilities: e.g. build, static analysis, debuggers, etc. To
accomplish this we would likely need to look at dependencies between
these various CDT components and see if we can isolate them better.
However, we haven't invested any time in this yet.
-Pawel
Paul Beusterien wrote:
Hi Pawel,
Thanks for the response. Are there any available artifacts from the
stripped-down IDE investigation? Any effort estimates?
Regards,
Paul
On Thu, Dec 10, 2009 at 4:07 PM, Pawel Piech
<pawel.piech@xxxxxxxxxxxxx>
wrote:
Hi Paul,
Complexity is a common complaint about Eclipse-based tools (not
especially limited to C - development tools). I don't know of any
efforts to overhaul the UI, but I expect that there would be a lot of
interest out there for it. For Wind River's part, we are investigating
creating a stripped-down version of the IDE specifically targeted at
Debugging use cases, but I know we won't be able to get far without
support from the community.
Cheers,
Pawel
Paul Beusterien wrote:
Hi CDT community,
I'm responsible for the tools strategy at the
Symbian Foundation.
Like the
Eclipse Foundation, Symbian depends on the contributions from open
source communities to drive its mobile device platform technology
forward.
I'm curious if you have any thoughts about one of the challenges we're
facing with understanding/determining the direction for Symbian C++
development tools.
There are two open source communities vying for the Symbian C++
developer -
Qt
Creator and Carbide (based on CDT).
Carbide's investments have been primarily focused on adding features to
give more power to device creators. While it has become very
feature-full, it has also become very complex and hard to learn,
especially for developers that want to just build simple mobile apps.
Qt Creator is a targeted C++ development environment with a big
emphasis on usability. For example, it has rigorous hurdles to add a
button or menu item. Now, it is rapidly adapting to improve its mobile
development capabilities.
Thus, we currently have a fragmented C++ developer story at Symbian.
It is unlikely that Qt Creator will ever support the rich set of
features that Carbide currently provides to the power user.
Are there any initiatives will enable CDT based IDEs to lower its
learning curve and better support the needs of a simple C++ application
developer?
Thanks,
Paul
--
Paul Beusterien
Development Tools Manager
Symbian Foundation
Foster City, California USA
twitter: paulbeusterien
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
