Hi Daniel, The team follows the public issue tracker on a regular basis and prioritizes future additions to the API based on developer requests. Features are chosen that affect the greatest number of users/ developers.
The one thing to keep in mind is that there's been a few larger issues/ features in the queue for some time (close to a year) like viewing doc contents, export functionality, pdf upload, arbitrary file upload, etc. http://code.google.com/p/gdata-issues/issues/list?q=label:API-DocumentsList Eric On Jan 19, 11:15 pm, Daniel Marashlian <[email protected]> wrote: > Eric, > > It seems that the word got out on our hold up for doing the google > docs integration, and a lot of our users have been commenting on the > public issue. > > I had 2 questions: > > 1. How do we establish a priority on this issue? > 2. What is the expected lead time for getting this done and deployed? > > thanks in advance, > Daniel > > On Jan 15, 12:07 pm, "Eric (Google)" <[email protected]> wrote: > > > Hi Daniel, > > > Sorry, I was completely on a different page :\ > > > I'll filled a public > > issue:http://code.google.com/p/gdata-issues/issues/detail?id=984 > > > Please star it so it gains traction. > > > Eric > > > On Jan 15, 10:23 am, Daniel Marashlian <[email protected]> wrote: > > > > Thanks for the reply Eric, > > > > I 100% understand that the writer role is a collaborator. I'm not > > > asking for any change to the way docs.google.com works, I'm asking > > > that the API would allow a developer to do the same thing that a user > > > from the front end can do. > > > > here is the scenario for how I HAVE the API working with our code: > > > > 1. owner (API) creates a document > > > 2. owner (API) adds a collaborator as a writer > > > 3. collaborator can log in to their DOCS account and edit. Though if > > > they go to the share page, they can invite others to collaborate on > > > the project (which I cannot have happen). > > > > here is the scenario for how I NEED the API to work with our code: > > > > 1. owner (API) creates a document > > > 2. owner (API) un-checks the collaborators can invite others checkbox > > > on the share page. > > > 2. owner (API) adds a collaborator as a writer > > > 3. collaborator can log in to their DOCS account and edit. But they > > > CANNOT invite new collaborators or delete other collaborators. > > > > This functionality is available from the frontend, all the owner needs > > > to do is un-check the "Collaborators may invite others" checkbox. But > > > this is currently not possible through the API. So what we need done > > > is 1 of 2 things: > > > > 1. give an option while creating the DOC to uncheck that option. > > > 2. after the doc is uploaded give an API function that can modify > > > those options. > > > > Thank you for all your help with this. > > > Daniel > > > > On Jan 15, 8:16 am, "Eric (Google)" <[email protected]> wrote: > > > > > Well, the 'writer' role is actually a collaborator. Since this > > > > is the behavior of docs.google.com (frontend), I would suspect > > > > implementing this differently in the API is nontrivial. > > > > > That being said, features are driven by our developers' requests. > > > > Please file a feature > > > > request:http://code.google.com/p/gdata-issues/issues/entry > > > > > Eric > > > > > On Jan 15, 12:48 am, Daniel Marashlian <[email protected]> wrote: > > > > > > is there a way to have your team make that possible through the API? > > > > > this is a CRITICAL issue for us while doing the google docs > > > > > integration. because the permissions will be managed by our app, not > > > > > the user. > > > > > > please let me know, > > > > > thanks for the help Eric, > > > > > Daniel > > > > > > On Jan 14, 3:56 pm, "Eric (Google)" <[email protected]> wrote: > > > > > > > There's no way to turn that off using the API, especially since > > > > > > that's the behavior in docs.google.com. > > > > > > > Eric > > > > > > > On Jan 14, 12:43 am, Daniel Marashlian <[email protected]> wrote: > > > > > > > > Eric, > > > > > > > > This is great an all for restricting the read/write mode to the > > > > > > > collaborators... though if you set a user to writer, they can > > > > > > > still go > > > > > > > into the share page, and invite other users. Is there a way to > > > > > > > turn > > > > > > > this off on the document from the API? > > > > > > > > On Nov 19 2008, 1:15 am, "Eric (Google)" <[email protected]> > > > > > > > wrote: > > > > > > > > > On Nov 17, 10:26 pm, Daniel <[email protected]> wrote: > > > > > > > > > > In Google Docs on a Document, I can go to the Share Page on a > > > > > > > > > Document, and access the Advanced permissions. There are 2 > > > > > > > > > options. > > > > > > > > > > 1. Collaborators may invite others > > > > > > > > > 2. Invitations may be used by anyone > > > > > > > > > > Is there a way to either check or uncheck those from the API? > > > > > > > > > #1 can be done since the ACLs feed can be used to set > > > > > > > > permissions > > > > > > > > for other users. Use <gAcl:role value='writer' /> for > > > > > > > > collaborators:http://code.google.com/apis/documents/developers_guide_protocol.html#... > > > > > > > > > #2 is not something the API supports. > > > > > > > > > Cheers, > > > > > > > > Eric > > > > > > > > > > I use the .NET C# API by the way. > > > > > > > > > > thanks!!! > > > > > > > > > > Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Docs Data APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Docs-Data-APIs?hl=en -~----------~----~----~----~------~----~------~--~---
