Newsfeeds

Tencent and NetEase announce Q3 results - by Lisa Hanson

Gamasutra.com Blogs - 22 November 2017 - 7:27am
The gaming trend that cannot be ignored is the global success of Battle Royale games. Not to be left behind, Tencent and NetEase recently unveiled plans to compete in this segment.
Categories: Game Theory & Design

Urza’s Dream Engine & The RoboRosewater RoboDraft: Creating a machine learning algorithm to illustrate Magic cards - by Andy Wallace

Gamasutra.com Blogs - 22 November 2017 - 7:27am
I spent that last two months teaching a bot to create illustrations for Magic: The Gathering cards designed by another bot. How I built Urza's Dream Engine to generate art for RoboRosewater cards and the tournament that humans played with automated cards.
Categories: Game Theory & Design

The Games That Inspired me to Become a Developer - by Michael Smith

Gamasutra.com Blogs - 22 November 2017 - 7:27am
These are the games that changed things for me, the games that made me what I am.
Categories: Game Theory & Design

The Entity-Component-System - An awesome game-design pattern in C++ (Part 1) - by Tobias Stein

Gamasutra.com Blogs - 22 November 2017 - 7:25am
In this article I want to talk about the Entity-Component-System (ECS). It is a design pattern – mostly encountered in video games – which allows you great flexibility in designing your overall software architecture.
Categories: Game Theory & Design

The Entity-Component-System - BountyHunter game (Part 2) - by Tobias Stein

Gamasutra.com Blogs - 22 November 2017 - 7:25am
This is the second part of my series "The Entity-Component-System". This time I am going to show how to use the ECS implementation from my first post and build a game with it.
Categories: Game Theory & Design

Privateer Press Black Friday Sales Announced

Tabletop Gaming News - 22 November 2017 - 7:00am
This is the season of buying things for cheaper than you’d usually have to spend. Pretty much every company out there’s got a sale going, and Privateer Press is no different. Their sale is actually already going. You’ve only got until Sunday to get these special deal pricings, though. From the website: Black Friday Sale! […]
Categories: Game Theory & Design

Dries Buytaert: An update on the Workflow Initiative for Drupal 8.4/8.5

Planet Drupal - 22 November 2017 - 6:57am

Over the past weeks I have shared an update on the Media Initiative and an update on the Layout Initiative. Today I wanted to give an update on the Workflow Initiative.

Creating great software doesn't happen overnight; it requires a desire for excellence and a disciplined approach. Like the Media and Layout Initiatives, the Workflow Initiative has taken such an approach. The disciplined and steady progress these initiative are making is something to be excited about.

8.4: The march towards stability

As you might recall from my last Workflow Initiative update, we added the Content Moderation module to Drupal 8.2 as an experimental module, and we added the Workflows module in Drupal 8.3 as well. The Workflows module allows for the creation of different publishing workflows with various states (e.g. draft, needs legal review, needs copy-editing, etc) and the Content Moderation module exposes these workflows to content authors.

As of Drupal 8.4, the Workflows module has been marked stable. Additionally, the Content Moderation module is marked beta in Drupal 8.4, and is down to two final blockers before marking stable. If you want to help with that, check out the Content Moderation module roadmap.

8.4: Making more entity types revisionable

To advance Drupal's workflow capabilities, more of Drupal's entity types needed to be made "revisionable". When content is revisionable, it becomes easier to move it through different workflow states or to stage content. Making more entity types revisionable is a necessary foundation for better content moderation, workflow and staging capabilities. But it was also hard work and took various people over a year of iterations — we worked on this throughout the Drupal 8.3 and Drupal 8.4 development cycle.

When working through this, we discovered various adjacent bugs (e.g. bugs related to content revisions and translations) that had to be worked through as well. As a plus, this has led to a more stable and reliable Drupal, even for those who don't use any of the workflow modules. This is a testament to our desire for excellence and disciplined approach.

8.5+: Looking forward to workspaces

While these foundational improvements in Drupal 8.3 and Drupal 8.4 are absolutely necessary to enable better content moderation and content staging functionality, they don't have much to show for in terms of user experience changes. Now a lot of this work is behind us, the Workflow Initiative changed its focus to stabilizing the Content Moderation module, but is also aiming to bring the Workspace module into Drupal core as an experimental module.

The Workspace module allows the creation of multiple environments, such as "Staging" or "Production", and allows moving collections of content between them. For example, the "Production" workspace is what visitors see when they visit your site. Then you might have a protected "Staging" workspace where content editors prepare new content before it's pushed to the Production workspace.

While workflows for individual content items are powerful, many sites want to publish multiple content items at once as a group. This includes new pages, updated pages, but also changes to blocks and menu items — hence our focus on making things like block content and menu items revisionable. 'Workspaces' group all these individual elements (pages, blocks and menus) into a logical package, so they can be prepared, previewed and published as a group. This is one of the most requested features and will be a valuable differentiator for Drupal. It looks pretty slick too:

I'm impressed with the work the Workflow team has accomplished during the Drupal 8.4 cycle: the Workflow module became stable, the Content Moderation module improved by leaps and bounds, and the under-the-hood work has prepared us for content staging via Workspaces. In the process, we've also fixed some long-standing technical debt in the revisions and translations systems, laying the foundation for future improvements.

Special thanks to Angie Byron for contributions to this blog post and to Dick Olsson, Tim Millwood and Jozef Toth for their feedback during the writing process.

Categories: Drupal

An update on the Workflow Initiative for Drupal 8.4/8.5

Dries Buytaert - 22 November 2017 - 6:57am

Over the past weeks I have shared an update on the Media Initiative and an update on the Layout Initiative. Today I wanted to give an update on the Workflow Initiative.

Creating great software doesn't happen overnight; it requires a desire for excellence and a disciplined approach. Like the Media and Layout Initiatives, the Workflow Initiative has taken such an approach. The disciplined and steady progress these initiative are making is something to be excited about.

8.4: The march towards stability

As you might recall from my last Workflow Initiative update, we added the Content Moderation module to Drupal 8.2 as an experimental module, and we added the Workflows module in Drupal 8.3 as well. The Workflows module allows for the creation of different publishing workflows with various states (e.g. draft, needs legal review, needs copy-editing, etc) and the Content Moderation module exposes these workflows to content authors.

As of Drupal 8.4, the Workflows module has been marked stable. Additionally, the Content Moderation module is marked beta in Drupal 8.4, and is down to two final blockers before marking stable. If you want to help with that, check out the Content Moderation module roadmap.

8.4: Making more entity types revisionable

To advance Drupal's workflow capabilities, more of Drupal's entity types needed to be made "revisionable". When content is revisionable, it becomes easier to move it through different workflow states or to stage content. Making more entity types revisionable is a necessary foundation for better content moderation, workflow and staging capabilities. But it was also hard work and took various people over a year of iterations — we worked on this throughout the Drupal 8.3 and Drupal 8.4 development cycle.

When working through this, we discovered various adjacent bugs (e.g. bugs related to content revisions and translations) that had to be worked through as well. As a plus, this has led to a more stable and reliable Drupal, even for those who don't use any of the workflow modules. This is a testament to our desire for excellence and disciplined approach.

8.5+: Looking forward to workspaces

While these foundational improvements in Drupal 8.3 and Drupal 8.4 are absolutely necessary to enable better content moderation and content staging functionality, they don't have much to show for in terms of user experience changes. Now a lot of this work is behind us, the Workflow Initiative changed its focus to stabilizing the Content Moderation module, but is also aiming to bring the Workspace module into Drupal core as an experimental module.

The Workspace module allows the creation of multiple environments, such as "Staging" or "Production", and allows moving collections of content between them. For example, the "Production" workspace is what visitors see when they visit your site. Then you might have a protected "Staging" workspace where content editors prepare new content before it's pushed to the Production workspace.

While workflows for individual content items are powerful, many sites want to publish multiple content items at once as a group. This includes new pages, updated pages, but also changes to blocks and menu items — hence our focus on making things like block content and menu items revisionable. 'Workspaces' group all these individual elements (pages, blocks and menus) into a logical package, so they can be prepared, previewed and published as a group. This is one of the most requested features and will be a valuable differentiator for Drupal. It looks pretty slick too:

I'm impressed with the work the Workflow team has accomplished during the Drupal 8.4 cycle: the Workflow module became stable, the Content Moderation module improved by leaps and bounds, and the under-the-hood work has prepared us for content staging via Workspaces. In the process, we've also fixed some long-standing technical debt in the revisions and translations systems, laying the foundation for future improvements.

Special thanks to Angie Byron for contributions to this blog post and to Dick Olsson, Tim Millwood and Jozef Toth for their feedback during the writing process.

Categories: Drupal

Fantasy Flight Previews Different Tones in Genesys

Tabletop Gaming News - 22 November 2017 - 6:00am
No, the headline doesn’t mean that we’re taking a look at the different bardic classes in the game. Here, tone refers to how the game comes across for players. Is it light-hearted and comedic? Is it dark and brooding? Is it gritty? When a system says that it’s universal, it should be able to cater […]
Categories: Game Theory & Design

Workbench Access Menu Link

New Drupal Modules - 22 November 2017 - 5:35am

This module provides access controls for menu hierarchies using Workbench Access and based on menu link fields.

Categories: Drupal

Sooper Drupal Themes: It's Happening! SooperThemes Portfolio Views For Drupal 8 and Drupal 7

Planet Drupal - 22 November 2017 - 3:50am

Our very first official Drupal 8 product release is our SooperThemes Drupal Portfolio Module! While working on a full release of all our themes and modules we saw an oppurtunity to re-invent our portfolio solution and wrote a new module from scratch, ensuring compatibility and ease of maintenance across Drupal 7 and Drupal 8 ecosystems. We're telling you that our new portfolio module is better, faster, sexier, and easier to use than any portfolio module you're used before, on Drupal or elsewhere.

Creating Professional Portfolio Views Has Never Been Easier

You only have mere seconds to impress people with your website. SooperThemes Portfolio offers 65 design settings and unlimited control over animation, color, and content to help you get it right the first time.

Leverage query building, ordering, and contextualization that made Views and Drupal big. Whether you're displaying nodes, files, or custom entities SooperThemes Portfolio will handle it.

65 Settings, 14 Caption Designs, Advanced Motion Design... And Still Easy To Use

As you've come to expect of SooperThemes' products customisability is something we pay attention to. Without being overbearing we provide settings that allow you to match your portfolio, showcase, or e-commerce grid to you site's branding and content. We implemented color pickers that support transparency, example caption designs, and individual motion design options for loading the image grid, filtering, and hovering items. 

Get the details on our portfolio module landing page:Portfolio Drupal Module
Upgrading Your Drupal 7 Site From Glazed Portfolio/MD Portfolio

First of all, if Glazed Portfolio is working fine for you, you don't have to upgrade. While the new module provides more features and easier customisability this doesn't mean it's worth your time to configure new views with SooperThemes Portfolio  if you're going to end up with the same design that was already working fine for you.

However, if your portfolio views are up for a make-over, or if some of the little bugs and limitations in the old module are bothering you this is the time to upgrade! Since both modules are based on the same grid system the views settings will be familiar. 

Upgrading is very simple:

1. Install new module

2. Create new view or edit example view. Customize to your liking

3. Reference the new view in your menu links and drag and drop pages

4. Uninstall glazed portfolio/MD Portfolio

Where are Drupal 8 Glazed Builder and Glazed Theme at?

Releasing SooperThemes Portfolio is just one of the stepping stones on the way to a full Drupal 8 release for our flagship products. The only 2 remaining stepping stones are finalization of our Entity Browser/Media integration in Glazed Builder and the migration of our theme demos to the Drupal 8 ecosystem. The release itself will take some work in terms of updating our provisioning software and content/documentation on sooperthemes.com. Expect new updates in December!

Categories: Drupal

Beating the Holiday Scheduling Blues

Gnome Stew - 22 November 2017 - 3:08am

Today’s guest article is by Craig Dedrick, who talks about holidays around and in gaming. He forgets to mention the best holiday of all – gnomexodus! It’s the holiday all the Staff Gnomes celebrate when they escape the warrens and get to avoid becoming part of the stew for one more day!- John”Only closed my eyes for a minute” Arcadian

With Thanksgiving, Festivus, and Christmas fast approaching, many RPG groups will encounter conflicting scheduling priorities as both family and work events demand attention. This is certainly a problem for many groups, but where others see problems, I see opportunities; opportunities to build a sense of community, if not family, with your gaming friends. There are a few ways to take advantage of these opportunities.

Gatherings

Holidays are a time for family and friends, and in my case, my RPG groups are comprised of many of my best friends. Every year I plan a Christmas party on a game night. Families are invited, food is brought, and a turkey is cooked. This provides a chance for families to meet each other, and fosters a sense of community around the game. Spouses and significant others get a chance to put faces with names, and may be more forgiving of the time set aside for regular game sessions. When this sense of community is created around a game, it increases the players’ commitment, and it tends to make for a more stable and long-lasting group.

Celebrate the Holiday In-Game

Organizing a holiday feast can be a lot of work, and some expense. However, you and your group can celebrate a holiday in-game as well. With a bit of planning and coordination, a clever game master can arrange for the “annual feast day” in your fantasy world to coincide with the Christmas season. Characters purchase gifts for each other and attend a gathering of some sort. It always amazes me how excited players get about purchasing and receiving gifts for their characters, and some very memorable moments can be created with this method.

Gift Exchanges

Gift exchanges don’t necessarily need to be limited to in-game exercises. Over the years, I have been in several groups that have organized an annual “secret Santa” gift exchange. The goal is to get something that the player will appreciate but is thematically appropriate for the character as well. Some memorable gifts include a toy car that had been modified to be a model of the character’s car in the game, an electronic “orc detector” for a player whose character had a hatred for orcs, and a fake magazine cover that featured articles and pictures of characters from a superhero game. This is another way to celebrate the holiday, and to foster emotional connections between players and around the game.

Theme Games

This type of activity works particularly well if festive snacks are provided at the table, and a few holiday-appropriate decorations go up. One of my groups are big fans of dressing in character at Halloween and eating grotesque amounts of tiny candy bars. Once the appropriate atmosphere is set, you can run a session with some sort of holiday theme. Perhaps Krampus is on the loose and needs to be stopped for a Christmas-themed game, or a coven of witches is planning something nefarious for a game on Halloween.

Something to Look Forward to

In the past, the holiday season was something that, as a game master, I viewed with some trepidation, knowing that a scheduling nightmare was around the corner. Now the Christmas-party games are something that everyone looks forward to, and players bend schedules so that they do not miss the special event.

How do you celebrate holidays with your gaming groups? Do you prefer in-game or out-of-game celebrations? Are there any other suggestions out there for avoiding the holiday scheduling blues?

 

Categories: Game Theory & Design

Webform Scheduled Tasks

New Drupal Modules - 22 November 2017 - 2:11am

Webform Scheduled Tasks is a module which allows the regular cleansing/sanitization of sensitive fields in Webform.

Using cron or drush, this module can update webform submissions to delete data which should only be kept for a limited period of time.

An example of this - a form where a user provides an email to receive a confirmation notification, but doesn't want their email to be kept indefinitely.

Categories: Drupal

Custom Voice Search

New Drupal Modules - 22 November 2017 - 1:40am

Custom Voice Search

This module adds the ability to any form having search field to add voice support.

Configure:
Enable like any other module.
Go to: /admin/config/custom_voice_search/customvoicesearch
Add Form id on which voice search needs to be implemented like: "user_login_form" not "user-login-form"
Add Input id like: "edit-keys" not "edit_keys"
Add Input field name attribute like: keys or name etc.

Categories: Drupal

qed42.com: Override existing Configuration entity types - Drupal 8

Planet Drupal - 22 November 2017 - 12:16am
Override existing Configuration entity types - Drupal 8 Body

Why do we need to override Config Entity Types?

  1. By default, Vocabulary list displays all the vocabularies. In case we want to restrict certain roles from viewing certain vocabularies. Overriding that Class(VocabularyListBuilder) function would be the solution to display specific/no/all vocabularies.
  2. Let's assume we need to specify vocabulary-path for each vocabulary apart from name, title, description, vid etc. In this case we would need to override the default Vocabulary Form of taxonomy_vocabulary config entity type.
  3. Suppose we want to custom access check for views on the basis of role/user/views operation or whatever, we would need to override ViewsAccessControllerhandler of view configEntityType and write our own logic.
  4. Another use case can be, if we want to display all the image fields which use image style being deleted, on confirm text message, we again need to override ImageStyleFlushForm class and redefine getconfirmText function.

In short, to customise and meet our dynamic requirements which may not be supported by config entity type definition as a part of @ConfigEntityType annotations in core or contributed modules, we need to override existing config entity types and write some custom code :).

How can we override Config Entity Types?

Entity types use object based annotation unlike array based annotation which is commonly used. Also, Unlike Content Entity Types where every thing is a field, NOTHING is a field for Configuration Entity type.

Every Drupal config entity type is defined as a particular ConfigEntityType Annotation. Entity controller is completely different from the Controller of MVC pattern. To avoid this confusion in terminology Entity Controllers are termed as handlers, each form related to a particular entity type say taxonomy_vocabulary is declared inside handlers with form key. 

In this article, will take an example of adding custom form elements to config entity type forms to explain this.

In case we need to add a custom element to any of these forms, we need to follow these 2 steps:

I) Set a new handler class specific to that form.

  1. Implement hook_entity_type_alter(array &$entity_types).
  2. Set new handler class as :  $entity_types[{id}]->setHandlerClass('form', ['{form_type}' => 'Drupal\my_module\MyModuleForm', '....', '....' ]);

    where, id = configEntityType id,  form_type eg: default, reset, delete etc is whichever form we want to override and MyModuleForm is the Class name of new form we'll define in Step II.
    Here is the sample code of overriding default form of taxonomy vocabulary.

    $entity_types['taxonomy_vocabulary']->setHandlerClass('form', ['default' => 'Drupal\my_module\VocabularyForm', 'reset' => 'Drupal\taxonomy\Form\VocabularyResetForm', 'delete' => 'Drupal\taxonomy\Form\VocabularyDeleteForm' ]);

     

II) Define the class set in Step I.

  1. Extend the actual class of the form we want to add new form elements to.  use Drupal\taxonomy\VocabularyForm as VocabularyFormBuilderBase;

    {this is optional, we need to do this to keep the new class name same as base class i.e VocabularyForm}.

    class MyModuleForm extends VocabularyFormBuilderBase

    OR simply, 

    class MyModuleForm extends VocabularyForm

    This override is important because we need to inherit functions and form elements defined in the parent class i.e VocabularyForm and also add additional feature i.e form element without disturbing the core code. This is purely OOPs concept of inheritance.

  2. We need to override the form function by 
    1. Inheriting the parent elements by parent::form(....) and
    2. Defining the new custom elements as the basic example below: $form['third_party_settings']['qed42_textfield'] = array( '#type' => 'textfield', '#title' => t('QED42 Custom Form Element'), '#default_value' => $vocabulary->getThirdPartySetting('my_module', 'qed42_textfield', 'Qed42 textfield default value') );

      Config Entities have by default "getThirdPartySetting()" function { Config entities inherit this function if these extend ConfigEntityBase class which implements ConfigEntityInterface interface which in turn extends ThirdPartySettingsInterface interface}. This thirdParty function allows to set and retrieve a value particularly for a module.

    3. Similarly, we can inherit the save function to save the value of newly added form element with Third Party Settings  as : 

      If the form is set as Tree we need to set value as

      $vocabulary->setThirdPartySetting('my_module', 'qed42_textfield', $form_state->getValue('third_party_settings')['qed42_textfield']);

      else :

      $vocabulary->setThirdPartySetting('my_module', 'qed42_textfield', $form_state->getValue('qed42_textfield'));

      and of course inherit the parent save function. 

    4. We can implement the same logic for extending definition of any existing method  AND can also define new functions inside our new Form.

Any Configuration Entity Type (Date format etc) can be overridden similarly, this can be extended to list_builder, access etc.  Apart from overriding, we can also add new flavours of entity controller using the above steps.

 

jyoti.bohra Wed, 11/22/2017 - 13:46
Categories: Drupal

Behind the Counter: Good customers make for good retailers. Simple as that.

RPGNet - 22 November 2017 - 12:00am
How customers make all the difference
Categories: Game Theory & Design

User Edit

New Drupal Modules - 21 November 2017 - 5:20pm

This module provides alias "user/edit" to have better user experience.
By using this, current logged in user can edit own profile and don't mind of his UID.
Sometimes, using "user/%/edit" is pretty uncomfortable.

The development is in progress.

Categories: Drupal

Battle Systems Running Core Battle Sci-Fi Skirmish Game Kickstarter

Tabletop Gaming News - 21 November 2017 - 3:00pm
You might know Battle Systems for all that awesome terrain that they make. Well, if you’ve been wanting a specific game to go with said terrain, your wish has been granted. They are running a Kickstarter campaign for Core Space, a new sci-fi miniatures campaign game. Grab your crew and head out into the black. […]
Categories: Game Theory & Design

Alternative Armies Posts New Releases and Black Friday Sale Announced

Tabletop Gaming News - 21 November 2017 - 2:00pm
Gavin over at Alternative Armies has been a busy bee. He’s got six new releases for you to check out. Along with that, there’s a bunch of sales stuff he’s set up that go live at the end of the week. Save some of your holiday dollars for them! From the announcement: Six brand new […]
Categories: Game Theory & Design

PreviousNext: Introducing the Display Suite Chained Fields module for Drupal 8

Planet Drupal - 21 November 2017 - 1:41pm
Share:

Need a way to mix fields from referenced entities with regular fields from managed display?

Then the Display Suite Chained Fields module might be for you.

by Lee Rowlands / 22 November 2017

So how do you go about using the module?

Step 1: Enable a display suite layout for the view mode

To use the chained fields functionality, you must enable a display suite layout for the view mode. Select a layout other than none and hit Save.

Enabling a layoutStep 2: Enable the entity reference fields you wish to chain

To keep the manage display list from being cluttered, you must manually enable the entity reference fields you wish to show chained fields from. For example, to show the author's picture, you might enable the 'Authored by' entity reference field, which points to the author. After you've enabled the required fields, press Save.

Enabling fields for chainingStep 3: Configure the chained fields as required

Finally, just configure the chained fields as normal.

Configuring chained fields

That's it - let me know your thoughts in the comments or the the issue queue.

Tagged Drupal 8, Display Suite

Posted by Lee Rowlands
Senior Drupal Developer

Dated 22 November 2017

Add new comment
Categories: Drupal

Pages

Subscribe to As If Productions aggregator