On 11.07.2013 22:22, vfclists . wrote:
Should TObject or TComponent have a Comment property?
I think they should. One for the design itself and one for describing
the usage at design or runtime.
Smalltalk has it.
Consider it a version of the Hint property but for the developer
I don't consid
Mattias Gaertner wrote:
and even then
displays a spurious " (Source)" after each comment line.
That is a hyper link to the source. For example when you install the
turbopoweripro design package the hints are HTML with clickable
links.
Ah. Couldn't that be replaced with a less-obtrusive Unico
On Fri, 12 Jul 2013 10:40:23 +
Mark Morgan Lloyd wrote:
> Michael Van Canneyt wrote:
>
> > You can put a comment in front of the object or any of its properties,
> > and the lazarus IDE will display this comment for you.
>
> Although if I recall correctly somebody was going to look at this
How do you know which object to use if the documentation isn't in a
separate, searchable file or website? Just query objects at random until
you find what you need? How do you even know what the available objects
are? Also, many people still use a lot of procedural code. Where is their
documenta
Michael Van Canneyt wrote:
You can put a comment in front of the object or any of its properties,
and the lazarus IDE will display this comment for you.
Although if I recall correctly somebody was going to look at this and do
a bit of cleaning up. For example, if a procedure is annotated with
On Fri, 12 Jul 2013, vfclists . wrote:
At the end of the day there is a deeper philosophical issue here. An IDE user
is like a spreadsheet user, he is both a developer and consumer and he
shouldn't have to revert to primitive or external tools
to customize or gain immediate functional insi
In our previous episode, vfclists . said:
> >
> At the end of the day there is a deeper philosophical issue here. An IDE
> user is like a spreadsheet user, he is both a developer and consumer and he
> shouldn't have to revert to primitive or external tools to customize or
> gain immediate functiona
On 12 July 2013 09:01, Michael Van Canneyt wrote:
>
>
> On Fri, 12 Jul 2013, vfclists . wrote:
>
>
>>
>>
>> On 12 July 2013 08:18, Michael Van Canneyt
>> wrote:
>>
>>
>> On Thu, 11 Jul 2013, vfclists . wrote:
>>
>> Should TObject or TComponent have a Comment property?
>>
>>
On Fri, 12 Jul 2013, vfclists . wrote:
On 12 July 2013 08:18, Michael Van Canneyt wrote:
On Thu, 11 Jul 2013, vfclists . wrote:
Should TObject or TComponent have a Comment property?
I think they should. One for the design itself and one for
describing the
On 12 July 2013 08:18, Michael Van Canneyt wrote:
>
>
> On Thu, 11 Jul 2013, vfclists . wrote:
>
> Should TObject or TComponent have a Comment property?
>>
>> I think they should. One for the design itself and one for describing the
>> usage at design or runtime.
>>
>
> No. It takes memory and n
On Thu, 11 Jul 2013, vfclists . wrote:
Should TObject or TComponent have a Comment property?
I think they should. One for the design itself and one for describing the usage
at design or runtime.
No.
It takes memory and needs management. Putting this in a basic class such as TComponent is
11 matches
Mail list logo
