> I've did it with "include into" and use a normal string variable, but IMHO
> this gives the same result as using save output(_request{"sidebar"})
You can use 'include into(_request{"sidebar"})'.
> Let's say I'd spice up your bicycle online store (the screencast) with a
> categories popup in the left sidebar, build from a 4D database and a right
> sidebar holding two dynamic areas, a condensed view of the shopping cart and
> a related products list, dynamically created depending on the selection you
> make in the main area. Would you incorporate these parts with this
> pseudo-circuit mechanism within the layout file for left:sidebar and
> right_sidebar?
Probably.
> Aren't nested circuits always a kind of plugins as long as they create an
> output?
Yes.
> And how can the main page (output of the parent circuit, or output of the
> root circuit ? ) know nothing about that nested circuit.
It knows nothing other than the fuseaction to call and the attributes it
expects. It's like calling a method and passing parameters.
> Or do you design the layouts initially from scratch and rely on Fusebox to
> preview the output, while styling the site?
I usually start with fusebox since I am usually the designer and the coder.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoy.org
_______________________________________________
Active4D-dev mailing list
[email protected]
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
