DjangoBot: #django-sprint

jacobkm: I"m not entirely clear about the difference between "topics" and "howtos"

should the custom template tags stuff be a topic rather than a howto, for example?

good evening

SimonW: I'm trying to have a difference between cross-topical "howto" guides -- things that cover a specific *task*, as opposed to coverage of a specific *topic*.

SimonW: There's a number of things which overlap; custom template tags are one.

OK

I like having it in howto/, though

I think I get it - "How do I ... ?" is a howto, whereas detailed introduction to e.g. the template system or the request/response cycle is a topic

topics = theory, howto = practical advice to achieve a goal?

Look at, say, howto/initial-data -- that covers models, SQL, django-admin, and fixtures; that's what I have in mind for howto/

exactly

I've been wanting to do a "How to use jQuery with Django" / "How to use YUI with Django" / "How to use Prototype with Django" series for a while

I also picture filling out howto/ with some of the great stuff folks are putting on their blogs these days.

almost as a joke

but mainly because I'm fed up of "Django doesn't support Ajax" comparisons

That would be awesome -- I'd love something like that.

We could have an FAQ:

Does Django work with jQuery? Yes.

Does Django work with YUI? Yes.

Does Django work with Prototype? Yes.

All linking to the same document :)

that said, I think it would be nice to get http://www.djangosnippets.org/snippets/154/ in to core

Maybe an "ajax and django"-faq should over those :D

since I use it (or a variant of it) on any project that uses Ajax

SimonW: How's Nat?

fine but bossy

she's not allowed to move for 48 hours

Ugh

Glad she's OK, though.

know if anyone's working on the forms documentation? I'm tempted to give it a go, maybe merge in a few bits from the newforms chapter in the Django Book at the same time

rats, "make html" is throwing an error

from jinja.utils import CacheDict, raise_syntax_error

ImportError: cannot import name raise_syntax_error

I've updated sphinx to most recent svn version, looks like jinja didn't quite make it along for the ride though

yuck... looks like easy_install has its various versions and dependencies mixed up

eek

I think the current svn version of sphinx may be broken

hm :/

I've got 0.1.61950 here

that's the version I'm fighting

hm, this works for me

I just did "sudo easy_install svn.python.org/projects/doctools/trunk/"

..on a mac

I'll try that

never done easy_install against a svn url before

it worked! thanks

:)

I was checking out and running sudo python setup.py install manually

it checks it out to a tempdir

ah

ok

another less approach is to have SVN WC and doing sudo setup.py develop from inside it. This crates some way all the svn up changes are automatically available without having to re-' setup.py install' over and over

*creates

sudo setup.py develop ? sound shandy

sounds handy

presumably works with a .pth file or similar

yes, it uses .pth magic

SimonW: if you wanna take on forms *be my guest*!

I'd planned on it since it's a pretty big task, but of course I'd happily let you do it :)

I've done a bit of shuffling, but wow it's a bigun

Yup

I'll hack on it for another hour and see if I'm making much progress

Nothing compared to models :)

I dunno... models are at least documented

feel free to crap out part-way through -- some work is better than none!

newforms is still missing a fair amount of stuff

Don't worry too much about adding missing content -- that's fairly easy to do once the structure's done.

I want to de-emphasize the bit about bound v.s. unbound forms

since I find I don't actually need that bit of theory much when I'm working with newforms

if you feel like it, be my guest... but don't shave too many yaks there!

I'd move the bound/unbound stuff to ref/, and have topics/forms just really cover usage.

SimonW_: dunno if you got that last bit: "I'd move the bound/unbound stuff to ref/, and have topics/forms just really cover usage."

my current yak to shave is csrf

I want csrf protection in my forms rather than in middleware

Yeah, a CSRF'd form would be sweet.

No, I'm working on documentation! Focus!

haha

do you have the code for making the docs look like the rest of djangoproject.com yet?

Um, sorta -- I've got part of what I'm going to use on the actual website, but I'd also like a standalone template that looks "right" when you run a local build.

That'll need to be Jinja templates since I don't want to fuck with making Sphinx use a different template engine -- Django and Jinja are close enough that I should just deal.

jacobkm: any hint how to link to a subsection of another doc file? e.g. don't know how to refer to the old ".. _RequestSite section of the sites framework documentation: ../sites/#requestsite-objects"

jezdez: maybe with this kind of markup?: http://sphinx.pocoo.org/markup/inline.html#cros...

jezdez: sorry, was a way for a bit. yeah the idea is to just create an aribitrary target wherever you'd like to link