Hi Alain,
Alain said to me:
PS as to Translation, if some day it kets Kittenized, surely I will
help :)
It is already kittenized in version 1.7 beta (maybe even before that,
I don't know). Currently I'm in the process of kittenizing all the
new code I added and I'm almost done. Once I'm done with that I would
like to put the code into CVS so long as it's reasonably stable so
folks can translate all the new messages I added. I'm afraid there
are a lot :)
Alain said to Johnson:
Yes, I agree that work should target at "same as DOS", but if the
original DOS option sucks, we can consider an alternative, like add
a
switch to "workaround", original DOS v6.22 or v7.10 is not perfect
In this case, MEM didn't stay resident, so I think bigger file size
is
not a problem, if someone interest, he can code a FDISK /menu or
FORMAT /menu with TurboVision like window
I agree, but I am sure that you will find many to disagree. For some
people here, size *is* an issue, apparently even for the non
resident files.
May I suggest something that I used for a PCI driver: you put all
the
functions that do the real work in separate files fropm the output
files, this way you can compile 2 targets and so keep one of them
small.
That is definitely what I am planning to do because of the fact that
MI has a bunch of options and it would be a mess to offer the user the
ability to use all of those different options and also offer all the
existing options without some confusing code. Besides, are the users
not used to typing "MI"? :) So I will make an MI.EXE. Eventually I
would like to make a Turbo Vision or similar UI version of MEM which I
would call, say, MEM For TurboVision or "MFT" which is coincidentally
the same name as QEMM's Manifest program :) It may coincidentally
offer the same options if someone tells me what they are, and similar
output if someone can describe/capture that for me.
The question I haven't thought about much yet is translations: there
would be some shared messages, so perhaps we'll have a shared NLS
files and MI.EXE would use MEM.EN, etc. Could be confusing for users,
but otherwise it may be annoying for me and anyone doing translations
to have to copy strings out of the MEM files unless we make a rule
that set numbers below X are common and can be copy/pasted directly
between the two applications' NLS files. Copy/pasting parts of
programs is almost always a mistake though :)
Regards,
David
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
