Hi Jerome,
after reading the spec :
"### The Program Manager Eternity Edition Manual. (A little less rough draft)
About:
At a casual glance, PGME looks fairly simple. It's predecessor PGM7.2 was
rather uncomplicated. But, PGME is truly a monster of complexity. It is
multi-language, completely theme-able, event driven behemoth built on-top
of a fairly comprehensive object oriented application framework I created
from the ground up. Everything you see is some sort of "control" that
inherits code from it's ancestor and has some sort of parent that "owns"
it. It even has a context aware self-assembling dynamic help
system."
I stopped reading, sorry.
you should realy have a TLDR section.
so you developed a hugely complex, turing
complete program to attach binary data to programs (similar to what KITTENC
does) and propose to use *this* instead of KITTENC.
may I ask, whether it is KITTEN compatible with very tiny additional
work? is it scriptable? what's the size increase for programs? what's
the overhead on memory use?
BTW: KITTENC is compatible with UPX, both before and after compression
(I *DO* know)
>Oh, if you want to glue data to a text file, I highly recommended sticking a
>EOF character at the end first.
>Then you can “TYPE” them without seeing all the stuff glued onto it. But, it’s
>really meant for binaries.
this is all about a free and open DOS. so text files should be
changable by others. very bad as the glue data will be lost after
editing text files :<
Tom
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel