TS6.1 - pre-collapsed containers?

I seem to recall reading or hearing about the ability to have DCT Forms drawn initially with all containers collapsed - but I cannot find the reference anywhere now.

Is my recollection correct? Is this possible?
There doesn't seem to be a 6.1 rev of the TST docs - and I don't see any mention of this in the 6.1 Release Notes - so if this is possible in 6.1 could someone share the information about it?

I'm especially interested to know whether it can be controlled on a field-by-field basis or whether it's an all-or-nothing deal.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Migrateduser

I don't know why it's not in the release notes for TS6.1, but the feature works as follows:

add a new attribute to the <viewoptions> tag in templating.cfg.

<viewoptions replicant-render='collapsed'/>

You can explicitly set it to normal with replicant-render='normal', this is also the default.

Hope that helps.

p.s. It is not configurable on a per-field basis.
______________________
Kerry Kartchner
Interwoven, Inc.

Edited by nochatting on 04/01/04 12:30 PM (server time).

Adam Stoller

Thanks for the info (I was pretty sure I heard that was coming) - when I get 6.1 up and running I'll play with it and possibly file a feature request for per-field control, or 0-instance pre-collapse.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

JeremyH

Is collapsing on a per-field basis in the pipeline?

Also, are there any other options for replicant-render?

And, is there a way to default non-replicant containers to a collapsed state, also?

gzevin

Frankly, I am very annoyed by the new 'features' that have been introduced into 6.1.

We relied on some behaviour in 5.5.2, and now we have to go and check EVERY template to see what could be wrong

and, we could control 'collapsability' of replicants by setting default/min.max number... now it all seems to be following 'collapsed/normal/' rule

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

gzevin

Is that possible that you tell me where is this documented?

I could work it out from DTD, but it's not mentuioned in the docs

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

gzevin

I have some complex replicant/container structure. And it looks that this collapsed feature works only for some replicants and not for containers, and for some other replicants. I cannot find out any rule so far...

and also - <replicant max="1" default="0"> - shows me expanded replicant...!! I think it's a bug

has any testing been done for this feature?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Migrateduser

> Is collapsing on a per-field basis in the pipeline?
If I understand your question correctly,
it applies to all replicant containers in a DCT.
It is not specifiable on a per-field basis.

> Also, are there any other options for replicant-render?
The only supported options currently are 'collapsed' and 'normal'.

> And, is there a way to default non-replicant containers to a collapsed state, also?
No.

______________________
Kerry Kartchner
Interwoven, Inc.

Migrateduser

The collapsed feature only applies to "replicants", and its purpose is for replicant *instances* to be collapsed - not the replicant container itself.
In the IWOV style DCT, this means items whose body is composed of a <replicant> element should be rendered with it's instances (if any) collapsed.
In the 6.0-style DCT, this applies to containers or items with min != max != 1.

In the case of an IWOV DCT with <replicant max="1" default="0" min="0">, the replicant container will still be uncollapsed. Any replicant instances, however, will be collapsed.
So if it were <replicant max="5" min="0" default="3">, you should see 3 collapsed replicant instances.

By all means, if there are replicant cases that it doesn't seem to be working on,
please contact support and file a bug.

This feature was intended for situations where a very large number of replicant instances are present in a DCT, but where these instances are typically accessed randomly [esp. via the tree control]. I am curious whether there is another use-case that we have missed.
Would you be interested in a means of specifying on a per-field basis whether an replicant/container is collapsed or not?
Would a FormAPI method to collapse/expand replicants and containers be a reasonable solution for your scenario?

Regards,
Kerry Kartchner

______________________
Kerry Kartchner
Interwoven, Inc.

gzevin

what I see is that I bring DCTs from 5.5.2 and they do look different on opening in 6. I don't mean different GUI, I mean that some replicants (with default=0) come uncollapsed, whereas they all were collapsed in 5.5.2. This creates a HUGE issue for us as the users are not happy as they have to scroll where everything was next to each other before.

yes, I figured out how to fix this, just by adding one more attribute, but what I see is the absence of backward compatibility, unlike what IWOV claims.

I cannot go to hundreds of DCTs and start doing FormAPI coding during our upgrade from 5.5.2 to 6.1. Later - maybe, but now I am thinking how to minimize the impact

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

gzevin

another thing - I
ve tried out

<viewoptions showtree="f" />

It's full of bugs... Just don't want to start on that.....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

Personally, I'd like the ability to set whether a field (including replicant/container item itself) is initially rendered as 'collapsed' or 'normal' at the DCT/field level (with perhaps the templating.cfg setting acting as a default if otherwise not specified) and being able to access/interact with this setting at the field level through FormAPI would be a natural extension of such a per-field attribute.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

As per use-case - we have situations in which the context (e.g. directory path) in which a particular DCR is created should determine whether certain fields should be displayed or not - and some of these fields happen to be replicant-sets. It would be a cleaner UI appearance if the entire replicant were collapsed by default rather than the way it shows up now.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com