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.
@baulers ctrl-b to comment selected & shift-enter are actually in for 0.1.0h! (they were missing from the changelog). Multi line edit I don't have any plans for though [yet]
@waporwave yep, 0 means a retrigger only on the first tick of that row. Alternatively, the instrument can have a flag set (also in 0.1.0h) that causes it to retrigger whenever its index is set in the instrument channel, which is a bit more flexible as it leaves the FX channel free for other things.
@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.
@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.
@zep what is the planned memory envelope for a #picotron app?
the doc mentions ‘16mb’ but unclear if that’s mappable memory and/or lua memory space.
(asking cause alpha is not enforcing any limit
afaik)
@fsouchu I'm aiming for 16mb total (includes Lua and ram), so you can never quite map all of 16MB of address space. It will become enforced in 0.1.1 ~ hopefully before anyone makes anything that large!
@fsouchu I see ^ _ ^;
It is very unlikely that fetch will support partial reads in the future -- I view the files themselves as the atomic chunks that are part of a larger thing (cartridge). Would it be hard to break that data up into pieces? I'm planning on enforcing RAM limits for 0.1.1 but will add a way to measure it before then.
It might also turn out there is a way to abuse /ram, but that also needs to have some kind of limit..
Hey Mastodon, I’m new here PICOPHONE 0.2.2 is out now on the BBS! Midi converter, Calculator, Color ID checker & Special Char checker - all in one tool.
Promise: by the time version 1.0.0 comes out you won’t touch your phone to search for stuff anymore, you’ll have the focus you meed to complete your #picotron gems. Thankyou @zep for making yet another crazy software.
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.
Got a small idea and wrote code for GUI: vertical and horizontal splitters.
Hey @zep, do you have any guidelines for GUI code? Right now those are piggy-backing the GUI lib's ability of regenerating a widget's dimensions with width_rel and height_rel. Do you have anything in mind regarding their usage? Do you think I should I offer an explicit way for the inner children to override the dimension assignment?
@Ronflaix I haven't tried to formulate any guidelines yet, but I think the built-in gui library will remain extremely minimal and won't change much: so if it works, it works. No problem for children to overwrite their relatives' data etc. -- that's what I would do for splitters I think. I won't try to introduce enforced information hiding or anything like that :)