Move default theme to it's own installable app

[pydanny]

I've realized the way we've implemented the default theme is problematic in that it doesn't follow the same installation pattern that other themes need to follow - specifically inclusion as a settings.INSTALLED_APP. This makes it really hard to use it as an theme-building example.

Perhaps move it to it's own app at:

• djadmin2.themes
• djadmin2.themes with it's own form display code so we can remove the dependency on crispy forms
• Some other location in the django-admin2 repo
• Another repo as it's own project?

Thoughts?

[pydanny]

Sphinx comes with a bunch of default themes, which makes it really handy for developers who want to try different themes without installing a ton of unnecessary stuff. Maybe follow this pattern as well?

[pydanny]

Hey @sehmaschine, this should make building themes much easier to comprehend. In the 0.7.0 milestone I want to focus on making theming easier. In 0.6.0 we are getting core logic in.

[sehmaschine]

@pydanny looking forward to 0.6.0/0.7.0 then.