---------- Forwarded message ----------
From: percious <[email protected]>
Date: Jun 5, 1:30 pm
Subject: ANN: Sprox 0.6(.1) released!
To: sprox


Well, it's been longer than I wanted since the last release.  (almost
4 months)  I was holding out because I wanted to get a few more
features working, but I realized this week that there was a lot of new
functionality, and so it was time to cut a new release.  It turns out,
the codebase grew by almost 20% with this release.  I see this as a
very stable release because I use almost every new feature at my day
job.  Here's a rundown on what is new.

* TableFiller can provide field_methods for customization of output.
* You can now customize the query TableFiller uses.
* TableBase now has __xml_field__ modifier that un-escapes the data
provided by the given list of fields.
* There is a new tutorial for TableFiller:http://www.sprox.org/
tutorials/table.html
.
* Sqashed #8: Synonym Properties causing Tracebacks.
* Added Mako Templates for every sprox widget. (SPEED!)
* Fixed the way relation form fields render.
* Brandon Rhodes provided a fix for TableBase that allows fields to
render with any Widget type.
* Teajay Bernard provided *experimental* support for Editable Dojo
Grid.
* Test framework fixed to be more forgiving of XML.
* Declarative Validation overrides now work properly.
* Field Class added so that you may override both the Widget _and_ a
Validator for a field (documentation pending).

Special thanks to Brandon Rhodes and Teajay Bernard for their
contributions.

You can get sprox from pypi at:http://pypi.python.org/packages/source/
s/sprox/sprox-0.6.1.tar.gz

--~--~---------~--~----~------------~-------~--~----~
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