Here's an example of file subscriptions: the monospace toggle directly modifies the code editor's config file, and all of the processes subscribed to that file get notified and can update their font.
@ArrowOnionbelly not yet, but I'm aiming for a spec that will eventually be able to handle PICO-8 tunes with an importing tool. It is already possible in theory but really needs features like SFX instruments to be workable in practice.
@zep that makes sense! Of course take your time, I'm not trying to pressure you, we're just all terribly excited. Is there also a plan for PCM sound eventually?
@zep Sorry for the piling mentions but looks like the web player still struggles with Long Line Theory (https://www.lexaloffle.com/bbs/?tid=141818). Have I been too aggressive on the CPU?
@Ronflaix (no problem!) I haven't figured out what's going on there yet, but I think the cart itself should be fine. Even once it is working, there is a theoretical limit to how good audio steaming can be under web though, as for now its all running under the same thread and so easy for the buffer to get starved.
Getting files in and out of #picotron more easily for 0.1.0f: drag & drop directly onto the desktop to copy from host, or automatically mount a folder on the (host) desktop for screenshots and other outgoing files.
(wallpaper: #rude_cat_wallpaper by robthedude)
WIP backups / file versioning for #picotron: all disk writes are (optionally) logged and earlier versions can be fetched by sticking a timestamp on the end:
> cat foo.txt@-30
-- shows foo.txt as it was stored on disk 30 seconds ago
@fsouchu There's no way to filter what is archived (yet), but it can be turned off at least. Also, it doesn't proactively search for changes that were made in external editors.
@zep hey zep! great stream of updates for lovely picotron :)
sorry to bring this up but: we are encouraged to read system code to understand things, we can copy apps and try edits, then we share code snippets and sometimes the edited apps. but what is the license for them? are we allowed to share snippets / diffs / edits?
@merwok hey :)
There is currently no license! I'm fine with sharing snippets diffs & edits, but still working on formalising that. Ideally there would be a single simple license that covers (most of) /system, exports and later the c runtime source. The challenge is to do that in a clear way that allows creating tools/makers etc similar in nature to Picotron, but without functionally duplicating [large parts of] Picotron itself.
I'll do another round of fixes this week, so don't fret if your report hasn't been addressed yet, or if you'd like to contribute to the bug megathread: https://www.lexaloffle.com/bbs/?tid=140647
Appreciate all the hard work you're putting into updates! Maintaining something so complex across a bunch of operating systems and devices is no small feat!
@zep picotron has been really fun, thanks! P.S what way should we be reporting bugs? There's a giant BBS thread, but it gets kind of hard to track them and what has already been submitted. Is there a better way to submit them to you with info or should we just use that?
@zep Qustion does that meant that there is now a key to activate picotron on lexaloffle? If so it's not on my humble account. If not sorry that I asked.