Re: Default Template discussion

On 7/21/07, Janne Jalkanen <[email protected]> wrote:
> > Alex, this is on the todo list. Actually, the BrushedTemplate has this
> > feature already.
> > It's just a matter of available ''porting'' time :-)
>
> Let's do it so that we have proper back-end support for this.
>
> /Janne

Janne,

The implementation in Brushed is just GUI-sugar.
It allows you to edit a particular section, navigate to other sections
for more edits and, when done, save all changes to the page. It is
also possible to toggle back the whole page and make some global
changes to. (eg with find & replace)
There is no server interaction at all during the whole edit session.
Everything rurns locally on your browser.

If you would go back to the server for each section, that would create
a high number of intermediate versions.
Unless you would provide an API to save intermediate changes, like
done for the preview ?
(the intermediate page is saved in the server session)
But what is the advantage of that, versus a complete edit-cycle
locally on the browser ?
The only thing I see is that, with the help of the server, you can
probably run the whole thing in a non-javascript browser. Allthough
I'm not sure how far we could get.

However, we probably can go further: look at the page in regular view
mode, and just change the section-under-edit into a wiki-markup
textarea. (aha ! ) In such case there is even no need for the famous
EDIT tab anymore :-D )
When done editing, that section would be converted back to 'rendered' markup.
At the end of such a cycle, you would still press Save,Preview or Cancel.
(these buttons would appear after your first EDIT activity)

An API for this could be a simple AJAX call to request the rendering
of a certain piece of Wiki Markup.

More thoughts...

dirk