Hrm, we don't pick up icons directly from there? We probably should, I'll file a bug.
In Ben's "Tips & Tricks" section at the bottom of http://www.bengoodger.com/software/mb/extensions/packaging/extensions.html
he says he's working on it.
Personally in the XPI, I'd like to see an "/icons" path for copying in icons, and a '/profile' for files that should be in the <profiledir>.
If it's a preference file, why do you need to ship a default anyway?
Because almost the entire window is comprised of any number of discreet collapsible/floatable panels. The preference file stores the default state for all the panels at each chrome URI.
Screen shot at: http://www.redbacksystems.com/projects/xulu/images/xulunew1.jpg And: http://www.redbacksystems.com/projects/mozngw/images/mozngw2.jpg
But there's an easier way to do this. Ship the default in your chrome, and parse it using the RDF system:
var rdfdatasource = rdfservice.GetDataSourceBlocking("chrome://content/myapp/defaultprefs.rdf"); rdfdatasource.QueryInterface(Components.interfaces.nsIRDFRemoteDataSource).FlushTo(mylocalfile.path);
Ok interesting I hadn't thought of copying it using this method.
Initially, we were just going to access this way, as the file is loaded
into a persistent datasource for use anyway. But I found if we loaded the rdf file into the datasource with an absolute path all worked. If we
loaded it with a chrome path our RDF observers fail - very odd. That
was the reason I gave up with the chrome URI.
Cool cheers for this.
N
_______________________________________________ Mozilla-xpcom mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-xpcom
