Am Montag, 2. April 2007 17:37 schrieb Graeme Geldenhuys:
> Hi,
>
> Was any study (or prototypes) done to help make the choice on how
> Lazarus would implement widget sets?
>
> For example:
>
> 1) Wrapping existing native widgets with the LCL (as is currently
> done) vs Writing a native (object pascal) widget sets from scratch
> (like fpGUI or MSEgui) and implementing the same compatible VCL
> interface for that widget set.
>
> 2) Ease of supporting new platforms. Using the current LCL (wrapping
> native widgets) vs having a native (object pascal) widget set, and
> only having to port the painting backend.
>
>
> I can think of many more such test cases... One vs Another. My main
> reason for asking, is to find out if there was a definitive reason
> why the Lazarus project decided on rather wrapping existing platform
> widgets in a LCL compared to writing a widget set from scratch.
>
> Our company is trying to determine if it will be a viable option to
> hire a few developers to finish the fpGUI project and interface fpGUI
> with Lazarus. Obviously to the extent that Lazarus itself compiles
> and runs using the fpGUI widget set. We don't want to branch Lazarus
> though. This is primary to get Lazarus ready for our commercial
> projects. I got pretty frustrated with Lazarus today and how the
> behaviour of widget sets differ between platforms. [It's been one of
> THOSE days!]
>
> The other obvious choice for would be to hire some full time
> developers to only work on Lazarus and sort out the issues we are
> experiencing. I can justify the expense compared to buying licenses
> of Delphi. Lazarus gives us a lot more flexibility. IDE wise and
> supported platforms.
>
> In my research so far I think Qt got it right. Implementing their own
> widget set, allowing them to handle all widget internals - events,
> painting, behaviour on different platform, etc.. With the fpGUI
> project I am experience that same result.
>
> Your input would be greatly appreciated.
Graeme, I share your frustration! First time I experienced this problem
was, when I tried to port a Delphi VCL app into a Delphi CLX app in the
hope, I could compile it with kylix then. E.g. in VCL
SpeedButton.OnClick happens after speedbutton.down property is updated
but in CLX OnClick happens before down is updated (or the other way
around).
However, with win32/gtk LCL this is even worse... seems like one never
knows, whether an event was fired before or after ..
Long story short: If you make fpGUI production ready, I'll buy it.
regards
Burkhard
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
