Finally, the first Release Candidate of Open Power Template is available to download, after 4 months of testing and implementing the remaining features. The library seems to be completed and stable enough for both development and production environments. Of course, there is still a small possibility that a fatal bug will be found, but I do not think this will happen, as there are lots of unit tests present and the code has been checked with two real-world web applications.

Invenzzia Summaries are the way to inform about what's going on in Invenzzia and its open-source projects. In the second episode we will talk about incoming OPT 2.0-RC1, OPL port for Zend Framework and the incoming first bigger practical tutorial about OPT.

A couple of minutes ago, we have finally run the new Invenzzia website with new layout, navigation and features, such as news/article commenting. We hope you'll enjoy it and we are waiting for your feedback and opinions. Please note that the links to the user manuals have been changed, as well as the download links. However, we keep the automated redirects.

Hi everyone, in the last few days, we had a lot of work around Invenzzia and its projects. In this entry I would like to inform, what currently is going on. We will talk about OPT 2, TypeFriendly, our new website and the activity in open source project trackers.

It's true, the new beta version of Open Power Template is available to download. It was planned to be released a week ago, but because of problems with SVN I didn't manage to do that (again, but hopefully for the last time). This is mostly a bugfix release, but there are some small improvements and changes in the component API, which was not documented then. The changes are not too big and were quite necessary to be introduced.

Today morning I've found on webresourcedepot.com a post written four days ago entitled "19 promising template engines". On the fifth position, I noticed the familiar logo of Open Power Template and a description that perfectly matched the 2.0.0-beta version. The link was redirecting to the Invenzzia website. I followed it and I was shocked - I forgot to update the main Invenzzia website! Invenzzia is no longer bilingual for some time, and here still lots of pages were empty, whereas the Polish text was very out-of-date. This was how we welcomed English readers for a couple of months :(. I decided not to wait till Extreme eXtreme (argh, note the uppercased letter - JJ) will finish the new website and to update all the information as soon as possible. And here it is!

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.

I'm currently working on a project written in Zend Framework and while trying to secure sessions, I noticed that this utility does not have any class that collects everything about the visitor and the request. The problem is quite serious, as many values in $_SERVER depend on the installed server software, PHP mode (module, CGI, FastCGI...) and many other things. This means that the scripts should not rely on them without a proper processing, because it can even crash whole website after the software change (I experienced it not so long ago). Thankfully, I noticed that in the old OPF code, I have a class called opfVisit that does this job. Now it's a part of the new Open Power Classes project :).

Recently we found that developing Invenzzia projects in bilingual way was a big mistake. As you can probably see, the result is that for example OPL is now closed for programmers that do not live and work in Poland, even if it is a quite nice country with beautiful language. Since now, it is going to change. We understand that English language simply gives us more profits and we want to correct our mistakes. So, what changes are expected?

Together with eXtreme, we work hard to make the first release available as soon as possible and we are quite close now. This is a perfect opportunity to tell something more about this project, which should be appreciated by those programmers who write their own scripts and libraries and look for a smart tool to make a documentation. The idea to write TypeFriendly was born in my head after I failed to add some necessary things to the XSLT sheets for DocBook. The PHP manual shows, what could be done with it (syntax coloring, lots of different formats, enormous amount of tags), but don't become too happy too fast. To achieve similar effects, we need weeks of coding and we must also fight against the portability. In fact, I'd rather use those weeks to write something more useful and friendly.