0 Members and 2 Guests are viewing this topic.
It would actually still be fast since this is how Repeat loops are typically handled anyways. I am doing it this way because it will help to prevent stack overflow issues. Math might change, too, by the way. I am still working out how I want to efficiently handle math. I will probably attempt Order of Operations so you can do something like 3+6*(a+b4) like you would in BASIC.
I was thinking about this and I at first thought I might be able to make one app for the editor, and one app to run the program. However, I was going to add a lot more commands to Grammer 3, so the parser would still need 2-pages Then you would have a 2-page app for running Grammer programs and a 1-page app for editing them. Instead, I will try to make it just 1 app that is 2-pages.
If the sprite is too big, I will have it display maybe a 16x16 portion and if the user wants to use edit it, a special editor will open.
That is a good idea. I will probably still stick menu options on the bottom row, though For example, 5 options for F1~F5:
I hope I actually finish it! I have been planning for over two years now, so hopefully you will get a chance to finally use it!
Cool ! Will the app support variables' declaration with the type ? And what about local variables ? Will we be able to do recursive functions ?
Why not put the most needed functions in the 1-page app parser, and then put other functions into several appvars which would be used like the DLL ? Programs needing such a appvar would require it, and even though the user would use all the functions, the final size woudn't be 16 kilo bytes. Of course, updating would be more difficult...
Finally, a 2-page app isn't so big when be think about Omnicalc and so. And the containing of an editor could appeal users of programs and give them curiosity to try to do something. Will you introduce hooks like the OS to customize the editor, like adding tutorials as you did ?
It's not really a good idea to my mind, because we couldn't see the difference between pictures which don't have any pixel on on the board up left.
Will you add the support of tilemaps and an editor of tilemaps ? Will you add a basic pictures compression ? What about gray-scale sprites ?
Please don't, it is usefull the first 5 minutes, but then we know the keys and don't need their action's description to be shown anymore, and a line of code is removed.
Yes, and I've been waiting for those two years ! And hope you'll finally do it !
NB : know that you're doing a 2-pages app, will you be able to add a command to parse pieces of code as someone proposed it ? But after having finally done this version 3 for sure.
Hmm, maybe I should display the whole thing, then? Either way, you would still be able to select it to open up a larger view.
Quote from: mdr1 on May 16, 2013, 05:09:22 pmNB : know that you're doing a 2-pages app, will you be able to add a command to parse pieces of code as someone proposed it ? But after having finally done this version 3 for sure.I am not sure what you mean, sorry .__.
I am thinking really hard about how to handle math. I can definitely make it handle order of operations, but it would be a little slower.
Quote from: Xeda112358 on May 18, 2013, 07:50:14 amI am thinking really hard about how to handle math. I can definitely make it handle order of operations, but it would be a little slower.A little slower ? Why not when parsing put the operations to the usual order ? Then it would be the same speed.
Author
Topic: Grammer 3-Concepts, ideas, requests (Read 66898 times)
