Star Wars Battlefront 2 angespielt: Miese Story, teurer Multiplayer

heise online Newsticker - 16. November 2017 - 7:00
Star Wars Battlefront 2 bietet endlich wieder eine neue Story im bekannten Universum. Die Abenteuer einer Spezialagentin des bösen Imperiums sind aber viel zu kurz geraten, um länger im Gedächtnis zu bleiben.

PreviousNext: Reusable style guide components using field formatters and twig embed

Planet Drupal - 16. November 2017 - 4:32

At PNX, style guide driven development is our bag. It’s what we love: building a living document that provides awesome reference for all our front end components. And Drupal 8, with its use of Twig, complements this methodology perfectly. The ability to create a single component, and then embed that component and its markup throughout a Drupal site in a variety of different ways without having to use any tricks or hacks is a thing of beauty.

by Jack Taranto / 16 November 2017 Create a component

For this example we are going to use the much loved collapsible/accordion element. It’s a good example of a rich component because it uses CSS, JS, and Twig to provide an element that’s going to be used everywhere throughout a website.

To surmise the component it’s made up of the following files:

collapsible.scss collapsible.widget.js collapsible.drupal.js collapsible.twig collapsible.svg

The .scss file will end up compiling to a .css file, but we will be using SASS here because it’s fun. The widget.js file is a jQuery UI Widget Factory plugin that gives us some niceties - like state. The drupal.js file is a wrapper that adds our accordion widget as a drupal.behavior. The svg file provides some pretty graphics, and finally the twig file is where the magic starts.

Let’s take a look at the twig file:

{{ attach_library('pnx_project_theme/collapsible') }} <section class="js-collapsible collapsible {{ modifier_class }}"> <h4 class="collapsible__title"> {% block title %} Collapsible {% endblock %} h4> <div class="collapsible__content"> {% block content %} <p>Curabitur blandit tempus porttitor. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Praesent commodo cursus magna, vel scelerisque nisl consectetur et. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus.p> {% endblock %} div> section>

This is a standard-ish BEM based component. It uses a js-* class to attach the widget functionality. We also have a {{ modifier_class }} variable, that can be used by kss-node to alter the default appearance of the collapsible (more on this later). There are two elements in this component title and content. They are expressed inside a twig block. What this means is we can take this twig file and embed it elsewhere. Because the component is structured this way, when it’s rendered in its default state by KSS we will have some default content, and the ability to show it's different appearances/styles using modifier_class.

Our twig file also uses the custom Drupal attach_library function which will bring in our components CSS and JS from the following theme.libraries.yml entry:

collapsible: css: component: src/components/collapsible/collapsible.css: {} js: src/components/collapsible/collapsible.widget.js : {} src/components/collapsible/collapsible.drupal.js : {} dependencies: - core/jquery - core/drupal - core/jquery.once - core/jquery.ui - core/jquery.ui.widget

This is a pretty meaty component so it’s got some hefty javascript requirements. Not a problem in the end as it’s all going to get minified and aggregated by Drupal Cores library system.

And there we have it - a rich javascript component. It’s the building block for all the cool stuff we are about to do.

Use it in a field template override

As it stands we can throw this component as-is into KSS which is nice (although we must add our css and js to KSS manually, attach_library() won’t help us there sadly - yet), but we want drupal to take advantage of our twig file. This is where twigs embed comes in. Embed in twig is a mixture of the often used include, and the occasionally used extend. It’s a super powerful piece of kit that lets us do all the things.

Well these things anyway: include our twig templates contents, add variables to it, and add HTML do it.

Because this is an accordion, it’s quite likely we’ll want some field data inside it. The simplest way to get this happening is with a clunky old field template override. As an example I’ll use field--body.html.twig:

{% for item in items %} {% embed '@pnx_project_theme/components/collapsible/collapsible.twig' %} {% block title %} {{ label }} {% endblock %} {% block content %} {{ item.content }} {% endblock %} {% endembed %} {% endfor %}

Here you can see the crux of what we are trying to achieve. The collapsible markup is specified in one place only, and other templates can include that base markup and then insert the content they need to use in the twig blocks. The beauty of this is any time this field is rendered on the page, all the markup, css and js will be included with it, and it all lives in our components directory. No longer are meaty pieces of markup left inside Drupal template directories - our template overrides are now embedding much richer components.

There is a trick above though, and it’s the glue that brings this together. See how we have a namespace in the embed path - all drupal themes/modules get a twig namespace automatically which is just @your_module_name or @your_theme_name - however it points to the theme or modules templates directory only. Because we are doing style guide driven development and we have given so much thought to creating a rich self-contained component our twig template lives in our components directory instead, so we need to use a custom twig namespace to point there. To do that, we use John Albins Component Libraries module. It lets us add a few lines to our file so our themes namespace can see our component templates:

component-libraries: pnx_project_theme: paths: - src - templates

Now anything in /src or /templates inside our theme can be included with our namespace from any twig template in Drupal.

Use it in a field formatter

Now let’s get real because field template overrides are not the right way to do things. We were talking about making things DRY weren’t we?

Enter field formatters. At the simple end of this spectrum our formatter needs an accompanying hook_theme entry so the formatter can render to a twig template. We will need a module to give the field formatter somewhere to live.

Setup your module file structure as so:

src/Plugin/Field/FieldFormatter/CollapsibleFormatter.php templates/collapsible-formatter.html.twig pnx_project_module.module

Your formatter lives inside the src directory and looks like this:

<?php namespace Drupal\pnx_project_module\Plugin\Field\FieldFormatter; use Drupal\Core\Field\FieldItemListInterface; use Drupal\Core\Field\FormatterBase; use Drupal\Core\Form\FormStateInterface; /** * A field formatter for trimming and wrapping text. * * @FieldFormatter( * id = "collapsible_formatter", * label = @Translation("Collapsible"), * field_types = { * "text_long", * "text_with_summary", * } * ) */ class CollapsibleFormatter extends FormatterBase { /** * {@inheritdoc} */ public function viewElements(FieldItemListInterface $items, $langcode = NULL) { $elements = []; foreach ($items as $delta => $item) { $elements[$delta] = [ '#theme' => 'collapsible_formatter', '#title' => $items->getFieldDefinition()->getLabel(), '#content' => $item->value, '#style' => NULL, ]; } return $elements; } }

And the hook_theme function lives inside the .module file:

<?php /** * @file * Main module functions. */ /** * Implements hook_theme(). */ function pnx_project_module_theme($existing, $type, $theme, $path) { return [ 'collapsible_formatter' => [ 'variables' => [ 'title' => NULL, 'content' => NULL, 'style' => NULL, ], ], ]; }

Drupal magic is going to look for templates/collapsible-formatter.html.twig in our module directory automatically now. Our hook_theme template is going to end up looking pretty similar to our field template:

{% embed '@pnx_project_theme/components/collapsible/collapsible.twig' with { modifier_class: style } %} {% block title %} {{ title }} {% endblock %} {% block content %} {{ content }} {% endblock %} {% endembed %}

Now jump into the field display config of a text_long field, and you’ll be able to select the collapsible and it’s going to render our component markup combined with the field data perfectly, whilst attaching necessary CSS/JS.

Add settings to the field formatter

Let's take it a bit further. We are missing some configurability here. Our component has a modifier_class with a mini style (a cut down smaller version of the full accordion). You'll notice in the twig example above, we are using the with notation which works the same way for embed as it does for include to allow us to send an array of variables through to the parent template. In addition our hook_theme function has a style variable it can send through from the field formatter. Using field formatter settings we can make our field formatter far more useful to the site builders that are going to use it. Let's look at the full field formatter class after we add settings:

class CollapsibleFormatter extends FormatterBase { /** * {@inheritdoc} */ public function viewElements(FieldItemListInterface $items, $langcode = NULL) { $elements = []; foreach ($items as $delta => $item) { $elements[$delta] = [ '#theme' => 'collapsible_formatter', '#title' => !empty($this->getSetting('label')) ? $this->getSetting('label') : $items->getFieldDefinition()->getLabel(), '#content' => $item->value, '#style' => $this->getSetting('style'), ]; } return $elements; } /** * {@inheritdoc} */ public function settingsSummary() { $summary = []; if ($label = $this->getSetting('label')) { $summary[] = 'Label: ' . $label; } else { $summary[] = 'Label: Using field label'; } if (empty($this->getSetting('style'))) { $summary[] = 'Style: Normal'; } elseif ($this->getSetting('style') === 'collapsible--mini') { $summary[] = 'Style: Mini'; } return $summary; } /** * {@inheritdoc} */ public function settingsForm(array $form, FormStateInterface $form_state) { $form['label'] = [ '#title' => $this->t('Label'), '#type' => 'textfield', '#default_value' => $this->getSetting('label'), '#description' => t('Customise the label text, or use the field label if left empty.'), ]; $form['style'] = [ '#title' => t('Style'), '#type' => 'select', '#options' => [ '' => t('Normal'), 'collapsible--mini' => t('Mini'), ], '#description' => t('See Styleguide section 6.1 for a preview of styles.'), '#default_value' => $this->getSetting('style'), ]; return $form; } /** * {@inheritdoc} */ public static function defaultSettings() { return [ 'label' => '', 'style' => '', ]; } }

There's a few niceties there: It allows us to set a custom label (for the whole field), it automatically assigns the correct modifier_class, it links to the correct section in the style guide in the settings field description, and it adds a settings summary so site builders can see the current settings at a glance. These are all patterns you should repeat.

Let's sum up

We've created a rich interactive BEM component with its own template. The component has multiple styles and displays an interactive demo of itself using kss-node. We've combined its assets into a Drupal library and made the template - which lives inside the style guides component src folder - accessible to all of Drupal via the Component Libraries module. We've built a field formatter that allows us to configure the components appearance/style. Without having to replicate any HTML anywhere.

The component directory itself within the style guide will always be the canonical source for every version of the component that is rendered around our site.

Tagged Twig

Posted by Jack Taranto
Front end developer

Dated 16 November 2017

Add new comment

DrupalEasy: DrupalEasy Podcast 198 - Dave Hall - Drupal Distributions and Puppies

Planet Drupal - 16. November 2017 - 2:53

Direct .mp3 file download.

Dave Hall (skwashd), Managing Director, Dave Hall Consulting joins Mike Anello to talk about the current state of Drupal distributions and what the future may hold.

Interview DrupalEasy News Sponsors
  • Drupal Aid - Drupal support and maintenance services. Get unlimited support, monthly maintenance, and unlimited small jobs starting at $99/mo.
  • - devPanel.
Follow us on Twitter Subscribe

Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.

If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.

Bericht: Nächstes iPad mit "A11X" und acht Kernen

heise online Newsticker - 15. November 2017 - 21:30
Aus Asien kommen Meldungen, laut denen Apple seinem bislang schnellsten Chip zwei weitere Kerne spendiert.

Mediacurrent: Content as the Common Language of Web Development

Planet Drupal - 15. November 2017 - 21:21

If there’s one thing I learned while attending DrupalCon Baltimore 2017 this past spring, it’s that those of us involved in building the web are only getting more and more specialized in how we help build it. It boggles the mind to witness the sheer amount of new session tracks, new technologies, new design patterns, and new discussions that come up each year at DrupalCon.

UPS will seine Flotte in New York teilweise von Diesel- auf E-Antrieb umrüsten

heise online Newsticker - 15. November 2017 - 21:00
UPS will in Zusammenarbeit mit der staatlichen Energieforschungs- und Entwicklungsbehörde von New York einen Teil seiner Zustellfahrzeuge von Diesel- auf Elektroantrieb umrüsten. Den Umbau soll Unique Electric Solutions LLC planen und durchführen

Windows-VR im Vergleichstest: Lenovo leicht, HP im Robocop-Look

heise online Newsticker - 15. November 2017 - 20:00
Mit Acer, Dell, HP und Lenovo bringen die ersten Hersteller Brillen für Windows Mixed Reality auf den Markt. Während sie in puncto Software künftig gleichermaßen von Steam VR profitieren, offenbaren sich bei der Hardware kleine, aber feine Unterschiede.

Starcraft 2 ist jetzt kostenlos spielbar

heise online Newsticker - 15. November 2017 - 19:00
Starcraft 2 ist jetzt ein Free2Play-Titel. Blizzards Strategiespiel ist damit zu großen Teilen kostenlos spielbar, DLCs müssen allerdings noch gekauft werden.

Drupal blog: An update on the Layout Initiative for Drupal 8.4/8.5

Planet Drupal - 15. November 2017 - 18:39

This blog has been re-posted with permission from Dries Buytaert's blog. Please leave your comments on the original post.

Now Drupal 8.4 is released, and Drupal 8.5 development is underway, it is a good time to give an update on what is happening with Drupal's Layout Initiative.

8.4: Stable versions of layout functionality

Traditionally, site builders have used one of two layout solutions in Drupal: Panelizer and Panels. Both are contributed modules outside of Drupal core, and both achieved stable releases in the middle of 2017. Given the popularity of these modules, having stable releases closed a major functionality gap that prevented people from building sites with Drupal 8.

8.4: A Layout API in core

The Layout Discovery module added in Drupal 8.3 core has now been marked stable. This module adds a Layout API to core. Both the aforementioned Panelizer and Panels modules have already adopted the new Layout API with their 8.4 release. A unified Layout API in core eliminates fragmentation and encourages collaboration.

8.5+: A Layout Builder in core

Today, Drupal's layout management solutions exist as contributed modules. Because creating and building layouts is expected to be out-of-the-box functionality, we're working towards adding layout building capabilities to Drupal core.

Using the Layout Builder, you start by selecting predefined layouts for different sections of the page, and then populate those layouts with one or more blocks. I showed the Layout Builder in my DrupalCon Vienna keynote and it was really well received:

8.5+: Use the new Layout Builder UI for the Field Layout module

One of the nice improvements that went in Drupal 8.3 was the Field Layout module, which provides the ability to apply pre-defined layouts to what we call "entity displays". Instead of applying layouts to individual pages, you can apply layouts to types of content regardless of what page they are displayed on. For example, you can create a content type 'Recipe' and visually lay out the different fields that make up a recipe. Because the layout is associated with the recipe rather than with a specific page, recipes will be laid out consistently across your website regardless of what page they are shown on.

The basic functionality is already included in Drupal core as part of the experimental Fields Layout module. The goal for Drupal 8.5 is to stabilize the Fields Layout module, and to improve its user experience by using the new Layout Builder. Eventually, designing the layout for a recipe could look like this:

Layouts remains a strategic priority for Drupal 8 as it was the second most important site builder priority identified in my 2016 State of Drupal survey, right behind Migrations. I'm excited to see the work already accomplished by the Layout team, and look forward to seeing their progress in Drupal 8.5! If you want to help, check out the Layout Initiative roadmap.

Special thanks to Angie Byron for contributions to this blog post, to Tim Plunkett and Kris Vanderwater for their feedback during the writing process, and to Emilie Nouveau for the screenshot and video contributions.

Vive Focus: HTCs Standalone-VR-Brille kommt nicht nach Europa

heise online Newsticker - 15. November 2017 - 18:30
HTC hat eine Standalone-VR-Brille für den chinesischen Markt angekündigt. In Europa soll die Vive Focus allerdings nicht auf den Markt kommen – HTC hat Googles Daydream den Rücken zugekehrt.

Big Data in der Medizin: "Das Smartphone des Patienten ist das Stethoskop des 21. Jahrhunderts"

heise online Newsticker - 15. November 2017 - 18:30
Big Data, Künstliche Intelligenz und Virtual Reality sollen zukünftig die Medizin revolutionieren, lautet die Botschaft der Medizinmesse Medica. Dafür werden Daten gebraucht, Daten und noch mehr Daten. Agencies: Don't keep passwords in your wiki!

Planet Drupal - 15. November 2017 - 18:16

You spend so much time writing secure code, and doing security updates, but you're putting all of that in danger with your wiki. A huge percentage of agencies put passwords into wikis - and other shared resources!!!

Using a shared Google/Office document, spreadsheet - even with black text on a black background - isn't much better! So, think of "wiki" in this context as being any "low-cost, low-security, high-accessibility, super-convenient storage."

You are putting your agency AND your customers at risk by keeping passwords in your company wiki!

Read more to find out why, and a better way to do it!

iOS 11.2 erklärt neuen WLAN- und Bluetooth-Button – Abschalten weiterhin nicht möglich

heise online Newsticker - 15. November 2017 - 18:00
Seit iOS 11 lassen sich die beiden Funkverbindungen nicht mehr über das Kontrollzentrum deaktivieren, sondern nur unterbrechen. Um Nutzer nicht länger zu verwirren, weist das System künftig darauf hin – ändert aber nichts am neuen Verhalten.

Drupal Association blog: Q2 2017 Financial Statement Summary

Planet Drupal - 15. November 2017 - 17:32

The Drupal Association Board is responsible for the Drupal Association’s financial health and as part of their duty, they vote to approve monthly financial statements. The board met on September 23, 2017 at the board retreat that took place before DrupalCon Vienna and voted to approve the Q2 2017 financial statements that were prepared by our virtual CFO service, Summit CPA.

This blog walks you through our Q2 2017 Financials and how we performed against the two financial KPIs that we measure against each month:

  • Cash Reserve: Have a cash balance of 15-30% of Total Revenue

  • Net Income Profit Margin: End 2017 with a net income profit of 10%

Below is a summary of how we performed against our KPIs each month in the second quarter of 2017.

KPI Goal April May June Cash Reserve 15-30% 60% of goal 84% of goal 88% of goal Net Income Margin (NIM) % 10% 49.9% -29.8% -48.9%

The table above shows that Q2 was strong as a whole, due to the big income assist DrupalCon Baltimore gave.

With May and June below the KPI goal, we reviewed the entire quarter results as a whole. The quarter was buoyed by DrupalCon Baltimore which produced a majority of the $2,328,367 in April’s revenue and after its expenses, April landed $1,163,390 in net income. Following DrupalCon, May and June collectively accounted for $542,530 in revenue, producing a $214,711 net loss. When taken in total, we generated revenue of $2,870,897 and net income of $948,679. This equates to a NIM of 33.04% for the second quarter measuring above the net income margin goal.

You can see we did not achieve our cash reserve goal this quarter. The Drupal Association is still in its financial turn around so we did not meet our goal for the second quarter, however we are much closer to doing so than we have been in the past.

This chart below shows how cash reserves are building in Q2 and getting closer to hitting the cash reserve goal for this quarter.

Monthly Updates

April results toward our KPIs had us holding $1.2M in cash, which is 84% of the stated cash reserve goal.  Due to DrupalCon Baltimore reporting strong sales in both trainings and general conference tickets, we resulted in 49.9% of net income KPI.  Expenses for DrupalCon Baltimore came in lower, catering had significant savings of $50K.

For May, our cash reserve goal increased 11% through additional sales in Digital Sponsorships programs and DrupalCon ticket sales.  May expenses had DrupalCon Baltimore $15.8k less than forecasted, and IT had some savings in their budget as well, which helped cash reserves. 

June had costs from Baltimore which lowered net income by $70k than originally forecasted. This was seen in event production costs that were $100k higher than anticipated, along with an unanticipated $14k in professional expenses. Reducing the impact of those costs, income in other programs came in $55k higher, the majority being rebates from DrupalCon Baltimore. This impacted the cash reserve KPI, where we reached 88% of our goal.

We would not be able to do our mission-driven work without the support and contributions of our community. Contributions come in many forms, through the purchase of DrupalCon tickets and event sponsorships, through our Supporters and Members, sponsors, recruiters who post jobs on Drupal Jobs and many other fantastic ways our community supports the Drupal eco-system. We are deeply grateful for everyone who contributes their time, talent, and treasure to move Drupal forward.

Thank you!

File attachments:  june cash reserve.jpeg

Neue digitale Bibliothek über Picassos "Guernica"

heise online Newsticker - 15. November 2017 - 17:30
Pablo Picassos Bild, das nach dem deutschen Angriff aus die baskische Stadt Guernica entstand, ist nun Gegenstand einer umfangreichen Multmimediapräsentation im Internet.

SpotMini: Boston Dynamics zeigt neuen vierbeinigen Laufroboter

heise online Newsticker - 15. November 2017 - 17:30
Die mittlerweile zu Softbank gehörende Firma Boston Dynamics will zeigen, was in der Robotik steckt; nun mit einer neuen Version eines vierbeinigen Laufroboters.

Red Hat Enterprise Linux erscheint für ARM-Server

heise online Newsticker - 15. November 2017 - 17:00
RHEL 7.4 läuft künftig auch auf 64-Bit-ARM-Servern. Außerdem hat Red Hat einige Software sowie Werkzeuge portiert und will die Linux-Distribution auf möglichst vielen Architekturen und Plattformen zur Verfügung stellen.

Android-Verteilung: Nougat überholt Jelly Bean & Kitkat

heise online Newsticker - 15. November 2017 - 16:30
In der monatlichen Android-Statistik ist vom aktuellen Android 8 wenig zu sehen, und Android 7 schiebt sich gerade mal vom vierten auf den dritten Platz. Das am meisten verbreitete Android bleibt Marshmallow.

Donald Trump Jr. hatte während des Wahlkampfs Kontakt mit Wikileaks

heise online Newsticker - 15. November 2017 - 16:00
Trumps ältester Sohn tauschte sich während des Wahlkampfs mit Wikileaks aus – der Plattform, die gestohlene E-Mails aus dem Clinton-Lager veröffentlicht hatte.

iPhone X: Stiftung Warentest warnt vor Sturzempfindlichkeit

heise online Newsticker - 15. November 2017 - 16:00
In der Falltrommel der Warentester zeigte sich das iPhone X anfälliger für Sturzschäden als das iPhone 8, dessen Rückseite ebenfalls aus Glas ist. Die Reparatur ist sehr teuer.