There are a few issues in finishing out the WebHelpers tickets. (By the way, the place for new tickets is Bitbucket: http://bitbucket.org/bbangert/webhelpers)
== #1 == On Sun, Nov 22, 2009 at 12:07 PM, Marius Gedminas <[email protected]> wrote: > Actually, it isn't completely backwards-compatible: you can no longer > pass HTML markup to Flash(). I filed a bug and uploaded a patch here, > I'd appreciate it if you could take a look at it: > http://pylonshq.com/project/pylonshq/ticket/659 > > There's another bug with an outstanding patch that I'd love to see merged: > http://pylonshq.com/project/pylonshq/ticket/656 Those are both applied in webhelpers-dev, along with your other auto_link tickets, except one that's going to take some significant parsing work: PylonsHQ# 657: auto_link(literal('<url>')) stops parsing too soon http://pylonshq.com/project/pylonshq/ticket/657 Anybody want to try to make a patch for it? == #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 We add a hidden field when the method is not GET or POST. The complaint is that all input tags need to be in a block construct like <div> or <p> rather than directly under the <form>, or it's not valid XHTML. But I don't want to add visual tags the user didn't specify in case it messes up their form layout. And it seems silly to put a hidden field inside a block tag because hidden fields aren't rendered. So should I put it in a <div>? == #3 == I upgraded Markdown to 1.7 last year, and now it's at 2.0. Last time I left the extension part out by just copying the main module. Now the main module is split into several modules, so I'll either have to copy everything, or make WebHelpers depend on Markdown, or make it an undeclared dependency. The latter two would mean deleting webhelpers.markdown . Or I could just leave it at 1.7 forever, because the UI is the same and it has all the basic features we care about. Except that both times the upgrade requests came from people who wanted to use Markdown extensions. WebHelpers is currently 888 KB. The old Markdown is 24 KB. The new Markdown is 200 KB (including all the extensions), so it's a significant increase. Generally WebHelpers uses undeclared dependencies so that people don't have to install packages they're not using. But this would be the first time an actual part of WebHelpers was replaced by a dependency, so maybe a setup.py dependency would be OK. Your thoughts? -- 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.
