It felt like a Monday morning. After my alarm clock didn’t get off (+ 1 hour), I noticed there was only a train 1 hour later, so instead of arriving at half past 9, I arrived at 11 and missed the first speaker.

Lightswith + Drupal

Anyhow. I picked up the last quarter of using Drupal together with Lightswitch (= Visual Studio). Apparently not a lot of devs had interest in the subject because there were only 20 people in the room. And those who didn’t attend were right, because all the speaker could tell us was that marrying Drupal and Lightswith could only result in a divorce.

Lightswitch can create a HTML5-admin environment based on a data layer. That data layer could be your Drupal database. Nothing works out the box for Drupal because MS of course wants to integrate their software (SharePoint, Office) and not someone else’s software.

Another downsides of all these MS-Drag-And-Drop-Automatic-Data-Layer-Builder-stuff, is that when you change your database, something on the other side might break and you could end up writing the data layer yourself (as a attendee commented). Plus, the actual html output looks weak and is unusable in a serious professional environment. Don’t try this at work, pro’s!

Drupal 8 discussion panel

Three Belgian core-devs (swentel, Wim Leers, aspilicious) had a one hour Q&A hour about Drupal 8. They all had a lot to tell so the number of actual public questions was limited.

You had to know some Drupal 8 in forehand, because new projects (say WSCCI, PSR or TWIG) were discussed without being explained.

The main message was that Drupal 8 is ready to port your modules to. But, there’s still a lot of work to be done. There are still upcoming API-changes, you can’t translate a node’s title yet and there are various other big and small release blockers. But: Views should be finished. Ah!

And why Drupal 8 should be better that its processors:

  • PSR proof. PSR is a PHP coding standard. (aimed for PSR 4 however, it’s uncertain if it the project will get there)
  • Display Suite is now a core module (however, is this really such a big plus?)
  • Getting rid of the hooks in favor for a more object oriented way (however, hooks still exist)

Continue reading “DrupalCamp Leuven 2013, a brief Saturday review.”…

  • Published:May 23rd, 2013
  • Category:Drupal 8

Everything! Really!

Drupal 8 changes for developers

Everything will change and certainly for developers

  • The code will be more object oriented,
  • there will be a Symfony-like approach of theming (say goodbye to the _theme() hooks),
  • migrating from local to staging or a live-environment will be easier, as you will be able to save certain local settings in the code,
  • there’s the development project WSCCI (pronounced “Whiskey”) that will give devs the opportunity to write output for json, for apps, or for anything else besides html,
  • the multi-language-approach will be more logical and out of the box (Europe sighs).

In short… you probably won’t be able to reuse a single line of code from Drupal 7 to Drupal 8.

If you want to learn Drupal from scratch, you might want to wait till the release of 8 before you start to study.

Changes for users

For the users the changes are less dramatic, but there’s one big new feature:

  • In-place-editing, found in almost every commercial CMS will finally come to Drupal. This means that when you want to edit a text on a page, you don’t have to press the edit button, find the right field and save, but instead you’ll be able to change text within the normal website layout.

Still a lot of work

But… there’s still a lot of work. Drupal 8 is far from ready. The official release is planned towards the end of 2013, but the date march 2014 is probably more realistic. The in-place-editing for example is currently not working for the title-field, because the title is technically not a field. WSCCI is also far from ready.

Things are even so not-ready that some new features might be cut.


Those who want to contribute or want a sneak preview, can install D8 through GIT. Though, it’s not stable, not even in beta, so don’t use it in a live-environment.

$ git clone --branch 8.x clearPaper by Copyright © 2012-2019 Robin Brackez. All rights reserved. By visiting this site you agree to accept cookies that are purely used to check how many visitors I have. Theme by: creativebits. Custom adaptations by Robin Brackez.