Talk:Theme Management API - Revision history

Egaudet at 19:31, 1 February 2010

2010-02-01T19:31:40Z

2010-02-01T19:30:47Z

2010-02-01T06:19:42Z

2010-02-01T00:33:16Z

2010-02-01T00:32:28Z

2010-02-01T00:19:08Z

2010-02-01T00:18:25Z

2010-01-31T18:36:13Z

2010-01-31T08:34:59Z

2010-01-31T06:19:38Z

egaudet v3

@@ Line 1: / Line 1: @@
 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 ===
+=== Organization ===
 I suppose we could list all the Parts of themeing and how we want to separate/organize:
 <pre>
@@ Line 11: / Line 11: @@
 Fonts
 </pre>
 ==== egaudet v4 ====
 theme_config.json sans required quotes

@@ Line 2: / Line 2: @@
 === Theme API Config File ===
 ==== egaudet v4 ====
 theme_config.json sans required quotes

@@ Line 22: / Line 22: @@
+   {
      image: relative/path/to/image
+   },
+}
 </pre>

@@ Line 4: / Line 4: @@
 ==== egaudet v4 ====
 theme_config.json sans required quotes
-Launch Point Icons are given a launchPointId, which by default is simply the <appid>_default.  Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file.
+Launch Point Icons are given a launchPointId, which by default is simply the <appid>_default.  Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file.  If no launchPointId is given, <appid>_default will be set.
 <pre>
+{

@@ Line 4: / Line 4: @@
 ==== egaudet v4 ====
 theme_config.json sans required quotes
 <pre>
+{
    applications:
+   [
-       { launchPointId: com.palm.package1_default, icon: relative/path/to/icon, cssFileName: relative/path/to/css },
+       { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },
-       { launchPointId: com.palm.package2_default, icon: relative/path/to/icon }
+       { appId: com.palm.package2, icon: relative/path/to/icon },
    ],

@@ Line 15: / Line 15: @@
+   {
      cssFileName: relative/path/to/global/css
+   }
+}

← Older revision		Revision as of 08:34, 31 January 2010
Line 20:		Line 20:

	Does this assume that the css files pointed to will be sparse? [[User:Rboatright\|rboatright]] 06:19, 31 January 2010 (UTC)		Does this assume that the css files pointed to will be sparse? [[User:Rboatright\|rboatright]] 06:19, 31 January 2010 (UTC)
		+
		+	---
		+
		+	I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet\|Egaudet]] 08:34, 31 January 2010 (UTC)

	==== PuffTheMagic v3 ====		==== PuffTheMagic v3 ====

@@ Line 18: / Line 18: @@
+}
 </pre>
 ==== PuffTheMagic v3 ====