Now there are three ways to set options framework options:

  1. The old optionsframework_options() method
  2. Returning an array() in options.php
  3. Adding a filter on 'of_options'

The advantage of devinsays#3 is that this provides more granular control
over options.  For example, a child theme could add its own options
in addition to the parent theme's options using this method.  It
also means that options can be set anywhere in your project--the
options.php file isn't necessarily required (well, it still needs
to be there for optionsframework_option_name(), but I plan to
change that, too, soon).

There were a few bugs with the new _optionsframework_options() method
that I've now fixed.  Everything should work well, now.

You can now use the Options Framework without the options.php file.
This flexibility is particularly useful in object oriented themes
where global functions are frowned upon.  Both the options and the
options name can be set via filters or actions.

If no option name is set by the current theme, Options Framework chooses
the name "optionsframework_{theme_slug}"

Also fixed some minor code formatting inconsistencies (to better match
the Wordpress coding standards)

…if there were no options for that theme.