Why a Carbide.c++ blog?
Hi, and welcome to the Carbide.c++ team blog. As befits a first entry, here’s our thinking on why a blog will do a world of good for you, us, and the tool.
A key topic on our roadmap is ease of adoption (another way of saying “usability”, I suppose). CodeWarrior is a powerful embedded tool, but as the Symbian platform evolves, we need more sophisticated application development capabilities. A number of great reasons supported the selection of Eclipse as our future core technology; usability is one of them.
Our team blog is about our daily work, in which abstract customer requirements are translated into actual product design. We serve a wide group of developers which means design needs to consider all kinds of issues. We also try not to assume we know what our customers want, but rather rely on customers actually telling us. This can be difficult. We send out alpha and beta releases and arrange user reviews of new functionality we’re prototyping, but a more frequent relationship with you — our user — is required. The way I look at it, this blog will be another good way to keep in touch. The plan is to involve our customers in the design process by commenting, suggesting, disagreeing, or supporting our work. In turn, we’ll be better informed on detailed design issues and create better tools. Seems like a win-win situation to me.
Maybe you guys should take a look at some of the points I made on Carbide.c++ here: http://www.tanzim.co.uk/blog/2006/05/24/carbidec-first-look/.
The C++ indexer needs to be really improved and so will the Visual Studio key emulation, facility for searching the file system among others needs to be looked at.
Thanks.
Tanzim, thanks for the link — I read through your post and the short answer is, once Developer Edition is released, I’m pretty sure you’ll like the improvements we’ve done (namely, a UI Designer and on-device debugging for S60 and UIQ devices).
As for the indexer, you’re right — it’s a real bad indexer, and we’re painfully aware of it. We’re hoping to get an improved version of this (and the key binding for Visual Studio) in future releases of Eclipse.
BTW, SlickEdit has an Eclipse plug-in, and apparently they have a VS key map.
Hello Markus,
Thanks for the quick feedback. Nice to know that you guys are working to improve things. Yes, I’ve tried the slick edit plugin, but the last thing you want is using a costly add-on while using a free tool!
Another S60 Blog is Born
Wow, talk about missing out. The S60 Blog Team has started another important blog highlighting the importance of Carbide.c in S60 development.Our team blog is about our daily work, in which abstract customer requirements are translated into actual pr…
It is really nice but is there some thing to make better of the debbuger of the carbide.c++