[EMAIL PROTECTED] writes: > contents.rdf file. There are plenty of examples around of what a simple > one should look like if our app only wants a 'content' sub-directory but > all go very quiet when we want to add skinning and locale support; How > should the contents.rdf file be modified to support these? One example > simply tells us to look at the jar file for the classic skin...all very > well but where is the full description of the structure of the > contents.rdf file, where is the syntax definition for this particular > form of RDF file? At present we are making extremely slow headway having > to sift through documents and examples for any scrap of information that > will point us in the right direction.
Hi Bob I realize you are making a point here about the lack of application developer information and not necessarily requesting information about manifests and the chrome registry, but in case you _are_ still trying to get this stuff working, I think Ramalingam Saravanan's XMLTerm extension (http://lxr.mozilla.org/seamonkey/source/extensions/xmlterm/) is a great example of getting a Mozilla application organized, registered, and installed. XMLTerm has a manifest.rdf that describes all three of the major parts of the user interface in one file (which is what the monolithic, manifest.rdf-style manifest does, as opposed to the part-specific contents.rdf files), and he has a lot of information about installatioin, bugs, building, and the application itself. The manifest is here: http://lxr.mozilla.org/seamonkey/source/extensions/xmlterm/ui/manifest.rdf Maybe we can talk about it in a couple of follow-ups? You're just right about the lack of good, whole application developer info for mozilla, though. You've made me think that a separate and largish document about the chrome registry and what it requires of you in the way of manifests and scripts would be a great thing. (And this, in turn, makes me think that I wanted to mention the flip side of the discussion about "createdoc/docnotes" we've been having in this ng and in bug 157668, and that is some way of noting requests in bugzilla for new documentation--'RFDs'--for which there are no notes or content or relevant bug(s) yet. Creating RFD bugs and keywording "createdoc" bugs might be two good, doable ways of getting lists of docs needed and docs-in-waiting together, and also assiging them to individuals.) .io -- Ian Oeschger Netscape Communications
