1. MEditor 2.0.2 release
- Posted by petelomax at blueyonder.co.uk Nov 13, 2002
- 416 views
{{{ This is pretty much the final version, anything else will likely be just a small bolt-on.
Rob, can you update the archive, I've written a new description for you at the end.
New features 13/11/02: Context sensitive help for win32lib routines and locally defined procedures, functions, and types. Shows parameters, comments, and allows direct jump to the code. You should use the new 'Parse for Context Sensitive Help' option on the Tools menu first; preferably when your "main.exw" is open & topmost. This creates the files "glocals.exh" and "win32lib.exh". I recommend using a fully-commented win32lib.ew.
Two additional colours added to syntax highlighting.
Reformat(re-indent) function added to Tool menu.
Several screen display problems addressed.
Mouse wheel support should now work (not that I have one to test it with)
Shift-left and shift-right now recognise numbers as works.
Shift-left mouse click now extends selection.
Enjoy! Pete
A full featured editor written entirely in Euphoria: Multiple documents, auto completion, automatic backups, run program, automated error processing, file and directory compare, find in files, macro, context sensitive help (built automatically from the sources of the current project), routine and section list, reformat (re-indent) program to find missing end statements, detailed manual, and more.
3. Re: MEditor 2.0.2 release
- Posted by Dan Moyer <DANIELMOYER at prodigy.net> Nov 14, 2002
- 425 views
- Last edited Nov 15, 2002
Pete, Looks interesting! 1. Why not word-wrap? Can't see the end of many lines, not pleasant to have to hit [end] to see all of longer lines. (had to use WordPad to read the manual comfortably.) 2. If the F1 Help-Context/Keyboard screen shows anything after "Help: F1 this screen", I can't see it 'cause I can't see the bottom of that modal window (no scroll); 3. Why make it so that window can't be closed except by [esc] key? If important to keep it that way, probably should have "[esc] to close" at beginning? 4. The "Quick Jump" window is too narrow (at least on my system) to see all of some entries, & un-resizeable. 5. Since you're showing the MEditor manual via the MEditor, it should auto turn off syntax coloring (& then back to whatever it was if tab to other file). 6. "CopyAppend" is WONDERFUL!!!! 7. The "QuickJump" is so useful, it should maybe be on a toolbar? 8. The "find" should maybe work across any includes included in a file being edited? That way if user is reading code & wonders "what's this routine do", & searches for it, & it's in an include, it's would be found. 9. Maybe "Find" in a toolbar too? All for now :) Dan Moyer ----- Original Message ----- From: <petelomax at blueyonder.co.uk> Sent: Wednesday, November 13, 2002 9:36 AM Subject: MEditor 2.0.2 release This is pretty much the final version, anything else will likely be just a small bolt-on. Rob, can you update the archive, I've written a new description for you at the end. New features 13/11/02: Context sensitive help for win32lib routines and locally defined procedures, functions, and types. Shows parameters, comments, and allows direct jump to the code. You should use the new 'Parse for Context Sensitive Help' option on the Tools menu first; preferably when your "main.exw" is open & topmost. This creates the files "glocals.exh" and "win32lib.exh". I recommend using a fully-commented win32lib.ew. Two additional colours added to syntax highlighting. Reformat(re-indent) function added to Tool menu. Several screen display problems addressed. Mouse wheel support should now work (not that I have one to test it with) Shift-left and shift-right now recognise numbers as works. Shift-left mouse click now extends selection. Enjoy! Pete A full featured editor written entirely in Euphoria: Multiple documents, auto completion, automatic backups, run program, automated error processing, file and directory compare, find in files, macro, context sensitive help (built automatically from the sources of the current project), routine and section list, reformat (re-indent) program to find missing end statements, detailed manual, and more.
4. Re: MEditor 2.0.2 release
- Posted by Dan Moyer <DANIELMOYER at prodigy.net> Nov 15, 2002
- 420 views
- Last edited Nov 16, 2002
Pete, >2. If the F1 Help-Context/Keyboard screen shows anything after "Help: F1 >>this screen", I can't see it 'cause I can't see the bottom of that modal >>window (no scroll); >When that happens I just use the Examine Code button... It shouldn't >be hard to change that though What "Examine Code button"? I didn't see anything like that anywhere. Scroll would be better, I think. >>3. Why make it so that window can't be closed except by [esc] key? If >>important to keep it that way, probably should have "[esc] to close" at >>beginning? >You can close the window by: right clicking on the title bar and >selecting close, clicking on the top right X, or pressing Alt F4, or >Alt C, or clicking on the Close button, or pressing escape If nothing in a file being edited is *selected* (or cursor isn't sitting next to a routine, which is a very neat touch!), then the right X to close is grayed out, and there's no option on right click title bar to close, just move; & can't see any "Close" button, may be at bottom which can't scroll down to. >>8. The "find" should maybe work across any includes included in a file being >>edited? That way if user is reading code & wonders "what's this routine >>do", & searches for it, & it's in an include, it's would be found. (er, "it would be found") >I use find in files when that happens This would work much better, I think, to find an included routine from an instance of calling it: Since F1 (when routine is selected or cursor is next to use of one) shows the include that routine is in (if it's in an include) on the title bar (or knows it's in the doc being edited if that's the case), if you let F2 be "find routine" (if it's not being used for something else) and just do the part of F1 that gets the include pathname info (if it's not in the doc being edited, no search needed to get that info), and then "jump" *directly* to a find in that include for the routine name (not the find dialog, just find it in the include & open the include & show the routine), that would seem relatively easy to implement, & very easy to use. That would be much better for looking for the actual routine than "Find in files", which shows every instance of calling the routine. Not *sure* how useful it would be, just something I instinctively tried when looking at MEditor. :) Dan
5. Re: MEditor 2.0.2 release
- Posted by petelomax at blueyonder.co.uk Nov 16, 2002
- 433 views
- Last edited Nov 17, 2002
On Fri, 15 Nov 2002 20:38:04 -0800, Dan Moyer <DANIELMOYER at prodigy.net> wrote: >What "Examine Code button"? Ah, different window. working.... I assume you are running 800x600; I'll retest everything at that res. PS when the routine details are shown try pressing return. There is a default button you cannot see. Pete
