[Lazarus] Inserting many components on form

[Fabio Luis Girardi]

I found another way to do this: extend the TCollection and write a new
procedure Add to allow choose what's the item class the user wants
create and make a Property editor for this new Collection class, that
will call this new Add method (yes, can be more easy if the Add
procedure of the TCollection as set as virtual, but...). Finally, my
tags will be a descendant of TCollectionItem class. It isn't hard to
do, and keep the features of TCollection.

I'll start the implementation of this new idea, and post the result here.


Regards,

Fabio

2011/6/28 Hans-Peter Diettrich <DrDiettrich1 at aol.com>:
> fluisgirardi at gmail.com schrieb:
>
>> Maybe I started my components with a wrong concept. Each component,
>> represents a memory (or a set of memories) on a remote device (like a PLC)
>> that can be read and/or written. These components can be linked with edits,
>> labels, progress bars and others controls created to show/modifies/stores
>> the value of these components.
>
> I'd "virtualize" the GUI, so that not every item is represented by a
> different component. It may help to store the items in a database, instead
> of using the component streaming mechanism and resource files.
>
> It's okay to use components (i.e. controls) for the GUI, but these should be
> limited to the required representation (dialogs...) of the data items. Then
> configure the visible controls to show the data for the currently selected
> item.
>
> DoDi
>
>