Re: commit (head): ease customisation of menu layout

From: Robert Staudinger <robert.staudinger_at_gmail.com>
Date: Mon May 30 2005 - 10:23:50 CEST

On 5/30/05, Tomas Frydrych <tomasfrydrych@yahoo.co.uk> wrote:
>
>
> One of the issues that the Nokia guys run into is the inflexibility of
> our menu layout system; it just gets too messy if you want provide very
> different menu layout. I have been thinking about how to make it easier
> to customise without completely decentralising it (which would mean
> increased maintanance) and I have come up with a simple solution, using
> technique based Hub's xap_Features.h
>
> First of all I added add ap_Features.h along the lines of xap_Features.h
> (since menus are defined in ap_ space).
>
> If a particular platform wants to provide a menu layout that is
> radically different from the standard abi layout, it would create the
> layout (using the same technique as ap_Menu_Layouts_MainMenu.h) in
> ap_*Menu_Layouts_MainMenu.h (where * is what ever identifier the
> platform uses, say ap_HildonMenu_Layouts_MainMenu.h)
>
> As a second step, in its ap_*Features.h it would then include
> #define APF_MENU_LAYOUT_MAIN_MENU "ap_*Menu_Layout_MainMenu.h"
> (It also needs to add the appropriate include statements into
> ap_Features.h).
>
> I modified the ap_Menu_Layouts_MainMenu.h so that the exsiting
> contents are included conditionally:
>
> #include "ap_Features.h"
> #ifndef APF_MENU_LAYOUT_MAIN_MENU
> // the existing AW layout comes here ...
> #else
> #include APF_MENU_LAYOUT_MAIN_MENU
> #endif
>
> I would appreciate if this could be backported before we create a branch
> for the N770 merger.

Does this really have to be backported /before/ the branching action
or can it just be backported to the "hildon" branch (assuming that
there won't be an AbiWord-official release of the 2.2 branch including
the hildon port)?

- Rob
Received on Mon May 30 10:24:02 2005

This archive was generated by hypermail 2.1.8 : Mon May 30 2005 - 10:24:02 CEST