Invenzzia... in English - Tag - svn

Invenzzia goes to github

Zyx — Wed, 26 May 2010 13:42:00 +0200

So far, our projects have been hosted with Subversion control system installed on our own servers. While it is quite convenient and we are not limited by resources, it causes some problems with authentication and simplifying access for users that wish to help us developing our projects. In the last days, we have been discussing on that and decided to switch to Git. In the near future, all the projects will migrate to Github which will become our official hosting platform. I hope it will make the collaboration much easier.

Note that one of our projects has already been ported to Github - TypeFriendly. The others, including OPL will migrate in the next weeks, as this requires from us some effort and time. Basically, we have some scripts that help us publishing new versions and they must be rewritten from SVN to Git.

Invenzzia Summary #3

Zyx — Tue, 12 May 2009 10:38:00 +0200

Welcome to the third episode of the Invenzzia Summaries. Today we will make a small celebration of the 100th revision to the OPL repository, as well as take a closer look at the recently implemented features, such as PHAR support, caching interface and the improved autoloader.

100th revision to the OPL repository

The Subversion repository has been used in OPL development for ages. However, for the first six months, Open Power Template 2 had to deal without any version control system due to the movement to the new group and abandoning the old network infrastructure. The first revision to the new repository was committed on 30th June 2008 and was relatively poor - in other words, nothing worked. In the last few months the use of the repository has significantly increased, providing the users the freshest versions of the source code and the documentation. Only in the last two weeks, there were 14 new revisions.

The 100th commit has been made to the OPL library. It includes the newest improvements to the autoloader and the PHAR builder.

New OPL autoloader

Recently, I have been corresponding with Amadeusz Starzykiewcz about the OPL autoloader improvements. We decided that it would be the best to make it more a general-purpose autoloading tool that suits not only OPL needs, but other libraries (i.e. Doctrine and Zend Framework) as well. The result is visible as the improved API with many limitations removed. The most significant changes are:

The autoloader can handle any library using the Foo_Bar_Joe class naming style.
The library-specific autoloading needs have been moved to the extra handler. Different libraries may use different handler or not use any.
Improved library configuration with addLibrary() method.
Added performance-tuning methods.
The special handler for PHAR-s is present.

PHAR support

The full PHAR support has been one of the primary goals for a long time. However, for most of the time, there were other priorities that must have been done, but finally there appeared the PHAR builder in the repository. It allows to produce a fully-functional PHAR from any OPL library. The archive is self-configurable and contains only the executable code. The PHAR-s will be available to download from our website together with the ordinary distribution packages.

The installation and usage of PHAR-s is described both in the OPT and OPL documentation. Please note that you need PHP 5.3 or PHP 5.2 with installed PHAR extension in order to use it. As we have the PHAR support, we need to work on the performance a bit. The developers claim that PHAR-s can be as fast as the ordinary files, but our tests show that OPT and OPL archives work a bit slower than the classic solution. Fortunately, it is only a matter of time. This is a relatively new piece of technology and we have to do some research in order to determine, how to get more from it.

SVN layout changes in OPL

Zyx — Tue, 23 Dec 2008 17:00:00 +0100

Merry Christmas everyone! We've had a small delay with OPT 2.0.0-beta1 concerning SVN problems, but they seem to be solved. After the Christmas, we are planning to make important changes in OPL repository layout and everybody whose scripts depend on checking out should upgrade their paths. It is connected with introducing the independent development cycles for each library. The details can be found below.

The new repository layout will consist of two parts:

components
releases

The components are simply the libraries which will be splitted. Their directory structure will be similar to the current one. For example, OPT will be packed as:

/components
/components/Opt/trunk
/components/Opt/branches
/components/Opt/tags
/components/Opt/trunk/docs
/components/Opt/trunk/lib
/components/Opt/trunk/lib/Class.php
/components/Opt/trunk/examples
/components/Opt/trunk/tests

However, unless you are a developer, you will probably have nothing to do with that directory, as it will be used for development purposes only. The end-user packages are always built of at least two libraries (the correct one and OPL, there might be some extra dependencies). This property can be found in the releases directory. It will be also splitted into trunk, branches and tags. Now, if we want to checkout the 2.0 branch of OPT ready to use, we go into /releases/branches/Opt-2.0/. There will be packed OPT and the necessary OPL core in the layout that you are already familiar with.

The new layout can be viewed online in our sandbox repository. Note that the libraries have not been physically imported there, only the raw directory structure is introduced: svn.invenzzia.org/svn/sandbox.

SVN is active!

Zyx — Mon, 30 Jun 2008 08:10:00 +0200

Unfortunately, the configuration of a version control system on our current server is not as simple as on Sourceforge.net. But now I found some time and ideas, how to make it work and finally... there it is, we have an SVN repository. It's available under the address http://svn.invenzzia.org/ - we still have to install a good browser. Today I'm going to upload the source code of the new OPL and TypeFriendly, a documentation generator almost ready to its first release. All the instructions, how to connect, will be published on the main site.