Criteria for Clubbing DCTS-

Hi,
We donot want to have a separate DCT for each type of content.
We are thinking of clubbing more than one DCT together.
like having a single DCT for header and footer file.
I want to know what is the best practice for clubbing it-
What criteria should be considered before clubbing

Find more posts tagged with

Comments

Adam Stoller

Hi,
We donot want to have a separate DCT for each type of content.
We are thinking of clubbing more than one DCT together.
like having a single DCT for header and footer file.
I want to know what is the best practice for clubbing it-
What criteria should be considered before clubbing

I don't think I've heard the word "clubbing" used in this manner - out of context it sounds like you're a member of the DCT hate group, and you want to go out and smash all the DCTs you can find ;-)

I believe more accurate terms would be:

That being said - there are a number of alternatives depending on the actual requirements. If the items to be "clubbed" are truly identical then most likely you're looking at an inline script (RTM FormsPublisher Developer's Guide).If that's not what you're talking about - please try to elaborate.

garima

The thing is that we dont want to have a lot of DCTS.
If we can include the functionality of two or more DCTS by a single DCT,then
we would like 2 go for a single DCT.
In this case:
Till now,we are doing this for DCTs that are almost similar -they have almost same type and number of fields.
the same thing can be done for DCTs that are different-by hiding the fields.
But is it a good approach?
Also if some other criteria should be taken into a/c b4 grouping them.
Then please suggest me.

Adam Stoller

The thing is that we dont want to have a lot of DCTS.
If we can include the functionality of two or more DCTS by a single DCT,then
we would like 2 go for a single DCT.
In this case:
Till now,we are doing this for DCTs that are almost similar -they have almost same type and number of fields.
the same thing can be done for DCTs that are different-by hiding the fields.
But is it a good approach?
Also if some other criteria should be taken into a/c b4 grouping them.
Then please suggest me.

Based on what you've written, I'd suggest using an inline script which could perhaps process some variable to determine which variant of the DCT you want and include the correct FormAPI file to hide/expose the different field. This is assuming that the two (or more) forms are something like 90% the same.

Sean_Hanck

I always try to "club" or group similar DCTs, I find it simplifies the user experience a bit.

I would concur with Ghoti here, read the documentation it will show you how do get it set up, but your stuck figuring out what you want done.

The way I have accomplished this in the past is to have an item (either drop down or radio) that would indicate the sub-group. I attach an onchange event to that item and through formapi hide or show the required fields. A caveat is that onchange script also needs to run onload for files that are being edited.

Sean