I like the idea a lot, James.
I should probably make a separate thread. But, along a similar vein ... I
was recently building up a zero project so as to have an example project in
a pluggable app that I'm building.
First, I just can't stand the base template that doesn't get copied into
your source control. So, I copied base.html to my templates directory and
stripped it to:
{% load i18n %}
<!DOCTYPE html>
<html lang="{{ LANGUAGE_CODE }}">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>{% block head_title_base %}{% if SITE_NAME %}{{ SITE_NAME }} : {%
endif %}{% block head_title %}{% endblock %}{% endblock %}</title>
{% block extra_head_base %}{% block extra_head %}{% endblock %}{%
endblock %}
</head>
<body class="{% block body_class %}{% endblock %}">
<div id="nav">{% block nav %}{% endblock %}</div>
<div id="subnav">{% block subnav %}{% endblock %}</div>
<div id="body">{% block body %}{% endblock %}</div>
<div id="footer">{% block footer %}{% endblock %}</div>
{% block extra_body_base %}{% block extra_body %}{% endblock %}{%
endblock %}
</body>
</html>
The base.html template is ugly (not the design of the pages but the html
source itself), sorry :) No self-respecting frontend guyirl is going to
allow the base template to come from framework magic. Also, is everyone
going to want to {% include "facebox_js.html" %} on every page? I would say
that most websites are not.
Anyways, that wasn't my main point. I really should have made a separate
thread or two :-)
Second, I didn't want people to have to install pinax to run my sample
project. So, I stripped out imports of pinax from the settings. I even had
the idea of maintain a project, "nopinax", just a (further) stripped down
zero project, geared to run with django latest stable without further
dependencies. Maybe there can be a "nopinax" project within pinax instead
;).
See you guys at Pycon!
Skylar
On Wed, Feb 23, 2011 at 2:59 PM, limist <[email protected]> wrote:
> This is excellent; for one thing, I'd dearly love to have the whole shebang
> of Pinax unit tests pass again. It'd also help keep Pinax in the role of
> being a canonical example of Django usage, w.r.t. apps, configuration,
> integration code, etc.
>
> What can those of us not on the Pinax core team do, to help accelerate this
> effort? Will someone review pull requests if we fork this branch and do
> some useful work?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Pinax Core Development" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/pinax-core-dev?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Pinax Core Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pinax-core-dev?hl=en.
