A component requires an action. A action can return multiple objects
as long as you have a view to arrange them. perhaps something like
this:
from gluon.template import render
def index():
"""
<html><body>
{{=LOAD('default','combined',ajax=True)}}
</body></html>
"""
return render(content=index.__doc__,context=dict())
def combined():
"""
{{=form1}}
{{=form2}}
"""
return
render(content=combined.__doc__,context=dict(form1=form1(),form2=form2()))
def form1():
return crud.create(db.person)
def form1():
return crud.create(db.dog)
On Mar 23, 12:26 am, mart <msenecal...@gmail.com> wrote:
> These are great! :)
>
> Question: if a component is a part of a page like a form, then another
> part of the page (like another form) is also a component. How would we
> (or rather could we) pair up 2 components and treat them as one? (I.e.
> like in a form to subform relationship?).
>
> As an example, I've been using one of your idea (the audit trail
> slice) to handle combining forms/tables to create tio appearance of
> having all these dedicated forms when really, its just a matter of
> combining. this works well, but the one thing thing that I would like
> to improve in this case is the idea that forms can be a little more
> dynamic (as opposed to having to pre-set different combinations).
> Something like fill form_1, then make a choice (like with a drop down)
> which may change the out come of the next form... but in the end (like
> with the audit trail) it has the full look and feel of being a single
> form.
>
> Thanks,
> Mart :)
>
> On Mar 22, 9:57 pm, DenesL <denes1...@yahoo.ca> wrote:
>
>
>
>
>
>
>
> > Thanks for this and other recent videos.
> > Keep them coming!!!
>
> > On Mar 22, 5:49 pm, Massimo Di Pierro <massimo.dipie...@gmail.com>
> > wrote:
>
> > >http://vimeo.com/21363988
>
> > > Because we do not use them enough and feel we have room for
> > > improvement.
>
> > > Massimo
