|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Making the connection with TRK | Main | Code Scanner is a champ! »
There has been a flurry of recent support questions on creating projects, debugging, and a host of other minor issues that doesn't include enough information to actually solve the problem. Upon further investigation it's discovered that the person is still using Carbide 1.2 or GASP, 1.1 as their development environment.
So the question is, why haven't you upgraded to Carbide 1.3 yet?
Carbide 1.3 includes support for Eclipse 3.3 and CDT 4.0, a host of build system improvements for large projects and indexing, a new System search capability, new debugger improvements like the Executables view and improved on-device debugger stability, new tool plug-ins like CodeScanner, Capability Scanner, Epocwind.out, and lots of bug fixes.
Carbide 1.1 and even parts of 1.2 really pale in comparison to what Carbide 1.3 offers. If this small message has struck a chord somewhere, go download the latest version here. Especially you Carbide 1.1 users as I'm sure you'll be pleasantly surprised at the improvements.
The real answer?
There is no excuse!
Comments
Well, if you guys would upgrade my student 1.2 license to 1.3, I would be more than happy to have it. Please e-mail me and don't let me have any excuses!
Posted by: pillar | May 3, 2008 12:27 PMHmm, don't see your email address so can only respond that way. Email me your current info and we'll see what we can do. Of course, you can always download the latest version anyway while waiting for upgrade info just to see what has changed for the better.
BTW, until you wrote in I didn't even know we had a student license edition out there. So busy developing the core product I've not paid attention to how its actually marketed or sold.
Posted by: frank | May 5, 2008 05:03 PMFrank, thank you for your response, but the same problem: I don't see your e-mail so I cannot email my current info :-) It is asked, but I guess it is not shown for anyone. pillar15 at gmail.com and you can send your email so that I can get you the info. Thanks for the support, it is really appreciated.
Posted by: pillar | May 10, 2008 06:26 PMYep, not sure why it doesn't work, I'll pass it onto the site admin to see if a setting needs changing. Email already sent to solve your problem. Thx for responding.
Posted by: L. Frank Turovich | May 12, 2008 03:11 PMBecause with Carbide v1.3 you CAN'T develop symbian applications for the 2nd edition... you can't generate the .SIS from the .PKG!!!!
Posted by: Anonymous | June 14, 2008 07:29 AMCarbide v1.2 should be uploaded again... the current download link at forum nokia doesn't work... :(
I could find 3 good reasons (excuses)
1. HOW THE HELL AM I SUPPOSE TO UPGRADE THE LICENSE??? ANOTHER MISTERY BY NOKIA...
2. Maybe because of the MANY MANY bugs and ANNOYING UI of Carbide 1.2. WE JUST DIDN'T THINK THAT ANY MINOR UPGRADE WILL MAKE MUCH DIFFERENCE!
3. Well I only have 2 excuses but it's enough ..
Posted by: bob harlem | July 2, 2008 02:42 AMAnonymous -- that is true. The decision was made to drop non-PlatSec supported SDKs for 1.3. In this case, staying with 1.2 is your only option. Send us an email to sales dot carbide at nokia dot com and we'll work on a solution for you.
Bob -- A quick glance in the help, mainly the Release Notes page, would have provided the email address for license questions. To update a license, send email to license dot carbide at nokia dot com with a copy of your current license so we can generate a new one.
Carbide 1.3 addresses many issues that 1.2 users had with Symbian development. I'd urge you to give it a try. Many of the UI issues are simply "how things are done" in the Eclipse IDE and not something we choose to fight against but instead embrace. While they may be annoying at first due to their different approach, it is not that hard to grow accustomed to the change.
If you have real problems with Carbide, I urge you to submit bug reports to https://xdabug001.ext.nokia.com/bugzilla/ so we can correct them asap.
Posted by: L. Frank Turovich | July 2, 2008 10:13 AMWhy haven't we upgraded? because Nokia told us we had to purchase a new license!
Posted by: Rob Charlton | August 5, 2008 04:00 AMPretty much each release of Carbide has required a new license purchase. Like many of you we too have sales quotas to make and a revenue stream to pursue. I do sympathize with your predicament but still think that the improvements we made would bear out the upgrade cost, possibly increase your productivity, and help you produce better products.
OTOH, we are prepping Carbide.c++ 2.0M1 for public testing now, please check it out once its available to see if it has features and other improvements that would be useful for you.
Posted by: L. Frank Turovich | August 7, 2008 12:57 PM