@nash-ye yeah, if you could extract the fixes you made for bugs you found and open a pull request for each smallish patch, we can then revisit the reorganization. But for now, you could close this pull request.

> Do we really need this?! for the run-time options? we will only have 3 methods it's really tiny class! and it will be harder to call them from outside the plugin class

It won't be hard to call from outside the plugin class either (which should be very rare anyway), since the instance will be assigned to the main plugin class, so you can (if we store instance à la singleton) do `Dependency_Minification::get_instance()->options->get( 'foo' )`.

In general, I believe the smaller the class the better. The more that classes (and methods) do just one thing and do it well, the easier it will be to maintain the plugin and (especially) be able to write unit tests, as each component class of the plugin can be replaced with another component that implements the same interface. You know, [mocks](http://en.wikipedia.org/wiki/Mock_object) and [dependency injection](http://en.wikipedia.org/wiki/Dependency_injection).