Our new wiki is available on-line now. I've been working for last few days to customize it and add the necessary extra functionality. However, there is still a lot to do. As you can notice, there must be added many technical templates, help pages and some navigation structure. I hope I'll manage to deal with it in the nearest days. The wiki is intended to keep community-driven materials on our open-source projects, as well as extra information on add-ons, such as framework ports. Feel free to share your solutions with everyone - you need only the discussion board account and some knowledge on MediaWiki syntax.

Well, after many adventures with SVN and recently discovered problems with XML prologs and DTD I finally managed to release the first beta version of Open Power Template. From now, we are going to focus on removing as many bugs and problems as possible and we need here your help. Furthermore, we also need to complete the English manual, which is quite big now, but still does not explain some issues.

Somewhere in the middle of November 2007, I wrote the first (working!) lines of the Open Power Template 2.0.0 source code. After a year of hard work, I've already uploaded a revision that finally gives you all the invented features implemented. For that time, OPTv2 grew and changed its shape. The first development releases resembled OPT 1.1.x when it comes to API and some features. They were just ported to the new XML compiler. Nowadays, OPT is a totally different library. It is much more modularized and designed to make the integration with frameworks easier. There is still a lot to do. The incoming release will be the last one with the "-dev" prefix, and in the next few weeks, the beta versions will appear, then Release Candidates and at last, the first stable release.

Recently I'm working on a special Wordpress cache plugin which would be appreciated by bloggers and their hosting providers. First tests are very promising and motivate for harder work.

At last, the translation of the manual into English is complete and the source code has been already released as the first version of TypeFriendly, the documentation generator. In is available in Files on the main site. The user manual is provided in the source form and it works also as an example, so please do not worry that something is missing. All the necessary information to build the HTML version can be found in /info/README.txt file. All you need is to type one command in the system console. The on-line documentation will be available soon, as we are preparing new website. To get more information about TypeFriendly, take a look at the previous note.

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.

The new development version became available a bit later that I planned, but on the other hand, I managed to add much more new things. The DTD issue is solved, as well as XML prologs, CDATA support and code escaping. The expression compiler is done and the programmers may use now brand new component implementation. This is a significant step towards the first beta release and the end is closer than further. There are only a few instructions to code, the rest is almost completed and works. The compiler, programmers' API and most of the stuff also works. I think of making the first real tests on my home website and creating the Open Power Forms library compatible with the new OPT.

One month ago we had no time to prepare a good website for our group so Zyx made something temporary. Today I present a better and more complex solution. The website has been updated with texts and articles about our team. We've got still a lot to do with organization but our website and devblog are almost finished.

According to the my announcement from the last week, the development versions are going to appear much faster than before. This is the first of such events. The third dev of OPT 2.0.0 is ready to download. This time, I've paid much attention to the attribute processing. They can do a lot of interesting things with the tags they've been added to. The earl implementation has been ready so far - there were even examples showing the "opt:section" working. But to satisfy both me and probably other programmers, I had to extend it.

From time to time, I return to the library licensing issue. Undoubtedly, the right choice of a license is quite significant for the project success or failure. Simple, permissive licenses are very easy to follow and use, but in my opinion, they are quite dangerous for the project itself and can lead to some abuses. On the other hand, we have a GNU LGPL license, which has been used by Open Power Template so far. It provides the correct protection of the code, however the linking with non-GPL software is quite complex and produces many questions. Let's take a look: we write the libraries for all the website programmers and authors of complete scripts, whether they are open-source or not.