A long time ago I made a small font program editor. At @Xeda112358's request I recently revived it and am working on beating it into a working shape. Im posting it here so I don't have to constantly upload to a 3rd party site every time I update it and on the off chance someone else might want to use it.

I want to be a part of this and help wherever I can. Whether it's testing for or giving ideas.

So at the moment I'm just getting comfortable with Xeda Elenara's Grammer 2. I have a friend who is teaching me the absolute basics of Axe and I'm learning it on my own through comprehensive tutorials that I found and printed. I'm slowly learning assembly using the Learn Assembly in 28 Days tutorials. I printed the entire thing out, hole punched it, inserted it in a binder, and started reading. So as of now I'm able to understand a little assembly. Xeda's asm hex tutorials helped me with learning how the structure works.

As for edit buffer, I would assume that it is a temporary location for the data in programs, above the ram(as not to erase any user ram) that is used to edit the data. I might be wrong though.

Ideas are another thing. I just have a large imaginative range and I can help with UI. My current process is to make a BASIC version of my idea then port it to Grammer, as it is more optimized. Then after I've learned enough with Axe, I will port the Grammer Port to Axe because Axe is super fast. I can help with bug reporting to. I've done so a lot with Grammer.

I can easily download an emulator. Like most calculator lovers, they probably have a lot of background knowledge of some type of OS. I use Windows 10 and will probably download and install the most popular Wabbitemu.

I will try to get as much feedback on the program as I can muster. (I'm glad I'm not the only one who has muscle memory already  )

As for Tokens... It's kind of hard not to know what they are. I think the whole idea that everyone is sharing is adding customs tokens for custom editors so that no one has to use the BASIC Tokens and create hooks that disguise them so they are more readable and understandable.

Also, I'll probably figure it out but..., witch source do I compile first?

Woah. The editor is super buggy. (I didn't expect that  )

When you put it on your calculator, open Axe and compile prgmEDITORSC (it takes a little bit; it's a lot of code!)

A little bit? You should see my 'main' project. The executable is over 100k and takes almost a half hour to do a full recompile.

So are you building it first before you optimize it?

A lot of the issues are with the menus I think. Every time I open a menu(except for the prgm menu) it freezes, opens the menu, then refreezes with random letters but not random numbers, then I have to pull the batteries.

Oh, yea. I forgot about that. I messed something up with the loop that selects the tokens. It doesn't *actually* freeze, just displays so many tokens on the screen at once that it is like 5 secs between frames.

As for optimizing it, the core of it is as optimized as it is going to get. The cursor movement and scrolling was a huge pain to get right and I'm not spending 10 hours optimizing it and fixing all the bugs I made for a boost in speed which won't matter once I limit the framerate. Not that it is terribly inefficient or anything though. Almost all the cpu's time is spent on text and displaying the screen. Im using a custom text routine that I made that is 2x faster than the OS's and Ill eventually make a custom lcd update that is 6+ times faster than the default one Axe is using. (partial update instead of the whole screen) Speed isn't an issue. And since the finished editor will be an app anyway space doesn't really matter. I think that pressing 2nd + right to scroll to the end of a really, really long line of code takes a long time but Ill deal with it later. Trying to scroll past the bottom line might be an issue.

Ill work intermittently on this as I find time / motivation. Don't expect speedy updates though. The whole reason I put this up was to help Zeda since she? is making one for Grammer 3. From what I have heard of what is done though, I don't know why mine is needed. That might get more constant updates but I really don't know.