[suggestion] throw display support (or other methods)

[Maxi2022gt]

it would be nice to have like some toggleable error display, because some bytebeats use it (for example, my Dheven, which I had to port to not have errors in order to post it to this platform).
people are already wanting it, since this platform is also becoming a "curated dollchan library" too or something

[pckerneis]

I love when creators use the error display for creative purpose. However, I don't know how to integrate this cleanly into BytebeatCloud: how large should it be? Should it be displayed only on post detail page or also in feeds? Should it be a unique toggeable panel or should it be displayed next to the post item?

I'll think about this. But I'd appreciate design ideas for both desktop and mobile layouts.

[Two2Fall]

Hello again, I recently found out a really good way to do this in this platform. Basically you can create something like an API or something like that using JS that contains a screen, basically a terminal, where you can print text or erase it. Just that, instead of using throw. This might open the bytebeat community adding demoscene stuff on it.

Here is an example that how it could be the API (it doesn't need to be complicated or hard, just that it works):

// basically the code 
c = t * (42 & t >> 10),

 // this syncs the code with the console, so they can run at the same time 
Console.sync(c),

 // this prints a text
Console.printLine("text"),

// this clears the console
Console.clear(), 

Talking about the console dimentions, it would variate from devices, but I can expect something like 96 x 64 characters (2:3 aspect radio). The good thing of all of this is that this prevents from using throw, and so the bytebeat can run easily. And about the tick length of the console, it would be just the sample rate seconds. Or maybe the tick is implemented by the users. You will see that.

[Maxi2022gt]

how would Console.sync work tho?

[Two2Fall]

If you see well, the console and the code cannot run at the same time, because I don't think someone of you are using threads on JS for this. So doing this makes the BytebeatCloud player sync the code, and that's good, it prevents of using NaN or multiplex.

[pckerneis]

@Two2Fall the problem is that adding a dedicated API would break compatibility with other bytebeat players like Dollchan's. And I don't understand why we would need Console.sync.

I think staying with "throw" is a good way to stay minimalistic and consistent with what people are already doing on other platforms. It can be used both for debugging and graphics. And it's already quite intuitive to use.

[Two2Fall]

But Javascript stops the program at that point if I remember well! I mean it would be kind of strange to use throw to print text, so there are two options: Make throw have another behavior, or make it just for compatibility stuff and implement the Console object.

[Maxi2022gt]

i think it would be good to stay with throw

[Two2Fall]

When are we gonna end this issue😭😭

[pckerneis]

I've been thinking about this but for now I came up with a separate project: textmode.cloud (repository).

It's only an editor and a player for now. In the long run, I'd like to have some kind of connection between BytebeatCloud and this new project. Maybe being able to display TextMode programs inside BytebeatCloud posts.

[Two2Fall]

Hey this is kind of cool!
I made some stuff with it

[Maxi2022gt]

if it's a .cloud TLD, you might as well implement an online sharing thing /j

...okay but seriously I haven't tried it out yet, but as far as I have seen it's really cool! wonder how long it would take for someone to do Bad Apple in it