On 12/05/06, Micha Nelissen <[EMAIL PROTECTED]> wrote:
Graeme Geldenhuys wrote:
> I think this is quite a elegant solution for application help and can
> even be applied to the LCL and FCL documentation which is currently
> stored in XML.
Sure there are a lot of elegant solutions, but who is going to write it
? Let's be realistic here. For CHM we already have a decoder and viewer,
I started with a prototype already... well more like putting some ideas to code.
A good help framework in the LCL is also important. Felipe mentioned
some ideas, and Mattias has implemented something already for Lazarus,
so I need to look at that as well, so see how flexible it is. Can you
used that for applications written with Lazarus, or was that for
Lazarus alone.
for the .jar way we need multiple decoders and translators AFAICS (jar,
xhp, css, xslt, more?) still to be implemented. Again, if anyone wants
* xhp is just XML and as for an example, LCL and FPC help already
comes in xml format.
* css can be added at a later stage, or a very basic style sheet could
be added for a start. All of 5 minutes work.
* xslt might take a bit longer, but looking at what fpdoc does to
convert the XML to HTML (as it currently does) should give a good
starting point. Also, I will be taking a look at what OOo did, and
maybe just massage their Translation Style Sheet to fit our needs.
* As for the HTML viewer component? Any suggestions? Do any support basic CSS?
to write all this, nothing is stopping you, but CHM seems like a faster
& more productive route ATM, if the coder doesn't care anyway.
Brings me back to the same old question everybody seems to avoid
answering. May we use the CHM format - is it proprietary/patented by
Microsoft?
Regards,
- Graeme -
--
There's no place like 127.0.0.1
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
