Why do Google have to keep
It can be frustrating that not all features available to widgets are allowed to work in extensions. And for someone as clueless as me, it's also frustrating trying to find the relevant documentation; some of it is out of date and links to a generic holding page for articles that have been moved to github, and the most useful docs are buried in an article system that is at best overcrowded. Thankfully, there is now a sticky in the extensions forum that points directly to the latest documentation and, of course, there are links in the drop-down menus on most dev-related pages. So, now that I know that the file i/o api isn't available for extensions, is there a way around it? Well, depending on what access we need, it turns out that there is.
Every now and then I try to do something incredibly stupid. Usually I want to save a bit of time, but invariably spend days/weeks/months wondering why. Something stupid like automatically saving certain images in a Web SQL database and extracting them later. Anything other than right-clicking on the image and Save image... (which is broken in Turbo mode), or copying the image from cache, or any other simple solution. I've already built up a nice little database but, as the relevant thumbnail images come from different servers, I was stuck. After all, with Opera extensions, it's a simple matter to over-ride the same-origin policy, and make use of the canvas element, right?
|November 2013January 2014|