Hi all
i was just thinking about the changes that have been added to H2 lately,
and how these will need to be described in the manual
i'm happy to update the manual of course, but i was wondering if we should
keep including the manual in H2 ?
i see 2 possible options :
1) simply remove the manual form the application and replace it with a
hyperlink to the on-line manual (note that this means that we need to put
several versions of the manual on-line : 1 for each released version of H2
+ you can only get help when you are online)
2) change the way the manual is currently included in H2 and make it
'dynamic' : add some sort of 'update manual' function + possibly an option
to let H2 check if a more recent manual is available for the version you
are using (maybe this can be a PDF version of the manual)
why ?
because this gives us more flexibility.
The manual usually is one of the last things that gets updated and
sometimes slows down the release (also translation is always later than we
would like it to be).
Taking the manual out of the application (or making it updatable) allows us
to fix errors and add new parts to the manual without having to make new
builds
any ideas ?
grtz
Thijs
--
follow me on my Audio & Linux blog <http://audio-and-linux.blogspot.com/> !
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
