On Monday 20 July 2009 06:59:39 Michael Pedersen wrote:
> I've begun working with Laurin Killian heavily on these updates, and
> they are starting to show some fruit. The initial checkout of the
> current tg2.1 mercurial repository showed over 200 warnings on a new
> "make html". We have that down to 0 now.
>
> We've also made a fairly long list of "todo" items, using the Sphinx
> todolist extension. And, on top of all that, we've started to make
> some dents in that list.
>
> All in all, I think the results are starting to show for themselves.
>
> http://web.icelus.tzo.com/~marvin/tg2 <-- the new docs
> http://turbogears.org/2.0/docs/index.html <-- current docs
>
> Any/all feedback is welcomed. If you've already sent in notes, they
> haven't been missed. I've got several more threads marked as "add
> these to docs too", but haven't gotten around to doing so. Been a bit
> busy getting the docs to this point :)
>
> The new docs link above will be automatically updated every night,
> whether or not I get updated docs uploaded to bitbucket. So it can
> always be used to check out the current progress of the updates.

First of all - great work!

I took a peek into the validation examples, and two things are missing IMHO:


 - a recipe to replace the old callable-argument-mechanism known in TG1 to 
dynamically decide which form (or other validator set) to use. 

 - how to work with validation inside the controller - actually, raising 
formencode.Invalid should work, and a small bit about how to do that with 
actually providing meaningful error messages.

Did you publish the HG-repository? I could try & enhance the docs myself then.

Diez

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to