Item9573: Better save buttons

We currently have a confusing array of save buttons, still an inheritance from the TWiki days:

I want to propose a better solution:

This separates the 3 main actions (save, preview, cancel) from the advanced actions. 99% of users will not need the options. The options block needs to be open at first sight, and it's state saved in a cookie.

-- ArthurClemens - 27 Aug 2010

I think Sven and others have pointed this out before: shouldn't the 'save' be a 'save and continue' like a normal desktop app?

The "save and exit" should be a separate button, or maybe the cancel/close is sufficient.

-- PaulHarvey - 27 Aug 2010

I don't mean to dismiss your original idea, this all up to whoever implements it. I'd be happy with the buttons you've proposed

-- PaulHarvey - 27 Aug 2010

It depends what you expect, and what the user's normal workflow is. In a desktop app you will continue with the document, as edit and view is the same state most of the time. When editing a web page you will be done after some time: you return to the view state to view or go to a different page.

I consider "save and continue" an expert setting.

-- ArthurClemens - 27 Aug 2010

Commenting is disabled while not logged in