Hey,

Werkzeug looks very nice.  It's pretty much exactly what I had in mind
to develop, but now I don't have to ;)

Anyway, I've been reading the docs, and I have some corrections:

For http://werkzeug.pocoo.org/:

==

        path.join(root_path)

Do you mean:

        path.join(root_path, 'templates')

==

For http://werkzeug.pocoo.org/documentation/tutorial/:

==

        instanciated

instantiated

==

        And endpoint is basically

An endpoint is basically

==

        makes it incredible easy

s/incredible/incredibly/g

==

In the example manage.py, where does make_app come from?

==

        'Your alias might not include a slash'

'Your alias must not include a slash'

==

        If you're wondering about the comment between the two input elements,
this
        is a neat trick to keep the templates clean but not create whitespace
        between those two. We've prepared a stylesheet you can use which
depends
        on not having a whitespace there.

The normal thing would be to do something like:

         <input ...
        ><input ...>

==

        which is a terrible good idea for heavy load environments but
somewhat of
        an overkill for that simple

which is a terribly good idea for heavily loaded environments but
somewhat
overkill for this simple

==

        just that it memorizes the result.

just that it memoizes the result.

==

        <a href="{{ url.short_url|e }}">

Shouldn't that be e(true)?

==

        no URls shortened yet

no URLs shortened yet

==

        The first thing we have to do is creating a new

The first thing we have to do is create a new

==

Thanks for the docs.  They're pretty good :-)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pocoo-libs" 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/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to