It seems to me that as long as a plugin can contain modules and views,
if speed is a concern, one could define components like
def component(request,reponse,session,*a):
...
return reponse.render('view_for_component.html',dict(.....)
and in view {{=component(request,response,session,....)}}
On Oct 3, 9:57 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
> On Oct 3, 4:58 am, Álvaro Justen [Turicas] <alvarojus...@gmail.com>
> wrote:
>
>
>
> > On Sat, Oct 3, 2009 at 02:47, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > On a second thought, Alvaro is right.
> > > I have implemented a rating component. It works but one may have a lot
> > > of them in one page.
> > > It should be possible for components work both via ajax a non.
>
> > > Moreover if {{load ... }} were to be implemented as Alvaro suggests as
> > > part of the template and run in the same environment it will be better
> > > than creating a helper.
>
> > > I still think this would introduce a lot more complexity but I would
> > > like to see a more detailed description of the idea and perhaps a
> > > proof of concept.
>
> > I have a "beta" version here but it don't work completly. Yes, we
> > should exec twice and I think it is a problem.
> > But I think we have to 'solve' this problem server-side, don't client-side.
>
> Why not allow both, there are advantages for heavy plugins to be
> loaded separately.
>
> > Other idea is: web2py, when see '{{load ...}}', create a
> > 'fake/proxy/whatever' connection to itself using same data of user's
> > request and then gets the response, so it includes the response in the
> > place that '{{load ...}}' was - it'll avoid AJAX but I don't think it
> > is a great idea too. :-(
>
> I do not think it would be too bad but the problem is that it would go
> in a deadlock because of sessions moreover we'd run in a lot of
> trouble with auth.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
