Jun 222014
  1. this-matter’s terms-of-use including privacy/confidentiality: JotHere’s(right column) except:

    1. none
    2. section history additional in REVERSE order:
  2. this section’s
    1. status including percent-complete and release status: see section history additional especially latest
    2. categories in the order 1.JotHere groups-then-alphabetizes:
      section history additional in REVERSE order:

      1. prior exists
      1. Google Drive M8SLXW
        1. add to
      2. HTML MJ90PD
        1. add to
      3. service to share file/folders across the Internet LGUBTX
        1. add to
    3. title

      composing/editing, or just viewing/reading, a single/individual public or private HTML file in Google Drive

      section history in REVERSE order:
  3. was 1st posted as a comment –to be moved & merged into here
  4. is quite important as
    1. HTML is seemingly the most popular format for textual content starting ~2004 thru the foreseeable future, and plus seemingly by-far the most powerful popular format
    2. Google Drive (main article) is big
      1. is probably among the top 5 Internet read-write shared file systems indeed cloud storage
      2. is readily available to seemingly every Internet user on seemingly any device
      3. is very inexpensive, plus every account gets ~15GB free: frankly it has always cost me 0
      4. is versioned (at least basically, at least for files, though some medium-serious problems)
      5. is seemingly automatically fully scalable (so good performance seemingly even if seemingly everyone in the world is simultaneously using your data!)
      6. appears near flawlessly reliable
      7. offers advanced security: ACL plus “only with the link”
      8. Con like most: Google administrators can fully access your data (unlike supposedly say SpiderOak)
  5. for just viewing/reading
    1. for files (HTML + more) fully public including in web search engines, indeed for seemingly everything to make up a website (HTML + CSS + js + images + more), Google has made it quite easy
      1. Google just gives the author URL for his/her file
        1. which seemingly can be used like your typical URL: the user can just open it fine in a web browser plus it can be included in web code (HTML, CSS, JS, etc.) to get additional file resources (images, code, etc.).
        2. which unmemorable and medium-long (as short as ~60 characters) but, if chosen well, is also permanent even if the file is renamed, moved, or changes owners
        3. but which will fail immediately if ever the file gets even mildest privacy
          1. for instance, the draft of this post: the URL is (err, would be) https://googledrive.com/host/0B1ockHRlkWswNnF2NDBJRmdkNWc and indeed this file is public, BUT “only those with a link”, so when anyone (including the author) tries to open that URL, Google replies quote(404. That’s an error.<br/>The requested URL was not found on this server.) then lies quote(That’s all we know.)
      2. Google Search(Google Drive host) quickly tells how and when and the details
      3. More tips TBA
    2. for any other type of file including with any privacy including weakest “only anyone with the link ” Google has left it semi-hard
      1. the power is under the hood, including for advanced privacy, but still 0 support (notably 0 GUIs) built-in (unless one only wants to only see raw HTML code in a crappy text editor), but seemingly fairly easy to program something to do the job but so far only around 3 have and none and all are just so-so
      2. Why does Google do this: brutally stops all private HTML from displaying? Possibilities:
        1. maybe for at least private writings, Google wants to force Drive users to use their Writely aka Google Docs word-processing doc but this uses a 100% proprietary undocumented text format, long abandoning HTML (and a lot less powerful than HTML) -as perhaps Google thinks they are bigger than HTML(!)
        2. maybe, as Google does (or else did initially) for YouTube, Google is now doing for text as well: is only willing to provide free hosting ONLY if its public including in their search engine
        3. I don’t know but I sure wish I did… as Google then forces HTML authors and even readers to do a tricky and somewhat-painful workaround.
      3. so presently before any private HTML file in Google Drive displays properly for a reader, the first-time only, s/he will have to do about 3-minutes of fairly simple up-front work
        1. yes, a tad painful the first-time due to Google not fixing this, but the simplest existing method I can find to securely-share (yes even if just for viewing) a private HTML file stored in Google Drive (fully public HTML files Google Drive shares no-problem).
        2. but the fix steps below
          1. are the simplest I can find
          2. open up powerful free capabilities for all sorts of future uses besides this
        3. specifically the reader must do each of these steps s/he hasn’t already done:
          1. first, log into the Google account granted access to the file  –quite acceptable but if you have multiple accounts, you may have to try each one or ask the person granting you access email address was given access to the file
          2. second, select and get-working an app for viewing the HTML file
            1. where easiest is to try those recommended until you find one that works
            2. choices are, from easiest first:
              1. less than 5 minutes: an app built for Google Drive files
                1. choices are from most recommended
                  1. a code-text editor with preview:
                    1. using Editey
                      1. has the cleanest presentation
                      2. in Firefox, worked fine
                      3. in Chrome, 1 of 2 times it failed to load due to a spurious “500” error
                    2. using NeutronDrive
                      1. loads a bit slow including annoyingly tries to open other previously open files
                      2. in Chrome, works
                      3. in Firefox, has minor spurious warnings of being an unofficial site due to the apparently-otherwise-good certificate having bugs
                    3. using ShiftEdit
                      1. tried but so far haven’t been able to get to here as the given URL doesn’t load the page, as it seems to require a domain or URL for “the site” but an individual Google Drive file doesn’t generally have one it would seem.
                    4. examples of both
                      1. of some of these, indeed the real uses causing this section to be written, are at /4405#N7JM6Y
                  2. that’s all I’ve been able to find after a few hours of searching 2 days ago
                2. grant the app access: after clicking on the URL to view the file in the particular app, {the reader needs to Accept the requested file viewer/editor app’s permissions then likely reload the file’s URL, iff s/he hasn’t already accepted these}
              2. 15+ minutes: any web browser (else an HTML editor with WYSIWYG else Preview) plus Insync or other converter app to make Google Drive appear in the local file system
                1. Unless the reader already has this working, first try the previous method as the converter app, while dramatically more powerful, also can at least 15 minutes to obtain, install, and get familiar with
  6. for composing/editing
    1. basically it’s the same as viewing a private file but where the viewing app is also an editor, as most appss are
      1. so just use most any HTML file editor (comparison) which supports one or more of, from easest first:
        1. Google Drive files, where all I’ve seen
          1. sadly none have WYSIWYG, but most have live HTML preview but that still fails to cursor-sync & scroll with the simultaneously displayed HTML code
            1. why I don’t use them (for HTML)
          2. all are in browser-editors -very handy
          3. Editey is specifically designed for creating public websites on Google Drive, simple thru seemingly very advanced, and these tools & hosting all free
            1. my 1 request for support was frightenly good: 2014.06.16 I reported a missing feature (auto-line wrap) & explained why its key plus how it probably easily could be fixed, and the company head replied fixing-it within ~9hours –unheard of!
        2. the local file system (as the typical editor does) –so using an adaptor between local file system and Google Drive, as described for viewing
          1. this I do almost daily for years
  7. section history additional, in order
    1. I needed to do this 1st use
    2. So I now create this post by Creating new post http://1.JotHere.com/4405 plus this file draft by editing-without-save latest 4405.N7BQOR.htm with initial text and saving to 4414.N7JS3R.htm.
    3. ~90% complete 1st draft..
    4. added about 70% more text, most details
    5. spellcheck: for 1-word section titles add another word so ExWeb Spellcheck will complete; #N7LRZA: verify all a-tag links; 100% complete 1st version; publish #1 pst2014.06.22Sun2000,2022,2109,2127.