/*

* Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies).

* All rights reserved.

* This component and the accompanying materials are made available

* under the terms of "Eclipse Public License v1.0"

* which accompanies this distribution, and is available

* at the URL "http://www.eclipse.org/legal/epl-v10.html".

*

* Initial Contributors:

* Nokia Corporation - initial contribution.

*

* Contributors:

*

* Description: 

*

*/

#ifndef __BLDPUBLIC_HRH

#define __BLDPUBLIC_HRH

#define LANGUAGE_IDS LANG sc 37 102 42 44 45 25 07 18 01 10 129 158 160 159 157 161 49 50 09 02 51 103 03 54 57 30 17 15 59 327 05 32 65 67 68 70 326 08 27 13 76 31 78 16 79 26 28 04 83 06 39 29 33 14 93 94 96 

/** #Camera 

Container for camera specific features

*/

#undef Camera                                             

/** #FF_3D_RINGING_TONES 

Device supports 3D ringing tones.

*/

#undef FF_3D_RINGING_TONES                                

/** #FF_3G_CELLBROADCAST 

Cell Broadcasting support on 3G mode.

*/

#undef FF_3G_CELLBROADCAST                                

/** #FF_ABC_AGRESSIVE_UI 

Display driver will provide an interface for switching Automatic Brightness

Control (ABC). More agressive Automatic Display Control (ABC) UI for display

driver will be in Settings display plug in, and as configurable for products,

but not neccessarily available for user. The agressive UI for ABC is

enabled/disabled by the feature flag.  

*/

#undef FF_ABC_AGRESSIVE_UI                                

/** #FF_ADAPTIVE_WLAN_SCANNING_SUPPORT 

Adaptive WLAN Scanning (AWS) is a component that tells WLAN engine how often to

perform WLAN background scanning. AWS listens and receives events from other

components, concludes what would be the preferred scanning period, and then

tells it to WLAN engine.

*/

#undef FF_ADAPTIVE_WLAN_SCANNING_SUPPORT                  

/** #FF_ADDITIONAL_FONTS 

This flag is to enable new font supports namely equivalents of Arial, Times New

Roman, Courier for content viewing mainly to be used in browser. If this flag is

not enabled it means it will continue to have only current fonts and no

additional font support.

*/

#define FF_ADDITIONAL_FONTS                                

/** #FF_AI_WLANSNIFFER_WIDGET 

Flag for WLANSniffer Homescreen widget.

*/

#undef FF_AI_WLANSNIFFER_WIDGET                           

/** #FF_ASYNCH_FILE_SAVE_QUEUE 

Camcorder requires support from the Asynchronous File Save Queue.

*/

#define FF_ASYNCH_FILE_SAVE_QUEUE                          

/** #FF_AT_COMMANDS_TEST_AUTOMATION 

Using FF_AT_COMMANDS_TEST_AUTOMATION will either include or exclude

atcmdplugin.dll from ROM

*/

#undef FF_AT_COMMANDS_TEST_AUTOMATION                     

/** #FF_AUDIO_MESSAGING_INCLUDE_IN_ROM 

This flags controls whether the Audio Messaing ROM files are included in the

build.

*/

#define FF_AUDIO_MESSAGING_INCLUDE_IN_ROM                  

/** #FF_AUDT 

Device supports Always Up-to-date Device Time (AUDT). This is an ability to

update the device time, date and country/city automatically in phone start-up.

*/

#undef FF_AUDT                                            

/** #FF_AUTO_REDIAL_FOR_VIDEO_CALL 

This flag indicates redial sequence, when video call is not succeeded for

certain reasons.

*/

#define FF_AUTO_REDIAL_FOR_VIDEO_CALL                      

/** #FF_AVKON_EMOTION_ICON_ENABLED 

to enable/disable the emotion icon support in avkon editor control

*/

#define FF_AVKON_EMOTION_ICON_ENABLED                      

/** #FF_BIRTHDAY_IMPROVEMENT 

This feature flag is required for the enabling/disabling customized birthday &

anniversary notifications for MyFaves contact in Calendar (under Community 1.0)

into 3.2.3 platform. 

The requirement is 

B’day & Anniversary Notification for MyFaves contact

•	Picture of the MyFaves contact in the popup which can be masked as circular

•	Currently Birthday notification is same as any other Calendar alarm

*/

#undef FF_BIRTHDAY_IMPROVEMENT                            

/** #FF_BLUETOOTH_DATA_PROFILES_DISABLED 

This flag is used to turn off bluetooth data profiles, and is to be used as part

of Enterprise Disabling of Bluetooth, allowing the device to use bluetooh for

hands free purposes only

*/

#undef FF_BLUETOOTH_DATA_PROFILES_DISABLED                

/** #FF_BLUETOOTH_DISABLED 

Flag used to disable all Bluetooth functionality in the device.  This will be

used for Enterprise Disabling of Bluetooth.  

This flag is required to be used instead of the __BT flag so that the Bluetooth

UI is still present after Bluetooth has been disabled, allowing the user to be

notified of why they cannot use it if they attempt to

*/

#undef FF_BLUETOOTH_DISABLED                              

/** #FF_BROWSER_PROGRESSIVE_DOWNLOAD 

This feature flag is needed to enable/disable the progressiveness of the

downloads in download manager server and its clients.

*/

#define FF_BROWSER_PROGRESSIVE_DOWNLOAD                    

/** #FF_CAL_MEETING_REQUEST_UI 

With this flag it is selected if Meeting Request UI included with flag

FF_MEETING_REQUEST_UI is available on Calendar side or not. If flag is not

defined MRUI is available only when MR Emails are opened from Email application.

If flag is defined then meeting requests can be opened also from Calendar

application and Calendar application will offer possibility to create new

meeting requests.

*/

#undef FF_CAL_MEETING_REQUEST_UI                          

/** #FF_CAPACITIVE_DISPLAY 

Device uses capacitive touch technology in its display.

*/

#define FF_CAPACITIVE_DISPLAY                              

/** #FF_CHINESE_FONTS_HIRES 

This flag controls whether Chinese variants use TrueType fonts instead of the

current stroke fonts in high resolution devices.

Current stroke fonts have good readability in small sizes and lower resolution

devices. However, with the introduction of ever sharper and larger displays

(HVGA, VGA), the stroke fonts look increasingly "too simple" and "stick-like" in

bigger sizes. Fonts with thicker, more stylistic strokes are required for a

proper look and user experience.

Following requirements already make a case for TTF fonts in Chinese:

417-16400: Chinese TrueType font for 9.1

406-137: TrueType font for Chinese

Note: The feature name intentionally avoids mentioning TrueType or TTF, as the

font technology is irrelevant, high resolution being the operative keywords.

*/

#undef FF_CHINESE_FONTS_HIRES                             

/** #FF_CHINESE_SELECTION_KEY 

Device uses this flag to differentiate if selection key existed

*/

#undef FF_CHINESE_SELECTION_KEY                           

/** #FF_CLOCK_MULTIPROCOL_SUPPORT 

This flag shall be used to determine if product programs need clock's

multiprotocol support, i.e. getting time information from different time source

protocols like GPS, SNTP, etc.. Product program can make a choice such that

multiprotocol feature support can be made on or off. When multiprotocol support

is off, then default NITZ protocol shall be choosen.

*/

#undef FF_CLOCK_MULTIPROCOL_SUPPORT                       

/** #FF_CMAIL_INTEGRATION 

5250+ specific features in Cmail are variated with this flag.

*/

#undef FF_CMAIL_INTEGRATION                               

/** #FF_COMMSDAT_CREATION_FROM_XML 

There will be a new component in S60 called CommsDatCreator (CDC) that will

initialize CommsDat using an input XML file which is generated by the

Configuration Tool.

When generating CommsDat the CDC needs that the default CommsDat in

Z:\private\10202be9\cccccc00.cre is empty. 

The requested flag FF_COMMSDAT_CREATION_FROM_XML  enables the empty CommsDat to

be included to the image as the default CommsDat.

*/

#undef FF_COMMSDAT_CREATION_FROM_XML                      

/** #FF_COMMSDAT_CREATOR 

This flags controls whether the CommsDatCreator component to be included to the

image.

*/

#define FF_COMMSDAT_CREATOR                                

/** #FF_CONNECTION_OVERRIDE 

The feature enables the better utilisation of the WLAN connections that the user

has manually opened from the WLAN widget. Such connections, called as 'user

connections', will be automatically utilised in all applications that would

normally use Internet SNAP connection. If the feature is enabled, the 'user

connection' is enforced by default. The user can still control the utilisation

of the 'user connection' by enabling/disabling the connection enforcement from

WLAN settings.

*/

#define FF_CONNECTION_OVERRIDE                             

/** #FF_CONTACTS_COMPANY_NAMES 

When enabled, contacts’ company names are shown after first+last name in

Phonebook Names list.

*/

#undef FF_CONTACTS_COMPANY_NAMES                          

/** #FF_CONTACTS_GROUP_FUNCTIONALITY 

We need a feature flag for ROM Creation time variation. The Phonebook2

application is constructed on a plugin based architecture. This design allows

the Phonebook2 application to be composed of various plugin components. The S60

platform Phonebook2 component contains a group UI plugin component, which

implements the whole contacts group functionality. To enable a variant to create

their own contact group functionality we need a feature flag so that the variant

can remove the platform group plugin component. This allow the component to be

removed from the ROM image, thus making the ROM size smaller.

*/

#define FF_CONTACTS_GROUP_FUNCTIONALITY                    

/** #FF_CONTACTS_MERGE 

If enabled, then phonebook UI contains the command for Merge.

*/

#define FF_CONTACTS_MERGE                                  

/** #FF_CONTACTS_MYCARD 

This feature flag controls whether phonebook application supports MyCard.

If flag is enabled:

- Phonebook has MyCard item at top of names list

- The user can open MyCard view from phonebook

- Other applications can launch the MyCard view 

*/

#define FF_CONTACTS_MYCARD                                 

/** #FF_CONTACTS_NICKNAME 

The nickname functionality needs a feature flag for the following reasons:

-Phonebook2 component exports a central repository initialization file, which is

used to improve the Phonebook application launch -The initialization file is

read by the Symbian Contacts model server to initialize the Contacts view during

the device boot sequence

 * S60 specifications define which fields take part in the device's contact name

creation (first name, last name, company name)

 * The nickname requirement changes the S60 name creation rules, by adding the

contacts nickname field to the above list of fields

 * Therefore the content of the Contacts view needs to be initialized

differently depending on whether the nickname feature is enabled or disabled

 * The initialization file contains the configuration of the view, e.g. the

contact fields which are used for sorting the Phonebook names list view

 * A feature flag is needed which allows Phonebook2 to export the correct

variant of the Contact view initilization file

 * There is a considerable RAM usage penalty associated with keeping the

nickname field in the contact view when the nickname feature is disabled

 * For further description of the Symbian Contacts view initilization see

\src\common\generic\app-engines\cntmodel\documentation\Contacts_How-To_Improve_Application_Start-up_Time.doc

-Run-time variation can be used inside the Phonebook2 application to configure

the application sort order

 * But the Symbian Contacts view's must be configured correctly in order to

maintain existing performance, see above description

*/

#undef FF_CONTACTS_NICKNAME                               

/** #FF_CONTACTS_PREDICTIVE_SEARCH 

When enabled, User can turn on/off Phonebook’s predictive search functionality,

using an item in Names list’s Option-menu.

*/

#undef FF_CONTACTS_PREDICTIVE_SEARCH                      

/** #FF_CONTACTS_REMOTE_LOOKUP 

When enabled, and a remote search service is installed in device, item “Search

remotely” is shown in Phonebook Names list.

*/

#define FF_CONTACTS_REMOTE_LOOKUP                          

/** #FF_CONTACTS_SOCIAL 

When flag is enabled, phonebook application has the following features:

- Names list shows social status texts

- Contact Card shows social status text & allows jumping to external social

application.

- MyCard shows social status text & allows jumping to external social

application.

- MyCard has button(s) that show(s) presence & allow jumping to external IM

application.

*/

#define FF_CONTACTS_SOCIAL                                 

/** #FF_CONTEXT_FRAMEWORK_V2 

This flag enables Context Framework version 2.

*/

#undef FF_CONTEXT_FRAMEWORK_V2                            

/** #FF_CONTEXT_PROFILES 

Context profiles enable the device to automatically adapt in users every day

life and combine current Profiles functionality with concepted and studied

Situations functionality. If the flag sets to true, context profiles are

enabled. If flase, otherwises.

*/

#undef FF_CONTEXT_PROFILES                                

/** #FF_CUSTOMER_HELPS_IN_USE 

Customer helps are included into image based on this flag.

*/

#undef FF_CUSTOMER_HELPS_IN_USE                           

/** #FF_DEVICE_DIAGNOSTICS_APP 

On enabling this feature flag GSDevDiagPlugin.dll would start the

DevDiagApp.exe. This would load all related plugins. The Diagnostics application

offers self-test service on the Mobile Applications and hardware for the phone

users.

*/

#define FF_DEVICE_DIAGNOSTICS_APP                          

/** #FF_DEVICE_ENCRYPTION_FEATURE 

This flag is required for Device Encryption feature which goes to Symbian

Foundation. The existing flag (FF_NATIVE_FILE_ENCRYPTION) will exclusively be

used by NFE, which doesn't go to SF. Hence a different flag is required for all

those middleware and application layer components of DE.

*/

#define FF_DEVICE_ENCRYPTION_FEATURE                       

/** #FF_DISABLE_OMA_SUPL_V2 

When this flag is ON SUPL v2.0 is NOT supported. Note that this flag is a

negative flag in order to minimize the risk for the master code line.

*/

#undef FF_DISABLE_OMA_SUPL_V2                             

/** #FF_DM_BROWSER_ADAPTER 

Browser adaper is used by Device Management to Set/Get the browser settings from

the operator server. This feature is requested by CMCC. The feature flag is used

to differentiate between Nokia Specific implemenation and OMA DM implementation.

*/

#define FF_DM_BROWSER_ADAPTER                              

/** #FF_DM_CONNMO_ADAPTER 

OMA Device Management Connectivity Managment Object (ConnMO) provides management

of connectivity settings. This flag will help in enabling ConnMO plugin.

*/

#undef FF_DM_CONNMO_ADAPTER                               

/** #FF_DM_INSTALL_SECURITY 

OMA DM SW installer implementation included in build.

*/

#undef FF_DM_INSTALL_SECURITY                             

/** #FF_DM_STREAMING_ADAPTER 

Streaming adapter is used by Device Mangement to Set/Get the streaming settings

from the operator server. CMCC has requested support for this new adapter. This

feature flag is used to differentiate the Nokia specfic implementation and OMA

DM implementation.

*/

#define FF_DM_STREAMING_ADAPTER                            

/** #FF_DUAL_LANGUAGE_SUPPORT 

This Flag is used to develop support for dual language feature. This is an

enhancement to the basic prediction feature where words predicted will come from

2 different language databases.

*/

#undef FF_DUAL_LANGUAGE_SUPPORT                           

/** #FF_DUAL_MODEM 

Flag for developing Dual Modem feature

*/

#undef FF_DUAL_MODEM                                      

/** #FF_EMAIL_FRAMEWORK 

Defines whether the product includes the email multiprotocol framework. When the

flag is defined all parts constituting new email solution are in ROM:

application, plugin framework + imap/pop plugin and related settings UIs. 

legacy email (__EMAIL_UI) must be disabled when FF_EMAIL_FRAMEWORK is enabled.

*/

#define FF_EMAIL_FRAMEWORK                                 

/** #FF_EMAIL_IPS_SERVICES 

Defines whether the product includes IMAP4, POP3 and SMTP protocol support.

*/

#undef FF_EMAIL_IPS_SERVICES                              

/** #FF_EMAIL_MCE_INTEGRATION 

This enables email client selection in MCE. Fex. Freestyle email mailboxes  goes

under email folder in mce-serttings. mce and sendui. Freestyle email settings

can be changed from mce-settings.

 All you need to do is install own mtm-plugin and configure central repository

key.

*/

#define FF_EMAIL_MCE_INTEGRATION                           

/** #FF_EMAIL_PROTOCOL_PLUGINS 

When defined, default email protocol plugins are enabled.

*/

#define FF_EMAIL_PROTOCOL_PLUGINS                          

/** #FF_EMAIL_UI 

Defines whether the product includes email UI application

*/

#undef FF_EMAIL_UI                                        

/** #FF_EMPTY_COMMSDAT 

The override flags FF_EMPTY_COMMSDAT, FF_VANILLA_COMMSDAT and FF_RND_COMMSDAT

determine which default CommsDat will be put to the image independent of image

type (prd or rnd):

- FF_EMPTY_COMMSDAT: Completely empty CommsDat is used. Typically needed as the

base when creating operator variants with Configuration Tool and

CommsDatCreator. Same as old FF_COMMSDAT_GENERATION_FROM_XML.

- FF_VANILLA_COMMSDAT: Otherwise empty CommsDat but the S60 default destinations

(Internet, MMS and Operator) as well as the Easy WLAN IAP (in case of WLAN

product) is included. This is suitable for vanilla variants of the phones.

- FF_RND_COMMSDAT: Platform releases contain typically the RND CommsDat that has

Nokia Test Network IAPs as well as some Finnish operator IAPs (DNA, Sonera,

Elisa) for RnD purposes.

Maximum of one of these flags should be defined at the time. 

If none of the override flags is defined then the used CommsDat depends on the

image type: vanilla CommsDat is used for PRD image and RnD CommsDat for the RnD

image. This is typically how it should be and the override flags should only be

used if some special functionality is needed.

*/

#undef FF_EMPTY_COMMSDAT                                  

/** #FF_ENABLE_ISI_COMMUNICATION_IN_USB_CHARGING_MODE 

Feature info adaptation will read the PP-bit value from ISA info server and map

the value of PP bit into KFeatureIdCertTesting. SSM then will read

KFeatureIdCertificationTesting and if system is in USB charging mode , then

start USB components into the mode where ISI communication is possible.

*/