On 01.09.2011 20:27, Jonas Maebe wrote:
On 01 Sep 2011, at 00:02, Jonas Maebe wrote:
On 31 Aug 2011, at 23:13, Sven Barth wrote:
On 31.08.2011 22:59, Jonas Maebe wrote:
I'll do a testsuite run to see whether I introduced any bugs in the string
handling, but to test the Android stuff you c
On 01 Sep 2011, at 00:02, Jonas Maebe wrote:
> On 31 Aug 2011, at 23:13, Sven Barth wrote:
>
>> On 31.08.2011 22:59, Jonas Maebe wrote:
>>>
>>> I'll do a testsuite run to see whether I introduced any bugs in the string
>>> handling, but to test the Android stuff you can also use a compiler
>>
On 01 Sep 2011, at 19:21, Alexander Klenin wrote:
> On Fri, Sep 2, 2011 at 03:50, Jonas Maebe wrote:
>>
>> On 01 Sep 2011, at 18:42, Alexander Klenin wrote:
>>
>>> This leaves the first point, however. Why is it prohibited at all?
>>
>> I think because class properties have several limitation
On Fri, Sep 2, 2011 at 03:50, Jonas Maebe wrote:
>
> On 01 Sep 2011, at 18:42, Alexander Klenin wrote:
>
>> This leaves the first point, however. Why is it prohibited at all?
>
> I think because class properties have several limitations that normal
> properties do not have:
> http://docwiki.emba
On 01 Sep 2011, at 18:42, Alexander Klenin wrote:
> This leaves the first point, however. Why is it prohibited at all?
I think because class properties have several limitations that normal
properties do not have:
http://docwiki.embarcadero.com/RADStudio/en/Properties#Class_Properties
Jonas__
On Fri, Sep 2, 2011 at 03:01, Florian Klaempfl wrote:
> Am 01.09.2011 17:48, schrieb Alexander Klenin:
>> First, I do not see a reason why normal property can not be
>> implemented by static field.
>> Second, even is such a reason is provided, compiler should error out
>> instead of generating bog
On 01 Sep 2011, at 18:01, Florian Klaempfl wrote:
> Am 01.09.2011 17:48, schrieb Alexander Klenin:
>> [Is there any method to either comment on or re-open resolved isses?
>> It is very frustrating to be forced to switch comminication channel]
Only the submitter and people with "developer" access
michael.vancann...@wisa.be schrieb:
I changed the text to:
If you only want to generate the RTL and FCL reference documentation
in HTML format, starting from the fpdoc XML descriptions, then the
following 2 commands should be enough:
$ make rtl.chk
$ make fcl.chk
Fine.
The prerequisite
Am 01.09.2011 17:48, schrieb Alexander Klenin:
> [Is there any method to either comment on or re-open resolved isses?
> It is very frustrating to be forced to switch comminication channel]
>
> I think this issue is resolved prematurely.
> First, I do not see a reason why normal property can not be
[Is there any method to either comment on or re-open resolved isses?
It is very frustrating to be forced to switch comminication channel]
I think this issue is resolved prematurely.
First, I do not see a reason why normal property can not be
implemented by static field.
Second, even is such a reas
On Thu, September 1, 2011 14:37, Graeme Geldenhuys wrote:
> On 01/09/2011, Tomas Hajny wrote:
>> mind would be skipping the '$' sign at the beginning (as that is
>> specific
>
> That is simply a "generic term/symbol" to indicate that what follows
> should be typed in at a command prompt. We can't u
On Thu, 1 Sep 2011, Hans-Peter Diettrich wrote:
Tomas Hajny schrieb:
I'm having difficulties understanding how the text can be misunderstood:
--
If you only want the html reference documentation (fpdoc format), type
What'
Tomas Hajny schrieb:
I'm having difficulties understanding how the text can be misunderstood:
--
If you only want the html reference documentation (fpdoc format), type
What's this "fpdoc format", and what's "html reference do
On 01/09/2011, Tomas Hajny wrote:
>
> Graeme, have you managed to move forward with supporting INF files
> requiring multi-panel views (as used in files from IBM) as discussed some
> time ago?
Yes, I have a offline branch that works somewhat with that. The
implementation is not very good because f
On 01/09/2011, Tomas Hajny wrote:
> mind would be skipping the '$' sign at the beginning (as that is specific
That is simply a "generic term/symbol" to indicate that what follows
should be typed in at a command prompt. We can't use bold or italics
or a different font, as is used in other types of
On Thu, September 1, 2011 13:05, michael.vancann...@wisa.be wrote:
> On Thu, 1 Sep 2011, Hans-Peter Diettrich wrote:
>> michael.vancann...@wisa.be schrieb:
>>
>>> There is a file called README.DOCS in the documentation directory.
.
.
>>> Idealists as we are in the open source community, we assume
On Thu, 1 Sep 2011, Marco van de Voort wrote:
In our previous episode, michael.vancann...@wisa.be said:
No, you are not silly - you only read your docs in your own context and
background, not how a user will read and understand it :-(
I'm having difficulties understanding how the text can
On Thu, September 1, 2011 13:23, Graeme Geldenhuys wrote:
> On 01/09/2011, Hans-Peter Diettrich wrote:
>>
>> This won't help the users of the fpdoc generated files. There exists no
>> "right" tool for everything and everybody, e.g. I'd prefer the old
>> WinHelp where I can add annotations to every
In our previous episode, michael.vancann...@wisa.be said:
> >
> > No, you are not silly - you only read your docs in your own context and
> > background, not how a user will read and understand it :-(
>
> I'm having difficulties understanding how the text can be misunderstood:
>
> --
On 01/09/2011, Hans-Peter Diettrich wrote:
>
> This won't help the users of the fpdoc generated files. There exists no
> "right" tool for everything and everybody, e.g. I'd prefer the old
> WinHelp where I can add annotations to every entry.
The latest DocView (in the fpGUI repository) supports i
On Thu, 1 Sep 2011, Hans-Peter Diettrich wrote:
michael.vancann...@wisa.be schrieb:
There is a file called README.DOCS in the documentation directory.
I've read this and many other docs :-)
It contains the answers to your questions. Especially line 19 and
following.
Idealists as we are
michael.vancann...@wisa.be schrieb:
There is a file called README.DOCS in the documentation directory.
I've read this and many other docs :-)
It contains the answers to your questions. Especially line 19 and
following.
Idealists as we are in the open source community, we assume that people
Graeme Geldenhuys schrieb:
On 01/09/2011, Graeme Geldenhuys wrote:
If you only want to generate HTML of the Class Documentation (RTL,
FCL) then a LaTeX executable is NOT needed. To do this, run the
following make command:
$ make rtl.chk
$ make fcl.chk
Here is a more complete command
Graeme Geldenhuys schrieb:
On 01/09/2011, Hans-Peter Diettrich wrote:
$make html [you snipped this essential detail]
Ah, I see the problem now... :)
That was my conclusion as well, but why should any *Latex* tools be
called for generating *HTML* output???
Because you are trying to create
On 01/09/2011, Hans-Peter Diettrich wrote:
> BTW, it would be very nice to have the class members sorted
> alphabetically, regardless of their type or arrangement in the class
> declaration. It's very hard to find Duplicates in the TStringList
> description :-(
Use the right tool for the job. :-
2011/9/1 Graeme Geldenhuys :
> Hi,
>
> I just looked at the FPC Wiki's Special:Version page. The FPC wiki is
> still using MediaWiki 1.9, and MediaWiki is already at 1.17. The
> latter contains a lot more improvements and fixes.
>
> Any chance of somebody updating the FPC wiki to the latest MediaWi
On Thu, 1 Sep 2011, Hans-Peter Diettrich wrote:
Graeme Geldenhuys schrieb:
On 31/08/2011, Hans-Peter Diettrich wrote:
$make html [you snipped this essential detail]
...
process_begin: CreateProcess((null), latex user.tex, ...) failed.
make (e=2): Das System kann die angegebene Datei nicht
On 01/09/2011, Graeme Geldenhuys wrote:
> If you only want to generate HTML of the Class Documentation (RTL,
> FCL) then a LaTeX executable is NOT needed. To do this, run the
> following make command:
>
> $ make rtl.chk
> $ make fcl.chk
Here is a more complete command - which I normally u
Hi,
I just looked at the FPC Wiki's Special:Version page. The FPC wiki is
still using MediaWiki 1.9, and MediaWiki is already at 1.17. The
latter contains a lot more improvements and fixes.
Any chance of somebody updating the FPC wiki to the latest MediaWiki version?
--
Regards,
- Graeme -
On 01/09/2011, Hans-Peter Diettrich wrote:
>
> $make html [you snipped this essential detail]
Ah, I see the problem now... :)
> That was my conclusion as well, but why should any *Latex* tools be
> called for generating *HTML* output???
Because you are trying to create HTML docs for the Langua
Graeme Geldenhuys schrieb:
On 31/08/2011, Hans-Peter Diettrich wrote:
$make html [you snipped this essential detail]
...
process_begin: CreateProcess((null), latex user.tex, ...) failed.
make (e=2): Das System kann die angegebene Datei nicht finden.
I have never tried to build the FPC docum
michael.vancann...@wisa.be schrieb:
For example
http://www.freepascal.org/docs-html/rtl/classes/tfilestream.create.html
In fact a bad example, because the option is not an enumerated type but
simple constants.
Nonetheless this one comes close to my expectations.
It e.g. explains why the met
Am 01.09.2011 06:54, schrieb Max Vlasov:
On Thu, Sep 1, 2011 at 1:13 AM, Sven Barth wrote:
I'll try to improve the unit names of the android unit and its dependencies
a bit and then it might become the first package for FPC-JVM ;)
Sven, thanks for your tests. Adding hwfpo (Hello World From
Am 01.09.2011 00:02, schrieb Jonas Maebe:
I'll try to improve the unit names of the android unit and its dependencies a
bit and then it might become the first package for FPC-JVM ;)
Great! Note that using the jdk15 unit in the android unit is not a good idea,
since it probably also exports JD
34 matches
Mail list logo
