Ok -
I just did that now have ((Navigation)context()) which was a
refactoring snap from ((Session)session())
I assume this will be more efficient as I am still having generic
hangs from my Session faced version
of this application.
Thanks
James Cicenia
On Apr 19, 2007, at 12:08 P
You might consider passing informations through worequest.userInfo
dictionary as an alternative to bindings.
From a sub component, you can still do bindings like " value =
context.request.userInfo.theKeyToSomethingINeed; ".
- jfv
Le 07-04-19 à 13:37, James Cicenia a écrit :
A navigation obj
A navigation object is a nice idea which is what I was using the
session for... so I can pass one.. but still...
is there would be a way to just grab the bindings in the child
component programatically so I don't have
to manually bind dozens of component contents with their children's
bindi
I have to do that for a Web site (www.acaiq.com). In the DA, I
create a Navigation object where I store the stuff that I need and I
send the Navigation object via bindings to components.
Hello -
I need a refresh here. I am trying to convert my catalog type
application to be
all DA in th
On Apr 19, 2007, at 9:46 AM, James Cicenia wrote:
Hello -
I need a refresh here. I am trying to convert my catalog type
application to be
all DA in the front end.
However, what is the best way to get at the values from the
contained content
within the component content ??
I have a few
Hello -
I need a refresh here. I am trying to convert my catalog type
application to be
all DA in the front end.
However, what is the best way to get at the values from the contained
content
within the component content ??
I have a few wrappers that get switched in from page. I need those
