for reference, where does the file exist? might be worth adding to aplwiki or something (if it's not already there, which i can't check as it's down :|)
Wait, was our trick for when messages are too long?
Here's the function taken from Dyalog/Ride (MIT license) which will parse the color scheme string. [TIO](https://tio.run/##fVVLk@JGDD5nfoXWU7XYwWNshmHBs85WOCS1h70kNSfCobvdfjB@bbtN2Ae/fVZqGyYQErqw1ZL86ZNalrdsx1qh8kbfVXUsX16SrhI6ryuIpfhTlPbegW8wmcA@TGoFcs/KppBgVV0ZJWl4P3tweRom7sp9QqEOvQdotSLT1P0Ioi6jJ@sGhp@oq1aDggghK1bKEPYe3V3Qmey3RoDDI4VUIe5AybYr9AUGQwx777X6SyFb@P4dRiPHa5si1/bkr3Y8cQwAO@O8/h/Slmu90sZNT3xziko4diE15BjYf8Tbe2BeIatUZ7gbj7FKJ2eAPAGbrfPNufZIniMGWQfCo2jU0@WhoYjh/4Pk5gpYimB87W8MQhoaALCpcKmqu8a58ogwjwSn@C7Gv@KW0TnhSah1ukExO/c5VWTbV2SLFRGnimxNRYiSwKT6dDAvSghvK/w/me2VtI7hmx0Ci/X2RDO8pH…
I remembered!
Now markup doesn't work... of course it doesn't. SE chat is such the worst.
The syntax I used for calling is a bit messy, it's:
@Adám I was listening to arraycast where you were talking. You were asking about the futures in J, and how they returned boxed values. Unboxing would be equivalent to an await operation. I don't know J, but I think this would be similar to using ⊂foo to box, and ⊃foo unbox.
The other person said it was needed because you don't know the shape of the result prior to evaluation.
@Adám I'm guessing the issue is, in APL terms, if you were to run something like (?10)⍴1 as a background operation, you don't know the size of the array until the computation is done?
@Adám Right. The reason I was a bit confused about the discussion is that I had a similar issue when I designed the defer operator. In this case I also needed to return an object which has not yet been computer. I simply let the dimensions be undefined until they are needed, at which point the computation is forced.
@EliasMårtenson Again, not a problem if the entire array is unknown. However, usually you'd want to leverage parallel execution for chunks of a large array.
Still that. Kind of a chicken and egg problem. We don't want to commit to the design until people try out the model, and people won't use the feature until we give it a glyph.
@KamilaSzewczyk I just read it through again, and now I wonder if it is really worth having a glyph for creating a new isolate. Wouldn't it make more sense to use ⎕NEW'Isolate' which can then optionally take various settings?
It's still a mess, but please feel free to leave an issue with your own theme and I'll add it in! If you share the encoded bit in prefs.json, that'd be great. Converting that to CSS is almost entirely automated already.
@KamilaSzewczyk Sure, and I like ∥ too, just like we have & for green threads, but creating an isolate (which is a type of object) to be used later seems much like creating any other object. And objects are generally created with ⎕NEW.
One could implement that instead, though I don't think this would be too hard
@Adám Well, exporting/importing themes to RIDE is a pain rn. And people don't necessarily want to import every theme in existence into their ride, just to try them out
@AviFS No, that's NOT what your site is doing. The two things complement each other. Adding a theme to your site should be as easy as clicking [Export] from within RIDE, thus creating a .ridecols file or something, and once someone finds a suitable scheme on your site, they should be able to click download to get a .ridecols file, and then clicking [Import] from within RIDE should be able to load it.
@Adám Yes, it's not a perfect metaphor. But, yeah. The carpets in this weird shop are glued in, and then, after browsing, you go and find it online to buy
Hence, for this system to be both normal, and successful, RIDE needs import/export facilities, and there's a much better chance of getting that if someone else than me asks for it.
At least it'll be documented somewhere, the main pain in the neck for someone reasonably tech-savvy is just figuring out how. This will have instructions on how
@Adám Right! Also, though it doesn't have to be that grand. I'm working on a bunch of little projects. I mainly just thought it'd be cool to easily see and showcase a bunch of themes we've all made as a community
And I thought having a place where themes are showcased would encourage people to make them. Because we have a serious lack of themes in APL!!
@AviFS So what's confusing to me is that you're describing a core content consisting of instructions, while you're showcasing content consisting of a theme renderer/
Importing/exporting is a slightly different issue. It's one I was hoping to make less of a pain in the neck, and it's definitely something I can steer more into if people would like. But it wasn't my main whatever
@Adám Right. It's a theme renderer!
Everything else is to-be-added
I did say it's an APL theme previewer :P
The instructions aren't meant to be the core content, at least not right now. They're the before and after.
