might as well have two copies of the source, one the original, the other the rendered output of that.

Then each page load would simply verify that we have a rendered version that is newer than the original code (and use it), or re-render the original.

2001/12/08 12:46 US/Pacific (via web):
I really like TWiki's method of handling this. You have a simple text entry box to enter your structured text in. However, instead of Save changes, you have a Preview button. You cannot save a page without first previewing it. To make edits to your preview, you just hit another button (the browser's back button does not always work; IE 5.5, for example, loves to lose edits this way!) to re-edit. After you're happy with the preview, then you hit the Save button.

It might sound complicated, but in reality, it's not very hard at all. It took me two times to edit a page, and then I was hooked, to get used to it.

Samuel A. Falvo II

2001/12/08 12:59 US/Pacific (via web):
This was more a comment about adding speed to the site, but I like the preview idea.

Jason Byron

2001/12/08 13:00 US/Pacific (via web):
Oh, so as you made your edits, the preview would update in real-time?

Samuel A. Falvo II

2001/12/08 13:17 US/Pacific (via web):
wow, no, what I meant was that a visitor going to a page would not make the page go through all of the formatting of the source (because that would be done on save) and thus the page would render faster (ie not need to render), and put less of a load on the server. - jason

2001/12/08 13:18 US/Pacific (via web):
Oops, my misunderstanding. I see what you're talking about here. Basically, pre-rendered caches. :) That actually sounds like a great idea.

Samuel A. Falvo II