User login

Benjamin Melançon

The Ultimate Notetaking Drupal Site

  1. Title must be optional.
  2. Saving must be automatic.
  3. Must allow multiple edit tabs to be open at once.
  4. Tagging and crossreferencing preferred.

For me, it should be the one place for everything. This implies, if done with one content type, possibly having an optional date field, a private textarea...


Ideally the tabs would be vertical, and somehow in the application, but really it can just use the browser's tabs.

Sadly, some brilliant text had to be jettisoned from the Definitive Guide. Some of it lives here.

Castaways from the writing process:

Of course we should have an API or three. We know Jeff Eaton would stick APIs in a novelty module called Eldorado Superfly. No, actually, he didn't. From this we can learn that if our module is simple enough and uses enough of Drupal's APIs, it doesn't need to create its own.

[Eaton] drawing on his experience with VotingAPI, which, we might note, puts API right in the name of the module, and if that doesn't mean something, what does?

Pushing our local repository to Gitorious

git checkout master
git remote add origin
git push origin master

This was for a module named "remarkup" as covered in

Agaric's Trac workflow

This is in etc/trac/trac.ini. Note that each project can override in its own trac.inin (which for Agaric's system is in /srv/trac/PROJECTNAME/conf/trac.ini).

Left and right double quotation marks with :before and :after pseudoclass content

Style blockquote with no indent, different color, and :before and :after open-quote and close-quote.

#block-views-featuredsupporter-block_1 blockquote {
  margin: 1em 0;
  color: #0e4e60;
  font-weight: bold;
  font-style: italic;

Increase main partition size in Ubuntu within VMWare Fusion

That was well nigh impossible. GUI fail, on gparted's part.

These steps won't be 100% complete because it's 7:15am and i spent the last hour frying my brain on this stuff (after the brain unilaterally called a break about 2:15am and i fell asleep), but they do fill in some gaps other resources out there don't quite cover. Some even seem to (falsely) suggest that unallocated space must be made into its own partition first. Here are some of the better links; my (final working) steps below.

[Agaric-specific] Set up a Trac issue queue for a project

Visitors, please note that while Agaric-specific documentation may be informative to you, it is meant primarily for Agaric's internal use and is highly unlikely to work step-by-step without fulfilling an awful lot of dependencies first.

After setting up the project per Deploying the Agaric way, we can use our trac setup vlad task to do most of the work.

From within the project:

rake test vlad:setup_trac

Drupal messages should not disappear before a page load

May i just say how much i hate the apparent alleged feature of Open Atrium of making messages disappear after about three seconds. What the heck is with that? The message was put there for a reason. So i know if i submitted the form already even if i come back after 5 minutes. So that i can read it and understand and maybe even click a link in it.

Syndicate content