MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> 2. Calling the "programmers manual" from the FLUID GUI (via
>> Help...) fails as it is looking for a file "main.html"; but
>> there is only "index.html". I think fluid should look for "index.html"
>
> This is being discussed in another thread, but it seems that there are
> two entry points for the docs; "index.html" uses frames whilst
> "main.html" does not, though they provide the same material. The fltk
> help viewer can not handle frames, so the correct entry point for the
> docs, so far as fluid is concerned, should be "main.html".
> That said, the fltk help viewer does not make all that good a job of
> displaying the more complex html that doxygen creates, so the rendering
> of the docs is less than ideal.
> You may do a lot better viewing the docs in a full browser in that case.
I'd suggest in the case of FLUID's 'Help' it should probably
test to see if the local index.html file exists:
* If it does, call fl_open_uri() to open it.
* If it doesn't, call fl_open_uri() to open the website docs
instead.
This is what I do in my own app's help, and it seems to work well.
Always shows the user what they want to see. It just means the docs
on the website have to not move around ;)
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
