On Mon, Mar 03, 2008 at 11:37:30AM -0800, Mike Orr wrote: > OK, let me get working on a reference implementation of WebHelpers, > and then you can update the Paginator to match it. There will be a > WebHelpers task during the Pylons/TurboGears sprint at PyCon, so I > should have something ready after that.
Very good. > h.url_for will exist but not in WebHelpers. It will proabably be > imported from Routes directly into pylons.helpers. For now, please > make your own shadow functions for framework-specific details > (url_for, session use, GET params, etc). When we figure out how > WebHelpers will access framework services,then you can update those > portions. Will do. > Is h.url() really needed? It "lazily evaluates url_for arguments". > Um, why? It's not like Routes is overhead-intensive. I think h.url > is just a Railsism that can go away. (The name may be used for the > url_for function, but 'url' is a very common local variable name in > user code, so I'm not sure it's a good idea.) Sorry, of course I meant h.url_for(). We already talked about the uselessness of h.url() and I think you said that h.url() would rather be doing the same job. Pretty frequent question on #pylons what the actual purpose of a lazy-evaluated h.url_for() is. > I'll leave you to figure this out. Certainly, providing standard > implementations for the major JS libraries would be a good thing. Implementations or documented examples? If I left the implementations in then we would still have framework-dependent Javascript code in the webhelpers. Hmm, I'll sleep on that. > > The main thing I'm scared of is breaking the API. But I assume that the > > webhelpers have to face a 90% API breakage anyway. > > WebHelpers will be quite incompatible, so this is a good time to make > any API changes. Those who want compatibility can use the older > versions of WebHelpers and your module. True. Let the API demolishing begin. Cheers Christoph -- [EMAIL PROTECTED] www.workaround.org JID: [EMAIL PROTECTED] gpg key: 79CC6586 fingerprint: 9B26F48E6F2B0A3F7E33E6B7095E77C579CC6586 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
