I'm developing an App for Google Docs. I have 2 users. User A shares a file *.customFileType with user B. I want to know how to setup a default application (customFileType App) to be used/suggested when I try to open the file type *.customFileType
User B opens an email with a link to fizz.customFileType.
I want to know how to setup a default application (customFileType App) to be used/suggested when I try to open the file type fizz.customFileType
Your application should indicate in the developer console that it supports the specific file extension and MIME type. This page talks about the steps to go through to configure your app.
See also this page specifically about integrating with open capability.
Related
I need to create an application that should refer an external file for url.
The external file should be manually edited by the user in case of change in URL.
The application should deployed for both ios and android application.
please suggest any other method like create preferences variables that can edited by user
You can create page with a from (with your preferences) and save the date from the form in your localStorage. The localStorage has no expiration date but will be lost when the user removes the app from his device.
The localStorage is a part of Web Storage API which is supported by all modern/major browsers (proof). Since cordova actually serves your app as a web page you can use the Web Storage API as well (cordova documentation)
Documentation info about localStorage can be found here
My requirement is to associate a .exe file with a Windows Store 8.1 app. Is it acceptable to give a link through about section of the store app to a web address from where the user can download the .exe file. Will there be any problem with the certification process. Please suggest any suitable alternative if possible.
There is nothing in the Windows Store Policies that says otherwise. You can't attempt to run the *.exe file programmatically of course, but you should be fine otherwise.
Since the app is network-capable, remember to add a Privacy Policy (see here) detailing whether any user information is sent to an external website/server.
Background
I'm writing an excel app using the Javascript API for Office. (Office 2013). Inside that app, I have several links to folders on my computer/server, which I want to access from the app using the file protocol.
I've tested the file protocol with a dummy HTML file, using this link:
C:\Users\User\Desktop
It works perfectly, opening up the Desktop folder. I've also tested using a networked drive, and it works as well.
Problem
When I add this dummy link into an HTML page in my Excel web app, clicking on it does nothing. When I right click -> Open, IE11 opens a new instance (which doesn't happen with mailto: links), and asks if I'd like to give permission. After I do give permission, the folder is opened.
Goal
I want a single left click to open the folder location without the permissions box ever popping up. Worst case, I want to be able to have the user open a dummy link once during app setup and then once permission is given avoid having to right click -> open.
Question
How can I accomplish the goal here? Is Office just locking down the links?
Update
The primary issue I've found out is that the site I'm hosting the app on wasn't a trusted site. Links using the file protocol only work on intranet and trusted sites. So the only question now is whether the Office store location is trusted.
The problem here lies in the way that Office Apps work. A manifest file is stored with the Office Store, and that is what users download. That manifest points to a server location that the app developer specifies, and that is the location from which the app is served. That is the location which must be added to Trusted Sites in IE.
Therefore to get the File Protocol working smoothly, I'd need to include instructions with my App on adding my hosting server to the Trusted Sites domain, and I'd have to avoid ever changing domains.
I have created a realtime document on Google Drive. When I attempt to share this file with someone who doesn't have my app installed, the file shares successfully, but when they click the file it says "Sorry, no preview is available".
This realtime document is a shortcut file. How do I get it to prompt the person to authorize my app?
I'm using the Realtime Playground as my example as I'm not sure of the specifics of your application.
App authorisation
When you created your application you visited the Google API Console and created a project with Drive API enabled. At some point you copied "Client ID" from the Google API Console into you application ID code.
In the realtime-playground case APP_ID is set in the javascript file rtpg.js (you might not be using JavaScript but there will be an equivalent step for other languages).
rtpg.APP_ID = '840867953062';
File creation
I believe that any drive realtime document/shortcut you created with your application will contain a reference to the creating application (mostly likely in the form of the client/application ID you obtained above).
File sharing
Once you can see your newly created Google Drive Realtime document/shortcut you can share this with somebody else using the normal Google Drive sharing methods. At this point they can see it but cannot do anything apparently useful with it. This is where I believe your application may differ from the realtime-playground example.
Integration with Chrome Web Store
On the GitHub repository for realtime-playground you'll notice a cws (Chrome Web Store) directory containing the stuff necessary to deploy the realtime-playground as Google Drive application in the Chrome Store including screenshots to be used. If you look at the manifest.json file you will see another reference to the client id:
"api_console_project_id" : "840867953062"
So if I share a realtime-playground file with somebody who doesn't have it installed, then clicking on the file in Google Drive will result in a "Connect app" popup which will try to locate the corresponding Chrome Web Store Drive app (using the common id as the key) and this will show something similar to what you might see if you found this application directly in the Chrome Web Store.
The manifest.json also contains:
"app" : { "launch" : {
"web_url" : "https://realtimeplayground.appspot.com/" } }
which tells Google Drive what to do when the installed app is called.
So my guess is that your application doesn't work like this as you don't yet have public visibility of your app in the Chrome Web Store.
See also: Create a Chrome Web Store Listing
I hope this helps.
That is fine. If you open your eyes, you will notice that Playground demo does not provide any preview either
Yet, you see, the associated app is available. You can click it and open-with works normally. Your app-created files operate similarly. They are associated with your app by default. You can open them by open with rather than by preview. Can you? No, you cannot. But that is another question.
Otherwise, I see no cleverness in associating your file with chrome extension rather than with your app.
How do I get it to prompt the person to authorize my app?
I recently had a similar question. Instead of linking your files with extension in chrome, pass the direct link, like http://your-app#fileId=..., as playground demonstrates to your shared fellow if open-with fails.
The preview seems to be another story.
Wait, Do you mean that I need to create a new fresh account to test how your file is unassociated with your app? How do you preview the files in your primary account? If you know how to preview you may answer my question, at least partially. But why do you associate authorization with preview?
As a developer ,I want my apps hide the Use by default checkbox , just like what HelloFax do.
where can I set this?
We try to empty the MIME and extension setting,but we got
Does that means I can not remove the Use by default checkbox if my app does not support creating new documents?
You list MIME types and extensions that the app can open by default in the Drive SDK section of the APIs Console: https://code.google.com/apis/console/
Leave both "Default MIME Types" and "Default File Extensions" empty to hide the checkbox.
EDIT: If your app has no primary type, you need to specify at least one type (or extension) as secondary or allow it to create new files.
This is because of the new security model which only grant access to files that a user has created with a given Drive app or files that a user opens with a given Drive app:
https://developers.google.com/drive/apps_overview#granting_file-level_access