Ofer Shaal shaal

Introduction

This is about documenting getting Linux running on the late 2016 and mid 2017 MPB's; the focus is mostly on the MacBookPro13,3 and MacBookPro14,3 (15inch models), but I try to make it relevant and provide information for MacBookPro13,1, MacBookPro13,2, MacBookPro14,1, and MacBookPro14,2 (13inch models) too. I'm currently using Fedora 27, but most the things should be valid for other recent distros even if the details differ. The kernel version is 4.14.x (after latest update).

The state of linux on the MBP (with particular focus on MacBookPro13,2) is also being tracked on https://github.com/Dunedan/mbp-2016-linux . And for Ubuntu users there are a couple tutorials (here and here) focused on that distro and the MacBook.

Note: For those who have followed these instructions ealier, and in particular for those who have had problems with the custom DSDT, modifying the DSDT is not necessary anymore - se

I have had a few requests for more information about using Lando with Drupal 8, the Emulsify theme and Gulp. In order to put what I've learned in one place, I'm adding my notes here.

My initial problem was reported here, but since then I have discovered a few additional things worth noting.

Once you have a working site on Lando and are ready to install Emulsify use the following directions instead of what has provided by the Emulsify developers. These instructions assume you have used Composer to install Drupal and that the root Drupal files are in the /web directory.

NOTE: To follow these instructions, you will need to run NPM commands from your host machine, which means you must have Node and NPM installed. Fortunately, they are installed together in one installation. If you wish to confirm you have them installed, run node -v and npm -v. To install, visit nodejs.org and follow the i

How to prepare for Drupal 9 Porting Weekend

If you haven't heard about it, there is an important event scheduled for May 22 & 23, 2020 to do mass porting of Drupal 8 modules and themes to Drupal 9.

The following a set of instructions will show you how to contribute to that effort.

For a more detailed detailed account please see Kristen Pol's blog post, Preparing yourself for Drupal 9 porting weekend.

1. Install Drupal 8 + Helper Modules

First thing to do, of course, is to install Drupal 8 - the recommended way is to use composer. For alternative setups, see @mradcliffe comment below.

Presentation Slides

https://docs.google.com/presentation/d/17Zpy5fZQsWsoZBhisA3rQiZy_JrK9MPR_HdgAisQ9XI/edit?usp=sharing

jQuery UI

Meta Issue: Remove jQuery UI components used by Drupal core and replace with a set of supported solutions
Tabbable: So close!
- Create AjaxCommand for focusing that does not require :tabbable selector
Autocomplete: ~80% done? It works and there are tests. The functionality needs to be moved to an NPM package similar to once() and needs heavy review.
- [Provide a new library to replace jQuery UI autocomplete}(https://www.drupal.org/project/drupal/issues/3076171) depends on (but not necessarily blocked by):
- Address jQuery UI position dependency
Dialog ~50% done? It works, but needs refactoring and test coverage.

	window.onload = function () {
	if (typeof history.pushState === "function") {
	history.pushState("jibberish", null, null);
	window.onpopstate = function () {
	history.pushState('newjibberish', null, null);
	// Handle the back (or forward) buttons here
	// Will NOT handle refresh, use onbeforeunload for this.
	};
	}
	else {

	<?php
	/**
	* Implements hook_theme_suggestions_HOOK_alter() for node.html.twig.
	*/
	function MYTHEME_theme_suggestions_node_alter(array &$suggestions, array $variables) {
	// Add template suggestions based on the current view mode.
	$node = $variables['elements']['#node'];
	$suggestions[] = 'node__' . $variables['elements']['#view_mode'];
	$suggestions[] = 'node__' . $node->bundle() . '__' . $variables['elements']['#view_mode'];
	}

	{% import _self as menus %}

	{#
	We call a macro which calls itself to render the full tree.
	@see http://twig.sensiolabs.org/doc/tags/macro.html
	#}
	{{ menus.menu_links(items, attributes, 0) }}

	{% macro menu_links(items, attributes, menu_level) %}
	{% import _self as menus %}

	{% import _self as menus %}

	{#
	We call a macro which calls itself to render the full tree.
	@see http://twig.sensiolabs.org/doc/tags/macro.html
	#}
	{{ menus.menu_links(items, attributes, 0) }}

	{% macro menu_links(items, attributes, menu_level) %}
	{% import _self as menus %}

	/**
	* Detects if two elements are colliding
	*
	* Credit goes to BC on Stack Overflow, cleaned up a little bit
	*
	* @link http://stackoverflow.com/questions/5419134/how-to-detect-if-two-divs-touch-with-jquery
	* @param $div1
	* @param $div2
	* @returns {boolean}
	*/

	<?php

	namespace Drupal\custom_commerce_recurring;

	use Drupal\commerce_order\Entity\OrderInterface;
	use Drupal\commerce_recurring\RecurringOrderManager as BaseRecurringOrderManager;
	use Drupal\commerce_recurring\RecurringOrderManagerInterface;
	use Drupal\Component\Datetime\TimeInterface;
	use Drupal\Core\Entity\EntityTypeManagerInterface;