to make it possible to create a TWikiApplication that is purely Forms based, it is necessary / desireable to hide the topic text edit box. I was not able to use css to hide the current text area, so I've surrounded it with a div section of class="twikiEditTextarea"

this is commited into DevelopBranch (as I'm going to use it for tracking Bugs in DevelopBranch)

-- SvenDowideit - 01 May 2005

Sven, this feature has alredy been implemented on SeparateWhiteBoardEditFromFormEdit. You can pass a parameter action into edit which either allows to edit only the form or only the text area, depending on its setting.

Did you only add a css div around edit? How are you going to hide this in a skin without css?

-- ThomasWeigert - 01 May 2005

Also, you did not indicate which label you used to check this feature in...

-- ThomasWeigert - 01 May 2005

oooo, thanks Thomas - when i asked in IRC no-one there knew of a way to do it

I'll leave in the css class as it will allow people to customise the textarea a bit..

mmm, its in r4207

-- SvenDowideit - 01 May 2005

this works fine for new bug creation, but how do you set action=form on the edit buttons on the skins?

-- SvenDowideit - 01 May 2005

What I do is that I create different templates for different applications.

But most of the time I have two edit buttons: edit form (calling edit with action=form) and edit text (calling edit with action=text). I put the edit everything onto the more page.

Sometimes I don't even use an edit text button, as I am using MultiEditPlugin to edit the text region by region.

-- ThomasWeigert - 01 May 2005

ah, ok

That does not work for me, as I am trying to get TWiki to the point where people can make custom TWikiApplications bu only editing topics and adding attachements. right now i'm going to use the css based solution, but I guess I should eventually go back to the solution I had previously (add a Set HIDEEDITTOPICTEXTAREA = on and then have some code to set it to hidden)

-- SvenDowideit - 01 May 2005

Sven, I guess you know that the loading mechanism of templates allows you to specify (in Cairo already) templates that you have defined as topics, see the documentation for Func::loadTemplate in FuncDotPm.

-- ThomasWeigert - 01 May 2005

Alas, the specification of user templates in Cairo is awkward (see SupportTopicSpecificTemplates). Therefore, I have implemented for Dakar the ability to pass the template specification through the Url. However, I really would like to store it in meta data to allow this to be done most conveniently.

To use this feature you could follow the example described in SupportTopicSpecificTemplates.