Hi,
In case there are anybody using tiOPF, please note the following. I'll also update the Free Pascal wiki in the next few minutes.

Mailing lists / lazarus / 2013-03
6 messages · 3 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi,
In case there are anybody using tiOPF, please note the following. I'll also update the Free Pascal wiki in the next few minutes.
Which branch should I checkout to use with Lazarus? The information on the website is bit confusing. The tiopf2 branch appears to date back to 2008
Frank Church wroteWhich branch should I checkout to use with Lazarus?
tiOPF2 branch.
FPC still can't compile the tiOPF3 branch, due to Unicode and other Delphi language features. Feature wise, tiOPF2 and tiOPF3 are near identical, and I keep them in sync.
The information on the website is bit confusing.
The tiOPF website or the FPC/Lazarus wiki?
I just updated the FPC/Lazarus wiki page with the latest information.
http://wiki.lazarus.freepascal.org/tiOPF
The tiopf2 branch appears to date back to 2008
Uh? The latest commit was done today.
Regards,
- Graeme -
Why you hate "master", i believe it is for last working version, here is tiOPF3, i do that, and for me it have all fixes in it, so who need last of every thing he will take "master".
I have managed to get the tiopf2 working. It is easier and clearer than the last time I used it. @Zaher Have you been able to get tiopf3 working on Lazarus?
Why you hate "master", i believe it is for last working version, here is tiOPF3, i do…
Zaher Dirkey wroteWhy you hate "master", i believe it is for last working version, here is tiOPF3, i do that, and for me it have all fixes in it, so who need last of every thing he will take "master".
I'm not sure I fully understand your email. But I'll explain what I think.
I don't "hate" the 'master' branch concept of Git. The way the tiOPF SubVersion repository was structured (very different to the normal SubVersion layouts), it was very hard to import the history into Git. Also in the tiOPF project there are two active branches being developed in parallel at the moment. Normally projects branch major versions, and older versions are not developed any more. This is NOT the case in tiOPF. FPC users can't move to tiOPF3 branch yet (at least last time I tested), due to FPC missing Delphi language features. So two branches (tiopf2 & tiopf3) are developed and maintained in parallel.
So there is no single development branch in tiOPF. That is why I decided to make 'master' an non-development branch. Git seems to expect a 'master' branch though (which I think is wrong design). So instead of me choose if 'master' must be v2 or v3 of tiOPF, I rather made it an entry point which just contains a README file explaining the repository layout. If the developer uses Free Pascal, switch to 'tiopf2', if they use Delphi 2009+, then switch to 'tiopf3' branch.
Regards,
- Graeme -