Am Sonntag, den 02.12.2007, 21:18 +0100 schrieb Marco van de Voort:
> > I'm trying to use the unit located inn
> >
> > fpc-2.0.4/fcl/xml/dom.pp
> >
> > to parse files starting like this (shortened):
> >
> >
> > > OfficeDocument ...
> > http://openoffice.org/2000/office"; ...
> >
> > OpenOff
> I'm trying to use the unit located inn
>
> fpc-2.0.4/fcl/xml/dom.pp
>
> to parse files starting like this (shortened):
>
>
> ...
> http://openoffice.org/2000/office"; ...
>
> OpenOffice.org 1.1.3 (FreeBSD)
> ...
>
> but the second line naming the document type makes the parser throw an
>
Hi,
I'm trying to use the unit located inn
fpc-2.0.4/fcl/xml/dom.pp
to parse files starting like this (shortened):
http://openoffice.org/2000/office"; ...
OpenOffice.org 1.1.3 (FreeBSD)
...
but the second line naming the document type makes the parser throw an
exception.
Is this an implem
On Sun, 2 Dec 2007 17:25:16 +0100 (CET)
Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> But I don't see how CHM is better than PDF. PDF offers all that CHM
> offers, plus well-formatted printed output.
In my case, I have the impression that CHM is much lighter than PDF
(which is logical consider
Michael Van Canneyt schreef:
On Sun, 2 Dec 2007, Bisma Jayadi wrote:
Can we have fpc's doc in chm format? It's easier to navigate and search
compare to other formats. :)
The reference material: If you complete the chm backend of fpdoc, yes.
The manuals: definitely out.
I once made a chm f
The reference material: If you complete the chm backend of fpdoc, yes.
The manuals: definitely out.
Actually, the HTML is all fine. I just don't like to always back and forth
between TOC and the content due its single page nature. It'd be better if
the layout is change to 2 page/frame. Left fr
On Sun, 2 Dec 2007, Bisma Jayadi wrote:
> Can we have fpc's doc in chm format? It's easier to navigate and search
> compare to other formats. :)
The reference material: If you complete the chm backend of fpdoc, yes.
The manuals: definitely out.
But I don't see how CHM is better than PDF. PDF o
Can we have fpc's doc in chm format? It's easier to navigate and search
compare to other formats. :)
-Bee-
has Bee.ography at:
http://beeography.wordpress.com
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mail
>>Then when I do compile, and see nothing happen, the "about" box
says:
Lightweight IDE: 0.2.9
FPC (Intel): Failed!
FPC (PPC): 2.2.0
GCC: powerpc-apple-Darwin8-gcc-4.0.1(GCC)
TransSkel: 4.0a1
Looks perfect! (As long as you don't need to compile for Intel.)
/Ingemar>>
That's fine, but I
Edward Kearns wrote:
First of all, note that LWP 0.2.9's demo is TransSkel.p, not
NewSkel.p, as in the Lightweight Pascal IDE notes.
Yes, that was my fault. I only included the newest demos, but NewSkel.p
should have been included all the same, since it is the example demo.
TransSkel is s
On Saturday 01 December 2007 12:28:21 pm [EMAIL PROTECTED] wrote:
> 6) Rebuild Lazarus without sucess... :(
in point 5 you succesfully got a libqt4intf.so ?. Great.
So the rest is just compiling lazarus.
cd lazarus
make LCL_PLATFORM=qt clean all OPT=dUSE_QT_4_3
and look at output
The option U
I'm interested, but I don't know the correct steps to do the libqt4intf... I
do:
1) Copy Qt4 sources to my home directory;
2) Build Qt4;
3) Copy the compile_lib.bash to compile_lib_fbsd.sh and change it to use my
Qt4 (in my home directory)
4) Run compile_libfbsd.sh
5) Put the libqt4intf.so in
12 matches
Mail list logo
