Newsfeeds

Rainbow Massacre Card Game Up On Kickstarter

Tabletop Gaming News - 17 May 2018 - 3:00pm
It’s never good when a population is forced to the margins. In the case of horses, the Zebras, long having looked at the love and affection given to Unicorns, have finally snapped. They’ve picked up whatever weaponry they can find and are going on the warpath. Those multi-hued, single-horned horses haven’t got a chance when […]
Categories: Game Theory & Design

DGS Games Letting You Pick Next Freeblades Faction

Tabletop Gaming News - 17 May 2018 - 2:00pm
DGS Games is consistent with their Freeblades Kickstarter campaigns. Each one has had a new faction. Each one has been successful. Each one has been better than the last. And each one has been delivered to backers on time. Well, they’re looking to have a 7th, but they’re also looking for your help. They’ve got […]
Categories: Game Theory & Design

Daggers Card Game Up On Kickstarter

Tabletop Gaming News - 17 May 2018 - 1:00pm
You all know my love of “gaming backpack games.” They’re the ones you toss in your pack and carry with you, ready to be played at a moment’s notice. Well, Daggers is such a game. It’s a quick, two-player card game that’s easy to teach. It’s also up on Kickstarter now. From the Kickstarter: Daggers […]
Categories: Game Theory & Design

Imaginarium Board Game Up On Kickstarter

Tabletop Gaming News - 17 May 2018 - 12:00pm
Think of the things you can build in your dreams. The possibilities of fantastic creations unknown of before. Now, make those dreams a reality. That’s what you’ll be doing in Imaginarium, a new board game that’s up on Kickstarter. Create, fix, and dismantle wondrous machines in an effort to create ever-bigger and better creations. The […]
Categories: Game Theory & Design

Call of Duty: Black Ops 4 won't have a single-player campaign but will offer battle royale

Social/Online Games - Gamasutra - 17 May 2018 - 11:36am

The upcoming first-person shooter won't include a traditional single-player campaign, opting instead to deliver narrative exclusively through multiplayer experiences. ...

Categories: Game Theory & Design

Opinion: Can World of Warcraft 'stat squish' its XP levels?

Social/Online Games - Gamasutra - 17 May 2018 - 11:23am

Gamasutra contributor Katherine Cross checks in on the state of Blizzard's aging MMORPG titan and asks: 'Why not simply hit the reset button and make the new level cap...60 once again?' ...

Categories: Game Theory & Design

Thursday Terrain Corner

Tabletop Gaming News - 17 May 2018 - 11:00am
It’s the latter half of the week. Just another few days and we’ll be back to the weekend. As always, I can’t wait. I’ve got D&D coming up Saturday. Our last session was over a month ago, and it was just an introductory one. This’ll be the real “Session 1” where we can actually get […]
Categories: Game Theory & Design

Far Cry 5 and Assassin's Creed Origins lead to record profit and sales for Ubisoft

Social/Online Games - Gamasutra - 17 May 2018 - 11:00am

Ubisoft exceeded its own sales projections by 92 million euros (~$108.5 million), something that helped the company achieve both record sales and profitability for the fiscal year. ...

Categories: Game Theory & Design

Dries Buytaert: Working toward a JavaScript-driven Drupal administration interface

Planet Drupal - 17 May 2018 - 10:42am

As web applications have evolved from static pages to application-like experiences, end-users' expectations of websites have become increasingly demanding. JavaScript, partnered with effective user-experience design, enable the seamless, instantaneous interactions that users now expect.

The Drupal project anticipated this trend years ago and we have been investing heavily in making Drupal API-first ever since. As a result, more organizations are building decoupled applications served by Drupal. This approach allows organizations to use modern JavaScript frameworks, while still benefiting from Drupal's powerful content management capabilities, such as content modeling, content editing, content workflows, access rights and more.

While organizations use JavaScript frameworks to create visitor-facing experiences with Drupal as a backend, Drupal's own administration interface has not yet embraced a modern JavaScript framework. There is high demand for Drupal to provide a cutting-edge experience for its own users: the site's content creators and administrators.

At DrupalCon Vienna, we decided to start working on an alternative Drupal administrative UI using React. Sally Young, one of the initiative coordinators, recently posted a fantastic update on our progress since DrupalCon Vienna.

Next steps for Drupal's API-first and JavaScript work

While we made great progress improving Drupal's web services support and improving our JavaScript support, I wanted to use this blog post to compile an overview of some of our most important next steps:

1. Stabilize the JSON API module

JSON API is a widely-used specification for building web service APIs in JSON. We are working towards adding JSON API to Drupal core as it makes it easier for JavaScript developers to access the content and configuration managed in Drupal. There is a central plan issue that lists all of the blockers for getting JSON API into core (comprehensive test coverage, specification compliance, and more). We're working hard to get all of them out of the way!

2. Improve our JavaScript testing infrastructure

Drupal's testing infrastructure is excellent for testing PHP code, but until now, it was not optimized for testing JavaScript code. As we expect the amount of JavaScript code in Drupal's administrative interface to dramatically increase in the years to come, we have been working on improving our JavaScript testing infrastructure using Headless Chrome and Nightwatch.js. Nightwatch.js has already been committed for inclusion in Drupal 8.6, however some additional work remains to create a robust JavaScript-to-Drupal bridge. Completing this work is essential to ensure we do not introduce regressions, as we proceed with the other items in our roadmap.

3. Create designs for a React-based administration UI

Having a JavaScript-based UI also allows us to rethink how we can improve Drupal's administration experience. For example, Drupal's current content modeling UI requires a lot of clicking, saving and reloading. By using React, we can reimagine our user experience to be more application-like, intuitive and faster to use. We still need a lot of help to design and test different parts of the Drupal administration UI.

4. Allow contributed modules to use React or Twig

We want to enable modules to provide either a React-powered administration UI or a traditional Twig-based administration UI. We are working on an architecture that can support both at the same time. This will allow us to introduce JavaScript-based UIs incrementally instead of enforcing a massive paradigm shift all at once. It will also provide some level of optionality for modules that want to opt-out from supporting the new administration UI.

5. Implement missing web service APIs

While we have been working for years to add web service APIs to many parts of Drupal, not all of Drupal has web services support yet. For our React-based administration UI prototype we decided to implement a new permission screen (i.e. https://example.com/admin/people/permissions). We learned that Drupal lacked the necessary web service APIs to retrieve a list of all available permissions in the system. This led us to create a support module that provides such an API. This support module is a temporary solution that helped us make progress on our prototype; the goal is to integrate these APIs into core itself. If you want to contribute to Drupal, creating web service APIs for various Drupal subsystems might be a great way to get involved.

6. Make the React UI extensible and configurable

One of the benefits of Drupal's current administration UI is that it can be configured (e.g. you can modify the content listing because it has been built using the Views module) and extended by contributed modules (e.g. the Address module adds a UI that is optimized for editing address information). We want to make sure that in the new React UI we keep enough flexibility for site builders to customize the administrative UI.

All decoupled builds benefit

All decoupled applications will benefit from the six steps above; they're important for building a fully-decoupled administration UI, and for building visitor-facing decoupled applications.

Useful for decoupling of visitor-facing front-ends Useful for decoupling of the administration backend 1. Stabilize the JSON API module ✔ ✔ 2. Improve our JavaScript testing infrastructure ✔ ✔ 3. Create designs for a React-based administration UI ✔ 4. Allow contributed modules to use React or Twig ✔ ✔ 5. Implement missing web service APIs ✔ ✔ 6. Make the React UI extensible and configurable ✔ Conclusion

Over the past three years we've been making steady progress to move Drupal to a more API-first and JavaScript centric world. It's important work given a variety of market trends in our industry. While we have made excellent progress, there are more challenges to be solved. We hope you like our next steps, and we welcome you to get involved with them. Thank you to everyone who has contributed so far!

Special thanks to Matt Grill and Lauri Eskola for co-authoring this blog post and to Wim Leers, Gabe Sullice, Angela Byron, and Preston So for their feedback during the writing process.

Categories: Drupal

Working toward a JavaScript-driven Drupal administration interface

Dries Buytaert - 17 May 2018 - 10:42am

As web applications have evolved from static pages to application-like experiences, end-users' expectations of websites have become increasingly demanding. JavaScript, partnered with effective user-experience design, enable the seamless, instantaneous interactions that users now expect.

The Drupal project anticipated this trend years ago and we have been investing heavily in making Drupal API-first ever since. As a result, more organizations are building decoupled applications served by Drupal. This approach allows organizations to use modern JavaScript frameworks, while still benefiting from Drupal's powerful content management capabilities, such as content modeling, content editing, content workflows, access rights and more.

While organizations use JavaScript frameworks to create visitor-facing experiences with Drupal as a backend, Drupal's own administration interface has not yet embraced a modern JavaScript framework. There is high demand for Drupal to provide a cutting-edge experience for its own users: the site's content creators and administrators.

At DrupalCon Vienna, we decided to start working on an alternative Drupal administrative UI using React. Sally Young, one of the initiative coordinators, recently posted a fantastic update on our progress since DrupalCon Vienna.

Next steps for Drupal's API-first and JavaScript work

While we made great progress improving Drupal's web services support and improving our JavaScript support, I wanted to use this blog post to compile an overview of some of our most important next steps:

1. Stabilize the JSON API module

JSON API is a widely-used specification for building web service APIs in JSON. We are working towards adding JSON API to Drupal core as it makes it easier for JavaScript developers to access the content and configuration managed in Drupal. There is a central plan issue that lists all of the blockers for getting JSON API into core (comprehensive test coverage, specification compliance, and more). We're working hard to get all of them out of the way!

2. Improve our JavaScript testing infrastructure

Drupal's testing infrastructure is excellent for testing PHP code, but until now, it was not optimized for testing JavaScript code. As we expect the amount of JavaScript code in Drupal's administrative interface to dramatically increase in the years to come, we have been working on improving our JavaScript testing infrastructure using Headless Chrome and Nightwatch.js. Nightwatch.js has already been committed for inclusion in Drupal 8.6, however some additional work remains to create a robust JavaScript-to-Drupal bridge. Completing this work is essential to ensure we do not introduce regressions, as we proceed with the other items in our roadmap.

3. Create designs for a React-based administration UI

Having a JavaScript-based UI also allows us to rethink how we can improve Drupal's administration experience. For example, Drupal's current content modeling UI requires a lot of clicking, saving and reloading. By using React, we can reimagine our user experience to be more application-like, intuitive and faster to use. We still need a lot of help to design and test different parts of the Drupal administration UI.

4. Allow contributed modules to use React or Twig

We want to enable modules to provide either a React-powered administration UI or a traditional Twig-based administration UI. We are working on an architecture that can support both at the same time. This will allow us to introduce JavaScript-based UIs incrementally instead of enforcing a massive paradigm shift all at once. It will also provide some level of optionality for modules that want to opt-out from supporting the new administration UI.

5. Implement missing web service APIs

While we have been working for years to add web service APIs to many parts of Drupal, not all of Drupal has web services support yet. For our React-based administration UI prototype we decided to implement a new permission screen (i.e. https://example.com/admin/people/permissions). We learned that Drupal lacked the necessary web service APIs to retrieve a list of all available permissions in the system. This led us to create a support module that provides such an API. This support module is a temporary solution that helped us make progress on our prototype; the goal is to integrate these APIs into core itself. If you want to contribute to Drupal, creating web service APIs for various Drupal subsystems might be a great way to get involved.

6. Make the React UI extensible and configurable

One of the benefits of Drupal's current administration UI is that it can be configured (e.g. you can modify the content listing because it has been built using the Views module) and extended by contributed modules (e.g. the Address module adds a UI that is optimized for editing address information). We want to make sure that in the new React UI we keep enough flexibility for site builders to customize the administrative UI.

All decoupled builds benefit

All decoupled applications will benefit from the six steps above; they're important for building a fully-decoupled administration UI, and for building visitor-facing decoupled applications.

Useful for decoupling of visitor-facing front-ends Useful for decoupling of the administration backend 1. Stabilize the JSON API module ✔ ✔ 2. Improve our JavaScript testing infrastructure ✔ ✔ 3. Create designs for a React-based administration UI ✔ 4. Allow contributed modules to use React or Twig ✔ ✔ 5. Implement missing web service APIs ✔ ✔ 6. Make the React UI extensible and configurable ✔ Conclusion

Over the past three years we've been making steady progress to move Drupal to a more API-first and JavaScript centric world. It's important work given a variety of market trends in our industry. While we have made excellent progress, there are more challenges to be solved. We hope you like our next steps, and we welcome you to get involved with them. Thank you to everyone who has contributed so far!

Special thanks to Matt Grill and Lauri Eskola for co-authoring this blog post and to Wim Leers, Gabe Sullice, Angela Byron, and Preston So for their feedback during the writing process.

Categories: Drupal

Prepared Data

New Drupal Modules - 17 May 2018 - 10:36am

A batch processing framework for preparing expensive data.

Concept / About this module

Suppose you have a site with pages which are mostly static, thus you want your
pages to live in your cache for a long time - but they're only *mostly* static,
not always. You instead have one or a couple of dynamic parts on your page,
which want to show some (at least almost) current information. Examples:

Categories: Drupal

Mustache Templates

New Drupal Modules - 17 May 2018 - 10:26am

Integrates Mustache.php plus Mustache.js into Drupal.

Includes a generic framework to build DOM content which can be automatically synchronized on the client-side. Any RESTful Json endpoint can be used for automatic content synchronization.

Using Mustache.php by

  • Copyright (c) 2010-2015 Justin Hileman

Using Mustache.js by

Categories: Drupal

Z-Man Games Posts New Lowlands Preview

Tabletop Gaming News - 17 May 2018 - 10:00am
When you live along the coast, you keep a careful eye on what the sea is doing. When your land is actually sitting below sea level, you take extra time to make sure things are alright along the coast. In Lowlands, players take on the role of farmers along the North Sea. In this preview, […]
Categories: Game Theory & Design

WizKids Announces Letter Go Party Game

Tabletop Gaming News - 17 May 2018 - 9:00am
WizKids is simply on a roll with these new game announcements. This time around, it’s Letter Go, a new party card game. Players are looking to create words from the consonant and vowel cards out on the table, but not using any of the ones that they drew, themselves. Stretch your word power to the […]
Categories: Game Theory & Design

IDW Launches Nickelodeon Splat Attack! Kickstarter

Tabletop Gaming News - 17 May 2018 - 8:00am
Food fight! Tacos and burgers and ice cream is flying all over the cafeteria in Nickelodeon Splat Attack!, the new game from IDW that’s over on Kickstarter now. Players gather teams of four characters and look to score Cool Points. But watch out for that flying bowl of soup or you’ll lose all the points […]
Categories: Game Theory & Design

Party GDPR

New Drupal Modules - 17 May 2018 - 7:37am

Under development.

Integration between the party module and the gdpr module.

Categories: Drupal

Horror wars – East vs West. - by Rafa? Basaj

Gamasutra.com Blogs - 17 May 2018 - 7:01am
The approach towards horror game development between the West and Far East cultures. A look from the perspective of 2 successful companies developing horror games: Bloober Team (representing the West) and Red Candle Games (standing in the Far-East corner)
Categories: Game Theory & Design

Steamforged Previews Frelsi For Falconer’s Guild

Tabletop Gaming News - 17 May 2018 - 7:00am
Almost every team in Guild Ball has a mascot (Blacksmiths just have to be different like that…). In the case of the Falconer’s Guild, as one would expect, it’s a bird of prey. Specifically, Frelsi, a bald eagle. Get a look at her stats in this new preview. From the post: The most striking thing […]
Categories: Game Theory & Design

Wim Leers: Two big milestones in API-First Drupal

Planet Drupal - 17 May 2018 - 6:12am

Two big “maintainability” milestones have been hit in the past few days:

1. rest.module now is in a maintainable state

For the first time ever, the issue tracker for the rest.module Drupal core component fits on a single page: https://www.drupal.org/project/issues/drupal?component=rest.module. 48 46 open issues, of which several are close to RTBC, so that number will likely still go down. Breakdown:

  • 19 of those 48 are feature requests.
  • 6 are “plan” issues.
  • At least 10 issues are related to “REST views” — for which we are only fixing critical bugs.
  • And 12 are postponed — blocked on other subsystems usually. (There is overlap among those breakdown bullets.)

Finally the REST module is getting to a place where it is maintainable and we’re not extinguishing whatever the current fire is! It’s been a long road, but we’re getting there!

2. Instilling API-First responsibility

Two days ago, #2910883: Move all entity type REST tests to the providing modules landed, which is a huge milestone in making Drupal 8 truly API-First: every module now owns its REST test coverage, which conveys the fact that every component/module is responsible for its own REST API-compatibility, rather than all responsibility lying in the rest.module component!

This is largely made possible by \Drupal\Tests\rest\Functional\EntityResource\EntityResourceTestBase, which is a base test class that each entity type should subclass to test how it behaves when exposed via REST. Every entity type in core has tests based on it, but contrib and custom entity types are encouraged to do the same!

API-First ecosystem

But the rest.module being stable is not the only thing that matters — it’s a key part, but not the only part of API-First Drupal. The remaining challenges lie elsewhere in Drupal: the issues tagged API-First Initiative are now mainly in the modules providing field types, entity types, Entity/Field API and Configuration API.

The good thing is that the fixes to any of those always help the entire API-First ecosystem:

If you want to follow along a bit more closely, or want the news right as it happens, follow REST: top priorities for Drupal 8.6.x!

Categories: Drupal

New DC Releases Available From Knight Models

Tabletop Gaming News - 17 May 2018 - 6:00am
With the focus on Harry Potter over at Knight Models, it’s been a while since we got some new DC Universe/Batman Miniatures Game releases. However, that comes to an end now, as new sets of figures are up in their webshop. Pick up a new version of Superman and Catwoman, along with characters like Mera […]
Categories: Game Theory & Design

Pages

Subscribe to As If Productions aggregator