Editor for FX
Started by
huhn_m
, Feb 19 2004 08:49 AM
6 replies to this topic
#1
Posted 19 February 2004 - 08:49 AM
The first alpha is out there
See the bugs list for known bugs.
Tell me about other bugs you noticed.
For features see the infos in the rar file.
Main feature: Save to flash.
Well, see yourself. it works quite well. Here is the file
The sources are included but not very well commented and not optimized.
Current filesite is 3301 bytes (Compressed)
See the bugs list for known bugs.
Tell me about other bugs you noticed.
For features see the infos in the rar file.
Main feature: Save to flash.
Well, see yourself. it works quite well. Here is the file
The sources are included but not very well commented and not optimized.
Current filesite is 3301 bytes (Compressed)
#2
Posted 19 February 2004 - 09:22 AM
cool, i am abouut to download it now should be very useful
#3
Posted 19 February 2004 - 05:05 PM
Well it behaves totally diferent than for example edit from dos/win98.
Cursor isn't visible so it is hard to navigate.
when deleting all text typed previously something strange happens - I cannot write anymore.
right arrow does some strange deletion.
I think that most people are used to the editing working like in edit or borland's editors.
Well it needs more work to be user friendly .
I don't know if it possible to make a bug free editor in asm (you can edit text in basic program not in low memory so memory is not a problem). Smaller fonts would be good too.
I would divide the editing part of code from presentation - i'd make some fuctions for editing like those:
- insert_letter_at_pos(offset,letter)
- do_backspace(offset)
- delete_after(offset)
(and so on)
those functions would modify cursor position too.
The presentation function would take file offset of the letter in the upper left corrner of screen and cursor offset
This are just my impressions, if you have your vision of the editor then you can ignore what i've said here.
Roeoender.
Cursor isn't visible so it is hard to navigate.
when deleting all text typed previously something strange happens - I cannot write anymore.
right arrow does some strange deletion.
I think that most people are used to the editing working like in edit or borland's editors.
Well it needs more work to be user friendly .
I don't know if it possible to make a bug free editor in asm (you can edit text in basic program not in low memory so memory is not a problem). Smaller fonts would be good too.
I would divide the editing part of code from presentation - i'd make some fuctions for editing like those:
- insert_letter_at_pos(offset,letter)
- do_backspace(offset)
- delete_after(offset)
(and so on)
those functions would modify cursor position too.
The presentation function would take file offset of the letter in the upper left corrner of screen and cursor offset
This are just my impressions, if you have your vision of the editor then you can ignore what i've said here.
Roeoender.
#4
Posted 20 February 2004 - 02:42 PM
i did something like this.
The position is defined by a pointer at insert char
you have a refresh screen routine.
In fact i forgot the delete button Sorry about that.
You can only move right until you reach the end of the typed text (at least it is supposed to be this way and then the
cursor vanishes. Else the letter highlighted is the cursors position.
It works nearly this way. It uses the current line and calculates the front most char by the current cursor position.
In fact it should work like edit in dos. Sorry if it doesn't.
I won't do my own fonts since this makes the thing much more complexer and, in my opinion too complex
for an editor. I'd also have to redo the casio font and some chars need a width of 5 and height of 6
So you'd only get 1 more line and I think this doesn't justify the imense work you need for this.
The delete functions will be the next thing i do.
I won't do copy & paste since this is way to complicated for such a prog and, in my opinion not worth the work.
About the right cursor. Tell me how I can reproduce this since it works for me. Maybe I already fixed this but
I've no problems. If I'm at the end of a document it simply doesn't move any further and the new chars are appended.
I've a question about your roe disk. Where in RAM does it start
and has it the same format as romdisk?
If you have any more suggestions please tell me.
The position is defined by a pointer at insert char
you have a refresh screen routine.
In fact i forgot the delete button Sorry about that.
You can only move right until you reach the end of the typed text (at least it is supposed to be this way and then the
cursor vanishes. Else the letter highlighted is the cursors position.
The presentation function would take file offset of the letter in the upper left corrner of screen and cursor offset
It works nearly this way. It uses the current line and calculates the front most char by the current cursor position.
In fact it should work like edit in dos. Sorry if it doesn't.
I won't do my own fonts since this makes the thing much more complexer and, in my opinion too complex
for an editor. I'd also have to redo the casio font and some chars need a width of 5 and height of 6
So you'd only get 1 more line and I think this doesn't justify the imense work you need for this.
The delete functions will be the next thing i do.
I won't do copy & paste since this is way to complicated for such a prog and, in my opinion not worth the work.
About the right cursor. Tell me how I can reproduce this since it works for me. Maybe I already fixed this but
I've no problems. If I'm at the end of a document it simply doesn't move any further and the new chars are appended.
I've a question about your roe disk. Where in RAM does it start
and has it the same format as romdisk?
If you have any more suggestions please tell me.
#5
Posted 20 February 2004 - 06:26 PM
about the bug: just write something and then try to delete everything
problem: if your editor won't be much better than the build-in one then a simple conversion of a basic file to flash file would be enough (some expanded enter.com would allow typing any characters). Well I was thinking about an editor with slammer fonst. I can provide you with .c files of the fonts I use.
roedisk:
1. as written in readme.txt andrd.asm: start is at 2000:0 (and i think both start there enen though the smaller one could be placed at 3000:0)
2. no it is just as every ram disk (block device) it writes what and where dos orders it.
BTW I gained some 24/7 acces to the net this is why everything of my casio work has been suspended ;-)
Roeoender.
problem: if your editor won't be much better than the build-in one then a simple conversion of a basic file to flash file would be enough (some expanded enter.com would allow typing any characters). Well I was thinking about an editor with slammer fonst. I can provide you with .c files of the fonts I use.
roedisk:
1. as written in readme.txt andrd.asm: start is at 2000:0 (and i think both start there enen though the smaller one could be placed at 3000:0)
2. no it is just as every ram disk (block device) it writes what and where dos orders it.
BTW I gained some 24/7 acces to the net this is why everything of my casio work has been suspended ;-)
Roeoender.
#6
Posted 21 February 2004 - 07:29 PM
Thanks for the infos on roesdisk but do your fonts containWell I was thinking about an editor with slammer fonst. I can provide you with .c files of the fonts I use.
all 256 Chars of the Casio Charset? And if yes how big are they (width / height).
if you would really gain an advantage AND the visibility of the chars remains I could
try it with this progs. The advantages of my editor to basic edit?
Well you can write in lines of 255 Chars (more clearly arranged code)
have access to all chars while writing the program and can see things like
current cursor position .
The problem with an Flash->BASIC & vice versa only converter is that you won't be able to enter some
necessary chars you need for programming in the BASIC editor and therefore can't really use
the results. Also the Linebreaks differ and may cause some compilers to be screwed up.
So I can access you RD with the DOS functions on int 21h? That would be great!
#7
Posted 21 February 2004 - 09:16 PM
my fonst use only visible chars of standard ASCII that is exactly from 32(space) to 126(~) (as 127 is some control char - you can test it by holding ALT and typing 127 at command.com (PC)) codes>=128 weren't defined in the ascii standard and this Most Significant bit was used for partity control.
I hope that you check if the opened file hasnt any lines longer than those 255:)
Well I don't need writing into flash as I can do it by using backup facility of the calc. Rather using BASIC files and ram disk would be enough.
Yes, ofcourse you should be able to use dos int's (and maybe Bios'es 13h, didn't test that) to access roedisk.
Roeoender.
I hope that you check if the opened file hasnt any lines longer than those 255:)
Well I don't need writing into flash as I can do it by using backup facility of the calc. Rather using BASIC files and ram disk would be enough.
Yes, ofcourse you should be able to use dos int's (and maybe Bios'es 13h, didn't test that) to access roedisk.
Roeoender.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users