On Wed, Dec 17, 2008 at 3:01 PM, Rod Morison <[email protected]> wrote:
>
> That .6 vs .7 status list is very helpful, esp for a Pylons newbie
> struggling with documentation which is part .6 and part .7, thanks.
>
> Are there any docs or examples for the new .7 helpers?

The documentation is in the source code, and is now available under
the "modules" section of beta.pylonshq.com.  The section in the
reference manual ("Forms, Validation, and Helpers") is very minimal
(and misses the HTML helpers entirely) because something needs to be
configured in Sphinx, and I'm hoping Ben knows what it is.

> I want to work towards the Pylons 1.0 "Factory approved" usage for
> helpers and templating, but am challenged figuring out what that will
> be. Specifically, I'm trying to work through the tutorials without the
> deprecated helpers, and still take advantage of helpers that will be in
> the forward releases. But, I look in
> webhelpers-0.6.3-py2.6.egg/webhelpers/html/form_layout.py and I see
>
>   """Helpers for laying out forms (EXPERIMENTAL)
>
>   **This module is experimental and subject to change or deletion!**
> If you want
>   to use it in an application, please copy it to the application.

The form_layout module has already been removed in WebHelpers 0.6.4.
It was the only experimental helper that was released; everything else
is either officially supported or deprecated.

Pylons 1.0 will be close to 0.9.7.  The main thing is to avoid
anything marked deprecated.  There are plans for a more modular
@validate but it will be backward compatible.

Routes 2 may actually appear someday, with a slightly incompatible
syntax.  However, the new optional syntax in Routes 1.10 was
backported from Routes 2, as was pylons.url (which will gradually
replace url_for).  So these are forward compatibilities.
Because Routes is only lightly coupled to the rest of Pylons, it
should be feasable to use Routes 1 even if the default switches to
Routes 2, though you may have to hack Pylons' egg-info to change the
dependency or import Routes 1 via a different package name; we're not
sure yet.

Those are the upcoming changes I can think of, so you can see there's not many.

-- 
Mike Orr <[email protected]>

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

Reply via email to