lp:~music-clockwork/resonate/mixes

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

619. By Brian Kassouf <brian@brian-laptop> on 2009-05-04

pulled in the new revisions from trunk branch

618. By Brian Kassouf <brian@brian-laptop> on 2009-04-22

added some files i forgot to include earlier

617. By Brian Kassouf <brian@brian-laptop> on 2009-04-22

merged in the changes from trunk so it is running off the version without
elixer and enabled the move track up and down buttons

616. By Brian Kassouf <brian@brian-laptop> on 2009-04-02

started work on User Constructed Mixes. features included in this
commit:

*create Mix
*enter/exit "Mix Mode"
*add/remove tracks to a mix

615. By Chris Wagner on 2009-03-30

Merge in changes from distributed-resonate branch.

614. By resonatedev on 2008-07-22

Oh, nothing...

613. By resonatedev on 2008-07-08

properly call init_resonate() from scan.py.

612. By chris on 2008-06-28

* Make 'username' a required field for the User model.
* Make the 'full_name' and 'location' attributes of the User model be required
  fields. They can be empty strings (""), but they cannot be None/NULL.
* Add "initial values" support to our forms library.
* Make the "edit profile" form be pre-populated with the user's current
  profile details (name, email, location).
* A few other, minor changes.

611. By chris on 2008-06-26

* maintain form values when a form does not validate. this fixes #778.
* add a little more testing for the "password" field type (since i had broke
  it while working on the above fix).

610. By chris on 2008-06-18

* no longer perform Resonate's initialization upon loading the "resonate"
  module; instead, the "init_resonate" function, which can found in the
  same module, must be called explicitly.
* some minor formatting changes to base resonate module (__init__.py).
* create a slightly cleaner system for dealing with
  initialization/configuration/environment errors. rather than print an
  ugly stack track when we have one of these (e.g., when we can't connect
  to the database, when an invalid database engine is specified in the config
  file, etc.) we'll now just print an appropriate message indicating what
  went wrong. right now, very little potential problems make use of this
  mechanism (i.e., raising the ConfigurationError exception), but we will
  plan to add more, appropriate error-handling code is we run across the
  potential problems that can arise [upon initialization].