Skip to Content

Newsfeeds

How to Create a Strong Game Plot - by Filip Wiltgren

Gamasutra.com Blogs - 10 January 2016 - 11:46pm
All you need to do to create a strong game plot are four words: Yes, But, No, And.
Categories: Game Theory & Design

Analyzing IronPython and IronRuby with PVS-Studio - by Marina Makarova

Gamasutra.com Blogs - 10 January 2016 - 11:46pm
Just a while ago, we released a new version of our analyzer PVS-Studio with support of C#-code analysis. For my experiments, I picked projects IronPython and IronRuby. In this article I shared results of analysis.
Categories: Game Theory & Design

Curiosity Development Report #1 - by Shaun Quaintance

Gamasutra.com Blogs - 10 January 2016 - 11:46pm
The first Curiosity Development Report, a weekly report of what we've done, what has gone well and what has gone completely wrong during the development of our next game.
Categories: Game Theory & Design

You are welcome - 2016 - by Sergey Yudovskiy

Gamasutra.com Blogs - 10 January 2016 - 11:36pm
The first post from russian developers team of mobile and PC games. Happy New Year!
Categories: Game Theory & Design

In-depth look at - Objective: Defeat Oryx, The Taken King - by Scott Fine

Gamasutra.com Blogs - 10 January 2016 - 11:36pm
We take a look at the "Defeat Oryx, The Taken King" encounter in the King's Fall Raid in Destiny. We discuss how the players learn what to do. And ask, what kind of feedback helps them to defeat him? This is part 3 of a 3 part series on the raid.
Categories: Game Theory & Design

Challenging Clash of Clans - Gods of Olympus - by Simon Newstead

Gamasutra.com Blogs - 10 January 2016 - 11:36pm
Clash of Clans has been on top for over 3 years. What will it take for another midcore game to give it a real challenge? In this article Simon looks at a new contender, Gods of Olympus, which takes an interesting new take on the battle pvp genre.
Categories: Game Theory & Design

Crumbling tiger, hidden canyon - by Geoff Lester

Gamasutra.com Blogs - 10 January 2016 - 11:11pm
Some tricks for making masks for dissolve effects in Far Cry 4: Shangri-La, using Modo and World Machine.
Categories: Game Theory & Design

OSTraining: Drupal 8 Themes for Beginners

Planet Drupal - 10 January 2016 - 5:21pm

A couple of years ago, we realized that a lot of Drupal beginners were asking us for simple, good-looking Drupal themes.

These beginners didn't want sub-themes, base themes, frameworks or complicated installs. So that meant no Omega, Zen, Fusion or Bootstrap. These beginners just wanted a theme could be installed easily and didn't look embarrassing. That lead to "Recommended Themes for Drupal Beginners", one of the most popular posts on this blog.

Now that Drupal 8 is here, we've started to hear the same question: "What theme should beginners use to create their first site?"

Unfortunately, the news is not good at the moment. Only 86 themes are ready for Drupal 8, and I could only find 3 that are suitable for beginners.

Categories: Drupal

Attiks: Dream permissions

Planet Drupal - 10 January 2016 - 12:57pm

The Drupal 7 admin/people/permissions is always been troublesome for big Drupal sites, there are some flaws, we hope we have solved.

By Peter Droogmans

Categories: Drupal

Phponwebsites: Drupal 7 – Hide Promoted to front page & Sticky at top of lists options

Planet Drupal - 10 January 2016 - 8:54am
    This blog describes how to hide "Promoted to front page" and "Sticky at top of lists" options from node form in drupal 7. When adding or editing a node, you can see "Publishing options" at bottom of the page which contains 'Published', 'Promoted to front page' and 'Sticky at top of lists' checkbox options. It should look like below image:


       The "Published" option is used to publish the content. The "Promoted to front page" option is used to display content in the front page. The 'Sticky at top of lists' option is used to keep the content sticked to the top of front page. If you don't want to show "Promoted to front page" and "Sticky at top of lists" options, then you can hide those options using hook_form_alter(), hook_form_FORM_ID_alter() and hook_form_BASE_FORM_ID_alter().

Hide Promoted to front page & Sticky at top of lists options in single node form:
       If you want to hide "Promoted to front page" and "Sticky at top of lists" options only in single node form, then you can remove those options from node form using either hook_form_alter() or hook_form_FORM_ID_alter() in drupal 7.  For example, we go to hide those options from article node form.
/**
 * Implement hook_form_alter().
 */
function phponwebsites_form_alter(&$form, &$form_state, $form_id) {
  // to hide promoted to front page option
  if (isset($form['options']['promote'])) {
    $form['options']['promote']['#access'] = FALSE;
  }

  // to hide sticky at top of lists option
  if (isset($form['options']['sticky'])) {
    $form['options']['sticky']['#access'] = FALSE;
  }
}
     Now you go to article node form and check whether "Promoted to front page" and "Sticky at top of lists" options are hidden or not. You couldn’t see those options in article node form. It should look like below image:

Hide Promoted to front page & Sticky at top of lists options in multiple node forms:
     If you want to hide "Promoted to front page" and "Sticky at top of lists" options in all node forms, then you can remove those options using  hook_form_BASE_FORM_ID_alter() in drupal 7.
/**
 * Implement hook_form_BASE_FORM_ID_alter().
 */
function phponwebsites_form_node_form_alter(&$form, &$form_state, $form_id) {
  // to hide promoted to front page option
  if (isset($form['options']['promote'])) {
    $form['options']['promote']['#access'] = FALSE;
  }

  // to hide sticky at top of lists option
  if (isset($form['options']['sticky'])) {
    $form['options']['sticky']['#access'] = FALSE;
  }
}
     Now you could not see those options in all node forms. Now you know how to hide "Promoted to front page" and "Sticky at top of lists" options from node form in drupal 7.Related articles:
Add new menu item into already created menu in Drupal 7
Add class into menu item in Drupal 7
Create menu tab programmatically in Drupal 7
Add custom fields to search api index in Drupal 7
Categories: Drupal

Théodore 'nod_' Biadala: Drupal gets a feature request out of the blue

Planet Drupal - 10 January 2016 - 2:42am

Word is that Drupal is getting a frontend framework. From the multiple options it seems EmberJS is currently a little ahead of Angular and React. As said in Dries original post as well as in the drupal core issue created, nothing is final and everyone interested is asked to check that the set of library in the comparison is sufficient and more importantly that the criteria used for evaluation are relevant.

Discussing those details is not what this post is about, like others I've been questioning the move from Dries. Since many of us are professionals, let's put this in a professional setting and pretend that Dries is just another client making a feature request seemingly out of the blue. To him the problem and solution is clear — obvious even — and it is the only way to achieve his vision. Let's check.

Client side (pun intended)

Drupal's user interfaces for content modeling (Field UI), layout management (Panels), and block management would benefit from no page refreshes, instant previews, and interface previews. These traits could also enrich the experience of site visitors; Drupal's commenting functionality could similarly gain from these characteristics and resemble an experience more like the commenting experience found in Facebook.

Should we decouple Drupal with a client-side framework?.

Pretty weak set of reasons. What is described later in the post can be achieved though regular Ajax and some resonable amount of javascript. Hardly a need for a frontend framework… until you remember what else Dries has been writing about.

As the Drupal community, we need to stop thinking of Drupal as a "content management platform" and start looking at it as a "digital experience platform" used to create ideal visitor experiences.

From content management to digital experience management.

Ideal as in enriched as in, for example, Acquia Lift. Don't get your pitchforks just now, there is no hidden agenda, just finish reading.

How serious is the client

Sometimes features can be swept under the rug and everyone will feel better in the long term. Sometimes the client does not let it go. So how serious is Dries about this? The two posts directly related to frameworks contain 3 387 words and if you include the related posts you can add 10 394 more words. A busy person doesn't write a short story just for fun. So I'd say he is pretty serious about this, and if you read the trail of posts this is not going away.

Client needs

We know a few things about what the client is trying to address:

  1. He expects the web to be completely different in 10 years.
  2. Most sites will need personalization.
  3. Better UX is crucial.
  4. One solution fitting core and contrib.

Since there needs to be one solution, it has to be in core from the start because contrib is not disciplined enough (by design) to come up with one homogeneous solution in less than 10 years.

A little extrapolation

If you have in mind all the posts Dries has been writting on the topic for the past two years it makes sense that web components or websockets do not address the issue of rich interfaces the way a frontend framework would, also in this discussion any PHP-based solution is off-topic. It looks to me that Dries is trying to get the community as well as Drupal ready for what he believes is coming. I deeply disagree on what the future holds for the web but it doesn't mean nothing should be done, just in case. At worst we'll burn the new people who came to help us switch to the new framework.

Solution

All in all, I would agree that under those assumptions, a framework is a valid tool to be using. Putting my JS maintainer hat on I would suggest to jQueryUI-it. Put it in core and use it anecdotally, and hope contrib will pick it up. Also we should chose the framework with the strongest opinion on how to do things. Because Drupal back-end is rather strongly opinionated about what the PHP should look like. It makes sense the JS should be the same.

On Acquia bashing

I've spent more than 2 years as an Acquia consultant, working closely with the Office of the CTO on several big D8 improvements so I've seen how the community is treated from the inside and I've only seen good will towards it. Sometimes things are downplayed, not out of malice, but out of concern for the issue at hand. Which is why I think Dries didn't explicitly mentioned Acquia Lift — but still hinted to it — to not get dragged in an argument about Acquia's influence. There is nothing wrong with that since compared to the fears expressed during D8 cycle, we're far from the worst scenario possible.

On that topic, when people say that Acquia, big companies or startups are influencing Drupal I think they're taking a shortcut. It's more like Acquia clients are influencing Dries, and in turn he steers Drupal to what he thinks is right. But don't forget that between clients and Drupal there is a filter, it's Dries. So far I think we can agree he's been pretty great at Dictatoring Drupal. So let's at least give him the benefit of the doubt.

Put your pitchforks back and grab some paint, there is a bikeshed to paint.

Categories: Drupal
Syndicate content


Google+
about seo