Me waiting for the code editor feature:
it could really elevate flowlab as a platform, so yeah, a code block is really cool, people could really do anything with it!
Yeah, I agree. But I think what they meant by code is a code editor because it says by āAPI blockā So maybe the code is a code editor and not a behavior.
Plus grazer is going to use haxe as a programming language for the code editor feature. It has 14 different programming languages.
an API Block could let you connect with databases, use custom accounts (so for example i make a website called Gamelogin and i can make a ālogin with Gameloginā, use custom databases, make discord games/companions for game progession and so much more!
I Am not sure if this is possible but maybe people could add in-app purcheses with this!
Even if its just an API block, it could do a lot
@LevelGames1, Thanks for the explanation. What I meant is why does an API has a block in the text and not by code so maybe is a code editor?
But I do appreciate the explanation!
Databases and custom accounts would provide huge opportunity for a game Iāve been thinking about.
In conclusion: I want an API block 
@johnpost, APIās are cool. But on the text it says API block but why is the other one not called code block, instead itās just called code. So is it a code editor? Or behavior where you could write code in it.
^I would guess it means a block for code/api. I donāt know how it would be implemented though. You could always ask grazer what his thoughts are for that.
@johnpost, Ye youāre right.
@grazer, Please help I am confused. Is it a code editor or behavior where you write code in it.
Hey @R0CK - that feature card is talking about two different things that would work together:
- A behavior block that would accept Haxe source code. This would be similar to the Expression block but with a large/better text edit area.
- An āAPIā to interact with using code. API stands Application Programming Interface - which basically will be a documented way to interact with the engine using code. For example, you might set the gravity using something like:
Flowlab.world.gravity.y = 50;
There needs to be defined and documented ways to interact with the engine, and they will be tough to change once people start using them, so I need to spend some time nailing them down. Coming up with the API and writing the documentation will probably take more time than actually adding the code block, TBQH.
6 Likes
Iām more exited now that itāll be a way to change the engine settings in a live game.
If we can also control object settings (like friction, bounce, and layer), this will be everything I need.
Really looking forward to it wither way!!
1 Like
@grazer, Ooooh.
But can there be a feature where if you would make a game. A popup would occur where it says "do you want visual code editor or Scripting editor. And if you choose to script you could choose one programming language out of the 14 programming languages.
Just like unity. Where you could switch between a code editor or a visual code editor for example bolt or playmaker = Javascript, Lua, Python, CSS, HTML, C#.
Ok, Sorry.
1 Like
No problem, but just learn from your mistakes
I believe that is what Grazer means, and that would revolutionize flowlab coding!
I canāt wait for this feature, and I hope it is everything we are making it up to be!
@Ramshacklegamestudios, When the code editor is added. I would code the hell out of that code editor. I am not sure if grazer is going to add visual coding scripts like the functions of the behaviorās but in scripts. So you donāt need to drop and drag with your fingers all day long, if I would do that everyday my fingers would decay over time, lol.
lol thatās true
and with this we could do so much more than just simple coding!