Forum OpenACS Development: Consistency of text input options

Collapse
Posted by Ben Koot on
I realize in some sections of the system it's a security risk to allow html but... wouldn't it be usefull to have the same text input option throughout all ACS modules as in Lars-blogger
1. enhanced text
2. plain text
3. fixed width
4. html

Right now each module has it's own option (or none) If this has been solved already, please advise.

Thanks
Ben

Collapse
Posted by Don Baccus on
Sort of solved ... we now have a "rich-text" form builder datatype that provides the various options in a sane way that's easy for packages to use.  This was a result of discussions between Lars and I a couple of months ago, after which Lars implemented the new datatype.

Now all that's needed is to rewrite all the packages to use the form builder, and in addition the new datatype ... don't hold you're breath in anticipation but at least there's a clear path to our having the kind of consistency you envision.  And that consistency was a primary motivation for adding a genuine form builder datatype for text fields that may optionally be html etc.

Collapse
Posted by Randy O'Meara on
If one were to rewrite using "form builder", or even write new using "form builder", what would it look like? Are there guidelines, examples, or docs?

Randy

Collapse
Posted by Ola Hansson on
Randy,

by virtue of its convenience/readability/choose-your-favourite-superlative one should use "ad_form" (which is built on top of the form builder) wherever possible.

Some links:

http://www.brasileiro.net/code/forms/
http://jongriffin.com/static/openacs/ad_form/using-ad-form
https://openacs.org/api-doc/proc-view?proc=ad%5fform

/Ola