Brant Langer Gurganus wrote:
* Mainly for Ian, can id's on any element be used instead of name'sYou mean IDs in the HTML? Can you give me a for instance? Pointing to A NAME in the HTML is a pretty efficient way to get things done right now, but I'm all ears about a way to improve this, because we _do_ have some problems setting the location in the content.
on the a element to identify destinations for contents and such.
The main reason is the name is lingering toward deprecation and it
also causes some weird scrolling issues where half of a line is
showing.
* Since a possible future move for the Mozilla Suite is to make eachThis is possible now. The file mozillahelp.rdf [link] takes a list of content and index files that are composed together. Currently, for example, we have one index file that simply lists the top-level letters under which the stuff is alphabetized and another one that contains all the entries themselves. But we could have help-indexAZ.rdf, help-indexMAIL.rdf, help-indexBROWSE.rdf given as datasources, and in fact I have been encouraging us to do so on the commercial side.
part individually installable, should I try to separate things
along product lines so that it will be ready when the time comes?
In addition, could it even be possible to create separate packages
which composite together in Contents, Index, etc? I think this
would be possible with some tweaking.
I would love to see help for these features included. I don't think that the user help should go away, but a top-level thing like "Developer Tools" where things like this could sit would be great.
* Given that Mozilla is more of a developer-centered product, how
user-centered does the Help need to be and should things like
Chatzilla, DOM Inspector, etc. be included?
Test.xul, you mean? Prolly not. I will pull it out of the build.
* I'll let you know any other questions as I encounter them.
By the way Ian, I found text.xul in help.jar which probably shouldn't be
there.
