ntech
Junior Member
Posts: 99
|
Post by ntech on May 4, 2020 2:27:51 GMT
Maybe I am losing acquaintence with these things since being away from this stuff for so long, but what does this code editor do? We already have that in JUST BASIC. Do we? Specifically, it offers a dark mode and a semi-transparent window mode with the current editor doesn't. |
|
|
|
Post by Enzo on Jan 12, 2021 20:08:38 GMT
Suggestion for word predictions
Read first (last) two characters typed to determine if variable or string$ or JustBASIC command use an array of the commands (although you might want to add a header at the end with a numerical character, I believe there is an error when using all these words as strings even in an array, have a character length variable and display every keystroke a new loop of the finished predicted word, this way it will change when deleted and different character is put, I've seen a double tap [space bar] to activate predictions on code editors within a timed loop (less than 700ms but more then 350/450ms); this allows for being able to actually still use multiple spaces in your code, or maybe the ALT key, it's very unused in computers and JustBASIC does register this key, without any special character needed.
To spell check you'll need an loop for all the combos of the misspelled command at correct length, this can be generated with JustBASIC and would be sort of a large bit of memory, might need to make it a file with functions (compared to JustBASIC application storage, system RAM) and search various instr$( to that array list without header, at different lengths of character count, parsing same character count commands could be done with first, last; one or two characters to match, considering the user types the first character correctly or were they coding fast and mistyped, basically count a variable of how close the mistype was to the different spellchecks, based on probability pick your value accordingly. A Basic way would be to instead of map out a common keyboard layout to mistypes have the spellcheckstring$ compare in place characters for next left$(spellcheckstrin$,var) var = var + 1 to the array justbasiccommands() and add a value of 1 to a different array counterarray(commandindex) to the count for every match, most likely the highest number after you've looped your parse will be correct.
|
|
|
|
Post by xxgeek on Jan 20, 2021 7:53:34 GMT
Thank you for the dark theme.
Seems to be working ok for editing, and easy on the eyes.
Any updates coming?
|
|
