[silva-dev] Quick introduction and async saving
paul at eurozope.org
Wed Jul 16 21:53:44 CEST 2003
Ok, makes sense. I think I can meet the objections pretty easily
without going too far into the next part. I'll try a few things and
see if it is worth it.
I have a few projects here in which the original XML is sent to the
browser and transformed into XHTML (for viewing) there.
For each change, instead of changing the XHTML, I change the original
XML, which I keep around as an XMLDOM object. I then reapply the
transform to draw on the screen.
In this model, SilvaXML is still in the browser and is the
"authoritative source" of data. Based on the level of complexity of
the SilvaXML model, we can also do some concept of validation on the
browser before sending it to the server (which would also validate it).
I realize these ideas are still filed under "believe it when I see it".
On Wednesday, Jul 16, 2003, at 20:08 Europe/Paris, Martijn Faassen
> Paul Everitt wrote:
>> Is anyone interested in asynchronous saving?
>> Right now, saving something usually means pressing a Save button,
>> gathers up the form data and does a POST. Unfortunately, it also
>> 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
>> 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
> to do the Silva XML transformation on the client side completely
> before this can work...
More information about the silva-dev