XULRunner: Difference between revisions

XULRunner (view source)

Revision as of 18:18, 11 March 2005

794 bytes added , 11 March 2005

→‎Profiles

Darin

272

edits

@@ Line 10: / Line 10: @@
 === Profiles ===
-An application running on top of the XULRunner should have a fully
+An application running on top of the XULRunner has a fully
-managed profile directory.  ("Managed" meaning that each app built
+"managed" profile directory for storing user specific data.
-on top of XULRunner should have its own <em>vendor/appname</em> directory
+XULRunner sets up the profile directory for applications
-for storing profile information.)
+automatically, and it uses the same profile locking mechanism
+used by existing applications like Firefox and Thunderbird.
-'''An application developer should not have to think too hard about profile details!'''
+The profile directory for an application is created under
-''What about sharing profile data (f.e., installed certs between xulrunnerized firefox/tbird)?  Not an uncommon request.''
+<em>vendor/appname</em> in the appropriate place on the user's
+system.  For example, under Windows this would be:
+ $USERPROFILE\Application Data\$vendor\$appname\Profiles\$random.default
+And under Unix systems it would be:
+ $HOME/.$vendor/$appname/Profiles/$random.default
+Where <code>$vendor</code> and <code>$appname</code> are chosen by the
+XUL application, and <code>$random</code> is generated by XULRunner to
+obscure the location of the user's profile data.
+The goal of this approach is to eliminate the need for the application
+developer to think about profile details.  The default configuration
+should simply work without much fuss.
+Down the road, we will want to allow XULRunner-based applications to
+participate in profile sharing.  The goal here is to allow applications
+to share data that is common to the web platform such as SSL certificate,
+cookies, and the web cache.
 === What's ''in'' XULRunner? ===