|
Hi everyone,It has been awhile since much has happened on the list. I've been working on tn5250 and x5250 but haven't committed anything yet. I've fixed several bugs in x5250 (particularly related to non-US keyboards) and added support for SAVE PARTIAL SCREEN to lib5250.so. This last fix is necessary for QSH to work in enhanced mode so it is probably a pretty important fix to commit.
I've also been working on organizing the source a little better. I see a few benefits from doing so: old source is moved out (like the slang interface), the code that builds lib5250 vs. the other executables is better distinguished, the various executables and library may all be built independantly of each other, and builds for external projects like x5250 are simplified. So I propose the following two organizational changes for your consideration:
midrange.com
structure 1:
Split the source into five top level sub directories of tn5250 like this:
tn5250->
curses->
files needed for autoconf
ChangeLog, etc.
src->
Makefile.am
cursesterm.c
cursesterm.h
tn5250.c
lib5250->
files needed for autoconf
ChangeLog, etc.
src->
Makefile.am
buffer.c
buffer.h
codes5250.h
conf.c
conf.h
dbuffer.c
dbuffer.h
debug.c
debug.h
display.c
display.h
field.c
field.h
macro.c
macro.h
menu.c
menu.h
printsession.c
printsession.h
record.c
record.h
scrollbar.c
scrollbar.h
session.c
session.h
sslstream.c
stream.c
stream.h
telnetstr.c
terminal.c
terminal.h
tn5250-autoconfig.h
tn5250-config.h
tn5250-private.h
tn5250.h
transmaps.h
utility.c
utility.h
version.c
window.c
window.h
wtd.c
wtd.h
lp5250d->
files needed for autoconf
ChangeLog, etc.
src->
lp5250d.c
scs.c
scs.h
scs2ascii.c
scs2pdf.c
scs2ps.c
python->
files needed for autoconf
ChangeLog, etc.
src->
Makefile.am
py5250.py
tn5250-python.c
slang->
files needed for autoconf
ChangeLog, etc.
src->
Makefile.am
slangterm.c
slangterm.h
tn5250.c (maybe?)
structure 2:
tn5250->
files needed for autoconf
ChangeLog, etc.
src->
curses->
(same as above)
lib5250->
(same as above)
lp5250d->
(same as above)
python->
(same as above)
slang->
(same as above)
I think either way would achieve the improvements I mentioned. Both
should be equal amount of work in terms of the build. So I think it is
just preference. So, structure 1, structure 2, or no change at all?
James Rich
It's not the software that's free; it's you.
- billyskank on Groklaw
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
