Difference between revisions of "Talk:Theme Management API"

From WebOS Internals
Jump to navigation Jump to search
Line 10: Line 10:
 
};
 
};
 
</pre>
 
</pre>
==== PuffTheMagic ====
+
==== PuffTheMagic Old ====
 
<pre>
 
<pre>
 
launcherIcons:
 
launcherIcons:
Line 16: Line 16:
 
   com.palm.package1 = relative/path/to/icon1;
 
   com.palm.package1 = relative/path/to/icon1;
 
   com.palm.package2 = relative/path/to/icon2;
 
   com.palm.package2 = relative/path/to/icon2;
 +
};
 +
</pre>
 +
 +
==== PuffTheMagic New ====
 +
 +
<pre>
 +
applications:
 +
{
 +
  com.palm.package1:
 +
  {
 +
    launcherIcon = relative/path/to/icon1;
 +
  }
 +
  com.palm.package12
 +
  {
 +
    launcherIcon = relative/path/to/icon2;
 +
  }
 
};
 
};
 
</pre>
 
</pre>

Revision as of 04:52, 31 January 2010

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

launcherIcons:
{
  appid: { icon = relative/path/to/icon };
  appid: { icon = relative/path/to/icon };
};

PuffTheMagic Old

launcherIcons:
{
  com.palm.package1 = relative/path/to/icon1;
  com.palm.package2 = relative/path/to/icon2;
};

PuffTheMagic New

applications:
{
  com.palm.package1:
  {
    launcherIcon = relative/path/to/icon1;
  }
  com.palm.package12
  {
    launcherIcon = relative/path/to/icon2;
  }
};

zsoc

HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER