Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Martin Grajcar 
On Mon, Apr 4, 2016 at 5:48 PM, Ondrej Pokorny  wrote:

> On 04.04.2016 12:05, Special wrote:
>
>> BTW too: Some English words became part of german, like 'Computer' und
>> 'Button'. We don't say "Elektronische Rechenmaschine" any longer, and more
>> and more german book authors say "Button" instead of the strange
>> "Schaltfläche". Yes, I confess, I used "Schaltfläche" too in some of my
>> early books three decades ago, but now I don't.
>>
>
> I see a good progress here. The first step was using "Computer" instead of
> "Elektronische Rechenmaschine", the second step was using "Button" instead
> of "Schaltfläche". The next logical step is to teach pupils from the very
> beginning that the programmer's language is English.
>
> English is part of the compulsory education from very early classes,
> AFAIK. They definitely can understand the very limited vocabulary needed to
> write programs. The word "Close" is used in event names, after all. So I
> really don't see a gain using "SchließenButton" instead of "CloseButton".


Agreed. For everything related to programming, using Non-English words is a
non-sense as you can only lose. How could "SchließenButton" make anything
better, when you can't invoke "Fenster.Schließen" anyway?

The only case when national identifiers make sense is when they come from a
business domain. Translation of e.g. financial business terms is not
exactly something a programmer should do, so either the customer supplies
English terms or I leave them as they are.

Except for removing diacritics. This is fortunately easy for the languages
I use. I wonder what I'd do if I used a language not based on a Latin
alphabet. Then I might end up with a 賣Button.

Regards, Martin.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] FLC-PDF and LazReport

2016-04-08 Thread Jesus Reyes A. 
En Fri, 08 Apr 2016 15:10:47 -0500, Michael W. Vogel   
escribió:



Hi,

In a project I use LazReport and TlrCairoExport, cause I need  
implemented fonts and unicode support.


Is there a plan to do it or anybody working on a wrapper for the new FPC  
PDF generator or is it even somehow possible today?


Thank you

Michl



It's planned, I was testing fpPdf (or how will it be named?) with that in  
mind. But if somebody is in a hurry and wants to jump in, please say so.


Jesus Reyes A.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread 

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Giuliano Colla 



Il 08/04/2016 18:56, Jürgen Hestermann ha scritto:
> If NASA or Airbus or Boeing engineers would use that approach, I 
guess a lot of rockets, planes and whatnot would fall on our heads.

> I am glad they do not seem to have this attitude.

I am not sure that they do not have it.
I saw a report on TV about a test flight of the A380 some years ago
where technicians were wondering, why the air craft computer was
pumping fuel from one tank to the other in a certain flight situation.
It seemed they needed a lot of time to find it out.
I would have expected that the complexity was not driven to a point
where even the engineers do not fully understand what they have built.
Could be that we just had a lot of luck.


This is more about *reading* the documentation, or maybe to 
*understanding* it, which is the subsequent step, once a decent 
documentation is available.


As the complexity increases, you cannot fit in the same page all the 
relevant information, and you must rely on reader's capability of 
understanding that what is stated at page 10 may carry implications to 
what is stated on page 900. This holds true for Airbus or Boeing, and 
for Lazarus and FPC.


I'm not an expert in avionics, but from my general knowledge even I 
could have told them the reason for pumping fuel from one tank to 
another, which is to balance the weight on the wings (fuel tanks are 
located on the wings). This function must be handled by some part of 
software related to the aircraft flight attitude most likely fully 
documented, but completely apart from the section which takes care of 
pumping fuel to motors!


A very similar case occurred with one of the first Airbus of Lufthansa. 
At landing it didn't stop at the end of the runway, and ended up in a 
cabbage field.

The subsequent investigation revealed that:

 * The Airbus had a protection preventing the reverse thrust if the
   landing gear isn't touching the ground. Reverse thrust was enabled
   only when all the wheels touch the ground.
 * Lufthansa procedure, in case of crosswind, is the sideslip landing,
   meaning the right (or left) wheels of the landing gear will touch
   ground much later.
 * As a consequence, in case of strong crosswind, reverse thrust was
   enabled too late.

It would appear that someone was unable to detect the problem generated 
by two fully documented facts, until an aircraft ended up in a cabbage 
field.


This sort of things do happen even when documentation is good, so let's 
imagine what may happen if documentation is poor or missing!


Giuliano



--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] FLC-PDF and LazReport

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 21:10, Michael W. Vogel wrote:
> Is there a plan to do it or anybody working on a wrapper for the new FPC 
> PDF generator or is it even somehow possible today?

I'm pretty confident it will be possible, but I'm not working on that.

I've written a PDF export filter, using fcl-pdf, for the fpReport (Free
Pascal Reporting) project that will be released some time this year.
fpReport still needs to bake a bit longer. ;-)  There are more features
coming in fpPDF too.


Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 20:22, Michael W. Vogel wrote:
> (60mm,100mm) Times-BoldItalic: Big text at absolute position
> Languages: English: Hello, World!
> Greek: Γειά σου κόσμος

If you could copy the text out of the displayed PDF, that means I got
the ToUnicode structure correct too. Nice. I forgot to test that one. :)


> As note: If I compile with -Cr, I got a Runerror 201 in unit fpparsettf 
> on line 810.

I made a note of that, thanks.


Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 19:55, Ondrej Pokorny wrote:
> Btw. you have a typo in the Russian "Hello, word". The first word should 
> be "Здравстуйте".

Not according to Google Translate. :)

[https://translate.google.com/#auto/en/%D0%97%D0%B4%D1%80%D0%B0%D0%B2%D1%81%D1%82%D0%B2%D1%83%D0%BB%D1%82%D0%B5%20%D0%BC%D0%B8%D1%80]

Anyway, I got that text from somewhere on the Internet, and used it for
various Unicode text handling. I never really checked how accurate the
non-English text was.

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] FLC-PDF and LazReport

2016-04-08 Thread Michael W. Vogel 

Hi,

In a project I use LazReport and TlrCairoExport, cause I need 
implemented fonts and unicode support.


Is there a plan to do it or anybody working on a wrapper for the new FPC 
PDF generator or is it even somehow possible today?


Thank you

Michl

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 21:29, Graeme Geldenhuys wrote:

On 2016-04-08 20:27, Ondrej Pokorny wrote:

Correct, when I took the font from Lazarus\components\aggpas as Michael
W. Vogel did, everything looks good!

Awesome!

Just curious. What is your Windows locale set at?


Currently Czech (+Windows 10).

Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 19:55, Ondrej Pokorny wrote:
> (Still it would be fine to provide links where compatible versions of 
> the fonts can be found.)

Our internal SVN repo had such a file - albeit not 100% complete.

As Michael mentioned, the unit tests will definitely be dependent on the
exact font version. I'll make sure the README file is updated, and try
and improve the unit tests to report more sensible errors (if font
versions don't match).

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 20:27, Ondrej Pokorny wrote:
> Correct, when I took the font from Lazarus\components\aggpas as Michael 
> W. Vogel did, everything looks good!

Awesome!

Just curious. What is your Windows locale set at?

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 20:13, Michael Van Canneyt wrote:
>> > Some Vietnamese characters and box drawing characters aren't rendered on 
>> > my 
>> > system.
> That probably depends on the font, Graeme will be able to say more about it.

Sjoe, that first PDF got me worried! :-)

It does look like a DejaVu Sans font version mismatch. These open source
font files get updated regularly, and I used the latest I could find.

I'll post the exact font files I have. Size and Version. I'll also
update that README file I mentioned.

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 21:13, Michael Van Canneyt wrote:
Some Vietnamese characters and box drawing characters aren't rendered 
on my system.


That probably depends on the font, Graeme will be able to say more 
about it.


Correct, when I took the font from Lazarus\components\aggpas as Michael 
W. Vogel did, everything looks good!


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Michael W. Vogel 

Am 08.04.2016 um 20:22 schrieb Michael Van Canneyt:


Hello,

Graeme has fixed a number of errors that should hopefully solve the 
problems with
codepages;  Changes have been tested on windows/linux/bsd but on 
Windows only

with a system that has an english locale.

These changes have been committed to FPC svn. (rev 33453)

We would appreciate it if someone could test the PDF generating demo 
on a Windows with non-english locale, and report whether the first 
page of

the generated PDF looks OK.

Michael.


I've tested it too. Thank you very much for your work!

I've just copied the font FreeSans.ttf from Lazarus\components\aggpas to 
FPC\packages\fcl-pdf\examples\fonts. It looks fine (Windows 7, 64bit, 
Lazarus 1.7 r52149 FPC 3.1.1 r33453 i386-win32-win32/win64 German locale):


(60mm,100mm) Times-BoldItalic: Big text at absolute position
Languages: English: Hello, World!
Greek: Γειά σου κόσμος
Polish: Witaj świecie
Portuguese: Olá mundo
Russian: Здравствулте мир
Vietnamese: Xin chào thế giới
Box Drawing: ╠ ╣ ╦ ╩ ├ ┤ ┬ ┴
Typography: “What’s wrong?”
£17.99 vs £17·99
€17.99 vs €17·99
OK then… êçèûÎÐð£¢ß
B субботу двадцать третьего мая приезжает твоя любимая теща.


As note: If I compile with -Cr, I got a Runerror 201 in unit fpparsettf 
on line 810.



Kind regards

Michl

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Lazarus Digest, Vol 99, Issue 32

2016-04-08 Thread Juha Manninen 
On Fri, Apr 8, 2016 at 9:33 PM, Alan Corey  wrote:
> OK, I was just hoping for a sentence or paragraph to be added to the
> documentation.

Welcome to open source.
Instead of complaining here and wasting everybody's time, you could
have improved the documentation yourself and provide a patch.

You also happened to trigger Jürgen Hestermann's passion to bash
Lazarus developers with whatever excuse, but that is not your fault.
We should impose some rules for such people. From experience I know it
can escalate indefinitely. Such people feel they have right to use a
free tool and then complain about how bad service they have got and
how the developers should do more and better for serve him.

One more thing:
Copying the whole e-mail thread history in your message is bad.
Please copy only small snippets that you want to answer to or comment.

Juha

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Michael Van Canneyt 



On Fri, 8 Apr 2016, Ondrej Pokorny wrote:


On 08.04.2016 20:57, Ondrej Pokorny wrote:

Sorry, I missed the latest revision. I'll update and report back!


I updated and now SetMultiByteConversionCodePage(CP_UTF8) isn't needed. The 
files are exactly the same (=the same byte contents) as before with 
SetMultiByteConversionCodePage(CP_UTF8).


https://drive.google.com/open?id=0Bx-flYubOTroemdJWG5Pb0xCcWc


Good to hear that, this is what we were aiming for :-)



Some Vietnamese characters and box drawing characters aren't rendered on my 
system.


That probably depends on the font, Graeme will be able to say more about it.

Michael.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 20:57, Ondrej Pokorny wrote:

Sorry, I missed the latest revision. I'll update and report back!


I updated and now SetMultiByteConversionCodePage(CP_UTF8) isn't needed. 
The files are exactly the same (=the same byte contents) as before with 
SetMultiByteConversionCodePage(CP_UTF8).


https://drive.google.com/open?id=0Bx-flYubOTroemdJWG5Pb0xCcWc

Some Vietnamese characters and box drawing characters aren't rendered on 
my system.





Ondrej
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Ondrej Pokorny 

Sorry, I missed the latest revision. I'll update and report back!

Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 20:43, Michael Van Canneyt wrote:
The test program to use to generate a PDF, is however 
"examples/testfppdf.lpi"


I should maybe have mentioned that more explicitly.


No problem. Thanks :)
(Still it would be fine to provide links where compatible versions of 
the fonts can be found.)


Here you go. Win 10, Czech locale.
Original file:
https://drive.google.com/open?id=0Bx-flYubOTroenRQcTRTYTQtYVk

If I set SetMultiByteConversionCodePage(CP_UTF8):
https://drive.google.com/open?id=0Bx-flYubOTroemdJWG5Pb0xCcWc

Btw. you have a typo in the Russian "Hello, word". The first word should 
be "Здравстуйте".


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Michael Van Canneyt 



On Fri, 8 Apr 2016, Ondrej Pokorny wrote:


On 08.04.2016 20:22, Michael Van Canneyt wrote:
We would appreciate it if someone could test the PDF generating demo on a 
Windows with non-english locale, and report whether the first page of the 
generated PDF looks OK.


I am now testing it. The unittests_console.lpr test fails with:

#0 fpc_raiseexception(0x1a099a4, 0x1, 0x19f6ae0) at 
P:\software\FPC\trunk_src\rtl\inc\except.inc:158
#1 TASSERT__FAIL(0x1a099a4 '"Failed on Numtables" expected: <19> but was: 
<18>', 0x433990, 0x5beea4) at .\fcl-fpcunit\src\fpcunit.pp:564
#2 TASSERT__ASSERTTRUE(0x1a099a4 '"Failed on Numtables" expected: <19> but 
was: <18>', false, 0x433990, 0x5beea4) at .\fcl-fpcunit\src\fpcunit.pp:591
#3 TASSERT__ASSERTEQUALS(0x5c15dc 'Failed on Numtables', 19, 18, 
0x5beea4) at .\fcl-fpcunit\src\fpcunit.pp:675
#4 TTESTLIBERATIONFONT__TESTDIRECTORY_NUMTABLES() at 
fpparsettf_test.pas:421
#5 TTESTCASE__RUNTEST() at 
.\fcl-fpcunit\src\fpcunit.pp:1039
#6 TTESTCASE__RUNBARE() at 
.\fcl-fpcunit\src\fpcunit.pp:1006

#7 PROTECTTEST(0x198ab70, 0x19f9fd8) at .\fcl-fpcunit\src\fpcunit.pp:1453
#8 TTESTRESULT__RUNPROTECTED(0x198ab70, 0x4456e0 , reading variable>) at .\fcl-fpcunit\src\fpcunit.pp:1471
#9 TTESTRESULT__RUN(0x198ab70, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1462
#10 TTESTCASE__RUN(0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:996
#11 TTESTSUITE__RUNTEST(0x198ab70, 0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1318
#12 TTESTSUITE__RUN(0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1308
#13 TTESTSUITE__RUNTEST(0x196aa28, 0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1318
#14 TTESTSUITE__RUN(0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1308
#15 TTESTRUNNER__DOTESTRUN(0x196a6c8, ) at 
.\fcl-fpcunit\src\consoletestrunner.pas:179
#16 TTESTRUNNER__DORUN() at 
.\fcl-fpcunit\src\consoletestrunner.pas:429
#17 TCUSTOMAPPLICATION__RUN() at 
.\fcl-base\src\custapp.pp:343

#18 main at unittests_console.lpr:28

I downloaded all needed fonts. What am I doing wrong?


Probably the version of the font differs from what Graeme is using.
(I also have several errors because of too much font files etc, these are
known)

But those are the unit tests.

The test program to use to generate a PDF, is however "examples/testfppdf.lpi"

I should maybe have mentioned that more explicitly.

Michael.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] help writing help [was: Re: Re: Suggestion for TRadioGroup documentation]

2016-04-08 Thread Martin Frb 

On 08/04/2016 19:24, Jürgen Hestermann wrote:

Am 2016-04-08 um 18:18 schrieb Martin Frb:
Or the person reading the code with the intend of documentation, is 
more clever than this. They could report any suspicious parts, and 
clarify the intend. That way the code would be additionally be 
checked for bugs.
Bugs where the original implementer may have had a wrong 
understanding of what he was doing. In which case had the original 
coder documented it, the bug would have gone into docs.
Assuming the original coder is available for comment, then a person 
different from that coder can often write much better documentation. 
(simple because then 2 (or more) people will have though about what 
it should be)


I aggree  that this can happen.
But it requires that the reader has at least the same skills
regarding the topic of what has been coded.
How long do you think would it take to (fully) understand the code for 
VirtualTreeView?

I have already found bugs in it but never understood why they occur
because I do not understand how the whole unit is coded.
So how should I even write documentation for it?



I have maintained SynEdit for nearly a decade now. Yet there is code in 
SynEdit I never looked at, and consequently I have not understood yet. 
According to you, it is a good thing I have not tried to add any docs. 
(Actually I should delete the parts I added to the wiki)


On the other hand according to me, anyone could have investigated a 
single property, or method. To do so would not require an understanding 
of everything. Yet that person could have documented the one 
method/property.

If so then at least some parts would have docs.

On VirtualTreeView: I dont know if the Author is around, and if he 
could/would answer questions, or even proof read contributed docs. But 
if he was, then the question  "How long do you think would it take to 
(fully) understand" is just the wrong question. The question should be: 
how much time do you have? Is there a chance, that in that time you can 
document at least one property or method? If yes, well then start. If 
you get more done (now or later), then even better.


The problem is, everyone (including me) is very good at pointing out why 
someone else should do it. And everyone just keeps pointing out it needs 
to be done.
Well that is fine. Lobbying for a cause is great. But the expectations 
in that case must be set correct. Someone else may also have a reason 
not to do it.


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Lazarus Digest, Vol 99, Issue 32

2016-04-08 Thread Alan Corey 
Re: [Lazarus] Suggestion for TRadioGroup documentation

OK, I was just hoping for a sentence or paragraph to be added to the
documentation.  In HTML you group radiobuttons by giving every button
in the group the same name but different values.  I started with a
tgroupbox then went to a tradiogroupbox when it didn't work.  Still
got -1 for ItemIndex so I defined some with tstrings and got a
duplicate set, but itemindex works on those.  Aha!  But a radio button
that doesn't belong to a group isn't much different than a checkbox.

I agree with most things said about documentation except that nobody
has time to read it all.  And it can change, so you have to keep
rereading.  Being a multilingual project complicates things too.  When
I started in Linux I read (and printed) howtos, took them very
seriously.  But by the time I got around to doing what I was reading
about I found the howtos were years old and almost worthless.

I don't have my internal help working yet, and it may not be as good
as Delphi's when I do.  So I Google a lot.  Documentation that looks
like it came out of doxygen turns me off because so much of it's bad.
Good internal help may be a thing of the past.

I've seen bad documentation that looks like it was written by
fledgling technical writers and tells you obvious things. I agree, the
programmer is the ultimate reference/authority but I've had to
document projects and didn't enjoy it either.  So I think some
compromise like the newbie tech writer writes it and the programmer
checks/edits it might work.  How that works in a multilingual
environment I haven't a clue.

Really, I'm sort of trying out Lazarus again.  A year or so when I
tried it last I kept getting an error which, from Googling, I thought
came from the fact that OpenBSD basically has no working locale and
little interest in it.  So I gave up on using it.  Now I find it's
better, and when I get the error doing a "clean up and build" seems to
always get rid of it.  "Illegal character in format string" I think it
was.

On 4/8/16, lazarus-requ...@lists.lazarus.freepascal.org
 wrote:
> Send Lazarus mailing list submissions to
>   lazarus@lists.lazarus.freepascal.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>   http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
> or, via email, send a message with subject or body 'help' to
>   lazarus-requ...@lists.lazarus.freepascal.org
>
> You can reach the person managing the list at
>   lazarus-ow...@lists.lazarus.freepascal.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lazarus digest..."
>
>
> Today's Topics:
>
>1. Re: Suggestion for TRadioGroup documentation (Michael Van Canneyt)
>2. Re: *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup
>   documentation (J?rgen Hestermann)
>3. Re: Suggestion for TRadioGroup documentation (Bart)
>4. Re: *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup
>   documentation (Ondrej Pokorny)
>5. Re: Suggestion for TRadioGroup documentation (J?rgen Hestermann)
>6. Re: *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup
>   documentation (J?rgen Hestermann)
>7. Re: *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup
>   documentation (Ondrej Pokorny)
>8. Re: *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup
>   documentation (Michael Thompson)
>
>
> --
>
> Message: 1
> Date: Fri, 8 Apr 2016 17:35:46 +0200 (CEST)
> From: Michael Van Canneyt 
> Subject: Re: [Lazarus] Suggestion for TRadioGroup documentation
> To: Lazarus mailing list 
> Message-ID: 
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
>
>
> On Fri, 8 Apr 2016, Graeme Geldenhuys wrote:
>
>> On 2016-04-08 15:54, Michael Thompson wrote:
>>> To be fair, a TGroupBox gets things dropped in it, and both nomenclature
>>> and look/feel are similar.
>>
>> I fully agree. As far as I can remember, even in my Delphi days I've
>> made that mistake of dropping radiobutton controls on a TRadioGroup.
>> Bart, it's not as obvious as you think. It's learning by error, and then
>> getting used to that fact.
>
> Or maybe read the documentation ? At least in the case of early Delphis
> that
> would have helped. (can't comment on current Lazarus)
>
> Thinking that you start without reading any form of documentation is an
> attitude which I highly condemn.
>
> Unfortunately, this attitude seems typical for IT.
>
> If NASA or Airbus or Boeing engineers would use that approach,
> I guess a lot of rockets, planes and whatnot would fall on our heads.
>
> I am glad they do not seem to have this attitude.
>
> Even cars come with a manual: usually located in the glove box, because
> your average citizen manages to open that

Re: [Lazarus] PDF generator: please test

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 20:22, Michael Van Canneyt wrote:
We would appreciate it if someone could test the PDF generating demo 
on a Windows with non-english locale, and report whether the first 
page of the generated PDF looks OK.


I am now testing it. The unittests_console.lpr test fails with:

#0 fpc_raiseexception(0x1a099a4, 0x1, 0x19f6ae0) at 
P:\software\FPC\trunk_src\rtl\inc\except.inc:158
#1 TASSERT__FAIL(0x1a099a4 '"Failed on Numtables" expected: <19> but 
was: <18>', 0x433990, 0x5beea4) at .\fcl-fpcunit\src\fpcunit.pp:564
#2 TASSERT__ASSERTTRUE(0x1a099a4 '"Failed on Numtables" expected: <19> 
but was: <18>', false, 0x433990, 0x5beea4) at 
.\fcl-fpcunit\src\fpcunit.pp:591
#3 TASSERT__ASSERTEQUALS(0x5c15dc 'Failed on Numtables', 19, 18, 
0x5beea4) at .\fcl-fpcunit\src\fpcunit.pp:675
#4 TTESTLIBERATIONFONT__TESTDIRECTORY_NUMTABLES(variable>) at fpparsettf_test.pas:421
#5 TTESTCASE__RUNTEST() at 
.\fcl-fpcunit\src\fpcunit.pp:1039
#6 TTESTCASE__RUNBARE() at 
.\fcl-fpcunit\src\fpcunit.pp:1006

#7 PROTECTTEST(0x198ab70, 0x19f9fd8) at .\fcl-fpcunit\src\fpcunit.pp:1453
#8 TTESTRESULT__RUNPROTECTED(0x198ab70, 0x4456e0 , reading variable>) at .\fcl-fpcunit\src\fpcunit.pp:1471
#9 TTESTRESULT__RUN(0x198ab70, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1462
#10 TTESTCASE__RUN(0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:996
#11 TTESTSUITE__RUNTEST(0x198ab70, 0x19f9fd8, ) 
at .\fcl-fpcunit\src\fpcunit.pp:1318
#12 TTESTSUITE__RUN(0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1308
#13 TTESTSUITE__RUNTEST(0x196aa28, 0x19f9fd8, ) 
at .\fcl-fpcunit\src\fpcunit.pp:1318
#14 TTESTSUITE__RUN(0x19f9fd8, ) at 
.\fcl-fpcunit\src\fpcunit.pp:1308
#15 TTESTRUNNER__DOTESTRUN(0x196a6c8, ) at 
.\fcl-fpcunit\src\consoletestrunner.pas:179
#16 TTESTRUNNER__DORUN() at 
.\fcl-fpcunit\src\consoletestrunner.pas:429
#17 TCUSTOMAPPLICATION__RUN() at 
.\fcl-base\src\custapp.pp:343

#18 main at unittests_console.lpr:28

I downloaded all needed fonts. What am I doing wrong?

Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] PDF generator: please test

2016-04-08 Thread Michael Van Canneyt 


Hello,

Graeme has fixed a number of errors that should hopefully solve the problems 
with
codepages;  Changes have been tested on windows/linux/bsd but on Windows only
with a system that has an english locale.

These changes have been committed to FPC svn. (rev 33453)

We would appreciate it if someone could test the PDF generating demo 
on a Windows with non-english locale, and report whether the first page of

the generated PDF looks OK.

Michael.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 20:19, Jürgen Hestermann wrote:

Am 2016-04-08 um 18:54 schrieb Ondrej Pokorny:
If everybody shared your approach, there wouldn't be anything like 
FPC and Lazarus. You should change your way of thinking.


You mean I should ignore facts?


Exactly.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 18:18 schrieb Martin Frb:

Or the person reading the code with the intend of documentation, is more clever 
than this. They could report any suspicious parts, and clarify the intend. That 
way the code would be additionally be checked for bugs.
Bugs where the original implementer may have had a wrong understanding of what 
he was doing. In which case had the original coder documented it, the bug would 
have gone into docs.
Assuming the original coder is available for comment, then a person different 
from that coder can often write much better documentation. (simple because then 
2 (or more) people will have though about what it should be)


I aggree  that this can happen.
But it requires that the reader has at least the same skills
regarding the topic of what has been coded.
How long do you think would it take to (fully) understand the code for 
VirtualTreeView?
I have already found bugs in it but never understood why they occur
because I do not understand how the whole unit is coded.
So how should I even write documentation for it?


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 18:54 schrieb Ondrej Pokorny:

If everybody shared your approach, there wouldn't be anything like FPC and 
Lazarus. You should change your way of thinking.


You mean I should ignore facts?

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 19:47, Jürgen Hestermann wrote:

Am 2016-04-08 um 18:38 schrieb Ondrej Pokorny:

On 08.04.2016 19:29, Jürgen Hestermann wrote:

But in the same way as others complain here about lack of coders
I am complaining about the lack of documentation.


Feel free to reduce this lack of documentation.


If I could only.
It would take me months to understand all the code
where the documentation is missing/wrong.


If everybody shared your approach, there wouldn't be anything like FPC 
and Lazarus. You should change your way of thinking.


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 18:38 schrieb Ondrej Pokorny:

On 08.04.2016 19:29, Jürgen Hestermann wrote:

But in the same way as others complain here about lack of coders
I am complaining about the lack of documentation.


Feel free to reduce this lack of documentation.


If I could only.
It would take me months to understand all the code
where the documentation is missing/wrong.


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 18:18 schrieb Ondrej Pokorny:
> This doesn't apply to Alan's problem. We try to document important things. It's not our 
problem that "it is not enough stressed that functionality XYZ is not available on 
ZYX". We really don't have crystal balls to know what people may think is not enough 
stressed.

I was answering to your statement: "If you think the documentation is bad, check the 
code and write it."
which was an answer to me writing: "When asking for documentation here I am often 
answered: Check the code."
I thought this was in general (at least my statements were).


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 19:29, Jürgen Hestermann wrote:

But in the same way as others complain here about lack of coders
I am complaining about the lack of documentation.


Feel free to reduce this lack of documentation.

Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 19:32, Jürgen Hestermann wrote:

Am 2016-04-08 um 18:18 schrieb Ondrej Pokorny:
> This doesn't apply to Alan's problem. We try to document important 
things. It's not our problem that "it is not enough stressed that 
functionality XYZ is not available on ZYX". We really don't have 
crystal balls to know what people may think is not enough stressed.


I was answering to your statement: "If you think the documentation is 
bad, check the code and write it."
which was an answer to me writing: "When asking for documentation here 
I am often answered: Check the code."

I thought this was in general (at least my statements were).


Yes and I am answering to you in general: we do our best providing 
documentation. If you think we are not good enough, participate in 
writing documentation. What is the problem?


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 18:18 schrieb Michael Thompson:

I do agree though, we're open source.  We should all pull our own weight and 
not expect others to pick up our own slack.  It's only in a corporate 
environment that I'd insist on professionals doing the documentation.


Well, of course, nobody can be forced to do anything in open source projects.
The same applies to coding:
If nobody is willing (or not has the skills) to code for an open source project 
then it is as it is.

But in the same way as others complain here about lack of coders
I am complaining about the lack of documentation.
And IMO all discussions about what should be coded should also end in the 
question:
And who will document it?
Code without documentation is a pain.
Documentation saves a lot more time than it cost to write it.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Michael Thompson 
On 9 April 2016 at 01:10, Jürgen Hestermann 
wrote:

> That's a bad idea.
> The person who wrote the code is the only person who knows what he
> intended.
> This person has to write the documentation.
>
>
That's a bad idea :-)

Sure, *some* programmers make good documenteers, but in my experience
they're the exception, not the rule.  My own documentation skills suck.
Essentially, if you think like me you'll have no problems.  I'm very bad at
seeing the problem from other people's perspective.  And I'm too old to
change now.  I'm at the "shout louder if they didn't understand the first
time" stage of life.

I do agree though, we're open source.  We should all pull our own weight
and not expect others to pick up our own slack.  It's only in a corporate
environment that I'd insist on professionals doing the documentation.

Mike
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Martin Frb 

On 08/04/2016 18:10, Jürgen Hestermann wrote:


Not only that it would take a lot of (unneccessary) additional time to 
wade through
foreign code (while the original coder already knew this after writing 
it).
Also, every bug would become part of the documentation as it is "how 
it is coded".


Or the person reading the code with the intend of documentation, is more 
clever than this. They could report any suspicious parts, and clarify 
the intend. That way the code would be additionally be checked for bugs.


Bugs where the original implementer may have had a wrong understanding 
of what he was doing. In which case had the original coder documented 
it, the bug would have gone into docs.


Assuming the original coder is available for comment, then a person 
different from that coder can often write much better documentation. 
(simple because then 2 (or more) people will have though about what it 
should be)


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 19:10, Jürgen Hestermann wrote:

Am 2016-04-08 um 18:04 schrieb Ondrej Pokorny:

On 08.04.2016 18:56, Jürgen Hestermann wrote:

When asking for documentation here I am often answered: Check the code.


Yep. Correct. If you think the documentation is bad, check the code 
and write it. Alan, you are welcome to modify the domunentation in 
the LCL and send a patch. You can also freely update the wiki docs. 
There's no problem about it and you don't have to ask for permission.


That's a bad idea.
The person who wrote the code is the only person who knows what he 
intended.

This person has to write the documentation.

Not only that it would take a lot of (unneccessary) additional time to 
wade through
foreign code (while the original coder already knew this after writing 
it).
Also, every bug would become part of the documentation as it is "how 
it is coded".


This doesn't apply to Alan's problem. We try to document important 
things. It's not our problem that "it is not enough stressed that 
functionality XYZ is not available on ZYX". We really don't have crystal 
balls to know what people may think is not enough stressed.


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 18:04 schrieb Ondrej Pokorny:

On 08.04.2016 18:56, Jürgen Hestermann wrote:

When asking for documentation here I am often answered: Check the code.


Yep. Correct. If you think the documentation is bad, check the code and write 
it. Alan, you are welcome to modify the domunentation in the LCL and send a 
patch. You can also freely update the wiki docs. There's no problem about it 
and you don't have to ask for permission.


That's a bad idea.
The person who wrote the code is the only person who knows what he intended.
This person has to write the documentation.

Not only that it would take a lot of (unneccessary) additional time to wade 
through
foreign code (while the original coder already knew this after writing it).
Also, every bug would become part of the documentation as it is "how it is 
coded".


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 17:59 schrieb Bart:
> But even if you don't read a manual or something like that, and just
> play with the component, after just a few minutes you must have seen
> the Items property, played with it and see what it does?

But then you only *think* you know how it works.
It maybe that some conditions exist, when things behave different.
You would never know about them if you have not read it somewhere.
It could be that you just wonder why things *sometimes* crash (or whatever).



--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Ondrej Pokorny 

On 08.04.2016 18:56, Jürgen Hestermann wrote:

When asking for documentation here I am often answered: Check the code.


Yep. Correct. If you think the documentation is bad, check the code and 
write it. Alan, you are welcome to modify the domunentation in the LCL 
and send a patch. You can also freely update the wiki docs. There's no 
problem about it and you don't have to ask for permission.


Ondrej

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Bart 
On 4/8/16, Michael Van Canneyt  wrote:

> Or maybe read the documentation ? At least in the case of early Delphis
> that
> would have helped. (can't comment on current Lazarus)

Yep, before the days of Internet, when I bought my copy of Delphi2, It
had a manual.
And even the I bought books on Pascal and Dephi and pressed F1 very
often (Delphi in those days had a very good help file).

(My initial TP 3.0 only came with a reader in Hebrew, which wasn't
very helpfull since I'm Dutch)

But even if you don't read a manual or something like that, and just
play with the component, after just a few minutes you must have seen
the Items property, played with it and see what it does?

Bart

Bart

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] *** GMX Spamverdacht *** Re: Suggestion for TRadioGroup documentation

2016-04-08 Thread Jürgen Hestermann 

Am 2016-04-08 um 17:35 schrieb Michael Van Canneyt:
> Thinking that you start without reading any form of documentation is an 
attitude which I highly condemn.

I would love to read documentations but very often there is none (or even worse 
it is wrong, outdated, confusing and incomplete).
When asking for documentation here I am often answered: Check the code.


> Unfortunately, this attitude seems typical for IT.

It has evolved into this.
When I started with Turbo Pascal very excellent documentation was wide spread.
Today with fast version cycling it seems that nobody has the time for it anymore
or (even worse) not even has the knowledge about how things exactly behave.
So we are all left to use trial and error which is realy sad.


> If NASA or Airbus or Boeing engineers would use that approach, I guess a lot 
of rockets, planes and whatnot would fall on our heads.
> I am glad they do not seem to have this attitude.

I am not sure that they do not have it.
I saw a report on TV about a test flight of the A380 some years ago
where technicians were wondering, why the air craft computer was
pumping fuel from one tank to the other in a certain flight situation.
It seemed they needed a lot of time to find it out.
I would have expected that the complexity was not driven to a point
where even the engineers do not fully understand what they have built.
Could be that we just had a lot of luck.


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Michael Van Canneyt 



On Fri, 8 Apr 2016, Graeme Geldenhuys wrote:


On 2016-04-08 15:54, Michael Thompson wrote:

To be fair, a TGroupBox gets things dropped in it, and both nomenclature
and look/feel are similar.


I fully agree. As far as I can remember, even in my Delphi days I've
made that mistake of dropping radiobutton controls on a TRadioGroup.
Bart, it's not as obvious as you think. It's learning by error, and then
getting used to that fact.


Or maybe read the documentation ? At least in the case of early Delphis that
would have helped. (can't comment on current Lazarus)

Thinking that you start without reading any form of documentation is an 
attitude which I highly condemn.


Unfortunately, this attitude seems typical for IT.

If NASA or Airbus or Boeing engineers would use that approach, 
I guess a lot of rockets, planes and whatnot would fall on our heads.


I am glad they do not seem to have this attitude.

Even cars come with a manual: usually located in the glove box, because
your average citizen manages to open that without "Quick start guide".

Michael.

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 15:54, Michael Thompson wrote:
> To be fair, a TGroupBox gets things dropped in it, and both nomenclature
> and look/feel are similar.

I fully agree. As far as I can remember, even in my Delphi days I've
made that mistake of dropping radiobutton controls on a TRadioGroup.
Bart, it's not as obvious as you think. It's learning by error, and then
getting used to that fact.

Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Michael Thompson 
On 8 April 2016 at 22:42, Bart  wrote:

> This is as it has always been, and as it was even in the Delphi 3 days.
> Use the component in the way it is designed to work.
> Why you would even drop individual radiobuttons on a TRadioGroup is beyond
> me.


To be fair, a TGroupBox gets things dropped in it, and both nomenclature
and look/feel are similar.  It also feels like every few years I make the
same mistake Alan has and groan :-)

But yes, design from prehistory - certainly don't need changing.

Mike
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Bart 
On 4/8/16, Alan Corey  wrote:

.  Creating a TRadioGroup as
> a container then adding TRadioButtons to it does nothing useful,
> ItemIndex is always -1.  Change Parent doesn't seem to fix it.  It
> seems like that worked in Delphi, I rarely used string lists.
>
> To use ItemIndex you have to populate the TRadioGroup using strings.

This is as it has always been, and as it was even in the Delphi 3 days.
Use the component in the way it is designed to work.
Why you would even drop individual radiobuttons on a TRadioGroup is beyond me.

Bart

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] Suggestion for TRadioGroup documentation

2016-04-08 Thread Alan Corey 
I don't think the existing documentation stresses the point enough
that if you use individual TRadioButtons you won't be able to use
ItemIndex to find out which one is checked.  Creating a TRadioGroup as
a container then adding TRadioButtons to it does nothing useful,
ItemIndex is always -1.  Change Parent doesn't seem to fix it.  It
seems like that worked in Delphi, I rarely used string lists.

To use ItemIndex you have to populate the TRadioGroup using strings.
I haven't found out yet whether the strings can be changed under
program control, but I was building a context-sensitive menu, planning
on changing the captions on the buttons to suit the context

New to the list, I've got a resume at
http://devio.us/~ab1jx/files/resume.pdf  I used mostly Delphi 3 from
when it first fascinated me about 1998 through the end of my last job
in 2009.  Turbo Pascal before that, VAX and Apple II Pascal before
that.  Used to tinker with Oberon Native.  I spend most of my time in
OpenBSD lately so I've been writing C for the last 6-7 years.  Delphi
was the thing I missed most about Windows.

  Alan
-- 
Credit is the root of all evil.  - AB1JX

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 13:02, Zeljko wrote:
> I don't see such empty emails. Where do they come ?

I see them too. They come from the list address.

Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Cant compile the IDE with the most recent fpc (3.1.1)

2016-04-08 Thread Michael Schnell 

On 04/08/2016 02:22 PM, Sven Barth wrote:


It should either be in /etc/fpc.cfg or ~/.fpc.cfg


there is one in /etc/fpc.cfg

it's rather long but it does include the lines

-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/*
-Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/httpd22



i.e. without the /local".

in fact in /usr/lib I do have /usr/lib/fpc/3.1.1/units/i386-linux/


"fpc" comes up with

Free Pascal Compiler version 3.1.1 [2016/04/05] for i386

so  $fpcversion = 3.1.1 and   $fpctarget  =  i386-linux might be correct.





*Later:**
**
**deleting a seemingly broken ~/.fpc.cfg file **did the trick. **
**
**Thanks a lot for your help!**
*

-Michael
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Cant compile the IDE with the most recent fpc (3.1.1)

2016-04-08 Thread Sven Barth 
Am 08.04.2016 13:12 schrieb "Michael Schnell" :
>
> On 04/07/2016 04:33 PM, Mattias Gaertner wrote:
>>
>> On Thu, 07 Apr 2016 16:25:26 +0200
>> Michael Schnell  wrote:
>>
>>> On 04/07/2016 04:19 PM, Mattias Gaertner wrote:

 What -Fu paths do you have in your fpc.cfg?
>>>
>>> I did suppose something like this.
>>>
>>> Am I supposed to manually edit this file even for the unmodified svn
d/l ?
>>
>> FPC does not care where the sources are coming from.
>> You need a valid fpc.cfg, usually /etc/fpc.cfg .
>>
> I do have this.
>
> Here multiple times $fpcversion and $fpctarget are used which supposedly
are provided by the compiler.
>
> Can it be that the compiler uses wrong values for those ?
>
> How can I check that ? (I did
>
> make FPC=`pwd`/compiler/ppc386 install INSTALL_PREFIX=/usr
>
> and hoped that would provide for this, and I suppose it did some time
ago, as )
>

Would you please test whether your installed trunk compiler works correctly
(e.g. by compiling a simple helloworld program)? Maybe also add -vi if
necessary so that the compiler will print its version information while
compiling.

Regards,
Sven
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Cant compile the IDE with the most recent fpc (3.1.1)

2016-04-08 Thread Sven Barth 
Am 08.04.2016 13:29 schrieb "Michael Schnell" :
>
> On 04/07/2016 04:30 PM, Michael Van Canneyt wrote:
>>
>>
>> I have this in my fpc.cfg, it is 2 lines long:
>
>
> In my lazarus/trunk dir (created by svn), there is no fpc.cfg file.
>
> Do you suggest it should ?

It should either be in /etc/fpc.cfg or ~/.fpc.cfg

Regards,
Sven
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Vojtěch Čihák 

IMO it is not my local problem, those mails can be found in archive too: 
http://lists.lazarus.freepascal.org/pipermail/lazarus/2016-April/thread.html
 
Vojtech
 
__

Od: Zeljko 
Komu: Lazarus mailing list 
Datum: 08.04.2016 14:01
Předmět: Re: [Lazarus] German umlauts in component names




On 04/08/2016 12:24 PM, Vojtěch Čihák wrote:

Why sometimes come these empty mails from jel...@misticnabica.hr?

Is it regular member or some bot?


I think it's hacked machine...I'll inform that ppl that they are sending 
spam. btw. I don't see such empty emails. Where do they come ? To your 
email or to list ?


zeljko

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus 


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Michael Van Canneyt 



On Fri, 8 Apr 2016, Zeljko wrote:




On 04/08/2016 12:24 PM, Vojtěch Čihák wrote:

Why sometimes come these empty mails from jel...@misticnabica.hr?

Is it regular member or some bot?


I think it's hacked machine...I'll inform that ppl that they are sending 
spam. btw. I don't see such empty emails. Where do they come ? To your 
email or to list ?


I get them too, they come through the list AFAICS.

Michael.--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Zeljko 



On 04/08/2016 12:24 PM, Vojtěch Čihák wrote:

Why sometimes come these empty mails from jel...@misticnabica.hr?

Is it regular member or some bot?


I think it's hacked machine...I'll inform that ppl that they are sending 
spam. btw. I don't see such empty emails. Where do they come ? To your 
email or to list ?


zeljko

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 12:40, Santiago A. wrote:
> I didn't know Delphi allowed to use above-127 chars for identifiers or
> component names. Since what version?

I would imagine since Unicode String support was added... So that would
be Delphi 2009.

Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Santiago A. 
El 02/04/2016 a las 10:14, Special escribió:
> How can I use names with German Umlauts and 'ß' in the Name Field of
> TButton components? For instance, I try to set MyButton.Name to
> "Schließenbutton" and get an error message "Komponentenname
> Schließenbutton ist kein gültiger Bezeichner".
>
> This happens with Lazarus 1.6 and FPC 3.0.0 under Win 10 (64) and
> under Raspian on a Pi3.
> We have many Delphi Programs with German Umlauts in component names
> and would like to go to Lazarus with them.
> Any hints?
>
> Hans

I didn't know Delphi allowed to use above-127 chars for identifiers or
component names. Since what version?

The short answer: You can't.

I would say that you needn't, component names are internal, for use in
source. Nevertheless, you can use any above-127 chars in captions, that
it is what final user sees and must be localized.

-- 
Saludos

Santi
s...@ciberpiula.net


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Cant compile the IDE with the most recent fpc (3.1.1)

2016-04-08 Thread Michael Schnell 

On 04/07/2016 04:30 PM, Michael Van Canneyt wrote:


I have this in my fpc.cfg, it is 2 lines long:


In my lazarus/trunk dir (created by svn), there is no fpc.cfg file.

Do you suggest it should ?

-Michael

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Cant compile the IDE with the most recent fpc (3.1.1)

2016-04-08 Thread Michael Schnell 

On 04/07/2016 04:33 PM, Mattias Gaertner wrote:

On Thu, 07 Apr 2016 16:25:26 +0200
Michael Schnell  wrote:


On 04/07/2016 04:19 PM, Mattias Gaertner wrote:

What -Fu paths do you have in your fpc.cfg?

I did suppose something like this.

Am I supposed to manually edit this file even for the unmodified svn d/l ?

FPC does not care where the sources are coming from.
You need a valid fpc.cfg, usually /etc/fpc.cfg .


I do have this.

Here multiple times $fpcversion and $fpctarget are used which supposedly 
are provided by the compiler.


Can it be that the compiler uses wrong values for those ?

How can I check that ? (I did

make FPC=`pwd`/compiler/ppc386 install INSTALL_PREFIX=/usr

and hoped that would provide for this, and I suppose it did some time 
ago, as )


-Michael

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Vojtěch Čihák 

Why sometimes come these empty mails from jel...@misticnabica.hr? 
 
Is it regular member or some bot?
 
V.
__

Od: "" 
Komu: 
Datum: 08.04.2016 11:31
Předmět: Re: [Lazarus] German umlauts in component names



--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus 


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Graeme Geldenhuys 
On 2016-04-08 10:29, Dennis wrote:
> procedure 賣; {means SELL}
> begin
> end;


The best code obfuscating ever! :-D


Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread 

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] German umlauts in component names

2016-04-08 Thread Dennis 



Andreas Schneider wrote:

Am 2016-04-02 14:38, schrieb Graeme Geldenhuys:

On 2016-04-02 13:16, Santiago A. wrote:

similar should be done. You would need to make compulsory a command in
source code to tell which code set is using.


As a contract programmer I already struggle working on code where
identifiers, Class names, methods, code comments etc are written in
non-English [I fully agree its their right to do so, as it is not
feasible to think everybody can speak or write English]. But adding
different character sets to the mix will massively increase that hurdle.


I used to strictly oppose non-english code as well. A colleague 
actually managed

to convince me that there are indeed reasons for "localized" identifiers:
in some projects the customers (usually with some industrial 
background) have pretty
specific wordings or use of the language. If developers now start 
introducing

their own wording (due to translating back and forth) you complicate the
communication and synchronization between business unit and 
development team.
In such special cases I now "accept" said code style. (Although I 
still don't

like it ;-))

I think those gains will be  limited in scope but the disadvantages are 
too huge for the general users.
Imagine relaxing this requirement, there will probably be new 
codes/libraries using non-english identifiers and if they become popular 
later, a lot of end users might be forced to use these non-english 
libraries.


e.g. if a hash library A uses a non-english identifier for a library to 
honour the Thai name of the scholar who invented it.

Then an encryption or communication library B uses this library A.
If this library B later becomes popular or a standard, all end users 
using B will need setup their development environment to support 
non-english identifiers, although only one of the many hash functions in 
A has non-english identifiers.


I am chinese myself. I cannot even type a Thai identifier, I will then 
have to copy and paste the identifier.  I could also easily confuse one 
Thai identifier from another one.
Imagine if I write a library with Chinese identifiers, most users won't 
able to tell apart 2 Chinese identifiers.

e.g.
procedure 賣; {means SELL}
begin
end;
procedure 買; {means BUY}
begin
end;


Can use tell them apart easily?

Dennis

___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus



--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus