[Lazarus] fpGUI

Mattias Gaertner nc-gaertnma at netcologne.de
Sun Jan 16 15:43:53 CET 2011


On Sun, 16 Jan 2011 16:00:44 +0200
Graeme Geldenhuys <graemeg.lists at gmail.com> wrote:

> On Sun, 2011-01-16 at 11:30 +0100, Mattias Gaertner wrote:
> > > Graeme must write for every component dedicated IDE integration 
> > > code AFAIK.
> > 
> > Not dedicated IDE, but dedicated streaming code. The LCL must do the
> > same, for example TBitmap.Data.
> 
> Like I mentioned before, fpGUI doesn't use the built-in streaming
> features of the RTL. fpGUI's property editors each know how to read or
> write it's data. fpGUI handles images differently, so there is no need
> for a Image1.Data property. In fpGUI you register images with framework,
> then simply reference those images by name. This also has the benefit
> that it reuses images (reducing the memory footprint).

What about other custom data, that can not be represented as published
property?

 
> > Graeme, how does the fpgui writer support circles?
> > For example:
> > 
> > object Edit1: TEdit
> >   AnchorSideLeft.Control = Label1
> > end
> > object Label1: TLabel
> >   AnchorSideTop.Control = Edit1
> > end
> 
> fpGUI doesn't have such properties, so those would fall under the
> "unknown lines" memo and simply get ignored by the UI designer. Then
> when you compile your project, any forward declaration will have to be
> added in code.

That is a big show stopper.
A pascal writer for lazarus forms must handle this automatically.


Mattias




More information about the Lazarus mailing list