search

brownplt / code.pyret.org

Website for serving Pyret to folks.
Other
24 stars 45 forks source link

can't "open with Pyret" from shared drive #402

Open thomascastleman opened 3 years ago

thomascastleman commented 3 years ago

Not sure if this is just a limitation of the Google drive API, but I noticed this behavior:

In my own drive, I can preview Pyret files and click "Open with" and then select Pyret to open the file in CPO. See below:

my-gdrive (1)

However, with a .arr file in a shared drive, I get no option to open with Pyret:

shared-gdrive (1)

This is unfortunate because in a situation where many people are working on .arr files in a shared drive, it seems the best solution is to download and re-upload those files each time edits are made. Is there a way around this / way of enabling "Open with Pyret" in a shared drive?

jpolitz commented 3 years ago

This is deliberate — you may want to enable “Full Google Drive Access” in the Pyret/Bonnie menu. This is a use case that was disabled by default for our summer update this year to restrict drive permissions:

https://www.pyret.org/release-notes/summer-2021.html

Let me know if you have that enabled and still see this.

On Thu, Sep 2 2021 at 4:06 PM, Thomas Castleman @.***> wrote:

Not sure if this is just a limitation of the Google drive API, but I noticed this behavior:

In my own drive, I can preview Pyret files and click "Open with" and then select Pyret to open the file in CPO. See below:

[image: my-gdrive (1)] https://user-images.githubusercontent.com/13399527/131926852-3d0875d9-df8e-4a33-b551-28d505bb544e.png

However, with a .arr file in a shared drive, I get no option to open with Pyret:

[image: shared-gdrive (1)] https://user-images.githubusercontent.com/13399527/131926953-d4b299a2-6ab4-4a84-a61c-eb30747847f3.png

This is unfortunate because in a situation where many people are working on .arr files in a shared drive, it seems the best solution is to download and re-upload those files each time edits are made. Is there a way around this / way of enabling "Open with Pyret" in a shared drive?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brownplt/code.pyret.org/issues/402, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA5IUYRTDG7TBC3ONLSNW3T777NTANCNFSM5DKE6CXA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

thomascastleman commented 3 years ago

Thanks, unfortunately I did enable full access from CPO and I still see this discrepancy between the shared drive and files in my own personal drive.

Indeed, it seems my other connected apps disappear as well when accessing the shared drive, so I wonder if this is more a property of what's possible with shared drives. I can't seem to find much online about this however.

jpolitz commented 3 years ago

Mmph, yeah that's likely. I don't know the details. It could be a number of things; for example, it could have to do with institutional settings on what apps are allowed to access the shared drives, it could have to do with what account or org counts as the “owner” of the shared drive, and so on. I don't understand shared drive (rather than shared folder) semantics well, except that they are often frustrating to me because useful, simple things needed to be routed through an org admin.

I'm going to leave this open in case someone comes along with more information.