Difference between revisions of "Talk:Theme Management API"
Jump to navigation
Jump to search
PuffTheMagic (talk | contribs) |
Rboatright (talk | contribs) (rb) |
||
Line 30: | Line 30: | ||
} | } | ||
}; | }; | ||
+ | </pre> | ||
+ | ==== rboatright ===== | ||
+ | |||
+ | global css replacements not related to apps | ||
+ | <pre> | ||
+ | { | ||
+ | cssFileName: relative/path/to/replacement/cssFile.css | ||
+ | } | ||
</pre> | </pre> | ||
==== zsoc ==== | ==== zsoc ==== |
Revision as of 05:38, 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 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