It wasn't me. You can't prove anything.


2008-12-02

Google Docs

It turns out that Google Docs is hosting the pictures I publish on the blog. When I write an entry and embed a picture 'img' link in to my Google Document, it is loaded in to the document and Google downloads the image, and assigns it a unique identification number. That number is used to access the image from my blog, not my server. This sis not what I want to happen. If I edit the HTML and type in the address it leaves the reference the way I want it. That is a pain in the ass. Besides, it eats up space on Google. I don't know how much room I have on Google Docs so I don't know what the limit is.

This is just one more thing that is coming between using Google Docs and some other editor. I can't embed videos and such for lack of support and now I cannot use the default image insert either. Shit, I might as well just use a text editor. Then just paste the HTML in to the blog and then in to Google Docs as a backup. Since I use Blogger and Google Docs, all my eggs are in one basket anyway. Can't win for loosing.

The editor is clunky with jagged edges. I constantly have to go to the HTML to fix things that get out of whack. You can't put two pictures on one line without editing the HTML. At least it leaves the code after I put it in by hand. When doing an embedded object, the code just goes away. You see, the editor itself is an embedded object and cannot edit itself. The removal of the code (for videos and such) is a defense mechanism.

At this rate the editor in Gmail makes for a better HTML editor. At least all the images are left as links. In conclusion, I say Google Docs sucks as a means to keep your Blog up to date and backed up.

No comments: