News aggregator

Australia's Direct Action fund may need $1bn more to meet emissions target

Datablog (the Guardian)1 hour 44 min ago



Breakdown of initial auction results shows fund’s biggest beneficiaries, as well as funding shortfall if price per tonne of emissions reduction stays at $13.95

The Australian government’s Direct Action emissions reduction fund could require up to $1bn of extra funds to meet its carbon emissions reduction goal, according to a Guardian Australia analysis based on initial auction results.

The results of the first Direct Action auction, revealed last week, showed emissions reduction contracts worth $660.4m had been awarded to prevent 47m tonnes of greenhouse gases entering the atmosphere.

Continue reading...

Conference Report: CHI 2015

EagerEyes.org3 hours 13 min ago



Last week, I had the pleasure of attending the CHI 2015 conference in Seoul, South Korea. CHI technically stands for Computer-Human Interaction, but it has become a name rather than an acronym in recent years. And CHI’s scope is very broad, it covers many areas that are not strictly part of HCI (Human-Computer Interaction – why use one acronym when you can have two?).

Below, I talk about a few papers that I found particularly interesting. CHI has 15 parallel tracks, so there is obviously no way to see them all. I mostly went to the visualization sessions, but even from those I’m only picking out less than half the papers here, to focus on the really interesting ones.

Visualization and Interactions

There were a few classic visualization papers (that would have fit InfoVis just as well) that presented new techniques or systems for data visualization. Statsplorer: Guiding Novices in Statistical Analysis by Chat Wacharamanotham, Krishna Subramanian, Sarah Theres Völkel, and Jan Borchers is a system that helps people with statistical analysis when performing experiments. It guides them through the entire process from planning to reporting, and helps avoid overtesting and other common mistakes. It’s web-based and open source.

Investigating the Direct Manipulation of Ranking Tables for Time Navigation by Romain Vuillemot and Charles Perin is a pretty straight-forward JavaScript library that provides interaction for working with rankings in tables by different criteria, especially when they change over time. They have some nice initial interactions, and the idea is for other people to contribute more. It’s not an earth-shattering new revelation, but it’s nice to see some new ideas about interaction in an area that doesn’t get a lot of love.

Dynamic Opacity Optimization for Scatter Plots by Justin Matejka, Fraser Anderson, and George Fitzmaurice presents a very interesting and fairly straight-forward metrics to choose the opacity for scatterplots to make them the most readable. Scatterplots often suffer from overplotting, and it can be difficult to find a good opacity level to see the data, especially when also zooming, filtering, etc. While the talks at CHI were generally pretty good, this was perhaps the best research talk I saw there. Very well done.

Following transitions is difficult, particularly when many points are moving. This is well known and documented, and even the very clever staging method doesn’t seem to work as well as previously assumed. The paper Trajectory Bundling for Animated Transitions (PDF) by Fan Du, Nan Cao, Jian Zhao, and Yu-Ru Lin proposes a technique that groups points that belong to the same class by moving them along bundled paths. This is basically taking the idea of edge bundling and applying it to motion paths. They argue that this works because of the gestalt law of common fate, but I think it mostly just reduces the number of targets you need to track (since each group essentially merges into one). There’s also a short video, though you’ll have to watch the important part a few times to get it.

Putting Science Into Infographics

Several papers dealt with issues in information graphics, attempting to generate some science around common assumptions. Infographic Aesthetics: Designing for the first Impression by Lane Harrison, Katharina Reinecke, and Remco Chang looked into quick aesthetic judgments of information graphics. Their most important finding is that people’s judgments are quite consistent and also vary over a large range (just because it’s an infographic doesn’t mean people like it). They also found some interesting gender differences (women respond stronger to color and prefer lower complexity, men prefer higher complexity but don’t respond much to color).

Another challenge is that there are commonly distortions to axes, etc. in the charts used in information graphics. Those are often considered to be bad, but do people actually get confused by them, or are they able to see through those? How Deceptive are Deceptive Visualizations? An Empirical Analysis of Common Distortion Techniques by Anshul Vikram Pandey, Katharina Rall, Margaret L Satterthwaite, Oded Nov, and Enrico Bertini reported on some experiments that showed that people actually misread the data, and just the way you’d expect. This means that it is possible to misdirect people’s understanding of data by choosing the kind of skewed representation that suits your purpose. There doesn’t appear to be a webpage for the paper, but Enrico Bertini has written about it in one of his rare blog postings.

Our paper, ISOTYPE Visualization – Working Memory, Performance, and Engagement with Pictographs is of course also worth a mention here. We looked at the ISOTYPE technique and found that is sometimes used in infographics as well, and found it to be quite effective (and never harmful) in presenting data.


An entire session was devoted to storytelling, though not all the papers really fit the theme. It started out with a bang though, with the paper Storytelling in Information Visualizations: Does it Engage Users to Explore Data? by Jeremy Boy, Jean-Daniel Fekete, and Francoise Detienne looking into whether stories actually lead to more engagement. They measured time and number of interactions in an interactive visualization that was either preceded by a short story or presented by itself. In both metrics, people were less engaged (i.e., spent less time and interacted less) after having seen the story. It’s an important study, but also easy to criticize: they did not measure memory or understanding, so it’s not clear if people learned more from the story (they probably did). But they certainly did answer the question, at least for a small set of stories. In addition to the paper, they also made the stories they used available online, which is great. I see more studies coming out of this.

I really liked Boy’s final slide too, where he asked whether information visualization should really be

  • a medium for communication and persuasion (traditional narrative vis approach)
  • a tool for exploration and analysis (traditional infovis approach)
  • a (data-agnostic) social object for triggering discussions and debate

Understanding Data Videos: Looking at Narrative Visualization through the Cinematography Lens by Fereshteh Amini, Nathalie Henry Riche, Christophe Hurter, Bongshin Lee, and Pourang Irani looked at the narrative structure of data videos. They used ideas from film and comic theory to analyze existing videos and to come up with guidelines for the design of the narrative arc of such videos.

Overall Impressions

CHI is a large conference (almost 3000 attendees), but it follows the standard format: there are keynotes, paper sessions, panels, posters, as well as an exhibition area for companies and an art show. This was my first time at CHI, so I wasn’t sure what to expect.

I found the quality of the visualization papers quite good. I was a bit underwhelmed at first (perhaps partly because last year’s InfoVis had upped my expectations quite a bit), but I saw some really good ones.

It’s still a bit unclear to me what gets accepted and why, and the extreme breadth of the conference can be a challenge. CHI is definitely a conference to follow if you’re interested in visualization, and will stay on my radar for publishing papers in the future.


11 Things About The Apple Watch That May Surprise You

Read/Write WebSun, 04/26/2015 - 19:22



Apple’s much anticipated new smartwatch has finally landed at its ultimate destination: on the arms of consumers. 

See also: There's Gold On Them Thar Wrists

As the earliest adopters get busy binding their wrists, practicing their “force touches” and updating their iPhone apps to work with the wearable, we took stock of a few interesting details that have clocked in with the Apple Watch’s arrival.

Your MagSafe charger can rat out your cheapskate purchase

Not that there’s anything wrong with picking up the Sport, the least expensive version of the Apple Watch. But if you’re touchy about it—maybe if you've even swapped out watchbands to hide that fact—then don’t plan on powering up on the go. Whipping out the plastic magnetic charger will be a dead giveaway. 

By contrast, the mid-range and super-special (read: pricey) versions of the Apple Watch—branded, confusingly, as the Apple Watch and the Apple Watch Edition—both come with metallic chargers. Fortunately, all of them work pretty fast, so the difference is really just skin deep.

Your MagSafe charger may power other devices ...

According to an Apple Insider reader named Albert Lee, an Apple Watch charger worked on his Moto 360 smartwatch, since both use the Qi wireless charging standard. Mashable confirmed this with its own tests

That’s actually a much bigger deal than it seems. Qi, the most popular among mobile makers, is just one of three wireless charging standards that’s trying to dominate the gadget world. Over the past year, the other two—the newer PowerMat and latest Rezence standards—have joined forces, making it easier for manufacturers to support both in one product.

See also: How Starbucks Could Take Wireless Charging Mainstream

At some point, the industry has to decide on one path to move forward, if it hopes to see wireless charging become as common as micro USB cables. If Apple has thrown its weight behind Qi, that could tip the scales back in its favor.

Or at least it would, if not for the following.

... but the Apple Watch can’t use other random Qi chargers (at least, so far)The Apple Watch can't receive power from other Qi chargers that aren't designed explicitly for the watch—at least not yet.

According to Mashable’s tests, the reverse scenario—with other Qi chargers sending power to the Apple Watch—doesn’t work. Now, the site only tried two charging products, and it's not clear whether the problem comes from a technical issue or if incompatible physical designs got in the way.

We don’t know which version of Qi the test chargers use, and that matters. Older versions can be notoriously fussy, forcing users to place devices on just the right spot on mats. But last year, an update brought support for a different, and much more flexible type of charging called resonance charging, which can send power from a farther distance. It’s possible the Apple Watch may eventually work with newer Qi products. If so, then these chargers could succeed in zinging the juice where others failed. 

We've already spotted third-party charging products designed for the watch—like docks and batteries (see below)—so charging doesn't look like an Apple-only scenario. 

The watch could be the beginning of Apple’s wireless charging assault

It has been a good year for Qi, which also saw IKEA pack the standard into its furniture. For Apple, stepping into wireless charging could have major implications across the company's entire portfolio of products. Take that new MacBook with just one port, for instance. If its watch experiment proves successful, an upcoming model of the laptop could boast wireless charging too, making that single port more reasonable and less aggravating. Along the way, the iPhones and iPads could get some Qi support too.

See also: How The New Apple MacBook Retired Steve Jobs’s Vision Of Computing

Apple’s tack may be "far from innovative compared with other wireless charging technologies currently in production or development,” as IHT analyst Ryan Sanderson put it in a press statement he sent me, back when Apple first announced the watch. But it doesn’t need to be innovative. Apple products tend to boost companies, tech standards and even whole industries, when they adopt them. And wireless charging, which has been on the brink of mainstream adoption for ages, could use a nudge in the right direction.

Finally, a justification for that confusing Digital Crown: underwater use!

The Apple Watch’s water-resistance comes as no surprise; it’s listed as a feature. But when FoneFox put it through a water torture test—showering and swimming with it, dunking it in a bucket—it discovered that the touchscreen couldn’t handle the waterboarding.

Fortunately, the "digital crown"—the little click wheel on the side—does, which may justify the addition of this feature. But don’t take that as a cue to try dunking the watch yourself. 

The watch could measure your blood oxygen levels (but it won’t)

When iFixit autopsied the 38mm Apple Watch, it found that the heart-rate monitor could measure more than beats per minute—it could measure blood oxygen. The approach, known to doctors as pulse oximetry, helps them ensure patients have adequate oxygen levels during surgery (or any other time they're under sedation), as well as while they’re taking lung medications or physically exerting themselves.

Naturally, that conjures certain activities—like rock climbing or, given its water tolerance, some light scuba diving. But stop right there. iFixit speculates that Apple stayed mum about this sensor due to federal regulations. Measuring oxygen levels in the blood skirts the line between quantified fitness and health, and the U.S. Food & Drug Administration can be rather particular when it comes to approving health equipment.

At this point, we don’t know whether the sensor will wind up as ResearchKit fodder for Apple's medical research initiative, or a tool to please extreme athletes. All we know for now is that it’s there, lying dormant until Apple’s ready and able to flip the switch.

Some parts are easy to replace ...

Batteries have a shelf life, often measured in the number charges they'll take throughout their life before they act up or even go completely dead. The Apple Watch’s lifespan too will eventually run out, which may spur some users to try swapping the battery on their own.

There’s good news and bad news there. The battery is relatively easy to replace, in and of itself; it's only attached with a bit of adhesive, making it easy to pop out. But you have to get to it first. The screen stands in the way. Apply heat to loosen the glue holding it down, and then unhook the display cable. The latter may be a bit tricky, judging by iFixit’s teardown.

When the site tore into the 38mm watch, it found a 205 mAh battery. The larger watch probably boasts a bigger battery, which may or may not affect how easy it is to dig the power cell out. Other parts, like the cables, speaker, buttons and the "Taptic Engine” (which deals vibration alerts) can challenge the far-sighted, with their small size and itty bitty screws, but don’t seem impossible to pluck out. The watch’s processor, however, looks like it’s practically a permanent fixture. (See below.)

Note that messing with the watch’s guts will void the warranty. This stuff is not for the faint of heart—or the poorly sighted. (There’s a reason watchmakers use a loupe.)

... but others, not so much

The Apple Watch runs off a fancy hardware nugget called the S1, which packs a processor, wireless radios, memory and sensors into one “system on a chip.” Though teensy, the technology is powerful. Apparently, so is the glue holding it together.

Few Apple Watch owners will ever stare into that wee abyss, and that’s a good thing, judging by iFixit’s experience trying to pull it apart: 

Despite rumors (and hopes) of an upgradable product, the difficulty of removing the S1 alone casts serious doubt on the idea of simply swapping out the internals.

Unfortunately, our first look is obstructed—that S1-emblazoned silver cap isn't a cap at all. It's a solid block of plasticky resin, hiding treasures deep within.

The fully encased S1 system makes board-level repairs impossible.

Just like regular watches, the straps will get nastyApple Watch straps may not ever get this nasty (unless you throw one into a campfire), but they won't look pretty forever

Even the majestic halo of Apple gadgetry can’t ward off the realities of simple chemistry. Users wear these gadgets next to their skin, which means grossness will force touch them over time—especially the straps. You can clean off metal, but you can’t bring back leather and fluoroelastomer watch bands back from discoloration and warping. 

There are already thousands of apps for the watch

Watch users can do a tremendous number of things from their wrists already. They can unlock Starwood hotel doors, read New York Times news headlines, shop, navigate the outdoors, check into Foursquare locations, stay on top of Expedia reservation updates, track packages, and many, many other things.

If that’s not enough, the IFTTT service (short for “If This Then That”) just integrated the Do Button and Do Note apps for the Apple Watch, giving users access to as many as 170 more apps. According to an IFTTT rep, "people can easily run their favorite recipes with just one tap, right from their wrist.”

It’s not clear yet how many of these features qualify as genuinely useful, or whether people really want to do that much from their wrists, but kudos to app developers for busting out their creativity caps. 

There are already a lot of accessories, and tons more are on the wayApple Watch Spigen armor case

Accessories makers have been licking their chops, waiting for the Apple Watch to hit the market. Now that it has, you should brace yourself for the new and incoming spate of fashion bands, battery bands, strap adapters, stands, power stations, portable batteries, bumper cases, and even a chunky suit of armor that also happens to hide the fact that you got the cheapest Apple Watch available. That’s just for starters.

I haven’t yet seen a skin that can disguise lower-priced Apple Watch models as one of its higher priced siblings, but as with all things watch-related, it’s just a matter of time. 

Lead photo by Shinya Suzuki; Apple Watch products and MacBook images courtesy of Apple; teardown photos screen captured from YouTube video by iFixit; photo of plastic MagSafe charger captured from YouTube video by TheMacintosh1; photo of MagSafe charging Moto 360 captured from YouTube video by Albert Lee; broken watch strap photo by theilr; Spigen armor case photo courtesy of Spigen

Google Maps Edits Cause Embarrassment

The Map RoomSun, 04/26/2015 - 19:00


Some embarrassment for Google Maps last week, as they were forced to apologize for an image of the Android mascot peeing on an Apple logo that turned up on the map near Rawalpindi in Pakistan. To say...

(Click through to read the entire post.)

DrupalOnWindows: Benchmarking Drupal 8 on PHP 7-dev

Planet DrupalSun, 04/26/2015 - 15:00



Bert Boerland: DrupalJam 2015, come for the Jam, stay for Drupal

Planet DrupalSun, 04/26/2015 - 07:22



Drupal. I didnt come to Drupal code 14 years ago, I came for the community and stayed for the functionality. That is part why I never liked the "Come for the code, stay for the community" slogan. Sure, it is a perfect cheesy slogan. If all you want attract are coders in the community, it is even a perfect slogan. For a perfect community, of perfect happy coders.

We have got to learn to address humans. Not just humans who can code. That is, if we want to be a true community for a product. A product that is well designed and does attract both the business and the user to participate in the product, the process and hence the community.

Leaderers. Entrepeneurs. Visionaries. Testesters. Document writers. Project Managers, marketeers. To name just a few. Of course developers can also have the skills to do these jobs, an often overlooked fact. But someone who is "just" a marketeer, will not come for the code. (S)He might come for the job at hand, money that might be involved, the functionality, but the best reason why an external non developer should come to the community to help out, is the community that is helping her/him out. Not clean lines of code, but helping hands of love.

This is I am active in the Drupal community, to help out to get others on board. With a rocking team ( Marja, Imre, Rolf and Peter and others) we are organising the DrupalJam event in the low lands. The DrupalJam started with 20+ persons and pizzas in a room and is now a big event with over 300 people attending, over 25 sessions and a budget in the tens of thousands.

DrupalJam -organised by the Dutch Drupal foundation- will be held in Utrecht, April 30 and it really represents the helping hands -not just the lines of code- of the community. With keynotes from Bruce Lawson ( HTML fame), Marco Derksen (digital strategist, entrepreneur) and featured speakers like Jefrey Maguire (moustache fame, D8), Anton VanHouke (leading design agency in the NL, introduced scrum in to strategy and design), Stephan Hay (designer, writer) and Ben van 't Ende (Community Manager for the TYPO3 Asssociation).

And like last year, Dries will do a virtually Q-and-A. If you want to ask him nearly anything, do so at this form.

The event will be held in an old industrial complex as can be seen in these shots

I am really looking forward to this event, it has a long tradition and always strengthened the community and brought in new blood. People who "Come for the business and stay for the community" Those who come of the need for design and stay for the love. Or love the functional and stay for organising the next DrupalJam.

PS: Now this head has rolled, it is time we decide what we do the body. If you have 5 minutes of your spare time, read this post and if you have one minute more, see this one from 2008 as well.

Week-end Reading : The Steve Jobs Way

AnythingGeospatialSun, 04/26/2015 - 01:40


TweetA little week-end reading for you Apple enthusiasts… In The Steve Jobs Way, Jay Elliot gives the reader the opportunity of seeing Steve Jobs as only his closest associates have ever seen...

[[ This is a content summary only. Visit my website for full links, other content, and more! ]]

PhD defense: Semantic Resolution Framework for Integrating Manufacturing Service Capability Data

Planet RDFSat, 04/25/2015 - 17:57


Ph.D. Dissertation Defense A Semantic Resolution Framework for Integrating
Manufacturing Service Capability Data Yan Kang 10:00am Monday 27 April 2015, ITE 217b

Building flexible manufacturing supply chains requires availability of interoperable and accurate manufacturing service capability (MSC) information of all supply chain participants. Today, MSC information, which is typically published either on the supplier’s web site or registered at an e-marketplace portal, has been shown to fall short of interoperability and accuracy requirements. The issue of interoperability can be addressed by annotating the MSC information using shared ontologies. However, this ontology-based approach faces three main challenges: (1) lack of an effective way to automatically extract a large volume of MSC instance data hidden in the web sites of manufacturers that need to be annotated; (2) difficulties in accurately identifying semantics of these extracted data and resolving semantic heterogeneities among individual sources of these data while integrating them under shared formal ontologies; (3) difficulties in the adoption of ontology-based approaches by the supply chain managers and users because of their unfamiliarity with the syntax and semantics of formal ontology languages such as the web ontology language (OWL).

The objective of our research is to address the main challenges of ontology-based approaches by developing an innovative approach that is able to extract MSC instances from a broad range of manufacturing web sites that may present MSC instances in various ways, accurately annotate MSC instances with formal defined semantics on a large scale, and integrate these annotated MSC instances into formal manufacturing domain ontologies to facilitate the formation of supply chains of manufacturers. To achieve this objective, we propose a semantic resolution framework (SRF) that consists of three main components: a MSC instance extractor, a MSC Instance annotator and a semantic resolution knowledge base. The instance extractor builds a local semantic model that we call instance description model (IDM) for each target manufacturer web site. The innovative aspect of the IDM is that it captures the intended structure of the target web site and associates each extracted MSC instance with a context that describes possible semantics of that instance. The instance annotator starts the semantic resolution by identifying the most appropriate class from a (or a set of) manufacturing domain ontology (or ontologies) (MDO) to annotate each instance based on the mappings established between the context of that instance and the vocabularies (i.e., classes and properties) defined in the MDO. The primary goal of the semantic resolution knowledge base (SR-KB) is to resolve semantic heterogeneity that may occur in the instance annotation process and thus improve the accuracy of the annotated MSC instances. The experimental results demonstrate that the instance extractor and the instance annotator can effectively discover and annotate MSC instances while the SR-KB is able to improve both precision and recall of annotated instances and reducing human involvement along with the evolution of the knowledge base.

Committee: Drs. Yun Peng (Chair), Tim Finin, Yaacov Yesha, Matthew Schmill and Boonserm Kulvatunyou

Are These The Winners & Losers Of Google Mobilegeddon?

Search Engine LandSat, 04/25/2015 - 12:52


Was Reddit the biggest loser? Early results say yes, while TV Tropes and Entertainment Tonight are seen as winners. The post Are These The Winners & Losers Of Google Mobilegeddon? appeared first on Search Engine Land.

Please visit Search Engine Land for the full article.

A Dev From The Plains: Yeoman Generators for Drupal: What’s out there?

Planet DrupalSat, 04/25/2015 - 11:39









I’ve been hearing about Yeoman for quite some time now. Pretty much since the project took off, or soon after. As a tool born in the Javascript community, I came across this little gem when I was learning about Node.js and the different tools and frameworks available for it, either in my free time, or as part of my labs time at my company. Sadly, I didn’t really pay much attention to it. At the end of the day, Node.js was just something I was learning about, but not something I was going to be able to put in place or introduce in projects in the short term. Or, even if it was something I *could* do, it wasn’t in my plans, anyway.

The other reason why I didn’t look into it closer, was that I mistakenly thought it to be a tool only useful for Javascript developers. Some time ago I noticed that Yeoman was getting plenty of attention from other communities too, and in a closer look, I understood that it wasn’t a tool for Node.js, but instead, a tool built on top of Node.js, so I decided to give it a try and see if I could make something useful out of it for Drupal development.

Warming up…

So, what’s Yeoman then? It’s a code scaffolding tool. That is, it’s an utility to generate code for web apps. What’s the purpose of that? Well, the purpose is that developers save time by quickly generating the skeleton of the web apps they build, leaving more time for the important things, such as the most complex business logic of the app, integrations, testing, etc… In short: it’s a tool that should help developers deliver more quality in their apps. To get a better picture of what Yeoman can do, I’d point everyone at their site, which has some nice tutorials and a very good documentation for writing your own generators.

My plan was to write a few generators for the most common pieces of boilerplate code that I normally have to write in my projects. Unsurprisingly, I found that there are a few yeoman generators for Drupal already out there, so I thought I should review them and see if they’re of any use to me, before writing one that already exists. Yes, that can be a boring task if there are too many generators, but I was lucky that there aren’t *that* many for Drupal, so I just spent a couple of hours testing them and documenting my findings. Hopefully, this blog post will help other Drupal developers to find out in a matter of minutes whether the existing generators are useful for them or not. So, let’s get into it!

1.- Generator-drupalmodule

Github repository hereCreation date: Around 2 years ago.

Structure created:

module: |- drupalmodule.css |- |- drupalmodule.js |- drupalmodule.module |- package.json

This one scaffolds a basic structure for a simple module. Needs bower and a package.json file to download dependencies, but not a problem anyway since you’ll probably have drush. Creation is a bit unintuitive: you need to create the module folder first, cd into it, then execute yo drupalmodule.

The generator asks if you want JS and CSS files, but it doesn’t even add functions to add them to the page. It’s a generic purpose generator, and doesn’t have anything that is not in module_builder already.

2.- Generator-drupal-module

Github repository hereCreation date: Around 2 months ago. Latest commit about 2 weeks ago.

Structure created:

module: |- templates (if hook_theme chosen). |- |- drupal_module.install |- drupal_module.module

More neat than drupalmodule in the surface, but doesn’t do much more. It asks us if we want hook_theme(), hook_menu(), hook_permission() and hook_block_info / view implementations, which is nice, yet that doesn’t make it much of a gain compared to other simple scaffolding tools, like PhpStorm live templates. In contrast to the drupal-module generator, this one doesn’t ask us if we want a CSS or JS file.

3.- Generator-drupalentities

Github repository hereCreation date: 9 months ago. Latest commit about 6 months ago.

Structure created (“publisher” entity):

Views and license files are optional, based on the settings specified in the command-line.

module: |- views |- |- |- |- |- |- LICENSE.txt |- |- |- publisher.install |- publisher.module |- publisher.tpl.php |- publisher-sample-data.tpl.php |-

Generates a full drupal module for a custom entity, based on the structure proposed by the model module.

One issue I experienced is that if I select to “add bundles”, the Field API screen seems broken (doesn’t load). However, a general “fields” tab appears, but if you try to add a field, you get some errors and get redirected to a 404. So, bundles are offered on the plugin creation menu, but not really supported! Same for revisions. It’s asked on the command-line prompt, but doesn’t seem to do much. Not choosing bundles support, still lets you add bundles on the admin UI, and doesn’t seem to break anything, though.

In spite of the issues I had testing it (I didn’t bother much investigating what was the issue), it seems to me an useful generator. The only reason why I doubt I’ll be using it, is that it’s based, as mentioned, on the model project for Drupal, which is quite nice, but rather outdated now (4 years old), and doesn’t leverage some of the latest Entity API goodies. Also, I’ve developed some opinions and preferences around how to structure custom Entity Types, so starting to use the model approach would be, in a sense, a step backwards.

4.- Generator-ctools-layout

Github repository hereCreation date: 5 months ago. Latest commit about 14 days ago.

Structure created:

my_layout: |- admin_my_layout.css |- my_layout.css |- |- my_layout.png |- my-layout.tpl.php

Generates a ctools layout plugin folder structure, with all the files needed to get it to work out of the box. It makes no assumptions about how the content will be displayed, so there’s no styling by default (which is perfect), and it allows to specify as many regions as desired. It’s quite likely that I start using this in my projects. No cons or negative aspects to mention!

5.- Generator-gadget

Github repository hereCreation date: 1 month ago. Latest commit about 1 month ago.

This one, rather than a code generator for Drupal elements, is a yeoman generator to serve as an scaffolding tool for another repo from Phase 2. While I didn’t get to test it out, the grunt-drupal-tasks repo really looked interesting (check the features here), and I might try to give that a go, although I’m familiar with Gulp and not with Grunt. Long story short: very interesting project, but it’s not meant to scaffold any code for your drupal modules.

6.- Generator-drupalformat

Github repository hereCreation date: 6 months ago. Latest commit about 3 months ago.

Structure created:

drupalformat: |- includes |- js |- drupalformat.settings.js |- theme |- |- drupalformat.tpl.php |- drupalformat.api.php |- |- drupalformat.install |- drupalformat.module |- |- generator.json |- LICENSE.txt

This one is very specific, tailored to provide views and field formatters for jQuery plugins, and it’s based on the owlcarousel module. It’s very useful if what you’re looking for is to easily integrate other jQuery plugins with your Drupal site. Very interesting generator, as it’s focused to scaffold the most repetitive parts for a very specific task, instead of trying to be a very generic solution that covers many things. You can see another great example leveraging this generator in’s blog, for the jQuery Oridomi plugin. Not something that I have to pick up daily, but I’ll definitely have this plugin in mind if I have to integrate new Javascript libraries.

7.- Generator-drupal-component

Github repository hereCreation date: 6 months ago. Latest commit about 3 months ago.

Structure created:

drupal_component: |- ctools-content_types |- |- drupal_component.scss |- drupal_component.html.twig |- |- drupal_component.js |- drupal_component.module |- drupal_component.tpl.php |-

I found this one rather peculiar. The boilerplate code it produces is rather basic, yet offers options such as creating a views style plugin by default, or a ctools content_type plugin. The good thing is that each component can be generated individually, which is rather convenient. The only issue that keeps me from using it is that, again, none of the components offer any options particularly advanced that could benefit from having an interactive tool like Yeoman (e.g: asking whether the ctools content type plugin will need one or more settings forms). For my particular case, I can generate all of these easily with PhpStorm live templates or template files easily.

Is that all, folks?

Ye… no! There are indeed a few more generators thought around drupal projects in the Yeoman registry (click here and search by “Drupal”). Some of them are very interesting, to do things such as:

However, I decided to leave those out of an in-depth review because, as interesting as they are, they cover several aspects of Drupal development, and people often has very specific preferences about how to structure a theme, for example, or what tools to use in order to create a Headless Drupal. 

Since the goal of this article was to give a bird’s eye view of what generators Drupal developers can use right now without changing anything in the way they work, I preferred to describe mainly the generators done around drupal modules, and more specific components. Hope this blog post has saved you some time. Expect to see a new one on this topic as soon as I’ve written my first Yeoman plugin.

Google Maps Hack Shows Android Mascot Relieving Itself On Apple Logo

Search Engine LandFri, 04/24/2015 - 21:46


VentureBeat chronicles another episode in the sometimes delightful, sometimes cringe-worthy history of off-color, user generated content on Google Maps. The subject of the hack today is the image of an Android mascot urinating on an Apple logo. Here’s the image as it appeared earlier today...

Please visit Search Engine Land for the full article.
Subscribe to The Universal Pantograph aggregator