Newsfeeds

A2J Viewer

New Drupal Modules - 8 January 2019 - 12:51pm

This module integrates the Center for Computer-Assisted Legal Instruction' A2J Author Viewer 6 into Drupal, allowing for the delivery of standalone A2J interviews within Drupal websites. It requires the A2J Viewer library.

Categories: Drupal

Splash Damage is cutting monetization from its free-to-play game Dirty Bomb

Social/Online Games - Gamasutra - 8 January 2019 - 12:10pm

Dirty Bomb is going free-to-play, in the most literal interpretation of the term. Following an update next week, all monetization will be patched out of the game. ...

Categories: Game Theory & Design

Img Extended

New Drupal Modules - 8 January 2019 - 11:04am

The Image Extended module allows you to add files with extensions like eps, svg, pdf or tiff on your website fully integrated into the image module.
Instead of having a form with multiple fields, an image field and a file field for pdf, eps, tiff, svg, this functionality is integrated into one field.

If you upload a file, you can have a preview in the upload section as well as an image linked to the source in a new browser tab for each format.

You can choose which format is available, the size of the file, if private or public like the core image module.

Categories: Drupal

Come to GDC 2019 and learn to help more people find (and play!) your game

Social/Online Games - Gamasutra - 8 January 2019 - 10:45am

Knowing how to get your game in front of the people who will enjoy it most has never been more important, and if you want to sharpen your skills, GDC 2019 in March is the place to be! ...

Categories: Game Theory & Design

Entity Quicklook

New Drupal Modules - 8 January 2019 - 9:55am

Render an entity in a modal using views.

Categories: Drupal

Request info

New Drupal Modules - 8 January 2019 - 9:43am

This is a tiny helper to add request information to Drupal's status report. This is helpful to verify that Drupal is configured correctly; e.g., trusted reverse proxy addresses are configured correctly and HTTP headers are followed.

Categories: Drupal

Dries Buytaert: Refreshing the Drupal administration UI

Planet Drupal - 8 January 2019 - 8:20am

Last year, I talked to nearly one hundred Drupal agency owners to understand what is preventing them from selling Drupal. One of the most common responses raised is that Drupal's administration UI looks outdated.

This critique is not wrong. Drupal's current administration UI was originally designed almost ten years ago when we were working on Drupal 7. In the last ten years, the world did not stand still; design trends changed, user interfaces became more dynamic and end-user expectations have changed with that.

To be fair, Drupal's administration UI has received numerous improvements in the past ten years; Drupal 8 shipped with a new toolbar, an updated content creation experience, more WYSIWYG functionality, and even some design updates.

A comparison of the Drupal 7 and Drupal 8 content creation screen to highlight some of the improvements in Drupal 8.

While we made important improvements between Drupal 7 and Drupal 8, the feedback from the Drupal agency owners doesn't lie: we have not done enough to keep Drupal's administration UI modern and up-to-date.

This is something we need to address.

We are introducing a new design system that defines a complete set of principles, patterns, and tools for updating Drupal's administration UI.

In the short term, we plan on updating the existing administration UI with the new design system. Longer term, we are working on creating a completely new JavaScript-based administration UI.

The content administration screen with the new design system.

As you can see on Drupal.org, community feedback on the proposal is overwhelmingly positive with comments like Wow! Such an improvement! and Well done! High contrast and modern look..

Sample space sizing guidelines from the new design system.

I also ran the new design system by a few people who spend their days selling Drupal and they described it as "clean" with "good use of space" and a design they would be confident showing to prospective customers.

Whether you are a Drupal end-user, or in the business of selling Drupal, I recommend you check out the new design system and provide your feedback on Drupal.org.

Special thanks to Cristina Chumillas, Sascha Eggenberger, Roy Scholten, Archita Arora, Dennis Cohn, Ricardo Marcelino, Balazs Kantor, Lewis Nyman,and Antonella Severo for all the work on the new design system so far!

We have started implementing the new design system as a contributed theme with the name Claro. We are aiming to release a beta version for testing in the spring of 2019 and to include it in Drupal core as an experimental theme by Drupal 8.8.0 in December 2019. With more help, we might be able to get it done faster.

Throughout the development of the refreshed administration theme, we will run usability studies to ensure that the new theme indeed is an improvement over the current experience, and we can iteratively improve it along the way.

Acquia has committed to being an early adopter of the theme through the Acquia Lightning distribution, broadening the potential base of projects that can test and provide feedback on the refresh. Hopefully other organizations and projects will do the same.

How can I help?

The team is looking for more designers and frontend developers to get involved. You can attend the weekly meetings on #javascript on Drupal Slack Mondays at 16:30 UTC and on #admin-ui on Drupal Slack Wednesdays at 14:30 UTC.

Thanks to Lauri Eskola, Gábor Hojtsy and Jeff Beeman for their help with this post.

Categories: Drupal

Refreshing the Drupal administration UI

Dries Buytaert - 8 January 2019 - 8:20am

Last year, I talked to nearly one hundred Drupal agency owners to understand what is preventing them from selling Drupal. One of the most common responses raised is that Drupal's administration UI looks outdated.

This critique is not wrong. Drupal's current administration UI was originally designed almost ten years ago when we were working on Drupal 7. In the last ten years, the world did not stand still; design trends changed, user interfaces became more dynamic and end-user expectations have changed with that.

To be fair, Drupal's administration UI has received numerous improvements in the past ten years; Drupal 8 shipped with a new toolbar, an updated content creation experience, more WYSIWYG functionality, and even some design updates.

A comparison of the Drupal 7 and Drupal 8 content creation screen to highlight some of the improvements in Drupal 8.

While we made important improvements between Drupal 7 and Drupal 8, the feedback from the Drupal agency owners doesn't lie: we have not done enough to keep Drupal's administration UI modern and up-to-date.

This is something we need to address.

We are introducing a new design system that defines a complete set of principles, patterns, and tools for updating Drupal's administration UI.

In the short term, we plan on updating the existing administration UI with the new design system. Longer term, we are working on creating a completely new JavaScript-based administration UI.

The content administration screen with the new design system.

As you can see on Drupal.org, community feedback on the proposal is overwhelmingly positive with comments like Wow! Such an improvement! and Well done! High contrast and modern look..

Sample space sizing guidelines from the new design system.

I also ran the new design system by a few people who spend their days selling Drupal and they described it as "clean" with "good use of space" and a design they would be confident showing to prospective customers.

Whether you are a Drupal end-user, or in the business of selling Drupal, I recommend you check out the new design system and provide your feedback on Drupal.org.

Special thanks to Cristina Chumillas, Sascha Eggenberger, Roy Scholten, Archita Arora, Dennis Cohn, Ricardo Marcelino, Balazs Kantor, Lewis Nyman,and Antonella Severo for all the work on the new design system so far!

We have started implementing the new design system as a contributed theme with the name Claro. We are aiming to release a beta version for testing in the spring of 2019 and to include it in Drupal core as an experimental theme by Drupal 8.8.0 in December 2019. With more help, we might be able to get it done faster.

Throughout the development of the refreshed administration theme, we will run usability studies to ensure that the new theme indeed is an improvement over the current experience, and we can iteratively improve it along the way.

Acquia has committed to being an early adopter of the theme through the Acquia Lightning distribution, broadening the potential base of projects that can test and provide feedback on the refresh. Hopefully other organizations and projects will do the same.

How can I help?

The team is looking for more designers and frontend developers to get involved. You can attend the weekly meetings on #javascript on Drupal Slack Mondays at 16:30 UTC and on #admin-ui on Drupal Slack Wednesdays at 14:30 UTC.

Thanks to Lauri Eskola, Gábor Hojtsy and Jeff Beeman for their help with this post.

Categories: Drupal

All the ways of doing a beta - by Joost van Dongen

Gamasutra.com Blogs - 8 January 2019 - 7:10am
There are many different ways to give players access to a beta. Which to choose? In this article I'll give a comprehensive list of options in today's market and discuss the differences.
Categories: Game Theory & Design

Scanning the Iconic Treasury Al-Khazneh of Petra - by Joseph Azzam

Gamasutra.com Blogs - 8 January 2019 - 7:09am
I needed to give a presentation in Jordan on Photogrammetry, and I challenged myself to scan the iconic treasury Al-Khazneh of Petra, put it in a game engine, and prepare a presentation, all in the span of 3 days.
Categories: Game Theory & Design

An Artifact Card Review - by James Margaris

Gamasutra.com Blogs - 8 January 2019 - 7:02am
20 pages of thoughts on Artifact cards that begin with the letter 'A'
Categories: Game Theory & Design

Direction Tools For Your Game's Dialogues - by Pietro Polsinelli

Gamasutra.com Blogs - 8 January 2019 - 7:01am
We present some concepts with which one can enrich the available toolset when writing and designing in-game dialogues, mostly inspired by comic design. In a linked video we also show the toolset in use.
Categories: Game Theory & Design

In VR boys learn best when the teacher is a drone -- girls lean better from virtual Marie

Virtual Reality - Science Daily - 8 January 2019 - 6:51am
The teacher is just as important in a virtual learning environment as in a normal classroom, but a new study shows that boys and girls differ greatly in terms of how they learn best: Boys learn best when their virtual teacher comes in the form of a drone, while girls get more knowledge from VR-teaching when they are taught by a young, female researcher-type named Marie.
Categories: Virtual Reality

Agiledrop.com Blog: Interview with Shawn McCabe, CTO of Acro Media

Planet Drupal - 8 January 2019 - 2:24am

This time we had a chat with none other than Shawn McCabe, the CTO of Acro Media. In our interview, the avid Drupal contributor talked about his most memorable Drupal moments, his love for open source and his reasons to opt for a more sustainable lifestyle. Have a read!

READ MORE
Categories: Drupal

Facebook Login REST

New Drupal Modules - 8 January 2019 - 1:13am

Facebook Login REST provides a rest resource for login with Facebook Token.

Categories: Drupal

Character Class: Multi-classing: Power Gamers, Part Four

RPGNet - 8 January 2019 - 12:00am
Should you power game?
Categories: Game Theory & Design

Commerce simplestock

New Drupal Modules - 7 January 2019 - 5:35pm

This is s simple field-based product stock implementation.
It has a order-type field to discern regular orders, supply, and stocktaking, so all stock changes are logged.
It intentionally does not prevent overbuying.
It was developed for a coop's self service shop and will not be extended.
For any more complex needs, go to commerce_stock.

Categories: Drupal

Video: How to encourage cooperative behavior during co-op play

Social/Online Games - Gamasutra - 7 January 2019 - 3:36pm

In GDC 2011 session, Ubisoft Toronto's Patrick Redding explores game mechanics that help encourage cooperative play for the benefit of other game developers. ...

Categories: Game Theory & Design

Migrate Process S3

New Drupal Modules - 7 January 2019 - 2:16pm
Categories: Drupal

Palantir: Federated Search: The Demo

Planet Drupal - 7 January 2019 - 12:57pm
Federated Search: The Demo brandt Mon, 01/07/2019 - 14:57 Ken Rickard and Avi Schwab Jan 7, 2019

See Palantir’s federated search application in action.

We recently published a blog post introducing our solution to Google Search Appliance being discontinued—an open source application we built and named Federated Search. If you haven’t already, we recommend checking out that first blog post to get the basics on how we built the application and why. Read on here to learn how you can see for yourself what the application does.

Search API Federated Solr is a complex application, and the best way to understand what's going on is to see it in action! Since the application requires a Solr instance in addition to a number of Drupal modules, we're not able to use Simplytest.me for demos. Instead, we've bundled all of the pieces together with Palantir's open source dev tools — the-vagrant and the-build — for a seamless demo experience that runs in a local virtual machine (VM) running on Vagrant. Head to GitHub to review the requirements, and then clone the repo and get started.

Setting up the environment

The-vagrant is a customizable vagrant environment that can be built into a project from scratch or easily retrofit an existing project (such as a new support client). On first setup, a handy install wizard takes users through a configuration process to choose hostnames, enable optional services like Solr, and enable further customization through Ansible tasks. The-vagrant is capable of handling single site, multi-site, or multiple-site (many docroot) setups in a single box, so it was a perfect match for our Federated Search environment.

The-build is a set of reusable phing targets for building Drupal projects. Once our VM is up and running, we use a standard set of these tasks to automate a number of complex tasks, such as:

  • Copying settings and services files into Drupal sites directories
  • Installing Drupal using an install profile and any existing config
  • Running post-install tasks like migrations
  • Running test suites
  • Importing databases from hosting environments
  • Deploying code to hosting environments

We have a shared set of phing targets that provide the foundation for many of these tasks, and each project extends them to meet their specific needs.

Building the demo

The Federated Search Demo repo builds a simulated multiple site environment, with a Solr server to boot, in the comfort of your own VM. Our demo site is expressly designed for both testing and development.

Because the application supports multisite, Domain Access, and standalone sites, we wanted to be able to demo (and develop for) all possible scenarios. To this end, the demo contains four docroots: Drupal 7 standalone, Drupal 7 Domain Access (coming soon), Drupal 8 standalone, Drupal 8 Domain Access. The D8 sites use the amazing core Umami profile to demo with real content, while the D7 site uses Devel Generate for some lorem ipsum-based content.

As of this writing, Domain Access is supported in the Drupal 7 module code, but not installed in the demo profile. The reverse is true for Drupal 8, and making the Drupal 8 version of Federated Search support Domain Access is under active development. We literally had to build the VM in order to finish those features!

There are a lot of dependencies involved, so let’s go to an application diagram:

There’s a lot going on there, but we suggest grabbing the repo and seeing for yourself.

What to expect

Once you clone the demo repo, there are full instructions on getting the VM and Drupal up and running. After installing all of the sites, you can start by visiting http://d8.fs-demo.local and use the search box to test a search (maybe try mushrooms, yum). You should see the React-powered search page with your results and a number of filters on the left side which you can experiment with.

Once you see the search results, you can dig in to how it works. In the Search App Settings (found at admin/config/search-api-federated-solr/search-app/settings) you can control a number of pieces of how the search page is displayed including it’s route and title. We set the page to default to ‘/search-app’ so as not to conflict with the default core configuration. Any changes made on this page should clear the cache for the search application and immediately be reflected on refresh.

Next, you may want to see how data is indexed. The search index field config page (found at admin/config/search/search-api/index/federated_search_index/fields) will show a list of all of the mapped fields the site is sending to the index. Clicking on Edit will show you the details of each, showing each bundle in the site and how it’s being sent to the index. The Edit modal includes a token picker, showing the true power of this tool—the ability to use tokens or text at the bundle level to send data to our index.

From this screen, try editing the config for a field, adding a token or changing a format. Once you do that, Search API will prompt you to re-index your data.

You can do so, then refresh the search results to see the changes. You might also want to inspect the raw data being sent to Solr. To do that, visit the Solr dashboard (at http://federated-search-demo.local:8983/solr/#/drupal8/query) and execute the default query. There you can see all of the fields being sent to the index.

Coming back to the search page, inspecting the results with the React Dev Tools will help you understand how the application is handling data. Once you install the browser extension, you can inspect the app, view the React components, see props being passed through the stack, and more. For an even deeper dive into the React application, you can clone that project and build it locally.

Contributing

In addition to providing a full demo environment, this repo also serves as a development environment for Search API Federated Solr and Search API Field Map. While those modules are installed by composer, the repo also links them into the ‘/src/’ directory for easy access. From there, you can add a GitHub remote or create patches for Drupal.org.

Issues for the demo can be raised on GitHub, and issues for the modules can be on either GitHub or Drupal.org. Be sure to read the handbook on Drupal.org for even more detail on how the system works.

Learn more about Federated Search in this presentation from Decoupled Days (or just view the slides).

Development Drupal Open Source
Categories: Drupal

Pages

Subscribe to As If Productions aggregator