[EMAIL PROTECTED] a écrit :
> On Dec 8, 3:24 pm, Samuel <[EMAIL PROTECTED]> wrote:
>
>>On Sat, 08 Dec 2007 13:06:15 -0800, Steve Howell wrote:
>>
>>>This is what I came up with:
>>
>>>http://pylonshq.com/pastetags/form_remote_tag
>>
>>I see that Pylons uses a standard templating systems with all t
On Dec 8, 3:24 pm, Samuel <[EMAIL PROTECTED]> wrote:
> On Sat, 08 Dec 2007 13:06:15 -0800, Steve Howell wrote:
> > This is what I came up with:
>
> >http://pylonshq.com/pastetags/form_remote_tag
>
> I see that Pylons uses a standard templating systems with all the JS
> renderers hooked into it as s
On Sat, 08 Dec 2007 13:06:15 -0800, Steve Howell wrote:
> This is what I came up with:
>
> http://pylonshq.com/pastetags/form_remote_tag
I see that Pylons uses a standard templating systems with all the JS
renderers hooked into it as standard template function calls. That's
great, now I just h
--- Samuel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Following the masses I was drawn to RoR's website
> today and I saw the
> following HTML template in one of the screencasts:
>
I know a lot of Rails goodies have been ported to
Python, so you might want to google some variations on
"form_remote_
Hi,
Following the masses I was drawn to RoR's website today and I saw the
following HTML template in one of the screencasts:
--
<% form_remote_tag :url => { :action => :search },
:update => :results,
:complete => visual_effect(:blind_down, 'image')
:before => %(Element
