I think I read once that google chrome was working on some kind of API for mapping file extensions to web sites, so that you could for example have a .docx map to a url like http://word.com?OpenFile=%1 Opening the file from your OS would fire up the browser and take you to the appropriate site and give the site access to the file.
Is this true or am I just going crazy? If so, where can I find the spec for that system?
Ha! Found it at http://googlecode.blogspot.com/2011/06/working-with-chromes-file-browser.html and http://code.google.com/chrome/extensions/fileBrowserHandler.html
Take that, close voters!
Related
I have developed a google extension and i want to share it with people without uploading it on chrome web store and without letting people to know about the content code of the extension.
What shall i do ???
You can't. The only way you can let people have your Chrome Extension without uploading it to Web Store, is by sending them a .zip file, that they unpack and load in chrome://extensions.
I don't see why you won't want people to know about the content of the extension, and why you won't just upload it to the Web Store.
There is no possible way, except the way Toke Raabjerg mentioned. (Involving developer mode)
Besides this, there is an option to upload the Extension and not list it on the store. With this option only people with the direct link can download your Extension.
The filesystem API cannot be used by unpacked extensions, which is awfully great for development.
But then the real surprise came when I realized I can't use it also with my extension packed, because Chrome tells me it cannot find it in the store and is thus greyed out.
Is there any way to actually develop with the filesystem API then?
My goal, in case this is the wrong direction in the first place, is to write some text to a file when some events in the browser happen. The file should be rewritten, rather than creating a new file, which is why I can't use the downloads API.
Is there any way out of this conundrum?
For anyone stumbling on the same issue - a decent solution is to use the chrome.downloads API to download the file in overwrite and incognito mode.
Overwrite will stop the automatic indices added to downloaded file names, and incognito makes the download invisible in the browser except for incognito windows.
The main shortcoming is that it is of course constrained to the user's downloads folder.
My chrome app needs to save a file with human-readable or standard format such as SQLite (It should be readable outside Chrome).
Is there any API suitable for this purpose?
Some files with .localstorage extension (SQLite format) are in Chrome\User Data\Default\Local Storage folder. Is it possible to create such files by the app?
Edited: The app should not ask user for extra permission.
Thanks for your consideration.
chrome.fileSystem API is what you need.
You will need to ask the user at least once where to save the file, but then you can retain the entry to write again to the same file/folder.
There is no way around asking the user to "escape the sandbox".
You'll want to use the Quota Management API. This is per-origin storage, and you request specific amounts of quota.
It sounds like you also want your users to open the files directly? There's an HTML5 filesystem explorer Chrome app that you can use. It'll show you the files, and you can figure things out from their URLs (e.g. I'm currently using filesystem:http://localhost:8000/temporary/bar for a local experiment).
Or are you looking for something more user friendly? I think you have to use file save in that case, the same way Google Drive does.
I'm about to start a Chrome packaged app project which will include a NaCl component to parse CHM files. But before I start, I just want to check if it's possible to get the app to automatically launch when a CHM is opened (when the users clicks on a link to an chm file, or possibly if a chm file is dragged into a Chrome window).
I've come across some Google documentation here which describes associating NaCl modules with MIME types in the extension manifest, but A: I'm not sure if this is relevant to my problem and B: I've tried doing as it describes, but nothing seems to change.
If anyone can point me in the right direction, I'd appreciate it!
I was able to hack around with chrome.webRequest to filter URLs with .chm extensions, but of course that only works when a user clicks on a direct link to a CHM file, and there is no way I know of to access local files outside the sandbox (for good reason no doubt).
I have since decided to make the project a Drive app with the C++ portion squirreled away inside a DLL on an ASP.net server, which makes a lot more sense to me.
This is, perhaps, a rehash of an older SO question "A html5 web app for mobile safari to upload images from the Photos.app?". I realize that iOS Safari simply does not permit file uploads. However, I was wondering if there are ways to leverage cloud storage API's such as Dropbox or iCloud so as to accomplish the same goal. So, for example, instead of a file upload dialog I would have a url that links to dropbox/icloud that could then prompt the user for the file to send.
Sorry if I'm being too vague - but I suppose I don't care too much about the mechanism of delivery.
If you mean the url belongs to a dropbox/icloud file then you don't even need to "select" any file since the url points to one already, so a simple textbox in a form should suffice.
If this is not what you mean, can you elaborate?