Some onboarding issues

[nightblade9]

Hey, just picked up MonoGo. Looks like it's just what I needed, so thanks for building that.

I ran into a few issues while "onboarding" - trying to get started. Namely:

• Doesn't seem to be any written, step-by-step tutorials. I ended up going through the samples code, which kinda works, but is not ideal ... (I came back to MG from Godot, which has very extensive docs, and tutorials.)
• Panels, by default, use an empty stylesheet, which makes them invisible. I spent a couple of hours fudging about (one panel? Multiple panels?) until I realized this. I think a more sensible default would be to make them visible.
• For some reason, the text value on a TextInput control is called Value instead of Text. That's weird, considering that Paragraph uses Text.

Last and most importantly: if I do anything that takes significant time (like, say, compiling code) inside Update, it pretty much freezes the entire UI until it's done. Threading, and calling thread.Join(), also freezes the UI. (Letting the thread run, which is a bad idea, resolves this). Am I doing something wrong, or is there a better way to get this to work?

[BlizzCrafter]

Hey @nightblade9 !

[...] step-by-step tutorials [...]

Yeah, this is currently lacking here. I'm working on something regarding this, but I can't tell when it's done.

Panels, by default, use an empty stylesheet, which makes them invisible [..]

I agree, the usage is a bit unclear. Here is a sample image which should make the usage of panels more obvious:

Basically you need to do nothing specific when creating a panel. Just call new Panel().
If you want the panel to become invisible, then just create a new panel like this: new Panel(null!). This sets the "StyleSheet" parameter to null, which makes the panel invisible.

Last and most importantly: if I do anything that takes significant time [...]

I don't know what you are trying to achieve, but there is a Job / Coroutine system built into the engine. Check it out:
https://github.com/MonoGo-Engine/MonoGo/blob/master/MonoGo.Engine/Utils/Coroutines/Job.cs#L5-L13

I hope this clears things up a bit.