Idea: Generalized file transforms for Edit

Robert: OK, I'll give it a go. Having to maintain an ON/OFF setting along with the string itself now means two profile variables, or some kind of hybrid string/ON|OFF. Yet more grungy code. Maybe some other method.

George

Robert: I've got the XFORM WRITE support going. Since there is no /ON /OFF ability (I am NOT adding it to SAVE etc.) the XFORM Write support is only active for the plain ordinary SAVE command.  All other flavors (CREATE, REPLACE, SAVEAS etc.) will work just like today.

When a file is loaded via XFORM, the Mode box on the status bar will change from say, Save to (X) Save and the box will be colored RED.

So if someone loads a file with XFORM, and does a SAVEAS - the file will be saved with the text as it appears in Edit. Not what the user wants?  Tough.

Also, the Write will use whatever XFORM macro was used to actually load the file.  No loading with ABC macro, changing XFORM and writing with DEF macro.

If a SAVE is attempted, and the XFORM macro reports an error (say at END time with AUTOSAVE ON) the session is not ended, you are left in Edit with some error messages.

If a file is loaded via XFORM, changing the Profile to XFORM NONE will not prevent SAVE from using the XFORM macro, you'd need to use CREATE/REPLACE etc. or CAN out.

This is all going to mean a lot of documentation.  So if you want tweaks, say so quickly before I get the Doc. underway.

George

OK, I'll cut out what I started from HnD. Not much but every bit I wrote made it more and more obvious I was on the wrong track. I'll email it to you.

George

Robert: IMACRO and XFORM have no problem co-existing. Remember XFORM is involved in loading the file; IMACRO is invoked after the file is loaded, regardless of how it was loaded.

Yes, WRITE support works.  The XRW demo macro does just that, you can edit and save normal ANSI files using it.  Remember, the heavy lifting part of all this is going to be in the macro, not in SPFLite.  We're providing an interface for replacing the file Read/Write functions.  The sample macros are to help users get started in writing their own macros.

As to creating a full Hex editor, that's a lot more effort.  One problem is that the dump format currently has a problem if the font used can't handle all 256 characters, it ends up with the character display shifted and distorted by unprintable characters.  That lovely Dump display is, after all, just print lines loaded into the editor.  SPFLite has no idea that it is some kind of file dump.

There's a lot to plan before tackling something like a hex editor.

George

SPFLite22.zip (446.53 KB)

Robert: I'll rename the EXE to SPFLite22.EXE, then you can just add it to the install folder. The macros can just be added to your normal MACROS folder. I'll package some stuff up. I'm not all done yet, still stuff to do with handling the other WRITE commands (CREATE/SAVEAS etc.) so no complaints about them are allowed yet.

The macros are:
XCFG - Displays Profile names from an SPFLite.CFG file
XHex - This is the basic hex file editor.
XLines - This dumps text type files in Hex/Char dump format.
XRW - Simple demo of reading / writing a text file via XFORM.
XZIP - Displays the filenames contained in a normal ZIP file.
 

George

George !

Here the XH XL  macros . 

MXform.7z (5.55 KB)

Nr of Bytes in Line and word can be tailored in macro .
for other changes see macro comment .
Here a sample screen shot of SPFLite2.exe Version id area . Above part is XH below HxD Display .   

 Thanks

George ! 

Yes  im XH macro i added the translate . 
Use XH and your XHEX macro to hex view  SPFLite2.exe and you will see the difference at  x'350' x'4a0' f.e.