[silva-dev] Quick introduction and async saving

[Martijn Faassen]

Paul Everitt wrote:
> Is anyone interested in asynchronous saving?
> 
> Right now, saving something usually means pressing a Save button, which 
> gathers up the form data and does a POST.  Unfortunately, it also means 
> that the screen disappears while the same screen you just left is sent 
> back to you.  Your cursor position is gone and you have to scroll back 
> to where you were.

Yes, this is ugly I noticed. So yes, we're interested in this.
Problem is that the Silva setup as it stands now takes
the XHTML coming in, transforms it into Silva XML, saves this, transforms this
back into XHTML, and sends it off back to Epoz. Since Silva is
minimalistic and picky about what kind of content it accepts,
this gives the user some essential feedback about what really happened...

> Even worse, some systems have send you back to the View page for that 
> resource.  You then have to click on Edit again to get back to where 
> you were.

This didn't seem to be a problem with Guido's code.

> Are these ideas worth investigating more deeply?

Yes, if my main objection is surmountable. Perhaps it would be necessary
to do the Silva XML transformation on the client side completely 
before this can work...

Regards,

Martijn