Hi,
I've been working on a new help system for fpGUI and Lazarus (IDE &
apps). Attached is a screenshot of the Help Viewer I am working on.
(please ignore the floating button - it's only there for debugging)
It is showing the FPC Language Reference documentation (not fully
converted from LaTeX yet
Graeme Geldenhuys wrpte:
I've been working on a new help system for fpGUI and Lazarus (IDE &
apps). Attached is a screenshot of the Help Viewer I am working on.
What is wrong with lhelp? Please evaluate solution which lazarus will
have in the next release (0.9.30).
http://wiki.lazarus.freep
On Thu, 1 Oct 2009, Graeme Geldenhuys wrote:
Hi,
I've been working on a new help system for fpGUI and Lazarus (IDE &
apps). Attached is a screenshot of the Help Viewer I am working on.
(please ignore the floating button - it's only there for debugging)
It is showing the FPC Language Reference
2009/10/1 Michael Van Canneyt :
>
> You plan to convert the FPC docs each time something is changed ?
> I hope you have a latex->something converter program :-)
That would be stating the obvious. ;-) The new help format is a
hybrid INF format (from OS/2 INF help files). INF is an excellent
format
On Thu, 1 Oct 2009, Graeme Geldenhuys wrote:
2009/10/1 Michael Van Canneyt :
You plan to convert the FPC docs each time something is changed ?
I hope you have a latex->something converter program :-)
That would be stating the obvious. ;-) The new help format is a
hybrid INF format (from O
2009/10/1 Paul Ishenin :
>
> What is wrong with lhelp? Please evaluate solution which lazarus will have
> in the next release (0.9.30).
See my comments regarding HTML help formats...
OK, lhelp seems to have improved and now support Indexes - last time I
checked, it did not. lhelp also seems to be
2009/10/1 Paul Ishenin :
>
> What is wrong with lhelp?
Searching sucks in any CHM viewer! See attached image and associated
help content as an example. One think pro about lhelp compared to
other CHM viewers under Linux - it includes a "search" tab, even
though searching doesn't work. ;-)
Regar
2009/10/1 Michael Van Canneyt :
>
> Good. Maybe you can add a compiled INF format then as well...
I'm will be working on a Object Pascal implementation of the IPF
compiler. Currently I'm using the WIPFC complier from the the Open
Watcom v1.9 (beta) project. They implemented their own IPF compiler
2009/10/1 Paul Ishenin :
>
> What is wrong with lhelp?
Another bug I ran lhelp. Then opened the "Beyond Compare 2" CHM
help file. Browsed around a bit in the help. Then I did "File > Open"
and selected the PINs.CHM help file. The title of lhelp changed, but
the content and the tab at the bott
On Thu, Oct 01, 2009 at 11:34:45AM +0200, Graeme Geldenhuys wrote:
> > You plan to convert the FPC docs each time something is changed ?
> > I hope you have a latex->something converter program :-)
>
> That would be stating the obvious. ;-) The new help format is a
> hybrid INF format (from OS/2
On Thu, Oct 01, 2009 at 12:02:21PM +0200, Graeme Geldenhuys wrote:
>
> By the way, why did you use line drawing in the syntax format
> diagrams?
There is no drawing in the FPC source. These diagrams are written by a
package. The PDF versions should be pretty hires. The png renderings for
html are
2009/10/1 Marco van de Voort :
>
> There is no drawing in the FPC source. These diagrams are written by a
> package. The PDF versions should be pretty hires. The png renderings for
> html are bit less beautiful.
I know the syntax diagrams are not Images in the PDF. But I am simply
a pain in the bu
On Thu, 1 Oct 2009, Graeme Geldenhuys wrote:
2009/10/1 Michael Van Canneyt :
Good. Maybe you can add a compiled INF format then as well...
I'm will be working on a Object Pascal implementation of the IPF
compiler. Currently I'm using the WIPFC complier from the the Open
Watcom v1.9 (beta)
2009/10/1 Marco van de Voort :
>
> Do you have an overview of what works and what not, and practical aspects of
> the system?
How do I generate the FCL and RTL documentation in INF (actually IPF) format?
$ make rtl.chk fcl.chk
This generates the HTML output. Not what I want.
> - what the "k
Graeme Geldenhuys wrote:
> 2009/10/1 Paul Ishenin :
>> What is wrong with lhelp?
>
Thanks for the help in spotting these errors. Most of them have been
fixed in r21945.
Can you send me the chm which has the Indy License Agreement over and
over in the TOC? I would like to fix this bug.
Thanks,
Graeme Geldenhuys wrote:
> 2009/10/1 Paul Ishenin :
>> What is wrong with lhelp?
>
> Searching sucks in any CHM viewer! See attached image and associated
> help content as an example. One think pro about lhelp compared to
> other CHM viewers under Linux - it includes a "search" tab, even
> though
2009/10/1 Andrew Haines :
>
> ms help workshop a list can be specified of words not to index. likely
> "are" was in that list as well as "the" "a" etc.
I see. I tried a few other words and lhelp did seem to find things ok.
I'll start using lhelp instead of xCHM, CHMSee etc.. to help bugtest
things
2009/10/1 Marco van de Voort :
> - What is the time to load the LCL index file and merge it with the FCL and
> RTL files?
I haven't managed to generate INF files for RTL, LCL or FCL yet, but I
took 7 of the largest files from the IBM Visage C++ for OS/2 cd-rom.
Copied them to my hard drive so th
Graeme Geldenhuys wrote:
>
> See attached image for some issues I just found.
>
All of these are now fixed in r21950
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Graeme Geldenhuys wrote:
> 2009/10/1 Marco van de Voort :
>> - What is the time to load the LCL index file and merge it with the FCL and
>> RTL files?
>
> So that's not bad. :-) 0.177 milliseconds to load 10.3MB of help and
> display the TOC to the user. In total, that was 13,197 topics (pages
Andrew Haines wrote:
>
> Is the TOC sorted or are the files appended together?
Sorry I was thinking of an index not a toc
Regards,
Andrew
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/li
2009/10/1 Graeme Geldenhuys :
> ---
> $ ../src/units/helpviewer
> cppclsug.inf+cppvbref.inf+cppvbug.inf+evfeclsh.hlp+gpi3.inf+pm2.inf+pm3.inf
> Elapsed time: 000:00:00:00.177130
> ---
>
> So that's not bad. :-) 0.177 milliseconds to load 10.3MB of help and
Oops, t
2009/10/1 Andrew Haines :
>>
>> See attached image for some issues I just found.
>>
>
> All of these are now fixed in r21950
Excellent service!!! :-) Thanks, I'll get an update tomorrow.
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pa
2009/10/1 Andrew Haines :
>>
>> Is the TOC sorted or are the files appended together?
>
> Sorry I was thinking of an index not a toc
That's the users choice... It can do alphabetically (mixed helpfiles)
or grouped by help file.
--
Regards,
- Graeme -
_
On Thu, Oct 01, 2009 at 01:19:58PM +0200, Graeme Geldenhuys wrote:
> > Do you have an overview of what works and what not, and practical aspects of
> > the system?
>
> How do I generate the FCL and RTL documentation in INF (actually IPF) format?
You tell me! I'm not the IPF expert. I assumed you
On 01/10/2009, Marco van de Voort wrote:
> >
> > How do I generate the FCL and RTL documentation in INF (actually IPF)
> format?
>
> You tell me! I'm not the IPF expert. I assumed you had found some way to
> export one of the existing formats to it.
I meant with the existing Makefile in the f
2009/10/1 Marco van de Voort :
> This is roughly how CHM works too, but the efficient versions of certain
> parts are not implemented yet. Fulltext search is fine and efficient, except
> for the generation (LCL takes 4 minutes to generate)
I managed to modify the Makefile's of the RTL and FCL docu
On Fri, 2 Oct 2009, Graeme Geldenhuys wrote:
2009/10/1 Marco van de Voort :
This is roughly how CHM works too, but the efficient versions of certain
parts are not implemented yet. Fulltext search is fine and efficient, except
for the generation (LCL takes 4 minutes to generate)
I managed to
2009/10/2 Michael Van Canneyt :
>
> Till you told me what the IPF exactly is, I had no idea what it was,
> I 'inherited' fpdoc from Sebastian Guenther, and it was not documented.
:-)
I'm actually busy updating the readme file now, highlighting the new IPF
make option. Expect a patch in the fpc-dev
On Thu, Oct 01, 2009 at 09:55:55PM +0200, Graeme Geldenhuys wrote:
> > > Explain "module"?
> >
> > Bundles of help generated separately from eachother.
>
> It's possible, and I have seen INF files that do that, but I don't
> know the tag format involved. I'll search the INF Reference manual for
>
2009/10/2 Marco van de Voort :
>
> MS' help compiler is probably a lot faster too, this is the own lib.
I did not look at 'lhelp' code yet. Do you guys have your own CHM
reader library, or do you use a publicly available library like
libchm.so?
> Since as far as analogies go, LaTeX to HTML still
In our previous episode, Graeme Geldenhuys said:
(several of these msgs ended up in my suspect box due to their mime aspects)
> See my comments regarding HTML help formats...
>
> OK, lhelp seems to have improved and now support Indexes - last time I
> checked, it did not. lhelp also seems to be re
On Sun, Oct 04, 2009 at 10:07:04AM +0200, Graeme Geldenhuys wrote:
> 2009/10/2 Marco van de Voort :
> >
> > MS' help compiler is probably a lot faster too, this is the own lib.
>
> I did not look at 'lhelp' code yet. Do you guys have your own CHM
> reader library, or do you use a publicly availabl
On Thu, Oct 01, 2009 at 12:35:59PM +0200, Graeme Geldenhuys wrote:
> 2009/10/1 Marco van de Voort :
> >
> > There is no drawing in the FPC source. These diagrams are written by a
> > package. The PDF versions should be pretty hires. The png renderings for
> > html are bit less beautiful.
>
> I kno
2009/10/4 Marco van de Voort :
>
> As far as I can see, the only issue is HTML. And that is then only your
> opinion.
HTML as a help format is my issue yes. I don't believe perfectly good
help contents must be in a format that a developer can screw up beyond
recognition. HTML is so non-standard in
2009/10/4 Marco van de Voort :
>> reader library, or do you use a publicly available library like
>> libchm.so?
>
> own reader and writer.
Good.
>> As far as I know there is just one INF (IPF) tag format.
>
> Well, it is similar in the sense that the average developer has to learn it,
> contrary
2009/10/4 Marco van de Voort :
>
> So just starting with anything random new is better? It will again have its
> own flaws. And more in the beginning.
>
> If you really care so much, try to notify the synt package author, and work
> towards a solution instead of playing in fixed fonts. (knowing tha
On Mon, Oct 05, 2009 at 09:09:13AM +0200, Graeme Geldenhuys wrote:
>
> >> As far as I know there is just one INF (IPF) tag format.
> >
> > Well, it is similar in the sense that the average developer has to learn it,
> > contrary to basic HTML.
>
> And looking at some of the websites out there, it
On Mon, Oct 05, 2009 at 08:56:02AM +0200, Graeme Geldenhuys wrote:
> 2009/10/4 Marco van de Voort :
> >
> > As far as I can see, the only issue is HTML. And that is then only your
> > opinion.
>
> HTML as a help format is my issue yes. I don't believe perfectly good
> help contents must be in a fo
2009/10/5 Marco van de Voort :
> - you don't need to know _full_ html to write help, and more importantly,
> tools to help you (and other tools that export it) are plenty.
You also don't need to know full IPF tags to write help. The least
amount of tags you would need to write INF help would be 2
On Mon, Oct 05, 2009 at 10:09:00AM +0200, Graeme Geldenhuys wrote:
> I don't know other exotic help formats, so I really cannot comment.
> What I can say though, is that FPC Text IDE is a really nice "library"
> of code for reading / learning help formats. It would be a shame to
> loose that librar
2009/10/1 Marco van de Voort :
>
> This is roughly how CHM works too, but the efficient versions of certain
> parts are not implemented yet. Fulltext search is fine and efficient, except
> for the generation (LCL takes 4 minutes to generate)
I finally got the rewrite of the fpdoc IPF writer to a
42 matches
Mail list logo
