[webkit-qt] mobile specific features and defines

Jocelyn Turcotte jocelyn.turcotte at nokia.com
Wed Jun 16 02:09:33 PDT 2010


We could segment and wrap different "mobile" features using something 
like #if ENABLE(TOUCH_INPUT) and have all these features enabled when we 
use CONFIG+=mobile.
This would allow different settings for individual features to be 
specified when compiling for half-mobile devices.

Jocelyn

On 6/15/2010 4:28 PM, ext Kenneth Christiansen wrote:
> Be careful about "mobile". A tablet is considered a mobile device and
> some of our define might more be related to touch being the input
> method than it being a mobile device
>
> Kenneth
>
> On Tue, Jun 15, 2010 at 11:13 AM, Simon Hausmann
> <simon.hausmann at nokia.com>  wrote:
>    
>> Hi,
>>
>> In the course of the discussion in
>>
>>         https://bugs.webkit.org/show_bug.cgi?id=40062
>>
>> I'm now wondering if we should perhaps replace all the occurences of Q_WS_S60
>> and Q_WS_MAEMO5 with #if PLATFORM(QT_MOBILE) or so and _require_ that when
>> building WebKit you have to pass something like
>>
>>     qmake CONFIG+=mobile
>>
>> in order to get a "mobile" WebKit build.
>>
>> We _could_ set this configuration automatically for makespecs where we know
>> that they're mobile only, such as symbian or maemo5, but otherwise this could
>> be an option developers have to provide.
>>
>> What do you think?
>>
>>
>> Simon
>>
>> _______________________________________________
>> webkit-qt mailing list
>> webkit-qt at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>>
>>
>>      
>
>
>    


More information about the webkit-qt mailing list