Bo,
I indeed have plans for making both the current theme more extensible
(right now it's not very, in fact, it's kind of locked down, no
worries though, just need to consolidate the CSS into something
more... simple, smaller--all in time), as well as a theming framework.
Installable zips would be a rather easy feat to accomplish, with a
theme uninstaller being nearly as easy. I'm also going to compress the
thread listing more, it's annoyingly huge now, if you ask me. The
theming framework is however further in the future than a few other
items on my list (which I'm somewhat adamant about committing to
verbatim in public).
In the future (within a few months) I'll make a more universally
likable theme, something more concrete, hopefully to become the
default theme. I really like the Lussumo Vanilla theme, as well as
many of their 3rd party themes, but I always spread my own margarine
over anything I design. The current template set in trunk is pretty
much unusable now as I've made that many changes.
I have plans to integrate django-app-plugins for plugin support.
django-messages for private messaging (should be the first plugin,
kind of an eating your own dog food thing). django-notification to
handle all the notifications and django-mailer to handle the
distribution of those notifications.
This morning I integrated django-registration. It works from trunk
with no modification, simply add it to your installed apps and
blam(!), registration. Considering making it a plugin after I get that
rolling. Need to figure out a way to handle URL's with plugins without
using another routing layer. Should be easy, might just require a
restart of the app to refresh the generated tree from a model, or
something. Just thinking out loud here, on a few tats of wiskey, no
less, really this is still a little way into the future.
I hope to have the source ready to go soon. How do you want to handle
that? There's a shit ton of changes. One by one? All at once? Branch?
Sam
On Jun 16, 8:07 am, "Bo Shi" <
bs1...@gmail.com> wrote:
> Hi Sam -
>
> Very nice work! I'm glad that you're eager to contribute back. I'm
> thinking it might be nice to design some sort of theming framework so
> that we can start adding contributed themes, JS libs, etc.
>
> This could start out, perhaps, as simple as being able to specify a
> template prefix for snapboard applications. Instead of current
> hard-coded "/snapboard/" template prefix, one could specify in some
> settings attribute "/snapboard/themes/samurai/". We could move the
> current template directory to something like
> "templates/snapboard/themes/default/".
>
> The media files and CSS would also need some sort of settings value.
>
> (sorry for the delayed reply - was interwebless for the weekend).
>
> Bo
>
> On Sat, Jun 14, 2008 at 3:23 PM, Sam Sutch <
samuraib...@gmail.com> wrote:
>
> > Hello fellow snapboard/django programmers, users and maintainers!
>
> > I've been working for the past little while on a massive visual
> > overhaul for snapboard. To check out a test version I've got running
> > (debug mode et all), log in with happytest/123456 here:
> >
http://beta.samuraifilms.org/snapboard/So far I've completed:
> > * Thread Display -
http://beta.samuraifilms.org/snapboard/threads/id/3/
> > * New Thread -
http://beta.samuraifilms.org/snapboard/newtopic/
> > * Fleshed out several views (re-wrote the profile one) and fixed 10ish
> > bugs (haven't been keeping track). Made several views much faster.
> > * Rewrote all the javascript interface stuff using jQuery.
> > preview_post is now available to any form you want! (as a jQuery
> > plugin)
> > * Ported the layout from yui grids to blueprint.
> > * Added some more detailed profile fields.
> > * Logo?
http://tinyurl.com/4cnaelDesigned just this morning. Could