[lazarus] A Little Cleanup

[michael at tfdec1.fys.kuleuven.ac.be]

On Sat, 24 Jul 1999, Curtis White wrote:

> 
> On 25-Jul-99 Michael A. Hess wrote:
> > 
> > I vote that they stay as tips. As you indicated that is what they are
> > called in GTK and I believe QT. I also know that that is what they are
> > called in many Windows add-on tools for VB and Delphi and whatever. I
> > think that Delphi is the only thing that calls them hints. To me a hint
> > sounds like I am cheating. What it really is doing is tipping you off to
> > what the tool can do.
> > 
> 
> I agree with Michael here if we aren't trying to be Delphi compatible. ToolTip
> is a much better (more accurate) name for it.

I think you should anyway try to be much more Delphi compatible. 

Experience with the compiler shows that this is what people expect.
90% of all users (if not more) says 'Hey, I have some TP or Delphi 
code, why won't it compile with FPC ?'

With the advent of 'Delphi for Linux' this situation is NOT going to 
improve; in fact I expect it to worsen a lot.

You may or may not like it; but this is a fact. So I would nevertheless 
opt for a large degree of delphi compatibility; definitely where the 
basic components are concerned, and low-level stuff as hints;

In the worst case, you just declare 2 properties; 'hint' and 'tip' they're
technically only aliases, so your code doesn't get heavier.

Don't think that I want you to make an exact Delphi clone; 
I'm just sharing my experiences here.

On the other hand; you will need to make a dfm2lfm tool anyway for the
very same reasons; you could make that tool 'property - aware' in the
sense that it could make a translation of well-known Delphi properties
to lazarus properties.

Just my thoughts.

Michael.