User:Epage/Branding

 
Line 1: Line 1:
 +
My focus would be on getting basic branding done, updating mer-cpa-about to use it, and then writing mer-cpa-hwbuttons to take advantage of device-branding
 +
Structure
Structure
* Seperate settings from branding
* Seperate settings from branding
Line 14: Line 16:
*** Images with model rendering
*** Images with model rendering
*** File that maps keycodes to names or images of the HW buttons
*** File that maps keycodes to names or images of the HW buttons
-
**** Implementing this will lead into also writing a CPA to map the buttons
 
** distribution-settings
** distribution-settings
*** Default plugins choices, like HIM
*** Default plugins choices, like HIM

Latest revision as of 14:32, 15 July 2009

My focus would be on getting basic branding done, updating mer-cpa-about to use it, and then writing mer-cpa-hwbuttons to take advantage of device-branding

Structure

  • Seperate settings from branding
    • Unlike Ubuntu
    • Allows multiple brandings in the system, settable through /etc/alternatives
      • Makes testing easier
  • Packages Types
    • distribution-branding
      • File with name and version
      • Images with light/dark, big/small, multiple resolution logos
    • device-branding
      • File with vendor, model
      • Images with vendor logo
      • Images with model logo, if applicable
      • Images with model rendering
      • File that maps keycodes to names or images of the HW buttons
    • distribution-settings
      • Default plugins choices, like HIM
    • device-settings
      • Default setxkbd settings for HW keyboard
      • Default for if softkeyboard launches
      • Default xmodmap settings for HW Buttons
      • first-boot.d behavior, like load blobs from Maemo