|
» 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 (8) » Carbide.c++ 2.0.x (1) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (24) » General (46) » Off-topic (4) » On-device debugging (13) » Performance Investigator (2) » Product features (16) » Product releases (16) » Screencast (12) » Support (30) » Tool setup (5) » UI Designer (8) » Usability (15) » Work in Progress (13) » Write-build-debug (4) |
|
» Launching from the SPN View » Tips for using the CodeScanner tool! » Carbide in the summer » Austin Eclipse DemoCamp » Where's my console output? |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Austin Eclipse DemoCamp | Main | Tips for using the CodeScanner tool! »
So, summer is here and as you may have noticed the number of entries on this blog has dropped a bit in the last few weeks as the team takes some well deserved time off to enjoy the Austin heat with their families. Unlike our corporate headquarters in Finland we don't take the entire summer off, but we do grab a week or two here and there to spend time away from the office recharging ourselves for the next project sprint.
In this lull between the release of Carbide 1.3.1 and the ramp up to 2.0 you should know that we are still hard at work planning, designing and implementing new features for the next release. Work seems to never stop here in the Austin office as one project rolls into the next with increased rapidity and the team continues to resolve user issues as fast as they can.
Internally, we've managed to get the Carbide sources to build using the latest Eclipse 3.4 and CDT 5.0 sources from Ganymede and are ironing out the initial bugs so we'll have something nice to show you soon. In addition, there is work going on to add additional features which address the usability, connectivity, and recording capabilities in the tools. I hope to start describing some of them in future blog posts as designs are completed and more information becomes available.
In the meantime, just to reiterate, posts here will be few until the summer works itself out and we're all back working the feature and bug backlog. From all of of us on the Native Tools team, have a safe and enjoyable summer. We'll see you back in a few weeks.