Hi Valeri, as Rene pointed out, there will be both .html and .root. The root file contains objects - storing those in html introduces an overhead that's not worth it. So instead of creating the application around a data format, there will be a data format that suits the application. Browsers read html, root reads root files. The root file will not replace the html doc; there will be an additional online help. Both output formats - html files and the online html help (and any other, non-html formats that people implement) - are generated from the objects stored in the root file. Cheers, Axel. > Hello Rene, > > Some question inspired by this discussion. > >> We intend to use this class to browse any html document and in >> particular >> the ROOT documentation itself that will be available in super compressed >> form in $ROOTSYS/etc/help.root. > > > Why do you want to save it in the very "root" format? > With the plain HTML one could have used it with and with no ROOT. > > Are you going to repeat the Microsoft approach? > They indeed had the own binary format for HELP files but then . . . > > The HTML text file can be zipped just one care about the file size. For > example, > Window XP can read transparently the files within ZIP archive without > bothering > the user to uncompress it first. ROOT can do that also. I mean, instead > of > reading the ROOT file with the help information; ROOT can unzip the text > file with > the HTML inside. > > By the way, it would have made it fully compatible with the corresponding > Qt text > widgets. > > As result, our Qt users will enjoy this format with no extra effort also. > > Just my 2 cents. > > > Hope this helps, Valeri > > >> >> Hi Thomas, >> >> Good that you ask this question! >> >> We are just about to introduce a new class TGHtml. >> We intend to use this class to browse any html document and in >> particular >> the ROOT documentation itself that will be available in super compressed >> form in $ROOTSYS/etc/help.root. >> Axel Naumann is working on a modification of THtml that will generate >> help.root >> file automatically (or any user classes). >> The idea that you should be able to get quickly the help from the >> browser, >> the command line, the pad, etc. >> >> The TGHtml class could be used to browse any kind of document. One could >> even >> imagine that stdout from ROOT could be automatically hyperlinked with >> this >> class. >> >> TGHtml will be introduced in CVS before the production release in >> December. >> The adaptation to the ROOT help system is scheduled for the first >> quarter of >> next year. >> >> Rene Brun >> >> Thomas Bretz wrote: >> > >> > Dear all, >> > >> > I have a suggestion: >> > It would be nice if there would be an option in the context menu of a >> > class drawn to a pad (eg TH1F in a canvas) to show the class >> description >> > as plain text on the console. I don't know how a implementation could >> > look like without storing the whole class description in the >> executable >> > and without starting a browser. Maybe it is possible to compile the >> > class description text into a root file which can be opened by the >> user. >> > If such a 'docu' file is open the corresponding help-entry appears in >> > the context menus. Through the TBrowser now all class descriptions >> would >> > be acessible. This gives an easy interface to an online-help in >> programs. >> > >> > What do you think? >> > >> > Best regards, >> > Thomas. > > >
This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:10 MET