[Lazarus] When do I need a component rather than a plain object?

[Sven Barth]

Am 17.11.2010 07:36, schrieb Graeme Geldenhuys:
> Op 2010-11-16 17:31, Michael Van Canneyt het geskryf:
>>> It's similar to me not seeing the point of the various "Dialog" (file open,
>>> font select, color select etc) components on the component palette - it's
>>> equally easy using them directly in code when needed. There is no advantage
>>> of having design time support for those - in fact it just uses extra memory
>>> when you do.
>>
>> I don't agree. I use the IDE to the fullest - it is RAD after all.
>> But use cases vary.
>
>
> Just curious and a bit off-topic I guess, but is there some advantage to
> have the various dialog components dropped on a form at design time? As I
> said, I think it just takes up memory while not being used, but honestly
> can't think of a single advantage it gives.

The only advantage that I am aware of (at least in Delphi): you can 
execute the dialog from within the IDE (although I've never used it up 
until just now ^^).

Right click on the dialog -> test dialog

Regards,
SVen