In the past couple of posts, we’ve put several different facets of Drupal 8 under the microscope and discussed how each one is going to change the way you develop for Drupal in the very near future. Now, we’d like to ask a question about Drupal 8 development, one that we believe is going to be quite important in particular for developers who’ve worked within the wider PHP ecosystem.
As we already know, Drupal 8 contains Composer as part of its main distribution. One of the main components of Composer’s workflow is that it processes a central composer.json file to obtain and download a list of dependencies, that are in turn stored in a central vendor directory, and that are in turn loaded via a central ClassLoader object.
This method works fine for Drupal core, as we know what dependencies it’s going to require and it installs everything in a consistent fashion that anything else within Drupal can get hold of.
What we’d like to know is how...
Tuning into some of the discussion on Drupal 8’s new additions, you may have heard about the Dependency Injection Component from the Symfony project. Its inclusion is one of the many architectural changes helping Drupal modernise its approach to code organization.
In this brief introduction, I'll endeavour to explain the concept of Dependency Injection, and see how it impacts our code, hopefully demystifying a topic which is simpler than you might think.
What is Dependency Injection?
If you're not sure what Dependency Injection is, I'm not surprised. It's a simple concept that lends itself to complicated explanations. Possibly because of the complicated and varying nomenclature being used around it and other closely linked concepts?
Let’s see the sort of definition I might be guilty of rattling off:
Dependency injection is a...
*updated to include clarification about DI*
If you’re working with Drupal, you’re probably aware that the next major release of Drupal is going to integrate with the wider PHP ecosystem in a big way. Its adoption of Symfony is a really big deal, not just for Drupal developers who will have a lot to learn, with access to a huge stable of components as a trade-off. It’s also a big deal for Symfony developers, who have a whole new platform to develop for, and also the PHP community at large, who Drupal developers are now able to contribute to at a much deeper level.
We had a look around for a comprehensive list of Symfony components that are going to be in Drupal 8, but we couldn’t really find one that was up to date. For your benefit, here’s a list we put together that outlines the current list of Symfony components used in Drupal 8.
Here’s a list of all components in Symfony: http://symfony.com/doc/current/components/index.html
You might have heard that last week the ABC got hacked. The truth is a bit more complex than this, and is not as alarming as the statement may imply; rest assured, most of Aunty's sites are fine. However, there are still plenty of lessons to be learnt for everyone concerned, whether you run a website or merely use a website's services. In this post, we'll walk you through some of these lessons, and we'll show how Drupal could have prevented this from happening.
Who's running my website, and what do they use?
What actually happened was that one of the ABC's minisites was compromised, and the database was exported and dumped onto anonymous hosting sites. The minisite was for Making Australia Happy, a TV program that compared Australians from different walks of life to determined what made them happy, and part of the site's functionality involved allowing users to register an account to discuss what made them happy. As far as we...
It felt like yesterday when it was announced that Sydney would host the DDU in 2013 at the Melbourne DDU 2012. After the great camp that Melbourne community had delivered, I was inspired to volunteer with the local Sydney team in putting on the DDU in my own city. But what I didn't expect was that DDU 2013 was going to turn into a the first DrupalCon held outside the U.S and Europe. The conference was held in Coogee at the Crowne Plaza, overlooking the beautiful beach.
My involvement in the organization of the DrupalCon evolved overtime. My first role was to gather content for the website. Just before the site launch, I got the opportunity to attend my first DrupalCon in Munich. This gave me a taste of what a DrupalCon is like. I got to meet members of the Drupal Association, whom I was working with putting on the DrupalCon together, as well as the organizers of DrupalCon Munich. The one...
A DrupalCon is one of the biggest events on any Drupal developer's calendar, and in February 2013, it came to Sydney for the very first time. We've had numerous DrupalCamps and Drupal Downunder events in previous years, and even some Drupal South events across the ditch, but we haven't really seen anything that covers the scale and gravitas of an official event. Now that I've actually been to one, I'd like to share my impressions of it.
CrossFunctional was one of the platinum sponsors for DrupalCon Sydney 2013, so we had a lot to do in the leadup to the event; writing things, preparing marketing material and other such stuff. It was a lot of hard work, but it was pleasing to see it all come together on the day.
One of the neat things about any major Drupal get-together was being able to meet up with Drupal developers, business owners and hackers from all over the place. According to the closing plenary, about 20% of attendees were from overseas, from places including Japan, Scandinavia, India and of course America and New Zealand. I was even able to meet some...
DrupalCon Sydney 2013 is now over! We had a fantastic time, and we'll be talking about that really soon, but first there's an important matter we'd like your help with.
The Drupal Association is looking for feedback on the sessions presented at DrupalCon Sydney 2013, and are encouraging you to submit it via the web. We understand that there are some issues with the submission form on the DrupalCon site, so we decided to help out by reminding people about a different approach for your feedback.
We've got a rating system already in place on the DrupalCon Sydney 2013 Mobile App. The data goes to the Drupal Association and the feedback is critical for the DA so that they have a better idea of what sessions people want to see, and what feedback to give to presenters. We really appreciate the many of you...
Since we announced and released the DrupalCon Sydney 2013 Guide a few weeks ago, we've seen quite a few people download it and give us feedback for it. Thank you, we really appreciate it! However, we decided that we weren't done with the app yet, and so we'd like to let you know about the update we've prepared for it.