These are the questions that were posted on the Carbide webinar on Jan 6-7.

Q: Applications that use serial port on the phone were until now not debuggable, will that be solved in the future.

A: Debugging on-device means users need to debug using Bluetooth or USB. In each case, the connection uses the COM services on the PC and the port is no longer available for other purposes. Generally we recommend that the user debug over one connection type (BT for example) while developing apps that use the other (ex – USB). We have updated TRK to operate with other debug services (in our case, software Trace and debug at the same time). The newer versions of TRK (3.0.x) MAY support this method, but we did not test this. We have added a connection type called USB (this is NOT the same as the UCB + COM port method). Using the method, the USB is not locked by the COM port issue and MAY allow other phone services to operate. We did not test for this but are now looking into this use case.

Q: Is Nokia working on the long startup of the emulator?

A: Nokia recognizes that startup time on the emulator is quite slow. We do have a simulator project underway that should address this issue. The simulator will operate on real ARM code and operate more like a real phone. The startup time may still be slow, but the user will not need to close the simulator and restart on each debug iteration. This is currently an internal project and we have not announced our plans for the general release of this project.

Q: For Performance Investigator, will there be agents with different capabilities for OEM and third parties?

A: These sorts of profiling tools can provide the OEM user with more access to system-level information compared to uses on production phones. There are three similar “profiling” type tools that are used in the Symbian community. As part of the new Symbian Foundation, we will combine the best of these tools into a better profiler that will hopefully provide more information to all users. Ideally all of these tools are provided as open-source so everyone can have access.

Q: Does Nokia have plans to create a Memory Leak tool?

A: Yes. This project is in development. Most of the major work is completed and we are working out the details to release to the developer community. One component will reside in Carbide, the other needs to reside in the phone. Only the newer devices will support this feature. We hope to have an update in our March release.

Q: When will be addition of Unit Test Module to Carbide.c++?

A: There are no immediate plans. The product feature is on our roadmap but not listed as a high priority at this time.

Q: Does Nokia provide a document for developers to develop and add a new rules for CodeScanner?

A: Starting with v2.0, CodeScanner was extended to bring in new rules. The Knowledgebase scanner, for example, is built on this extension. The document for making new rules was inadvertently dropped from the 2.0 product and will be added to the 2.0.2 product due out in March 2009.

Q: How does the performance of the v2.0 IDE compare to older versions of Carbide?

A: The most notable improvement in the IDE is the indexer. This is the key component in the IDE used to provide context-sensitive assistance to the developer (code completion, color coding, etc). The indexer is greatly improved in this release. We do not have any benchmarks related to the IDE.

Q: What are the plans with on-device debug? We would like to support this over WLAN interface.

A: ODD will experience an overhaul this year. Our goal is to improve the experience in such a way that the user just needs to connect to the device with an active IDE and the debug interface is automatically configured. The “Plug-and-play” debugger will first support USB. WLAN is on the roadmap but no definite plans are in place.

Q: Regarding Qt support in Carbide.c++, currently Qt operates in GPl and Commercial licenses; will Qt also be completely free like Carbide.c++?

A: The Qt runtime and Qt tools are two different offerings. Within Carbide, Qt tools are totally free. It is our hope that many developers use Carbide for Qt development. Other configurations of Qt tools outside of the Carbide tool are determined by other teams in Nokia.

License models for the Qt runtime have not been announced at this time.

Q: For CodeWarrior there had been a limit in the amount of project files to link (source files). Does Carbide have this same limitation?

A: We are not aware of any limitation in CodeWarrior or Carbide. Certain versions of CodeWarrior did have a limit to 10-20 images for linking, but this was a limitation set because the product was free. There is no such limitation on Carbide.c++ v2.