On that note, this may be useful, it's a 16 color palette designed for versatility, and in my experience does a decent job with dithering across a variety of photos. It desaturates them but often captures most of the frequency detail.
gfodor
6
Posts
1
Topics
A member registered Sep 15, 2023
Recent community posts
Yep, fair enough - I empathize. I linked the spec later in the thread so you can keep an eye on it if it does actually get adopted by the other browsers.
Edit: also, to be clear, the 'push to origin' add-on I'm asking about in this thread for git etc is unrelated to this in terms of implementation, but I thought I'd mention it in case you weren't aware of it
Here's where the spec for that API is: https://github.com/WICG/file-system-access
also maybe worth checking out with Webspaces is my use of the (non-standard) file system access API in Chrome which allows for a more traditional "File -> Save" workflow when working with a local saved file. I believe this same method would work for Decker if the API is available in the current browser context.
Ah thank you. I was actually planning on doing this for the web version however. I am looking to extend Decker to allow "origin writeback", which would allow a user to edit the Deck "in-place" on their web host, and have the changes automatically sync back to origin via git. (I implemented this for a project called Webspaces, see https://webspaces.space or the writeup here https://gfodor.medium.com/rebooting-the-web-in-3d-with-webspaces-9e58847e042c, decker has similar design goals of long term durability and coherent artifacts, but my project is about 3d multimedia environments not 2d)
Hello, I am interested in prototyping something with Decker and it requires extending some of the core functionality - specifically a way to directly build and deploy the current deck into a GitHub repo via something like a "Deploy..." menu item. I was looking for ways I could do this that would be the most "master branch friendly", to maximize the utility of anything I put together (even if it's just from a exploration standpoint.) I'm imaginging something like a way to add menu elements in a plugin-style approach, where the menu item can kick off a contraption (in this case, a dialog and so on that lets you enter github credentials) and so on that would continue to have access to the 'source deck' that was active prior to the menu item being activated. Thanks for any insight!