[Twisted-web] Re: Freeform default button label (+How do you customise the Freeform form-error message)

[Paul Reznicek]

I see a lot of usecases for more buttons, one I'm writing now:
DB record browser/editor, where are at least
   [previous|next|search] + [reload|new|copy|save|delete]
are necessary.
You are right, it is possible to do this with hyperlinks,
but this allow users to bookmark every of this actions,
and to use the browser's back button with undesired effects.

To extend the discussion about freeform:
- please also pay attention to the fact, that all labels, errors
messages, tips, etc. should be easy localizable.
- error messages can vary depending on field contents:
integer error is from user's point of view not a numeric error,
(i.e. "please enter your age as whole number")

Paul

Richard Wall wrote:
> On 16/07/05 20:22 Donovan Preston wrote:
> 
>>Thanks for mentioning this. It gave me an idea about a better way to 
>>support submit buttons in formless (more like forms does it).  However,
>>in the meantime, would it be enough if it said "Submit"  instead of
>>"Call"? Or do you want no buttons at all?
> 
> 
> I think "Submit" would be a much better default.
> 
> It might be useful to be able to add extra buttons to the form but in
> most cases I find it better to have one submit button and a series of
> hyperlinks css styled as buttons.
> 
> For example a form that saves a DB record at...
> http://www.example.com/events/1/edit
> ...would save its contents to recordID=1.
> A "cancel" button would link to...
> http://www.example.com/events/1/
> ...a "delete" button would link directly to...
> http://www.example.com/events/1/delete
> ...which presents a confirmation form. Finally a "duplicate" button
> links to...
> http://www.example.com/events/new/?id=1
> 
> I'm sure there are usecases for multiple submit buttons but I haven't
> yet needed them.
> 
> -RichardW.