/*

* 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

//Defining only language 01 for SF build purposes

#define LANGUAGE_IDS LANG sc 01  

/** #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_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_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_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

*/

#undef 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_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_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_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_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_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_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_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.

*/

#undef FF_DEVICE_DIAGNOSTICS_APP                          

/** #FF_DM_INSTALL_SECURITY 

OMA DM SW installer implementation included in build.

*/

#undef FF_DM_INSTALL_SECURITY                             

/** #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_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_FARSI_CALENDAR 

S60 calendar should provide possibility to integrate Farsi calendar application

to S60 calendar.

 S60 calendar should provide variation point to calendar main menu, from where

Farsi calendar application can be launched. In addition S60 calendar setting

should provide access to the Farsi calendar settings. User should comfortably

move btwn Gregorian and Farsi calendars. 

Farsi calendar will be enabled in the variants English & Farsi. These variants

can be extended further as per the need. 

This feature is approved and targeted for 3.2.3 products. So variation required

from 3.2.3 onwards. 

*/

#undef FF_FARSI_CALENDAR                                  

/** #FF_FLASHLITE_SCREENSAVER 

When enabled/defined flash can be used as Screensaver.

*/

#undef FF_FLASHLITE_SCREENSAVER                           

/** #FF_FMTX 

FMTX application and Nseries Music Player support for FMTX

*/

#undef FF_FMTX                                            

/** #FF_FULLSCR_HWR_INPUT 

Indicates whether a device needs fullscreen HWR (HandWritingRecognition) input

or not.

*/

#undef FF_FULLSCR_HWR_INPUT                               

/** #FF_GENERIC_FONTS_ASSETS 

This flag is used to check if generic font assets are to be used, this is used

for Symbian foundation where freetype rasterize as well as EFF fonts need to be

used.

*/

#undef FF_GENERIC_FONTS_ASSETS                            

/** #FF_GSTREAMER 

Device supports GStreamer APIs.

*/

#define FF_GSTREAMER                                

/** #FF_HDMI 

Feature flag to indicate HDMI availability.  IIf defined, device supports HDMI

(High Definition Multimedia Interface)

*/

#undef FF_HDMI                                            

/** #FF_HELP_TUTORIAL_MERGE 

The end-user shall be provided with animated help (tutorial kontent) from CSX

Help application. Both applications will continua existing as separate

applications, though Tutorial will not be visible in application grid, but only

provide animated content for CSX Help.

This is for REQ 417-16797. Help & Tutorial will look like one application. User

will not feel that they are 2 different applications. To implement this REQ

without breaking the compatibility, one feature flag is needed to make Help &

Toturial applications know if Tutorial is embedded in Help or running as a

standalone application. Also refer to REQ 101-39505.

*/

#undef FF_HELP_TUTORIAL_MERGE                             

/** #FF_HIJRI_CALENDAR 

S60 calendar should provide possibility to integrate separate Hijri calendar

application to S60 calendar.

S60 calendar should provide variation point to calendar main menu, from where

Hijri calendar application can be launched. In addition S60 calendar setting

should provide access to the Hijri calendar settings. User should comfortably

move btwn Gregorian and Hijri calendars.

Hijri calendar will be enabled in the variants English, Arabic, Urdu , French &

Farsi. These variants can be extended further as per the need. 

This feature is approved and targeted for 3.2.3 products. So variation required

from 3.2.3 onwards.

*/

#undef FF_HIJRI_CALENDAR                                  

/** #FF_HITCHCOCK_APP_SHELL 

"Feature flag 'FF_HITCHCOCK_MENU' to control which AppShell menu to use. If

disabled, old xml based menu2, and if enabled, new hitchcock based menu3."

*/

#undef FF_HITCHCOCK_APP_SHELL                             

/** #FF_HOMESCREEN_COMMON_IDLEFW 

Feature flag for enabling common idle framework to support new widgetized

stand-by mode application of Active Idle 3 on S60 by REQ "101-40598: HomeScreen:

3rd Party widget support" as alternative of existing Active Idle 2 and yet

enabling even custom made stand-by mode app to be active. The binary objects

which comprise common idle framework related components and new active stand-by

application, selection of alternative,  and its depended components, can be

selected at image creation time in case where common ilde fw is accepted by

product/variant decicion.

*/

#define FF_HOMESCREEN_COMMON_IDLEFW                        

/** #FF_HOMESCREEN_OPEN_MENUFW 

Feature flag for activation of open menu framework to support alternative main

menu applications on S60 by REQS "101-40417: Open Shell UI internal menu model

for other applications", "417-8821: Non-touch VGA support for Matrix" and

"404-3950: Matrix: Basic Menu". Existing main menu app, Hitchcock AppShell, can

still be used if product/variant decides so, however, open menu fw which enables

altenative menu applications to run on same content, can be chosen as well. The

binary objects which comprise open menu fw and active main menu application with

its depended components can be selected at image creation time, as well as it is

possible to request appropriate main menu application UID when needed to

configure S60. These requests are, for example, setting the application UID to

launch main menu by "applications" hw-key and hide menu application from itself

etc. 

*/

#define FF_HOMESCREEN_OPEN_MENUFW                          

/** #FF_HOMESCREEN_SWITCHABLE_ROOT 

Homescreen root configuration replaces existing concept of Active Idle

themes/modes from S60 5.1. FF_HOMESCREEN_SWITCHABLE_ROOT variates S60 by

enabling/disabling possibility to switch homescreen root. Homescreen root switch

must be enabled to end user to select operator/product  specific alternative

homescreen active, for example, an alternative root or External Homescreen. This

feature must be able to set at run time also for post-product provision of

alternative homescreen.

*/

#undef FF_HOMESCREEN_SWITCHABLE_ROOT                      

/** #FF_IAUPDATE 

If defined, the phone supports Independent Application Update feature.

*/

#define FF_IAUPDATE                                        

/** #FF_IAUPDATE_PHASE2 

Flag to control whether phone's Independent Application Update feature,

controlled by FF_IAUPDATE, is version two or later, a.k.a. IAD client phase 2.

*/

#define FF_IAUPDATE_PHASE2                                 

/** #FF_IMAGEPRINT_BT_PROTOCOL 

Flag to control whether ImagePrint supports Bluetooth-printing

*/

#define FF_IMAGEPRINT_BT_PROTOCOL                          

/** #FF_IMAGEPRINT_MEMORYCARD_PROTOCOL 

Flag to define whether ImagePrint supports printing to memorycard

*/

#define FF_IMAGEPRINT_MEMORYCARD_PROTOCOL                  

/** #FF_IMAGEPRINT_PICTBRIDGE_PROTOCOL 

Flag to define whether ImagePrint supports PictBridge printing - meaning

printing over USB.

*/

#define FF_IMAGEPRINT_PICTBRIDGE_PROTOCOL                  

/** #FF_IMAGEPRINT_UPNP_PROTOCOL 

Flag to define whether ImagePrint supports UPnP printing

*/

#define FF_IMAGEPRINT_UPNP_PROTOCOL                        

/** #FF_INCLUDE_CHINESE_DICTIONARY 

This feature flag  controls the inclusion/exclusion of chinese dictionary in

chinese variants. The flag is used in dictionary_variant.iby

*/

#undef FF_INCLUDE_CHINESE_DICTIONARY                      

/** #FF_INPUTS_PER_ORIENTATION 

the feature is implemented to adjust dynamically available input methods

according to autorotation status. 

when autorotation is ON, if orientation is landscape, show menu items exclude

"virtual ITU-T" and virtual ITU-T is also unavailabe, else if orientation is

portrait show menu items exclude "FSQ" and FSQ is also unavailabe.

*/

#undef FF_INPUTS_PER_ORIENTATION                          

/** #FF_INTELLIGENT_TEXT_INPUT 

Generic QWERTY framework and 2nd generation text input engine integration

*/

#undef FF_INTELLIGENT_TEXT_INPUT                          

/** #FF_JAVA_GLOBAL_INDICATORS_API 

Enables Java Global Indicator API. Global Indicator API can be used to add

indicators to phone status pane.

*/

#undef FF_JAVA_GLOBAL_INDICATORS_API                      

/** #FF_LAYOUT_360_640_NONTOUCH 

New non touch NHD (=QHD) resolution. Flag determine which layout dlls are put to

hw image. 

*/

#undef FF_LAYOUT_360_640_NONTOUCH                         

/** #FF_LAYOUT_360_640_TOUCH_QHD2 

Layout data for QHD2_TOUCH resolution.

*/

#undef FF_LAYOUT_360_640_TOUCH_QHD2                       

/** #FF_LAYOUT_480_640_VGA3 

Layout data for VGA3 resolution.

*/

#undef FF_LAYOUT_480_640_VGA3                             

/** #FF_LAYOUT_640_360_NONTOUCH 

New non touch NHD (=QHD) resolution.  Flag determine which layout dlls are put

to hw image.

*/

#undef FF_LAYOUT_640_360_NONTOUCH                         

/** #FF_LAYOUT_640_360_TOUCH_QHD2 

Layout data for QHD2 TOUCH resolution.

*/

#undef FF_LAYOUT_640_360_TOUCH_QHD2                       

/** #FF_LAYOUT_640_480_VGA3 

Layout data for VGA3 resolution.

*/

#undef FF_LAYOUT_640_480_VGA3                             

/** #FF_LBT_ENGINE 

To enable/disable LBT engine from S60. By default this should be ON

The Location Triggering subsystem provides a service to applications for

notifications based on the user’s location. Applications can create and remove

location based triggers, and applications can be notified or started when one of

their triggers is fired, i.e. the triggering conditions are met

Feature wiki : https://s60wiki.nokia.com/S60Wiki/Location_based_triggering

REQ: 101-34742

BREL : 405-1756

*/

#define FF_LBT_ENGINE                                      

/** #FF_LBT_EVENTSUI 

To enable EventsUi application. Default is ON

Location events  help the users to create location-based reminders. It allows

the user to create a event and assign a location to it.  When you get close by

to the location, it prompts you with a reminder by playing a alarm tone or

displaying a text note or voice note assigned to that event.

REQ : 403-1621

BREl : 405-1781

*/