Daniel Nouri's Blog

I attended the SuperCollider Symposium 2007 in The Hague last week, which was fantastic. So many interesting people with their interesting projects gathered in one place! Too bad I missed out the last part of the symposium because of a cold.

Dan Stowell blogged about the symposium. There's some other cool things to discover on his page, like his Evolutionary Sound System (which he developed with SuperCollider), and him getting his hair cut.

Gregorio Garcia Karman took some nice photos at the conference.

You can learn more about SuperCollider on the SC home page and on Wikipedia. You might find these links particularly useful:

• SuperCollider on Ubuntu Linux, which describes how to install SC from subversion and how to install the sced SC editor for Linux, which you might find easier to use than the Emacs bindings.
• The ixi SuperCollider tutorial is a concise resource that will get you started quickly if you're already a programmer.
• If you speak German, there are excellent lecture notes from Hanns Rutz to get started.
• A list of tutorials on the SC wiki. Get David Cottle's book!
• And finally, my list of supercollider links.

After finding out about plone.recipe.bundlecheckout yesterday, I thought I'd mention infrae.subversion, a similar recipe for zc.buildout. These are the key differences:

• p.r.bundlecheckout allows you to specify one URL per part, whereas with infrae.subversion you can specify a list of URLs. Why does this matter? Because it helps you keep the exact URLs and therefore versions of the components that you use in your buildout configuration, which is better than keeping them in a svn:externals property.

• infrae.subversion takes care not to wipe any changes that you might have done in the checkout. That is, you can safely use its checkouts for development.

  Why not instead make a separate products directory and use svn:externals for development? Because again, we want to keep all dependencies in the buildout configuration. And it's good to keep the development buildout as close as possible to the deployment one, to minimize the chance of error. With infrae.subversion, you also have the advantage of being able to run bin/buildout and have all dependencies updated, instead of having to run svn up in some directory manually, which is a source of confusion.

• p.r.bundlecheckout works with both SVN and CVS, while infrae.subversion only works with SVN.

The Silva buildout is an example of a buildout that uses infrae.subversion.

[my-products]
recipe = infrae.subversion
urls = 
  https://svn.plone.org/svn/collective/FCKeditor/trunk FCKeditor
  ...

[prep-fckeditor]
recipe = plone.recipe.command
command =
    ${buildout:executable} ${buildout:directory}/parts/my-products/FCKeditor/utils/base2zope.py
update-command = ${prep-fckeditor:command}