How to Open Browser with a url in UIQ3.x

OpenBrowserWithUrlL(const TDesC& aUrl, CCoeEnv& aCoeEnv)
   {
   TVwsViewId id( KUidQWebApp, KUidQWebPageView);
   TQWebDNLUrlEntry obj;
   obj.iUrl = aUrl;
   TQWebDNLUrlEntryBuf buf(obj);
   aCoeEnv.AppUi()->ActivateViewL(id, KQWebCustomMsgId, buf);
   }

Auto-start In UIQ

The auto starter in UIQ did not have any particular order

To register with the auto starter your application must write a .ast file to the auto starter's import folder [\private\10274b9f]. On start-up the auto launcher parses the .ast files and will then add new ast files to its database of applications to be started. The ast format contains only the .exe name in plain text as the following example indicates:
calc.ast:

calc.exe

Note:
1. No path is needed: the file is a plain text, one-line executable name. The auto launcher will look across different drives for the executable to launch and no path need be specified; if you install to a MS then the auto launcher will launch from the MS; if the executable cannot be found it will be ignored. The ast file must be written (either by the application or via SIS) to the following import folder:- c:\private\10274b9f\import\

2. Security : The Auto starter will only start your application if it has the capability "WriteUserData".

What does the Application framework takes care while launching an application ?

The Framework will do following before starting the application.

    1. Create a connection to the file server.

    2. Create a connection to the window server.

    3. Create a connection to the memory manager.

    4. Do some application registration.

    5. Make sure the application is able to handle erroe and out-of-memory situtions.

    6. Initalize other application services like font etc.

    7. create default screen elements like status bar, menu bar, soft keys etc.

    8. Start active scheduler. (or you can send event loop)

What the term "Downgrade path" mean in UIQ3.

If a application is not coded to work on all available "UI Configurations" the UIQ3 UI framework will try to look for a nearest match and configures the Screen to that configuration, this process is called "Downgrade path".

"Downgrade path" also makes it possible for an application to run on a device which has a UI configuration that was not available at the time the application was written.

How to configure UIQ3 emulator to a specific "UI Configuration" ?

When launching the emulator we have to pass -ui parameter to it get the desired "UI Configuration"
eg. uiqenv -ui softkey
OR
We can use the SDKConfig application provided by the SDK.

What does UIQ3 UI Configuration is consist of ?

UI of UIQ3 is very versatile and can be configured by a 4 high-level configuration parameters. Combination all these parameters are called a UI configuration.

    1. Screen Mode.

        The following resolutions are commonly used.

        a) Portrait (QVGA, 240x320 pixels)

        b) Landscape (QVGA, 320x240 pixels)

        c) Portrait Small(240x256 pixels)

        d) Landscape Small(256x240 pixels)

    2. Screen orientation.

        Indicates whether screen is used in

        a) Normal Mode.

        b) Inverted Mode. (screen roated in 180 degrees)

    3. Touch Screen.

        Indicates whether to use advanced digitizer (Touch Screen) or Not.

    4. Interaction style.

        There are 2 general interaction styles used.

        a) Pen-Style. Optimized for pen use. also know as (Point Touch method)

        b) Softkey-Style. Optimized for one-handed navigation.

        

UI Configurations are enumerated in "Qikon.hrh" as

#define KQikSoftkeyStylePortrait (EQikScreenModePortrait  | EQikTouchScreenNo | EQikUiStyleSoftkey | EQikOrientationNormal)

As you can see the UI Configuration can have any combination above 4 parameters. But most commonly used paramets are

    a) KQikSoftkeyStylePortrait. Generally known as "SoftKey Style"

    b) KQikPenTouchPortrait. Generally known as "Pen Style".

What a UIQ3 SDK contains ?

    1. Library, header and binary files.

    2. Compilers 

        a) GCCE compiler for device build,

        b) Nokia x86 compiler for emulator builds.

    3. Tools and scripts (including perl scripts) for building application in C++ and creating installation files to distribute applications.

    4. PC-Based emulator (No Simulator) of the UIQ3 platform to enable fast development and turn around time.

    5. Documentation.

        a) API reference.

        b) Guides.

        c) Sample code.