The slides of the eZ publish Conference 2006 are now online, available in the www.ez.no presentations section.Most notably, the slides of the talk about the recently announced eZ platform and eZ application server for PHP are also included. They have been presented by the brilliant Jan Kudlicka and show a graph of the whole eZ platform stack – check out the slides: Future of development at eZ (PDF).
Just a few days ago, at the eZ publish conference 2006, we had the very first eZ awards night.
The eZ awards is a prize awarded by eZ systems during its annual conference to give special recognition to key people within the eZ ecosystem.
It was a great show, the winners were overwhelmed and the audience had a lot of fun celebrating.
Check out the eZ awards pages and you can tell from the pictures how great an event this was.
Fresh from the eZ publish conference (1st day today):
eZ systems announced the development of the eZ platform, which will ship with a PHP application server called “eZ application server”.
Of course, eZ platform will be build on top of eZ components.
More information in the news announcement:
eZ systems announces eZ platform for PHP application development.
My dear colleague Zak Greant has written a nice article, where he leaves no doubt about what eZ systems thinks about software patents: well, we simply think they stink 🙂 Zak of course formulates this in a more eloquent way and he also provides some reasons why we don’t like them.Software patents might be one of the biggest issues to gain more freedom, also in democratic societies. Let’s thus say with Martin Luther King: I have a dream, that one day I will live in a world without software patents, where true competition of ideas and innovation exists.
Yes, and I am proud to be in a company not afraid of clear statements.
He is a slow hand when it comes to guitar playing and a fast hand when it comes to photo shooting: BÃ¥rd Farstad got a Weblog, named Papelipe. He is one of the co-founders of eZ systems and a true LAMP addict.
You wonder what the blog name means? He writes:
The name Papelipe was invented by my then 2 year old daughter which used it to name unknown things. It is unique and I found it suitable for my blog. At the time it was registered there were no mentions in Google for Papelipe.
Well, that says it all 🙂
BÃ¥rd currently writes about his findings while torturing the 6 servers cluster he uses for eZ publish performance testing.
In the realm of the 3rd steering committee meeting of the tOSSad EU project, I had the chance to visit Istanbul. While being there, I also attended and presented at the FOSS Days 2006, the bigest FOSS event in Turkey.
Let me share some pictures with you:
The hotel I stayed at is located in the Istiklal Avenue of Istanbul, the place with the most nice restaurants and pubs around. Oh yes, food is really good in Istanbul 🙂
Istanbul and the Bosporus at night.
The interior of the Sultan’s harem.
Always enter the Suleiman Mosque at the right side, because that’s the good side…
Interior of the Suleiman Mosque.
The famous madonna of Hagia Sophia.
The relaunch of the Swiss TV news site SF Tagesschau is based on eZ publish. Now, a 11 pages case study has been published, written by me and my colleague Marcus Rölz. The document explains the most important features and also provides some screenshots.
Yet, the case study is only available in German.
One major feature which will be part of the forthcoming eZ publish 3.8 release (out in May) is content version diff functionality. It will sit on top of the versioning and archiving system, which is included by default since the early days of eZ publish 3.
Integrating content diff is a logical move, if you consider that eZ publish 3.8 will also include enhanced multilanguage handling. The new multilang features are most useful when translating content, and here, content diff is just perfect to spot changes in the language version which is supposed to be translated.
Combined with the content object model of eZ publish, you will be able to diff content per object attribute. This means, that it is not just one big text field like in Wikis, where you can identify changes. Actually, the cool thing is that you can diff accross any “form field” of your content, or in eZ publish linguage: accross the various datatypes.
Of course, diffing does not make sense for all datatypes, for example, binary data like images. Indeed, what you can do with the image datatype, is to diff its metadata like filename, size, and modification date, also the alternative text.
The following datatypes will have diffing capability: price, URL, email, date, time, datetime, float, string, xml field, keyword, media, etc.
Read more in the Content Version Diff specification.
Now you can take a look into the future of eZ publish development, as well as the eZ components. I have conducted and published an email interview with five of eZ systems’ leaders of the development team.
Ideas for future eZ components are:
Our dev leaders provide lots of valuable information and are doing a fine job as fortunetellers – as they are predicting a future they shape themselves, it should become a self-fullfilling prophecy 🙂
Honestly, I fully trust in what they are saying and doing, there’s a lot of intelligence accumulated at eZ systems. Just look at the high quality of eZ components, and you will be able to anticipate just how good eZ publish 4, the next big version of eZ publish, is going to be.
A short while ago, I published the eZ publish 4.0 Features List written by my dear colleague Frederik Holljen.
It provides information about 52 features which will be improved, added, and a few of them which will be implemented after 4.0 is out.
This baby will rock!
