Oh yeah, and you should also check out those minification web helpers that
were posted here a few days ago. They're incredibly useful. I can combine,
minify, and then cache the result of all my javascript and css only once and
serve it up during production, but have the unminified, separated files
during debugging so I can debug everything in Firebug. As easy as
"${javascript_include_tag('/js/jquery.js', '/js/jquery.innerfade.js',
minified=True, combined=True)}".On Jan 8, 2008 2:05 PM, Devin Torres <[EMAIL PROTECTED]> wrote: > On Monday 07 January 2008 14:35:12 Mike Orr wrote: > > * There are three text-to-HTML helpers: 'htmlgen', 'textile', > > 'markdown'. Do we need all of these or can we standardize on one? Do > > they even need to be in WebHelpers at all? The user could import them > > separately. > webhelpers.rails.form_tag is laughably useless. > > > * Are you satisfied with Scriptaculous/Prototype? Which other > > Javascript libraries would you like to see in WebHelpers. Do you use > > any of the 'webhelpers.rails.prototype' functions besides > > 'link_to_remote'? Ben wants to replace 'link_to_remote' with a > > function that has more client-side-Javascript, to avoid the > > inefficient eval of the JSON result. Are there any other functions > > which would be useful? > jQuery. Nobody uses Prototype or Scriptaculous anymore, jQuery's > simplicity fits in well with Pylons, and I find jQuery more Pythonic than > even Mochikit. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
