Theme Management API - Revision history

Rboatright: 3

2010-01-31T19:00:06Z

Rboatright: put in egaudet's them_config.json stuff

2010-01-31T18:59:36Z

put in egaudet's them_config.json stuff

Egaudet at 23:11, 29 January 2010

2010-01-29T23:11:30Z

Rboatright: /* Theme Management app */ 2

2010-01-29T22:39:35Z

Theme Management app: 2

Prenos at 22:34, 29 January 2010

2010-01-29T22:34:02Z

Rboatright: 6

2010-01-29T22:20:56Z

Rboatright: /* Writing the theming css files */ 5

2010-01-29T22:11:31Z

Writing the theming css files: 5

Rboatright: 4

2010-01-29T22:10:37Z

Rboatright: 3

2010-01-29T22:03:32Z

Rboatright: 2

2010-01-29T22:00:18Z

@@ Line 25: / Line 25: @@
+   }
+}
 #: paths are relative to the folder thisTheme.

@@ Line 4: / Line 4: @@
 # Create a new theme folder in /media/internal/.themes/thisTheme/
-# Create a new themeinfo.json file in that folder which contains the following:
+# Create a new theme_config.json file in that folder which contains the following:
-#* Themename: Display name for theme
+<pre>
-#* themedesc: quoted text of html for description of theme
-#* themethumb1:  filename of thumbnail image 1 for theme
+  themename: Display name for theme
-#* themethumb2:  ditto image 2
+  themedesc: quoted text of html for description of theme
-#* themethumb3:  ditto image 3
+  app:
-#* themeauthor: author name
-#* themehome: URL of homepage for this theme
+    { com.palm.package1: { icon: relative/path/to/icon, cssFileName: relative/path/to/css },
-#* themeversion: version number
+    { com.palm.package2: { icon: relative/path/to/icon }
-# In that new folder, place a file for each image that you intend to theme.
+  },
-#: The new file must be placed in the exact same relative path as before... that is to say, if the file was previously at /usr/palm/images/1.png  then the new file must be at /media/internals/.themes/thisTheme/usr/palm/images/1.png
-#: The new file must have the same name, and be of the same type as the original file.
+  global:
-# The themer must include a file for each CSS file that he wants to theme...
-#: If the css file being overridden is an application css, it must be placed in the exact same relative path as it would have been in the application.
+    cssFileName: relative/path/to/global/css
-#:: If the original application was /usr/palm/applications/phone/stylesheets/phone.css  the theming css must be in /media/internals/.themes/thisTheme//usr/palm/applications/phone/stylesheets/phone.css
+  },
-# If you are overriding one of the palm global stylesheets they must be placed in the correct place as well.
 # In your theme override stylesheets references to your images that override the default images should refer to /var/activetheme/... not to /media/internals/.theme/mytheme
 # When your theme is chosen as the active theme, the system will symlink YOUR theme directory to /var/activetheme.

@@ Line 18: / Line 18: @@
 # The themer must include a file for each CSS file that he wants to theme...
 #: If the css file being overridden is an application css, it must be placed in the exact same relative path as it would have been in the application.
-#:: If the original application was /usr/palm/applications/phone/stylesheets/phone.css  the theming css must be in /media/internals/.themes/thisTheme//usr/palm/applications/phone/stylesheets/theme.css
+#:: If the original application was /usr/palm/applications/phone/stylesheets/phone.css  the theming css must be in /media/internals/.themes/thisTheme//usr/palm/applications/phone/stylesheets/phone.css
-#:: the theming file must ALWAYS be called "theme.css"
+# If you are overriding one of the palm global stylesheets they must be placed in the correct place as well.
 # In your theme override stylesheets references to your images that override the default images should refer to /var/activetheme/... not to /media/internals/.theme/mytheme
 # When your theme is chosen as the active theme, the system will symlink YOUR theme directory to /var/activetheme.
-A one-time patch will be made against the framework files in /user/palm/framework which will add loading themeXXX.css after each reference to XXXXX.css and which will modify launcher so that when an application is loaded,  after appname.css is loaded, theme.css will be loaded from /var/activetheme -- matching CSS classes from those files will then automatically override the previous ones from the defaults.
+A one-time patch will be made against the framework files in /user/palm/framework which will add loading /var/activetheme/<orig_path>/XXX.css after each reference to <orig_path>/XXX.css and which will modify launcher so that when an application is loaded,  after appname.css is loaded, /var/activetheme/<app_dir>appname.css will be loaded -- matching CSS classes from those files will then automatically override the previous ones from the defaults.
 ==Writing the theming css files==

@@ Line 41: / Line 41: @@
 * Upon tapping on a theme name a descriptive page (stolen from preware) comes up and displays the thumbnails and description and otherdata with an INSTALL button
 * Upon pressing install, the theme app's service symlinks /media/internal/.themes/chosenTheme to /var/activetheme
-*: '''(is a luna restart required at that point?) ''' <-- no :>

@@ Line 41: / Line 41: @@
 * Upon tapping on a theme name a descriptive page (stolen from preware) comes up and displays the thumbnails and description and otherdata with an INSTALL button
 * Upon pressing install, the theme app's service symlinks /media/internal/.themes/chosenTheme to /var/activetheme
-*: '''(is a luna restart required at that point?) '''
+*: '''(is a luna restart required at that point?) ''' <-- no :>

@@ Line 20: / Line 20: @@
 Theming css files must be "sparse" that is, they ONLY contain the classes being overridden not the entire global css file.  So, if for example you are overriding the "button_one" class in the phone application css,  your theme.css in /thisTheme would be /usr/palm/applications/phone/stylesheets/theme.css  and would contain ONE class
+<pre>
 {button_one:
     background-image: /var/activetheme/yadayadayada/1.png
+}
+</pre>
 '''NOTE NOTE NOTE -- I know that's wrong -- I'm trying to get an Idea out here ok? '''

← Older revision		Revision as of 22:10, 29 January 2010
Line 16:		Line 16:

	A one-time patch will be made against the framework files in /user/palm/framework which will add loading themeXXX.css after each reference to XXXXX.css and which will modify launcher so that when an application is loaded, after appname.css is loaded, theme.css will be loaded from /var/activetheme -- matching CSS classes from those files will then automatically override the previous ones from the defaults.		A one-time patch will be made against the framework files in /user/palm/framework which will add loading themeXXX.css after each reference to XXXXX.css and which will modify launcher so that when an application is loaded, after appname.css is loaded, theme.css will be loaded from /var/activetheme -- matching CSS classes from those files will then automatically override the previous ones from the defaults.
		+
		+	==Writing the theming css files==
		+
		+	Theming css files must be "sparse" that is, they ONLY contain the classes being overridden not the entire global css file. So, if for example you are overriding the "button_one" class in the phone application css, your theme.css in /thisTheme would be /usr/palm/applications/phone/stylesheets/theme.css and would contain ONE class
		+
		+	{button_one:
		+	background-image: /var/activetheme/yadayadayada/1.png
		+	}
		+
		+	'''NOTE NOTE NOTE -- I know that's wrong -- I'm trying to get an Idea out here ok? '''

← Older revision		Revision as of 22:03, 29 January 2010
Line 14:		Line 14:
	# In your theme override stylesheets references to your images that override the default images should refer to /var/activetheme/... not to /media/internals/.theme/mytheme		# In your theme override stylesheets references to your images that override the default images should refer to /var/activetheme/... not to /media/internals/.theme/mytheme
	# When your theme is chosen as the active theme, the system will symlink YOUR theme directory to /var/activetheme.		# When your theme is chosen as the active theme, the system will symlink YOUR theme directory to /var/activetheme.
		+
		+	A one-time patch will be made against the framework files in /user/palm/framework which will add loading themeXXX.css after each reference to XXXXX.css and which will modify launcher so that when an application is loaded, after appname.css is loaded, theme.css will be loaded from /var/activetheme -- matching CSS classes from those files will then automatically override the previous ones from the defaults.