So if I understand correctly, tiOPF no longer has components on the 
pallette, as there is no longer a design time package?
(Indeed the tiOPFLCL package compiles perfectly..)
Btw, tnx

Brave Cobra.

On 05/16/2010 05:10 PM, Graeme Geldenhuys wrote:
> On 16/05/2010, Brave Cobra<[email protected]>  wrote:
>> The tiOPF package compiles. The tiOPFGUI is giving me trouble, notice
>>   it's FPC 2.4.0, not 2.4.1, and that it's 64 bit instead of 32:
>
> No problems, based on the above, I already see the problem. :-)
>
> tiOPFGUI.lpk is no supported any more and I will be removing it as it
> confuses a lot of developers. The packages you should be using is
> tiOPF.lpk and tiOPFLCL.lpk.
>
> The difference between tiOPFGUI.lpk and tiOPFLCL.lpk is as follows.
>
> tiOPFGUI.lpk:
> ---------------------
>   * This was meant has a design time package installing the ported
> tiOPF GUI components into the component palette.
>   * Due to to many differences between LCL and VCL the tiOPF GUI
> components simply had to many IFDEF statements making the code
> unreadable.
>   * Also, due to the bugs/limitatiotns in the Lazarus Forms Designer
> with composite components (various standard components on a panel
> acting as one component), the Lazarus forms designer did not work well
> with the tiOPF GUI components and you could actually crash the IDE
> relatively easily.
>
> tiOPFLCL.lpk
> ------------------------
> Because of the issues porting the tiOPF GUI components to LCL, I
> started an alternative method of integrating GUI components with
> tiOPF. The new method is called Model-GUI-Mediator. This design
> pattern allows you to use standard VCL, LCL or fpGUI components and
> allow them to act as "object-aware" components. This is similar to
> DB-aware components, but without the need for descendants components.
> tiOPFLCL.lpk is a runtime only package, so it does not register
> components in the IDE's component palette.
>
> The other benefit is that most of the Model-GUI-Mediator (MGM)
> implementation is non-gui code, so can easily be unit tested and the
> code is shared between VCL, LCL and fpGUI Toolkit. For an example of
> how to use MGM, take a look at Demo 21 (Address Book demo).
>
> Units of interest for MGM is:
>    tiBaseMediator.pas -  most of the implementation an is non-gui
>    tiMediator.pas - basic mediators for edit components handling single
>              item properties. eg: TEdit, TTrackBar, TCheckBox, TComboBox, etc.
>    tiListMediator.pas - mediators that handle lists. eg: TStringGrid,
>              TListView etc.
>    tiModelMediator - this is a mediator that handles a complete "model"
> (object) on
>              a form. You create one instance of this in your form,
> register the properties
>              it should model, and it will create all the other
> mediators for your.
>



------------------------------------------------------------------------------

_______________________________________________
tiOPF-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tiopf-talk

Reply via email to