On Mon, Nov 30, 2009 at 12:32 PM, Mike Orr <[email protected]> wrote:
>
> == #2 ==
>
> There's another ticket that I'm not sure what to do about.
>
> PylonsHQ# 626: form() produce invalid HTML markup when PUT/DELETE method is 
> used
> http://pylonshq.com/project/pylonshq/ticket/657

OK, I put the _method field in a '<div style="display:none">'.  That
way it's XHTML correct, and the style prevents the div from being
displayed or affecting the layout.  I also added an arg
``hidden_fields``, which is a dict or iterable of additional hidden
values to put in the div.

> == #3 ==
>
> I upgraded Markdown to 1.7 last year, and now it's at 2.0.

Deprecated webhelpers.markdown.  Users can install Markdown or the
alternate Markdown2 in PyPI.

Added a 'markdown' argument to
``webhelpers.html.converters.markdown()`` to specify the
implementation module.  If none is specified, it will try to import
``markdown``, or else fall back to ``webhelpers.markdown`` (with a
deprecation warning.)

> == #1 ==

Does anybody want to make a patch for the remaining bugs in
auto_link()?  I'm not a parsing expert, nor do I use this helper.

"webhelpers.html.tools.auto_link should allow slash characters in query string."
http://bitbucket.org/bbangert/webhelpers/issue/10/webhelpershtmltoolsauto_link-should-allow-slash-characters-in-query

"auto_link(literal('<url>')) stops parsing too soon"
http://pylonshq.com/project/pylonshq/ticket/657

I also made a rather significant change to the basic tag builder
(HTML.a() and html.tag("a")).  A new arg ``_nl=True`` inserts newlines
between the child elements for readability.  This isn't much but it's
a refactor to the basic tag building code, which affects all HTML
tags. The tests all pass but if you want to test it with your
application.

I'll be releasing 1.0b2 in a day or two.

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