tutorial

use the entityapi to create a custom entity type that has view modes, custom fields, its own database table, and views support. no revisions yet.

A reverse geocaching box works similar to other geocaching devices. It will guide you to certain coordinates on earth and instead of finding a geocache located at those coordinates, you carry the box with you, and it opens for you at a predetermined destination. This is also a great way to do a scavenger hunt (making someone go to multiple locations before the box opens).

A reverse geocaching box works similar to other geocaching devices. It will guide you to certain coordinates on earth and instead of finding a geocache located at those coordinates, you carry the box with you, and it opens for you at a predetermined destination. This is also a great way to do a scavenger hunt (making someone go to multiple locations before the box opens).

The environment is built around a two-panel view: The left being an Ace editor and the right being a canvas.

All of the user’s code is written using JavaScript and uses Processing.js to generate all the graphics.

All code is executed in real-time. Not only is the code re-run but the code that you change is live dynamically injected into the runtime — this gives you the ability to change variables, colors, or even functions on the fly without the program ever restarting.

The unique skill and taste of an Instrument Maker is what sets the stage for great music. Any object that makes sound can be an instrument, but true music starts with expert design and craftsmanship. Before Miles Davis could play his trumpet, there was a Maker who built his sonic tool.

Circuit Benders can customize and hack technologies to do things they aren't designed to do. They can turn toys into musical instruments or transform household gadgets into things that are truly bizarre. A Circuit Bender explores what's under the hood of the electronics all around us.

The magic is in the --patch argument to git-add(1). This instructs Git to display all changes to the files specified on a hunk-by-hunk basis and lets you choose one of the following options for each hunk
...

In this case, I staged (y) about half of the hunks (the ones that were bookmark related) and left the other hunks unstaged (n). Now my index has all of the changes to synchronize-bookmarks plus half of the changes made to models.rb.

In the end, one argument against using Views for our content queries overrode all others: we wanted our client to use Views. Our client had specified that once they received the sites, their own developers would be using Views to build blocks and pages themselves. We knew that if we worked in Views for our own work, the Views we created would eventually be exposed to them, which leads to possibilities of regression and error. We wanted our core querying functionality to continue to function without concern that it might be tampered with.

wondering why I wouldn't just build this in Views. Indeed, this might look a bit masochistic if you're used to Views. However, there are a few things to consider:
EntityFieldQuery is core. If you are interested in keeping your installation as lean as possible, this is something to consider. Views is a contributed module, and so it automatically adds size and overhead to your Drupal install.

A background image that fits the entire web page can be more challenging. I’ve learned that a simple graphic with a strong diagonal feel, sized to fit 100% of the page’s height and width, can be a fun and effective background graphic that seems to be a custom fit to the web page size