Having references to the stylesheet in 'usersguide' means that the 'db' javahelp is dependent on another module. For
NetBeans Platform applications such as Instant JChem, which make use of the 'db' module's JavaHelp without any other
JavaHelp in the IDE, this is a problem. Would be much better of this module was self-contained, i.e., the CSS references
should point to a stylesheet within the 'db' module, not to a stylesheet in the 'usersguide' module, even though this
means having two stylesheets with the same content, one in 'usersguide' and one in 'db'.
Actually would be even better to be able to set a CSS in the application, instead of in the module. That would require
modules in NetBeans IDE to do the same: i.e., they should not have hardcoded references to a CSS within a module (not in
another module and not within its own module) but to a CSS that's outside the module, within an application-wide folder.
I would vote for having the option to specify a single stylesheet that could be used in java help in all modules of a nb
platform based app.
This is presumably a build issue, as it applies to any module?
Of course I would expect there might be a need for each module to define its own stylesheet that override the default,
but that would be less common.
resetting priority. I don't think a broken css reference counts as a P2 where a feature doesn't work - http://wiki.netbeans.org/BugPriorityGuidelines; ideally,
we should have a place for the css that is independent of content location, but I don't think the current type of scenario (where one help is reused but
usersguide help isn't) is one that is that common. So, a general solution, which would have its own side effects might be over-architecting. I suggest merely
copying the ide.css into the db module and updating the references in the help topic
Regarding a more generalized solution, it might make sense to file a separate issue (core/help system) and cc me. I'm suggesting the quick fix to the db
module so that Tim can have a fix without having to wait for architecture debates to conclude
In addition to this, all direct references to "NetBeans" need to be removed from the "db" helpset. Even within its own
frame of reference (i.e., assuming that "db" module isn't being reused at all) the title "Using MySQL with the NetBeans
IDE" should actually be "Connecting to a MySQL Database", when you look at the screenshot below:
As a result of the above, the "db" module can't be reused within other applications at all right now.
When I wrote "direct references to NetBeans", what I meant was: "the word NetBeans should not need to be mentioned at
all in the "db" module, especially not as prominently as in the help topic that I referenced".
I disagree that the topics should be "Connecting to a MySQL Database." Only a small part of the topic is about
connecting. The topic covers administration and creation of a database too.
Well, whatever it ends up being called, please don't use "NetBeans IDE" anywhere. I believe, but could be wrong, that
that is standard policy.
I have removed direct references to NetBeans from the database topics and TOC.
Geertjan: please do not copy ide.css to other modules. If you wish to make some modules' help sets independent of the
usersguide module, the proper approach is to create a new module containing nothing but ide.css, then make usersguide as
well as other modules with help sets depend on it.
Makes sense. So long as that module really contains nothing other than 'ide.css', so that it can be reused by modules in
Changing the status of the issue: from defect to enhancement.
The discussion outcome is that there should be a separate single module that would contain only the ide.css file. This is a request for enhancement, not a defect.
We need to take a look at this post-6.8 FCS
Can you please take a look and evaluate whether your suggestion is still needed?
The DB javahelp has been reworked by James to make it as much database-type-agnostic as possible. Is the issue resolved or there is still the need to create a separate module with only ide.css ?
Closing the issue, as no clarification as to whether it should be kept open has been made. From the docs side, the db javahelp has been reworked.
If needed, please reopen.