drupal

eps & kaas

2014 marks the beginning of a new company called eps & kaas which I cofounded with 3 other people. We're a digital agency, providing services ranging from mobile applications, websites, consultancy and design.

While you can still contact us (and me, from time to time) for Drupal development, my personal focus is now on Android and iOS development, but also different web technologies like Symfony or Ruby on Rails.

You can find us on the web, Twitter and Facebook. Drop us a note if you think we can help you!

So what about contributions ?

No, I'm not leaving Drupal. However, it's not going to the main technology anymore in my day-to-day work which is why I'm minimising my work on contributed modules: Display Suite is now in the hands of Bram 'aspilicious' Goffings, who has been a major contributor for the module since years. Most other projects have found a new maintainer, others are still waiting, maybe you're interested ?

I'm still around co-maintaining Field API for Drupal 8, or helping out in other areas that interest me, most notable the new configuration management system. We're slowly seeing the end of - yet another - long development cycle, hopefully marked with a release in june. The next big effort to get as many as bright minds together in one place is happening in March for the Drupal Developer Days in Szeged, Hungary. Anyone can help out in different ways: programming, reviewing, playing music, sponsoring plane/hotel tickets and so on.

Music and play

I've been writing songs since september for an album I want to get out this year - no release date yet. This is currently on hold as I need to rehearse songs to play with Last Exit To Loonville on the preselection of Humo's Rock Rally on the 25th of january in Gent. Tickets and more details are on the site of the Vooruit where the event is taking place. So, 8 years after my first appearance on Belgium's biggest rock talent event and more or less the last time I've been on a big stage, I'm back. What a great feeling that will be.

And, as if this year isn't going to be busy enough, I've started writing a play. The goal is to get it performed somewhere in october, so there's still some six months to finish the script. The main characters are alive in my head, the plot is as good as ready; if you're into a bit of absurdness and feel like Mark Everett and the theories of his dad are interesting topics, you'll want to attend this!

I'm sure 2014 is going to be a fantastic year, let it be a great one for you too!

An open source app for DrupalCamps

On september 14 and 15, Leuven will host the annual Belgium DrupalCamp. During those two days, people come together learning and discussing the open-source content management system Drupal. The program will be available on the website, but we decided to also create an application this year. We've tried to make it abstract as possible, so other Drupal events can easily built from the source code which is available online.

The apps will be available for Android and iOS. As soon as the program is ready, we'll publish them, so keep an eye out for the camp website, twitter or, of course, this article. The Android version is available on Play Store.

Features include:

  • Built with speed in mind: native app
  • Works offline
  • Sessions and speakers
  • Mark your favorite sessions
  • Maps integration when online

Collaborate

The code is freely available on GitHub, so anyone can easily send in bug reports, interface translations or create pull requests to make the applications even better.

Proudly built by @swentel, @TimLeytens and @leenvs.

So, who will make the Windows mobile and Firefox version ?

Live commit of the Field API to CMI patch at Frontend United

At BADCamp 2011 in San Francisco, Yves Chedemois, Greg Dunlap and I sat down to talk how we'd have to convert Field API to the configuration system that is now in Drupal 8.

Fast forward to April 13 2013. After months of hard work, with initial work done at DrupalCon Munich, the patch was finally ready to be committed. The Drupal core maintainers agreed that Alex Pott and I could commit this patch live on stage at Frontend United! And I had the honor of pushing the final button. I'll never be closer than this being a core comitter :)

Graham Taylor (@g_taylor) captured it all on video. 5 minutes of Drupal History.

We can use your help

But we're not done yet. A lot of work still needs to be done for Field API to be ready for Drupal 8. We've setup a site which collects the most important patches. So bookmark following site and pick your favorite topic: http://realize.be/field-api/

Thanks to everyone involved, with special mentions to Yves Chedemois (@yched), Alex Pott (@alexpott), Jess Myrbo (@xjmdrupal) and Greg Dunlap (@heyrocker).

Topics 

drupal, field api, planet

Introducing Field formatter conditions for Drupal

The Field formatter conditions module for Drupal allows you to add conditions and actions per field on the manage display screens of entities (nodes, users etc). For example: you can hide a field on path x. Or hide it when the current user has role 'Administrator'. The module ships with several built-in conditions and actions for common use cases we encountered during projects at work. And thanks to jpstrikesback a couple of more will be added before we hit a 1.0 release.

It's easy to write your own specific use cases for a project, consult the API or look into the code how to built a form, condition and callback yourself in a few minutes. Field API and Display Suite fields are supported, Field API's extra fields are not, and most likely neither in the future.

Rules support

It gets better though. The API is limited to the fact that a callback is both the condition and the action. But what in case you want more conditions ? That's where Rules comes into play. You can build unlimited rules with fancy conditions and then fire off actions on a specific field. Currently, the module ships with two rules actions which can hide a field or change the image style of an image formatter. The event for these rules always needs to be 'A field is rendered'. Depending on the use cases, more will be added later, but it's easy for developers to write their own actions targeted for a specific project.

See it in action

See how it works in a short screencast. Happy conditioning and a very good new year!

Help out with Field API for Drupal 8

Last week, I attended the Field API pre Drupalcon sprint in Munich. My major motivation was to start working on the conversion of Field API to CMI and little than a week later, we have a patch that is green. While there's still a lot of work on it, it's still a good feeling after one week of hacking and discussions. After driving 8 hours home after a fantastic week, I decided to step up as a co-maintainer of Field API. But me stepping up won't make the big difference, we need more people joining us!

Anyone can help in many different ways

  • Gardening the queue: go through bug reports, ask for more info when something is not clear or close duplicates.
  • You can work on an issue by creating patches. Assign an issue to yourself so we know who's working on it.
  • Help by reviewing and testing patches to see if they actually work as intented.
  • Come bring us coffee and cake :)

Where should I start ?

There's a lot of work, that's for sure: CMI, widget and formatter plugins, Field API vs OO and so on. We have a site which lists the most important issues: http://realize.be/field-api - Bookmark that if you're interested!

We are also available on freenode.net on #drupal-fieldapi in case you have any questions.

How much time should I invest in this ?

That is totally up to you. Remember, this is voluntary work, so we do not expect anybody to work 40 hours a week - although that would be more than fantastic of course :) As an example, this is roughly what I think my weekly schedule will look like:

  1. Continue working further on the CMI patch. I have sponsored time from Wunderkraut so I can focus hard on getting this critical piece of functionality in. Goodbye field_config and field_config_instance tables!
  2. Go through the queue twice a week for about an hour and review existing patches from other people.
  3. Go through the queue twice a week for half an hour and close duplicates or ask for more info.
  4. Pick one 'quick win' issue per week to create a patch from it, either a bug or feature request.
  5. Work on Display Suite issue queue, this usually happens once a week for about 3 hours. Been like that since forever.

So wait, I thought you didn't sleep?

Yes I do, and I do other things as well. It's not worth spending all your nights on coding, you'll get burned out before you know it. But wouldn't it be great to go to sleep and someone else was doing some great work ?

So, who's helping along?

Pages

Subscribe to RSS - drupal

You are here