Cross media collaboration #98
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As showcased for #91 (shared progress) the inclusion of drawings by kids bring a very nice touch and showcase agency right away. It makes it instantaneously obvious that kids did contribute.
Could rely on #18
Coherent with #75 and #37
Consequently the process should be radically simplified.
For example take a picture with a photo and share it as an asset to an existing XR room, live. That picture can be the result of a drawing.
Could rely on screenshot backend/frontend code and #68 mechanism.
Convenient way to do this with very little programming would be a WebDAV component with this CopyParty instance configured https://copyparty.benetou.fr and a specific directory https://copyparty.benetou.fr/Prototypes/BiggusGate/CrossMediaCollaboration/
This directory could then have a dedicated
ReadMe.mdfile explaining more what format would work, e.g. just JPEG files with the.jpgextension and ideally below a certain size.It would have to be tested on mobile specifically.
See https://biggu.benetou.fr/games.html?play=bookshelf relying on WebDAV.
If one adds or removes images to https://copyparty.benetou.fr/Prototypes/BibIxellesVirtualLibrary/?notree they'll be added when after refreshing the page in XR.
Updated to check periodically, e.g. every 1min, if there is new content (only ending with
.jp[e]gor.png, if so add it.Could also
Consider also native to CopyParty tricks, e.g https://github.com/9001/copyparty/blob/hovudstraum/README.md#other-tricks
In that URL
?play=bookshelf&componentproperties={%22webdavPath%22:%22/Prototypes/Aza_Zangemann_Vol2_XR/%22}one can change the end, e.g.Aza_Zangemann_Vol2_XRcould become another directory e.g.BibIxellesVirtualLibraryor evenBibIxellesVirtualLibrary/IdeaFromSomeoneElseso no need to change the code itself to exploreCould become 1 directory per workshop or even groups within a workshop session. Participants will nnot mix up their sketches or texts (as photos) together if they don't want to.
Flexibility gives virtual spaces per participant without a hugely complex CMS with users, rights, etc.
Reliance on CopyParty needs work on backbend setup for offline workshops.
Consider https://github.com/villadora/express-http-proxy and updating https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/documentation#setup-for-fully-offline-workshop accordingly.
copyparty-sfx.pyis present on the demo microSD for RaspberryPi Zero and thushttps://192.168.4.1:3923/works (even though on self-signed certificate) butlet client = WebDAV.createClient( 'https://192.168.4.1:3923/' ); client.getDirectoryContents('/');does lead to CORS errors.Use from filters e.g. #16
Could be asymmetric live collaboration paired, e.g. 1 participant in a headset while 1 or more giving them content in the form of 2D photos, sound, etc to compose. Then they alternate. The only agreement in the directory name.