This topic contains 3 replies, has 3 voices, and was last updated by 
AdamStrange
2 years, 8 months ago.
-
Posts
-
I’m now using Ted21 as my main mx2 editor and thought a good time to share some thoughts on how it’s all progressing:
First off it’s starting to work so it can almost be used.
I have 1 base debug version running, this is running a second debug version which I use for coding. The second runs a third which is the test version.
Why all these versions?
Well… to catch bugs of course.
I’m currently working on the help system and it’s nearly ready to be put on git.
Finally the mojox gui is making sense so I can start to go back and change the code. but I know that Mark has already made significant changes – I’ll have to wait there then.
In use it feels very nice to use and I am happy with the results
I’m starting to catch all sorts of little things and these are all being fixed as they are found or pointed out
I would love to try ted21 for mx2 coding but could not change the font size (too small for me, have to change screen resolution…). It would be great if we could chose some fonts and their sizes, would it be a big work to have that? It’s kind of mandatory for a serious editor. (Or I missed something!?)
Looks like you have done some great work so far! and it will be great if you merge you additions with Marks mojox update.
I think adding a config.json file for controlling some of the settings (font/size, colours, etc…) would be good, like Visual Studio Code does.
currently there is no res panel, although it is coming. The text in the new Ted21 is larger than the previous + the code text is now correctly monospaced
Mark has said that he would not be merging these mojox components into the final mojox as there are some hard coded stuff going on in mine. He is also not finalised on what mojox will be like as a module, so there are bound to be changes to the internals. but not to worry about these.
You must be logged in to reply to this topic.