On Thursday, September 11, 2014 6:13:31 PM UTC-7, Andrew Ashling wrote:
>
> I'm considering buying a Chromebook. 
> Is there any progress re saving TW-Classic in Chrome.
>
 
TWClassic uses the TiddlySaver.jar Java applet to provide local file I/O 
functions for Chrome (on PC and Mac).  TiddlySaver was recently updated to 
work with the latest update to the Java engine that affected permissions 
for local file I/O with signed vs. unsigned applets.

Unfortunately, Chromebook does not support native Java applets, so 
TiddlySaver can't be used there.  However, as of version 2.8.1 (June 2013), 
TWClassic provides a fallback handler that uses the browser's built-in 
"download-and-save" mechanism when no direct file I/O method is available. 
 This works by re-assembling the TW target file from the current runtime 
memory, and then simulating a "download" event to send the file image to 
the browser so that it can then prompt you as to where you want to save the 
file.  If you select the same path/filename as the current document, it 
will overwrite it, saving the changes to the local file.  Note that this 
fallback handler does *not* automatically create backup files, but it does 
allow you to give a new filename to the current document each time it is 
saved, so you can manually avoid overwriting the "original" document 
content until you are satisfied that the new changes are correct.

Alternatively, is there a comprehensive, easy-to-follow how-to for 
> installing TW-Classic on your own domain.
>

The easiest way to publish a TWClassic document is to simply upload the 
file to your website hosting space, and name it "index.html".  This is 
exactly how updates to http://classic.tiddlywiki.com (and 
http://tiddlywiki.com) are published.   Once you've uploaded your TWClassic 
index.html file, anyone visiting your domain will automatically be 
presented with the complete TWClassic document for viewing in "read-only" 
mode.  You can then periodically update the hosted document by editing a 
copy on your local computer, and then uploading it to your domain, 
replacing the previous index.html file.

If you want to edit the hosted document directly online, or allow your 
visitors to edit the document, then a more involved solution is needed. 
 Generally, this requires some custom plugins installed in the TWClassic 
document to provide an "upload" handler that replaces/extends the default 
file I/O handlers.  In addition, some kind of server-side script or service 
is needed to receive the uploaded file data and store it in the desired 
location.  One system that has implemented this type of solution is 
http://www.TiddlySpot.com, which provides 3rd-party hosting for both 
TWClassic and TW5 documents.  There should be some documentation (and a few 
people on this group) who can help you with setting up TiddlySpot-like 
services on your own domain.

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

YOUR DONATIONS ARE VERY IMPORTANT!
HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...
   http://TiddlyTools.github.com/fundraising.html#MakeADonation

Professional TiddlyWiki Consulting Services...
Analysis, Design, and Custom Solutions:
   http://www.TiddlyTools.com/#Contact

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to