Good advice, Stephen.
The specialized tool I am building is ultimately intended for "authors" who are creating a website from stacks that they are editing, and that are normally deployed in a desktop application. The final result will be uploaded and served to yet other users as a "web version" of the desktop app, with the application logic resident on the server. The 'preview' will ultimately serve these website-creating users, who will have to adjust their source stack’s content so it looks OK in the web environment. A network connection is not guaranteed during the editing cycle…and there will be multiple simultaneous users… and each page depends on resources that would have to be uploaded with it… and… and…. Previewing local files is instant, clean, informative, and, I hope, accurate. On Nov 20, 2011, at 12:06 PM, stephen barncard wrote: > Tereza, > > Is there some reason why you can't work on http pages on an online server > rather than on your local machine? > This 'sandbox' could be a directory on a server that is password protected > until ready for public. Then the 'Disable Caches' method in the Developer > menu of Safari will work. > > As web pages are text and usually small, the upload time is quite fast and > all the popular FTP programs will allow the double clicking in FTP listings > and launch the document in the assigned text editor. Moreover (at least on > the Mac) when you SAVE this document as you normally do, the file is not > saved locally, but patched back into your FTP program and saved on the > server. > > Your *edit, 'compile' , run and refresh* cycle can be nearly as fast as > working on the desktop, even with an ordinary DSL line. > > In the days of using Dreamweaver and avoidance of hand editing, working > locally with a shadow set of files and reconciling made sense with slow > connections. The method above is much more efficient and works for 'fixing > in situ" as well. > > On 20 November 2011 09:13, Tereza Snyder <ter...@califex.com> wrote: > >> >> On Nov 20, 2011, at 10:15 AM, Andre Garzia wrote: >> >>> Tereza, >>> >>> If you are using a local webserver, set it to send no-cache HTTP headers. >>> This way, no matter if you are using RevBrowser or something else, you >> will >>> be safe. If you are just opening file urls in RevBrowser, then, use META >>> tags to disable caching. >> >> I *am* using: >> >> <meta http-equiv="cache-control" content="no-cache"> >> >> No joy. >> >> I haven’t had a chance to try Ken’s or Rodney’s approaches, but I have >> high hopes. >> -- Tereza Snyder Califex Software, Inc. <www.califexsoftware.com> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
