Is it possible to program "Share with others" in Google docs through some API/interface etc., Essentially I want to reach out "Email Spreadsheet" or Docs page and utilize its services
Yes, this is possible through access control list feeds (ACL).
You can retrieve an ACL feed for any given folder/document/spreadsheet etc, modify it and POST/PUT it back. More info here.
There are also libraries for Java and .NET that make it easier. Documentation for Document List API v3.0 isn't up to date for .NET yet though (although the v3.0 code is available in trunk), but for Java there is more info available.
Related
I am trying to integrate Acumatica with an interfacing system and I need to be able to send and receive data in xml format, say for example one is Customer info, that should be sent to the interfacing system.
For some reasons, we ruled out the Import/ Export scenarios and we need to achieve the interface using FTP.
I'm unable to find much info online on how to FTP data in and out of Acumatica. So if anyone can share links to some documentation, it will be very helpful. Thanks.
Seeing as you want to be able to send and receive data in an XML format, you might want to check the Web Service options.
There are two possibilities, the Contract Based SOAP API and the Screen Based SOAP API. Both of these are sending SOAP request in XML format.
If you are starting a new project, Acumatica is suggesting you use either version of the Contract Based API (SOAP or REST). So your best bet is probably in looking at Contract Based SOAP API.
As there is not much information on the structure behind what is being sent you will probably have to create yourself project in c# first and inspect the structure of the package being sent to the server hosting the Acumatica instance so that you can reproduce it using your own FTP Interface.
You need to work with .Net native FtpWebRequest class. You can find more information at MSDN FtpWebRequest.
I am trying to develop a contextual gadget, but not getting any documentation for it. Google provides a document which is very old and not updated from long time. Process explained in that documentation to develop a gadget is deprecated.
Please if anyone have solution, help me.
You may want to check full documentation in Gmail Contextual Gadgets which was last updated June 29, 2016.
To develop a Gmail Contextual Gadgets, you may want to first check the given implementation parts also discussed in the documentation. Then, you may go through these summary of steps:
Use JQuery, or write JavaScript that conforms to ECMAScript 5 Strict Mode.
Note: You need to be using the correct development frameworks to provide an extra layer of protection between your gadget's potential vulnerabilities and your end users. To find out why, see Using the right frameworks for security.
Choose one or more pre-canned extractors. This determines which type of content will trigger your gadget.
Write a manifest for the gadget.
Write the gadget spec. This determines what the gadget will do when it is triggered.
Publish the gadget spec to a location which is accessible on the public Internet. An intranet will not work. Your hard drive will not work. (Why? Google's servers need to download the gadget. If they can't reach it, then Gmail can't display it.)
Install the gadget.
Test the gadget by sending yourself some email. The gadget should appear in Gmail whenever you read an email that contains the right sort of content. For more tips on testing gadgets, see Publishing Your Gadget in the gadgets API site.
It will really help if you go through the documentation as there are best practices, limitations and important details that you should note.
This related SO post might also help.
What is the main reason that we go for Rest Api in SharePoint 2013. Already we have Client Object Model for implementing application. Anybody can please guide me.
The Client Side Object Model is built upon the REST API so that is one reason for it to exist. For good JavaScript developers they may like the simplicity of the REST API. For people trying to keep their page size to a minimum, they may appreciate forgoing the size of the CSOM and its dependencies. Lastly, in mash up scenarios with other tools, having an easy way to address content via REST urls makes for better interoperability with other tools instead of relying on a product specific API (i.e. the CSOM).
I know it's deprecated and all (or I think it is), but I just want to do some tinkering, and the source code I have requires this library. According to the project's GitHub website (https://github.com/Equalify/Miniplayer), you have to ask for this library.
I'm a Premium Spotify user.
How can I get this library?
Thanks.
You should already have received the library via mail.
When i githubbed the miniplayer project the library was still very much work in progress - and it still is - which is why i did not want to include it.
It would not be good for me to provide the public with a possibly buggy/crashing library, so i opted for the "contact me to get it" approach where there will be a direct line of communication between me and the people that has the library.
For anyone else, the contact info is on the github page and in the library header file.
or, Can i create/modify google docs by 3rd application?
Google does not share info on their native, proprietary format--possibly called "kix" according to this StackExchange answer.
You CAN programmatically create, modify and destroy Google Drive document files in 3rd party apps (or build your own) by manipulating representations of those files exposed by various Google APIs and scripting services. It took a bit of truffle-hunting through the online documentation, but I did find a description of the structure of a Google Doc here: Extending Google Docs.
Again, this is a description of a representation of the file, not the file itself.