Re: [iPlanet-JATO] TiledView - getting Values

Question

Kostas--
This is because in TiledViewBase.mapRequestParameters(), calling
getChild(String name, int tile) before setting the values in the request,
will not set the location for the models other that the primary model-
effectively we are only setting one value (more that once if there aremany
values being submitted). So we get the value of the last value in thetiled
view. This is because getChild only changes the location on the primary
model. Which is why I the following code change worked.Ah, I admit I didn't connect the problem to this. Thanks ver much for
clarifying.
As you stated it might be better to add a place holder for all other
auxillary models and keep them in sync with the primary model.Agreed, this sounds like the correct approach. My unstated assumption was
that all location changes to the primary model would also occur on the
auxiliary models, so that would mean that the mapRequestParameters() method
would then work as intended.
How about making the primary model the controlling model. We would have to
"prime" the other models to ensure they all have the same number of rowsas
the highest model for the request. Otherwise we will the followingsituation
I detailed in the prevoius email:That works for me, but it will no doubt result in some strange behavior for
someone down the road. I'll see what's possible about syncing primary and
auxiliary models more explicitly, or at least checking for the situation
where the primary has more rows than the other models.
This way developers would not have to determine if a DisplayField is bound
to non primary model and do additional processing. I suppose it is aslight
design question as well. Enforcing a MVC approach is about going to the to
the Model to get you data. Onthe other hand NetDynamics just allowed youthe
get the value(s) of a field regardless of the Data Object it was or wasn't
bound to.Right, and I think it's important for JATO developers to preserve both techn
iques. The nice thing the technique of accessing the fields directly gives
you is the ability to obtain data in a non-model-specific way. This can be
just as valuable as providing model-only interactions.
Thanks for your feedback Todd. Let me know what you think.Same to you. I hope others on the list have similar suggestions that they
share with us. I think the above approach is sound and I'll be putting it in
for the next patch version, 1.1.2. If anyone has any final comments, please
let me know ASAP.
Todd

Answer 1

Hi,
I wanted to know how the getValues() method works the reason being,
when the tiled view is NOT bound to a model, it populates all the
fields with the same name as some thing like
PageDetail.rDetail[0].tbFieldValue
PageDetail.rDetail[0].tbFieldValue
in which case, the getValues() method works fine.
But in case where the tiled view is bound to a model, it populates
with different field names such as,
PageDetail.rDetail[0].tbFieldValue
PageDetail.rDetail[1].tbFieldValue
in this case, the getValues() doesn't work. Any soultion to this?
We are using Moko 1.1.1.
thanks in advance,
raju.
--- In iPlanet-JATO@y..., "Todd Fast" <toddwork@c...> wrote:
Does anyone know of is there a single method to get all values of a
display
field in a tiled view without having to iterate through all the
values ie
resetTileIndex() / nextTile() approach.
ie Something that returns an Object[] or Vector just like ND returned a
CspVector. I tried using the getValues() methods but that allways returns
a
single element array containing the first element.
(I think now, that method is used for multi selecteable ListBoxes)Actually, no. We can add this in the next patch, but for now, I'd recommend
creating a simple utility method to do the iteration on an arbitrary model
and build the list for you.
Todd