(No bites on the version discussion, other than Emanuel's pro 5.0 vote on the 
bugs list, so I'm introducing a little bait into the subject line here.)

There's been some talk about dependencies and whatnot, and one of the package 
dependencies on one of the distros was khelpcenter.  That got me thinking 
about the Help menu, and how we're going to make it work.

Should we bundle the Rosegarden Handbook with the application, and refer to it 
via the help menu? If so, what browser do we use to access it?  For that 
matter, it's SGML that used to be turned into something readable through some 
mysterious process I never quite understood, and it's probably not all that 
portable as a format in terms of just pointing 
$EXTERNAL_KDE3_DOCBOOK_FORMAT_AWARE_BROWSER at it to open the file.

There is apparently already some mechanism in place for putting the thing 
online in HTML form.  What do we think about just starting with the converted 
HTML version and using that as our source going forward?  (Shelagh, I'm 
especially talking to you, since you just did all those big Docbook updates.)

What do we think about not bundling a manual at all, and putting all the 
documentation online only?  I rather like that idea myself, because we have 
traditionally managed to stay at least one step behind with a lot of the 
documentation, and version x.y releases with new documentation for features 
that were actually new in x.x.

It's a bit early to be worrying about this, but this kind of thing has been my 
bailiwick for a long time, and I figure the least I can do to pay everyone 
back for doing all the heavy code lifting I couldn't manage myself is to deal 
with all these ugly documentation details as thanks for not letting 
Rosegarden die after all, and making me apologize to Julie, in particular, 
for being such a damn pessimist, and admit formally that I was wrong.  (There 
you go, Julie.)

Of course we're completely touched in the head if we start in on any major 
documentation work until after this whole thing has had a good while longer 
to settle down.  It's OK to start thinking about how it's all going to work, 
and to get it in place, and perhaps even to do a bit of rewriting here and 
there, but NO NEW SCREENSHOTS until this has settled considerably.
-- 
D. Michael McIntyre 

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to