# HG changeset patch # User fturovic # Date 1264435782 21600 # Node ID cc0961d7c88d2430411db0aef448ef40c3595225 # Parent 125f1619c573e98bf47150b6d417b33b5bb8e083# Parent 3a264b9d91efd1d1ded5991dc5faff944eea0f2e daily merge diff -r 3a264b9d91ef -r cc0961d7c88d core/carbide_releases/readme/readme_sdks.html --- a/core/carbide_releases/readme/readme_sdks.html Mon Jan 25 08:53:08 2010 -0600 +++ b/core/carbide_releases/readme/readme_sdks.html Mon Jan 25 10:09:42 2010 -0600 @@ -6,17 +6,22 @@ SDK Support in Carbide.c++ - +

You're not done installing just yet...

-

Release: 2.1.0
- Revised: June 2009

-

Read the Release Notes and Bug Fixes for the latest infomation about this product. In Carbide.c++ simply click the Help > Help Contents > Carbide.c++ User Guide to find the pages.

+

Release: 2.5
+ Revised: Jan 2010

+

Read the Release Notes and What's New for the latest infomation about this product. In Carbide.c++ simply click Help > Help Contents > Carbide Help.

To complete your installation and start Symbian C++ application development, you must install the following:

@@ -39,27 +44,27 @@ +

Also, you must install at least one of the following SDKs to develop Symbian applications:

-

NOTE Carbide.c++ requires SDKs built to support WINSCW format.

-

S60 Platform SDKs (forum.nokia.com/main/resources/tools_and_sdks/carbide/)

+

NOTE Carbide.c++ requires SDKs built to support WINSCW format.

+

Symbian Foundation

+
    +
  • Application Development Toolkit (ADT) + (download) +
+

S60 Platform SDKs

    -
  • S60 5th Edition -
  • S60 3rd Edition, FP2 -
  • S60 3rd Edition, FP1 -
  • S60 3rd Edition, MR -
-

Qt SDKs (www.trolltech.com)

+
  • S60 5th and 3rd Editions, N97 + (All-in-one SDKs) +
  • S60 3rd Edition, FP1and earlier (S60 Platform SDKs) + +

    Qt SDKs

      -
    • Qt SDK for S60 +
    • Qt for Open Source C++ + (download)
    -

    UIQ SDKs (developer.uiq.com)

    -
      -
    • UIQ 3.1 -
    • UIQ 3.0 -
  • -

     

    - +
    + diff -r 3a264b9d91ef -r cc0961d7c88d core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jan 25 08:53:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jan 25 10:09:42 2010 -0600 @@ -19,7 +19,7 @@

    The Symbian OS Emulation launch configuration uses the Main page to define the process to be launched by the emulator.

    The behavior that occurs when launching a debug session varies based upon the SDK. Normally, starting a debug session launches the emulator (epoc.exe) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.

    -

    Figure 1. Main page (Emulation shown)

    +

    Figure 1. Main page (Emulation shown)

    Table 1. Emulator Main page —items
    @@ -53,7 +53,7 @@

    Run-mode Main page

    The Symbian OS Application TRK launch configuration uses the Main page to defines the project and the process to launch on the target device.

    -

    Figure 2 - Main page (Application TRK shown)

    +

    Figure 2 - Main page (Application TRK shown)

    Table 2. Run-mode Main page —items
    @@ -90,7 +90,7 @@

    Stop-mode Main page

    The Symbian OS System TRK, Sophia, and Trace32 launch configurations uses the Main page to defines the project and the executable to launch on the target device.

    -

    Figure 3. Main page (TRACE32 shown)

    +

    Figure 3. Main page (TRACE32 shown)

    Table 3. Stop-mode Main page — items
    diff -r 3a264b9d91ef -r cc0961d7c88d core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Mon Jan 25 08:53:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Mon Jan 25 10:09:42 2010 -0600 @@ -9,7 +9,7 @@

    Carbide supports the use of code styles in projects via the C/C++ Code Style preference panel. Use a code style profile to set specific smart typing features, like indentation, tabs or spaces, and many more options. There are several preset code styles like GNU, while Carbide supplies these profiles:

    Setting a code style sets it for the entire workspace. When a new file is created the currently selected code style rules are applied as you edit the file. You can apply a set of rules to a previously created source file by opening it in an editor view, then right-clicking and choosing Source > Format (CTRL+SHIFT+F).