I could not (but i really wanted) play Heavy Rain. The core feature is the very flexible story. Players can end up with a very different experience. Its focused in the storytelling and reviews say that the lack of game over… the story always progresses.
_Lack of game over? Where is the challenge?__ ;Ok, here we go: Heavy Rain is a game? A more profound question: what is a game? That is the difference between a game and a puzzle? Or a simple challenge?
So lets define:
movies and books are not games. Games are interactive
jigsaws and puzzles are not games. Games must have multiple players;(even if they have different role). Not that we could assume that a AI could be considered a player as well
racing and swimming are not games. Gamers must interfere in the performance;of the other players
toys and sandboxes are not games. Games must have rules and objectives
So, games should be interactive, multiplayer, competitive, defined by rules and they have a goal. Clark Abt defines _“A game is an activity among two or more independent decision-makers seeking to achieve their objectives in some limiting context”.
The curious thing is that if we take this concept to actual games, mane famous video games are not… games. Sim City, The Sims, Monkey Island, City Ville, Portal, World of Goo and Heavy Rain and several others fail in at least one aspect that makes a game.
Knowing this is a good way to correct position products against each other.
Getting Things Done (GTD) is an organizational method created by David Allen, described in a book of the same name. The Getting Things Done method rests on the principle that a person needs to move tasks out of the mind by recording them externally. That way, the mind is freed from the job of remembering everything that needs to be done, and can concentrate on actually performing those tasks.
I read the book and love it. It balances between theoretical reasoning and practical attitudes. It says explicitly that it is not about a computer program, or a special type of note book. You are free to use any system you want. Webmail, Outlook, notebook, folders, color tags… you decide. But the book is smart enough to give you hints about using them, just for the sake of starting soon and being practical.
It at least opens the mind for being more productive in our ordinary life. Just dont go crazy to think about it all the time because, paradoxically, it can be really nonproductive.
PS: I recommend you to strive to use for 3 months, forcing yourself. Its easy to start but because it requires a new mindset, keeping using the system harder and harder with time.
Creating GUI is no easy task. But creating GUI creators is a even more complex task. Almost a nightmare. But the long road walked by GUI creation programs, we already know somethings that are good and somethings that are bad.
Drag and drop
Quite a long time, desktop IDE’s acknowledged that letting developers to create GUI with some kind of drag and drop interface were critical. That were because GUI were less and less created by programmers but more and more by designers, that have little knowledge and patience to deal with programming code. It also facilitate the adoption by beginners.
A too designer/beginner driven interface for creating GUI might also not be a good choice. The whole customization and generalization possible by programming is lost. Its too case-by-case development. Its not cost efficient. That’s why a middle term is needed. Some kind a language that is easy enough for designers but programmable. Drupal CMS uses the Form API, a PHP array that will be used to create HTML forms. Its quite easy to be used by newbies. I heard that QT is preparing some custom language for creating their UI too.
Most GUI element have a fixed set of parameters. But sometimes the GUI should be generated on the fly. Developing GUI like this is very try-and-error. To facilitate the creating phase, its important to be possible to see it working with some generic data.
Widget or data separation
The UI 101 rule is to separate the data to the layout. But it is important to let the users to chance any of them. For example, the user can enter his birth year by a textfield or a dropdown list, or some nice JS calendar. This example show how to change the widget, the GUI element. However, the user might need to change the data type. If the birth year was originally text, the user might decide to change it to integer number. The challenge here is to convert saved data. But for most cases, it is feasible.
Developers of both desktop and internet applications are experiencing a quite interesting phenomenon: the same application must have several outputs, like netbook version or mobile sites. With the rise of HTML5, sites now might need multiple different outputs. Also, we must have different outputs when we are creating, viewing or update content. The concept of multiple contexts might be anticipated by the GUI creators.
Custom data structures
Integers, float numbers, strings… all developers know these data types. But they know that in some cases it is needed a more complex data types; combination of primitives. Some programming languages have structures and objects to address this idea. But GUIs can also be the combination of multiple primitives. Imagine a “password_checker” GUI element that is, in fact, two form fields that will check if the user typed the password correctly or an “address” element that is in fact a group of *country, province and city* fields. Users might be enabled to create and edit these type of custom data structures.
UPDATE (2009-10-05): I just saw a issue posted against CCK module called State of the multigroup module. It has close relationship with this post. Curious is that it is more a hack than a core idea.
Views is the most popular module on Drupal. Its not a coincidence: the ability to create custom lists on any Management System is critical. Views goes even beyond by creating a display API and enabling export some options to the end users.
I’m in fact really puzzled by the fact the Drupal next version, 7, does not integrate it into core. It IS a core module, by any perspective. Several administration pages should be designed as Views from the beginning and the whole DB schema data also should be redesigned to implement integration with that.
But I still see some features that Views could still implement.
The first is external data sources. Today we know that search huge amount of data is no easy task and Drupal core does it poorly. That’s why external programs like Solr, Sphinx are becoming more and more popular among Drupal masters. Views yet does a very little integration with those tools. The whole …8220;query builder" should redesigned to control other data sources. Ideally, it could search on any known data structure. By plugins, it would be possible to search external feeds directly, or some web services’ data, like Twitter, Flickr and Facebook without replicating the whole data locally.
I hope the newly created version 3 implements such abstraction.