A new project on its way...

edit8X+ will mainly be a text viewer|editor.
The main idea is to be able to read text imported from a computer.
I know that doesn't sound very original, but i really wanted to code my own.
Also, i might use it later for a larger purpose.
A challenge will be to make the code OS-independant (avoiding system routines when possible).

*****

PLANNED FEATURES :

compatibility with as many models as possible
The default large font will be used but the characters order will match :
 ASCII printable characters (full compatibility)
 ISO-8859-1 printable characters (partial compatibility)
 CP-1252 printable characters (partial compatibility)
block selection , cut , copy , paste
undo
compatibility with the tab control character
compatibility with different versions of the enter control character :
 $0A
 $0D
 $0D,$0A
temporary system & extra ram usage during edition
view-only mode for archived files too large to be edited (if unsufficient free ram)
new , save as , save
backspace (maybe)
horizontal scrolling
...

*****

WHAT'S DONE FOR NOW :

The font :

242 printable characters
153 of them are compatible with notepad (instead of 92 in the original system font).
The other 89 are specific to the calculator (I needed them for another project).

11 undefined characters (dedicated sprite)

The 3 remaining slots are used for control chars (tab & enter).

*****

Any suggestions are welcome =]

disp_char routine coded =]

I can provide a backspace routine from cmdOS if you want, it's OS-independant

I can provide a backspace routine from cmdOS if you want, it's OS-independant

I'm far from that part but thanks a lot for the proposition =]
I'll think of it if i encounter difficulties.

You mean like I could do .txt.8xp? or rename a .txt to .8xp?

I'm not totally sure which variable type i'm gonna use but i'll probably go for the 8xv format.
But yeah, the file will have to be converted to that format before sending it to the calc (not just renamed).
A converter should be included.

Unfortunately, files won't be larger than 65535 bytes, due to VAT limitations.
The converter will automatically split the file if necessary.

If you are keeping track of character coordinates, you could try to make 'tab' work by adding, say, 4 to the coordinate, then use AND %11111100 to mask out the lower bits. Or, for 8 or 16 (like if you are doing it by pixel), you could add 8 or 16 and mask with AND %11111000 or AND %11110000 respectively. That will make sure that it aligns properly

I'm actually designing the view mode algorithm.
Is it true that an archived file cannot cross a sector or is it just rumors ?
If yes, that would compromise the handling of large files...

Hmm...
I assume the reason for that is the way how swapping is performed by the OS or something.
Or maybe ti coders were too lazy to handle the sector status byte.

I'm still curious to see what happens when sending a 65535 long variable.
I'll check that out.

That definitely sucks =[
I guess the only way to support very large files would be to handle them as applications.
Unfortunately, that implies some space wasting.

Anyway, if i decide to do so, i have an idea :
Defining a special header that automatically calls edit8x+ when the app is executed.
What you think ?