Lee Worden - 2014-10-23

I think I could do a sequence where

  • you get dynamic operations while editing and previewing
  • when you save, it rebuilds the page contents using dynamic operations the first time you see it
  • the rest of the time, when anyone loads the saved page, it's not dynamic.

I guess people might want a way to make an exception (in either direction - always display the page dynamically, or never), but I think in the majority of cases, while editing is the only time you want to know in detail what the make and load operations are doing and have feedback about what's taking time. It's irritating to wait for the files to load one by one when nothing has changed and you know it's just going to show the same thing as every other time you load the page.

This just-the-one-time-after-saving feature could be implemented by setting a cookie and then unsetting it once it's used.

That would introduce a race condition if another viewer loads the page after you save it but before you view it - then the other viewer would get a slow page load while waiting for files to make. This seems like it might be acceptable. Or maybe I can mark the page on the server side rather than using a cookie, so it'll run dynamically the first time regardless of who loads it.