nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

User Inteface Improvements through FORM API

cheeku

I was able to remove the left frme of my DCR by using the following code & hence had better UI.

//to hide the left framein the DCT
top.document.getElementsByTagName("frameset")[1].cols=("0,*");

Could you please tell some another methods by which I can improve my UI through Form API

Find more posts tagged with

Comments

Adam Stoller

What version of TeamSite are you using?

The mechanism you showed is almost definitely *not* officially supported.

If you're using 6.x you don't need to use FormAPI to do that - you can control whether the left navigation frame shows up via configuration settings in the templating.cfg file - likewise you can control which of the buttons (SaveAs, Preview, Generate, etc.) appear above the form via the same configuration option in templating.cfg.

If you're using pre-6.x then you can control / override a number of these items with FormAPI code - but it's only semi-supported. 6.x's mechanism is completely supported.

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

cheeku

We are using Teamsite 5.5.2 version. can you tell me How I can control Various Buttons through Forn API. Can I change
the Look, spacing & place of my various items, container & lables through API in this version & how?

Thanks in advance

Michael

I don't believe you can do any of those things in a supported fashion in 5.5.2 using formAPI.

If you search the forums you will find unsupported techniques for hiding buttons such as Save As. There is probably nothing stoping you replacing the provided images for buttons with other ones to change the look -- but once again this isn't supported and you will likely lose your customisations when you upgrade.

Speaking of which, the templating look'n'feel is much improved in 6.x -- perhaps you are better off planning for an upgrade so you can get these things 'out-of-the-box'.

Cheers
Michael

Migrateduser

> Speaking of which, the templating look'n'feel is much improved in 6.x -- perhaps you are better off planning for an upgrade so you can get these things 'out-of-the-box'.

Yes. On top of that, some of the things people are trying to do on this thread, like removing the navigation tree and removing operation buttons, are officially supported features.

--Daniel

cheeku

Thanks for your suggestion. We will definately uograde to version 6.0. But as of now I required
some code snippets of improving UI through workarounds in 5.5.2

Adam Stoller

In 5.5.2 you are very limited in terms of what you can do to improve the UI - at least in a supported manner. For unsupported manners you can hack JSPs, CGIs, etc.
For supported manners you can override the functionality of buttons like Generate and Preview using FormAPI code to trap the event (and I believe there are examples of doing this throughout the forum postings - so I'd suggest searching through the forums if that's sufficient for your needs)

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

Migrateduser

You can always use FormAPI to redirect the browser to an ASPX or JSP page where you have full control, which writes the DCR back to TeamSite in the prescribed format. A lot of work and VisualFormat won't work, but the default UI is pretty weak and buggy (at least through 5.5.x).