Re: FPDoc or PasDoc?

Graeme Geldenhuys wrote:
> On 30/11/2007, Lee Jenkins <lee <at> datatrakpos.com> wrote:
>> Thanks guys.  It does seem a bit more work, but I've been looking at the
>> docs/wiki, etc and it looks like the IDE add-in could help, but I have no clue
>> as to how to use it!
> 
> Which IDE add-in is that?
> 
> 
>> Am I supposed to write the actual xml markup using it?  Or is it preferred to
>> use a separate XML editor?
> 
> 
> OK, I'm not sure how familiar you are with fpdoc, so I'll cover the basics.
> 
> Lets say you have no docs, just you source code.  You use the tool
> called 'makeskel' which will generate skeleton xml description files
> of each source code unit.  The xml layout is quite a flat hierachy so
> is easy to edit with a plain editor (if needed).
> 
> No to actually write the documentation (which will be in the xml
> files) you can use one of three tools.
> 
>   1. A plain editor - handy in a pinch or for quick fixes or when you
> know the fpdoc syntax.
> 
>   2. LazDoc - located in the lazarus\doceditor directory. It's a
> external tool to edit the xml files. It has many features to help you
> and toolbar buttons to insert simple syntax in the descriptions.  To
> edit a xml file you select File|Open  and select the xml file of

help: postgres on upgrading build script to do cross-builds too

For the deb cross building scripts to build for arm-wince I'm starting 
from the regular building script and just extending it to do cross building.

Applying this (slightly dodgy, in-progress) diff:

Index: create_fpc_deb.sh
===================================================================
--- create_fpc_deb.sh (revision 13066)
+++ create_fpc_deb.sh (working copy)
@@ -105,25 +105,20 @@
# architecture dependent stuff

Arch=`dpkg --print-architecture`
-if [ "$Arch" = i386 ]; then
- ppcbin=ppc386
-else
- if [ "$Arch" = amd64 ]; then
- ppcbin=ppcx64
- else
- if [ "$Arch" = powerpc ]; then
- ppcbin=ppcppc
- else
- if [ "$Arch" = sparc ]; then
- ppcbin=ppcsparc
- else
- echo "$Arch is not supported."
- exit -1
- fi
- fi
- fi

Re: Serial Comm Support Windows

Stephano schrieb:
> Jeff Steinkamp wrote:
>> I know there is a serial unit for Linux/Unix, but is there similar
>> support for serial communications for the Windows Platform?
>>
> 
> http://www.luisdigital.com/programacion/fpc/serial.pp

May I add this to the rtl?

Re: help: postgres on upgrading build script to do cross-builds too

On Sat, 01 Dec 2007 09:17:53 +0000
Sam Liddicott <sam <at> liddicott.com> wrote:

> For the deb cross building scripts to build for arm-wince I'm
> starting from the regular building script and just extending it to do
> cross building.
> 
> Applying this (slightly dodgy, in-progress) diff:
> 
> Index: create_fpc_deb.sh
> ===================================================================
> --- create_fpc_deb.sh (revision 13066)
> +++ create_fpc_deb.sh (working copy)
> @@ -105,25 +105,20 @@
> # architecture dependent stuff
> 
> Arch=`dpkg --print-architecture`
> -if [ "$Arch" = i386 ]; then
> - ppcbin=ppc386
> -else
> - if [ "$Arch" = amd64 ]; then
> - ppcbin=ppcx64
> - else
> - if [ "$Arch" = powerpc ]; then
> - ppcbin=ppcppc
> - else
> - if [ "$Arch" = sparc ]; then
> - ppcbin=ppcsparc
> - else
> - echo "$Arch is not supported."

Re: FPDoc or PasDoc?

On Fri, 30 Nov 2007, Graeme Geldenhuys wrote:

> On 30/11/2007, Michael Van Canneyt <michael <at> freepascal.org> wrote:
> >
> > Use of XML, tight documentation editor support in lazarus. Lazarus
> > now offers tooltips which it gets from the fpdoc sources.
> > And you can refer to the existing fpdoc-documented units of the
> > FCL/RTL/Lazarus.
> 
> 
> Michael is 100% correct. Those are all good points, especially the new
> tooltip/fpdoc integration in the latest Lazarus.
> 
> The downside is keeping the docs in sync with the code while
> refactoring.  It takes a bit more effort, but I much prefer the fpdoc
> output to pasdoc.  The good definitely outweighs the bad.

And, if all goes well, really soon there'll be a wysiwyg editor for fpdoc.

Michael.

Re: FPDoc or PasDoc?

On 01/12/2007, Michael Van Canneyt <michael <at> freepascal.org> wrote:
>
> And, if all goes well, really soon there'll be a wysiwyg editor for fpdoc.
>

Oh boy.... Santa read my wishlist letter!  

Regards,
  - Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

Re: App Localization

Re: help: postgres on upgrading build script to do cross-builds too

Sam Liddicott wrote:
> dbf_pgfile.pas(795,23) Error: Identifier not found "LockFile"
> dbf_pgfile.pas(809,23) Error: Identifier not found "UnlockFile"
> dbf_pgfile.pas(918) Fatal: There were 2 errors compiling module, stopping

It's impossible to lock files under windows ce? What is the API? Isn't
it a multi-tasking operation system? Anyway, locking was already
possible under DOS...

Micha

Re: App Localization

On Sat, 1 Dec 2007 11:22:31 +0100
wile64 <wile64 <at> gmail.com> wrote:

> > I'm not sure what I should do with this unit.
> > How is this related to the TTranslateString support in the IDE?
> >
> >
> As a first step to determine whether all TTranslateString a Form can
> be read as
> I also did a test with TWriter.OnWriteStringProperty.

Do you know, that the IDE already uses this to write the
TTranslateString properties to a file?
You just need to setup Project / Project Options / i18n / PO file
directory.
Then the TTranslateString properties will be extracted from the form on
every 'save' and will be automatically written to a .po file.

 
> Or find the active form in the IDE?

Mattias

Re: FPDoc or PasDoc?

On Fri, 30 Nov 2007, Graeme Geldenhuys wrote:

> On 30/11/2007, Sebastian Günther <sguenther <at> gmx.de> wrote:
> >
> > By the way, actually I'm working on a visual editor component which can
> > be used for developing a full-featured visual fpDoc editor quite easily
> > (we'll have to see wether I'll have time for this, or some other person
> > will take this job.)
> 
> 
> That sounds like something I wanted to start in fpGUI. A full featured
> visual Doc Editor - I already have a template app for it. One change I
> wanted to make to fpDoc was to allow for interchangeable description
> formats. 

I think this is a rather daunting task, the fpdoc engine is tightly
intertwined with the XML format and data structures. It might be easier
to do a preprocessing step, to convert <insert your favourite format here>
to XML as understood by fpdoc. We can integrate this preprocessing in FPDoc 
if you want.

XML has the advantage of being structured and manipulatable. 
Most wiki formats are not. 

If there is a wysiwig editor, it doesn't matter anyway what format 
is used, so it might as well be the native fpdoc format. 

Michael.