LoginLogin

What program should I make that would make using SmileBASIC easier?

Root / Talk About Programs / [.]

HTV04Created:
Title.

A program editor that autocompletes with your own variable/constants/functions names. (More specific syntax-highlighting would be a bonus). Or, a “visual” SPDEF generator. At least I’d like one, the ones I’ve tried seems unnecessarily difficult to use.

SB4 port

SB4 port
Sounds great I’ll have it done by tomorrow Kidding, I was thinking the reverse (SB3 interpreter) might actually be possible though. Maybe I could try that someday. after SB4 releases in the US smh

SB4 port
Sounds great I’ll have it done by tomorrow Kidding, I was thinking the reverse might actually be possible though. Maybe I could try that someday. after SB4 releases in the US smh
Porting a SB4 game may be easier said than done, instead of just sending the code over, it's probably better to optimise some things & code some of your own stuff, you should also consider using the bottom screen as the 3DS has a much smaller screen.

I'm gonna try to port a few features from SB4 to SB3.

Want a hard one? You can say no to it, no worries. I thought 12me21 might like this idea since he seems interested in compilers. Anyway what I want is basically WebPack for SmileBasic. https://webpack.js.org/. The idea is you could break your SmileBasic code up into smaller modules, then this would glue them all together in a big blob of code to actually run. Sounds simple but you can't just glue them together. You need some namespacing so variable x in one file doesn't get stomped on by variable x in another. You would need some sort of way to mark methods as visible outside the module so it doesn't get namespace mangled (maybe reuse COMMON DEF) so it can be called from a different file. Then you would need to edit the code to use the namespace mangled names. I also wanted some sort of Python-esque if __main__ command so you can have code that is only included if it is the project entry point. All of this would have some sort of config file to say what is in the project and which file is the entry point too. Bonus points if the final output is minified. I might get to it in a few years but no time soon. If you want a crack at it feel free. It would make coding easier if we didn't have monolithic code files, and would make code more reusable too. I was also thinking of a gui library (buttons, labels, images, canvas, lines, and frames, etc.) if you want that one. Bogged down in properties system on my own at the moment since I don't want them hard wired. You start one little form and it balloons into a gui library. I wasn't planning on a gui builder, but maybe a form definition file. Anyway that would help with menus and help viewers and dialogs and such. Let me know if you want an easier idea.

What you do is you make some external hardware that can read minds, sell it on ebay or something, and make a program that programs for you. jkjk