Any one work with Lazarus with OPF?

What are you doing?

What persistence framework? Pressobjects?

2009/12/2 Osvaldo Filho :

http://lazarus.freepascal.org/index.php?PHPSESSID=5ca1e078c15770ad5ae317f9996540cf&topic=8079.0

We have a small application (teacher's gradebook) that is written in Lazarus, using tiOPF and embedded firebird.

tiOPF works in Lazarus/Delphi, is very mature and flexible, but has a bit of a learning curve.

Michael.

2009/12/11 Osvaldo Filho :

Any one work with Lazarus with OPF? What are you doing? What persistence framework?

Been using tiOPF since around 2002-2003. I initially ported tiOPF to Kylix 3 and then later (4-5 years ago) to Free Pascal.

Initially I also ported the GUI components (object aware components) in tiOPF to Lazarus LCL. But due to inconsistencies and differences between GUI frameworks and Form Designers, I halted that effort. Instead I implemented the Model-GUI-Mediator (MGM) design pattern to make standard GUI components (no matter which GUI toolkit you use) "object aware" without having to create descendant / customized components. A few years later, with help from Michael van Canneyt, we improved the MGM implementation even more - making it much easier to use. MGM included with tiOPF now supports VCL, LCL and fpGUI Toolkit.

tiOPF is a very stable and flexible framework with over 1600 unit tests run daily under Linux and Windows servers. It also supports 32bit and 64bit system. tiOPF has been used in commercial software since 1999. Work on tiOPF v3 has just started with the main goal of making it Unicode compatible.

tiOPF might not be the easiest framework to learn, but I guess that's one side effect you get with power and flexibility. Knowing and understanding bit about design patterns will be beneficial in learning tiOPF. Other than that, there are lots of documentation available and news archives of the last 8 years.

For more information about tiOPF, have a look at its website and join its newsgroups for any more questions regarding it.

http://www.tiopf.com

I'm looking in using tiOPF. Is it safe to use the svn trunk?

Luiz

2009/12/11 Luiz Americo Pereira Camara :

I'm looking in using tiOPF. Is it safe to use the svn trunk?

99.99% of the times yes! :-) Please do not use the "latest release" download on SourceForge - that is *very* old.

I'm currently about 15 revisions behind trunk - simply because we are in the late testing phase of one of our companies new products, so no new features are allowed at this point. We have no problems at all with tiOPF trunk.

Due to the fact that tiOPF is mostly used in commercial products and that we have daily build servers testing it, trunk (unlike many other open source projects) is pretty much always in a stable state.

The big documentation and support part is a major part of my decision to take a closer look and use it in future for a bigger application.

Are there any plans to support sqlite? For smaller desktop database applications, this would simplifiy a lot.

greets
Michael

2009/12/12 Michael Fuchs :

Are there any plans to support sqlite? For smaller desktop database applications, this would simplifiy a lot.

SQLite is already supported via SqlDB (part of FPC) and the Asqlite library from http://www.aducom.com/sqlite

I don't use SQLite myself, so can't comment on how stable those implementations are. I mainly use Firebird via the SqlDB persistence layer.

I can confirm this.

Michael.

It should work almost out of the box if you use the SQLDB layer.

Michael.

I think I started a Persistence Layer for SQLite using SQLDB components a year or so ago but didn't finish it up since the project that I needed it for took a different path in terms of database (ended up using FB).

I was pretty easy to do though and I think I have the unit around somewhere if anyone is interested.

I am. :)

regards
Michael

Lee Jenkins wrote

I was pretty easy to do though and I think I have the unit around somewhere if anyone is interested.

The SqlDB persistence layer already included in tiOPF should do the job. I have a few refactorings for the SqlDB persistence layer when I tested it with PostgreSQL - those refactorings should allow SQLite to work too. I haven't committed those changes yet. I'll try and make some time tomorrow to commit those.