This week I was at the International PHP Conference. It was a nice conference with interesting topics. It was however a bit of a pity that the PHP conference got 'cornered' by the Webinale conference, which was a lot bigger and caused the PHP sessions to be in way too small rooms. But most of the sessions I visited were interesting, so all in all it was a nice conference.

There was one particular thing I noticed though: the amount of people using macbooks. I know that it's a popular notebook, but almost half of the laptops there was a mac!

See picture:

4 of the visible laptops are macbooks, and there were even more not directly visible on this picture.

Maybe my own laptop got scared of this, because it decided to die during the second day of the conference. It's probably a motherboard failure and repair will be expensive, so I'm thinking of buying a replacement.

Now I'm stuck with a dilemma. Should I buy a macbook?

Regardless of it's Cool Factor, what makes a macbook useful for PHP developers? What are features that are good, what are features that are hard to get used to for a developer switching to mac? Any ideas?

One thing I will miss if I buy a mac is the ability to write on it; I had a tablet pc and since I got it, all my notes were digital. So the alternative is a new tablet.

Tough choice!

(If you're curious, the picture was taken during Stephan Schmidt and Frank Kleine's talk on Annotations. Interesting presentations, although I have my doubts abusing the docblocks for declarations)

For the impatient, I've took only a few pictures, you can see them in my gallery.

Most reviews I've read so far were either of speakers or visitors. I hope to provide a little bit different perspective as I had a booth for ATK.

We arrived on monday, on the management day. The exhibition was officially on tuesday and wednesday, but optionally we could already exhibit on monday. So we drove off at about 7.30 in the morning, to arrive in Frankfurt at about noon. We could only check-in to our rooms from 15.00h, so we decided to setup our booth first.

Our booth was located quite nicely. Whereas some projects were located in a kind of corner room, we were located right outside that room, next to Pearson VUE and O'Reilly, on a spot that a lot of people had to pass by on their way to the sessions. That first day was meager though. Not too much managers were walking around, and the people attending the workshops did not really walk around at the exhibition much.

We had lunch, where we were joined by Daniel Convissor, and had a conversation about what he did, what we did, etc. When telling him about Achievo he appeared to be a user of Achievo, so we discussed some features he would like to see in Achievo. He was in a bit of a hurry though, as his laptop had broken down and he had to arrange a new one before his sessions on wednesday. Later I read that he didn't manage to get a new one. A pity, I would've borrowed him mine for the session had he asked.

Anyway, for the exhibition, monday wasn't too interesting. In the evening we visited Frankfurt to have a glimpse of the city center (which for some reason reminded me of Gotham City, with its tall black buildings with yellowish lighting).

Tuesday was excellent, we had a lot of visitors at our booth, and those who saw the demo were enthousiastic. Some wondered why they hadn't heard of us before. To them I can only say: help us spread the word :).

At dinner, we had a conversation with a manager from MySQL AB, who gave some interesting insights into their business model. This was interesting, as we, like MySQL, employ a dual licensing model.

Later that night in the PHP lounge, I had a beer and a very nice conversation with Danne Lundqvist (triggered by this blogpost). I showed him ATK, and he showed me a preview of his wysiwyg editor. What made this conversation interesting was that he seemed to share some of the same ideas that we try to incorporate into ATK, such as code minimalisation, and he also took pleasure in writing generic, clean code. When his editor is finished a bit more, I will integrate it into ATK.

Wednesday was interesting too. A lot of attention again at our booth, although somewhat less than tuesday. At about 15.00h we drove home.

(In between demo's, I managed to add some features to ATK which I will put in 5.4 once I released 5.3)

In general, it was a nice conference. One worry though; I spoke to a lot of people who visited sessions, and while some of them were good, there were also complaints about a lot of them (ill prepared, too shallow, too specific). I can imagine that it's hard to get to exactly to the right depth, as there is a great variety in audience, but if a presentation is not prepared well enough, that's really a pity. People pay a lot of money to visit a conference. The least the speakers can do is prepare. But in general, the responses were positive.

This was my first time in Frankfurt, whereas I had a booth twice at the spring edition in Amsterdam. What I noticed about that was that the Amsterdam conference seemed to be a little bit more 'international'. There, we had a lot of visitors from France, Spain, Italy and other countries, whereas in Frankfurt most were German.

All-in-all, it was a pleasure being there. The hotel was nice, the people were nice, the conference was nice. See you at the Spring Edition in Amsterdam next year!

I'm preparing for the PHP conference. In about 5 hours, I'll be driving off with Sandy to Frankfurt. I hope to arrive there at around 11 o'clock, so we have some time to check in to our rooms, and populate our booth in the afternoon.

I have to get some sleep before I depart, but I'm currently preparing my laptop for the demo's. I've started this much too late this time, but luckily, Sandy prepared all the demo's so all I have to do is do a 'cvs -q update -d' and I should be up and running. Currently installing Open Office 2.0 to showcase the open office template engine we've added to ATK recently.

On to a different subject. This week, one of our users wrote a nice testimonial about his experience with ATK. It's always nice to receive compliments, but messages like this are of course extra motivating.

I know my way around PHP. I've been working on frameworks, web applications and CMS'es for almost 6 years now. I'm even a Zend Certified Engineer.

Still, last week I amazed myself in how stupid I can be.

ATK can be downloaded with a demo application. To aid the developer, most pages in the demo application have a 'view source' link. What was I thinking when I used __FILE__ to determine the source file and pass that to a viewer through the url, not checking the validity of the filename? I created a 'Local File Include Vulnerability': any logged in user was able to tamper with the URL, and for example use ?file=/etc/passwd to view any file that the webserver has read access to.

I've read numerous blogs about the subject, read slides and articles from security experts such as Chris Shiflett, but still, one unguarded moment of late night, sleep-deprived hacking and bang, there you have it.

Luckily, it was only the demo application, which is usually not installed in public places, and also, you still have to log in to actually be able to exploit anything, but still, given how relatively easy it is to make such mistakes is discomforting.

(A fix was immediately released of course, at http://www.achievo.org/atk/download you can find the 5.2.2 version which fixes this issue).

There is also some positive news about ATK. Boy wrote a new howto on custom record actions. This shows how to do a lot more with your app than the usual CRUD operations.

Guido did some excellent work last week on an Open Office template engine. It is now possible to generate Open Office documents right from an atkNode. As usual, documentation comes second, so it's undocumented right now, but it is already available in the nightly build. If you want to experiment with it, we can help you on IRC or in the forum. We will give a demonstration of this new functionality at our booth at the PHP Conference in Frankfurt next week.

Finally, Sandy created a new CRM module for Achievo. It's far from finished (it only works with Achievo 1.1, not yet with the development version), but it's a start. This one is available from Achievo's nightly build page.