I have been playing with the latest beta of Carbide.c++ Developer Edition. This will be the (non-free but relatively low cost) version that will include ‘RAD’ support for creating the UI and the ability to perform on-target debugging.
My first impressions are that importing existing .mmp files is much improved over (the free) Carbide.c++ Express. However, it still doesn’t recognise all the statements in typical .mmp files. Furthermore, it’s often not clear which statement is causing the problem. This makes things frustrating and it’s all too easy to go back to the more robust Codewarrior 3.1. Let’s hope this is fixed for the final release.
The RAD features are great and work in a similar way to Borland C++ BuilderX 1.5. Many hours can be spent just creating a typical Series 60 UI and Carbide.c++ simplifies this repetitive process greatly. UIQ 3.0 RAD support seems to be missing. Again, let’s hope this makes the final release as I have a feeling UIQ 3.0 may end up being more of a hobbyist’s playground than S60 3rd Edition.
Meanwhile, it’s great to see the Carbide.c++ team are continuing to innovate. The Carbide.C++ development team blog describes a mockup for a Capability scanner. Working out what capabilities your application uses is a bit hit and miss at the moment – you currently have to running your app, try to go through all scenarios and look in the debug trace for error messages. The tool would analyse your code and tell you what capabilities to put in the mmp file.