Talk:Theme Management API

The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like

Theme API Config File

egaudet v3

theme_config.json sans required quotes

{ 
  app:
  {
    { com.palm.package1: { icon: relative/path/to/icon, cssFileName: relative/path/to/css },
    { com.palm.package2: { icon: relative/path/to/icon }
  },

  global:
  {
    cssFileName: relative/path/to/global/css 
  }
}

Does this assume that the css files pointed to will be sparse? rboatright 06:19, 31 January 2010 (UTC)

PuffTheMagic v3

applications:
{
  com.palm.package1:
  {
    launcherIcon = relative/path/to/icon1;
  }
  com.palm.package2:
  {
    css = relative/path/to/css2;
  }
  com.palm.package3:
  {
    css = relative/path/to/cs3;
    launcherIcon = relative/path/to/icon3;
  }
};

rboatright =

global css replacements not related to apps

{
  cssFileName:  relative/path/to/replacement/cssFile.css
}

zsoc

HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER