create new tag
, view all tags

Rendering of forms below page data

When using forms they're rendered (on viewing the topic) directly beneath the originally page data, without even so much as a line break between it.

It's better to keep some space between the topic text and the form. Perhaps some configurable display behaviour (not in a templeta but as variable?)

Note: It's not a big bug, but still annoying (IMO)

Test case:

  • View any topic with uses a form (like this one)

-- HansDonner - 24 Sep 2001

I think that templates are the correct place to change this, or possibly if it's done via a (skin?) Plugin, then by plugin configuration. Some meta expansion variables allow an argument of prefix which is added if the item exists (e.g. for %META{"parent"}), I suggest we add this to %META::ATTACHMENT%.

On a more general point, do people want flexible rendering of attachment tables? If so, then an obvious route would be an extra plugin entry point. A plugin could then be written for general use (possible using a a template) or skins could change the display in anyway required. If we did go for an extra plugin function, would it be just for attachment or for all meta data rendering?

I've changed this to a feature request.

-- JohnTalintyre - 24 Sep 2001


I'm not talking about attachments (but now that you bring it up...), I was refering to forms like the WebForm used here (the "new" topic classification).

-- HansDonner - 24 Sep 2001

For the BugReporting web that i am making I have added a new tag ( HIDEEDITBOX ) and I added some code in both the edit and view scripts to hide the non-forms info. I also thought of it as a bug needing fixing.

John - are you suggesting that I can specify the template used to display a particular topic (mmm thinking about it - the TigerSkin doesn't even seem to use my home page setting ... ? mmmm)

-- SvenDowideit - 24 Sep 2001

Oops, sorry about that. Exactly the same comments apply to forms and attachments. There is a specific entry in the view template for rendering of forms and another for attachments. You can already force a line break before the form display, but it will be there even if there is no form. Again, I see this as a feature change, it's not a bug that has a clear fix required, first we need to work out what TWiki users want here.

-- JohnTalintyre - 24 Sep 2001

A simple solution isto add a hard coded =<p> tag before a form or attachment (in case there are).

Thinking again, it would have been better not to split up the text, form and attachment into separate variables. A simple %TEXT% (e.g. dropping %META{"form"}% and %META{"attachments"}%) and some ways of controlling the edit box width from a form would be better. See SimplifyInternalMetaDataHandling.

-- PeterThoeny - 24 Sep 2001

I unclear how dropping =%META{"form"}% and %META{"attachments"}% would help. They do give the advantage of allowing different skins to position the information in different places. Also additional options could be added to alter formatting in the future. These could be passed through to plugin functions so as not to bloat the core.

-- JohnTalintyre - 25 Sep 2001

There appears to be two seperate issues here... the position of the Form - which is easy to modify using the templates, and the actual look of the form (which is what I am not happy with).

We display our forms on the top right of every topic. I have severly hacked the renderFormData procedure in TWiki.pm to display it the way we want it, what I think we need is a way to customize this without hacking at the code.

-- JaredQuinn - 10 Sep 2002

"customize without hacking the code" sounds like a definition of style (and thus CSS)... See my comment on LessIntrusiveForms

-- ColasNahaboo - 10 Sep 2002

See also related SimplifyInternalMetaDataHandling, HandleMetaTagsInHandleCommonTags.

-- PeterThoeny - 08 Sep 2003

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r11 - 2003-09-08 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.