tvision-users Mailing List for Turbo Vision
Brought to you by:
set
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
(17) |
Jul
(6) |
Aug
(9) |
Sep
(14) |
Oct
(5) |
Nov
(5) |
Dec
(13) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(6) |
Feb
(20) |
Mar
(7) |
Apr
(12) |
May
(12) |
Jun
(2) |
Jul
(3) |
Aug
(4) |
Sep
(2) |
Oct
(11) |
Nov
|
Dec
|
2004 |
Jan
(8) |
Feb
|
Mar
(7) |
Apr
|
May
|
Jun
(2) |
Jul
(5) |
Aug
(9) |
Sep
(5) |
Oct
(5) |
Nov
|
Dec
(1) |
2005 |
Jan
(9) |
Feb
(6) |
Mar
|
Apr
(14) |
May
(31) |
Jun
(3) |
Jul
(23) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: steve d. <dy...@si...> - 2015-04-24 19:06:28
|
Has anyone managed to get the Linux-TV to work under LinuxMint (Xfce 32bit)? I am (almost) a Linux virgin and so I am struggling with 2 or 3 new technologies all at once! If LinuxMint doesn't work do I go for Ubuntu or Debian? (I originally chose Mint because it looked like it provided a complete, ready built environment that Windows users would be comfortable with). I am looking for a run-time environment that is stable and dependable (and preferably user friendly and pretty idiot proof). The program I have to port has to run reliably from 22:00 through to 18:00 every day and I do like my sleep! Thanks. Regards, Steve -- Please respond to dy...@si... |
From: Salvador E. T. <sal...@in...> - 2014-09-03 13:02:51
|
El 02/09/14 14:45, steve dyson escribió: > Most of these are TV/Linux questions and this may be the wrong place > for them. If it is then I apologize. I have labelled each question to > make it easier to refer back to them. > > Please can you explain why there are different TV ports for > different Distributions. (a) How much does the TurboVision code have > to change between each Distributions or it it just recompiled for each > target Linux? Same code, just different way to pack the stuff (and different dynamic libs) > > (b) If TV has been ported to version x of a Distribution is it safe to > assume it will work with all subsequent versions? Hmmm ... for the last years: yes, but you never know when something important will change. The name of dynamic libs and the gcc compiler introduce problems from time to time. I use TV on Debian GNU/Linux (stable version) since 1998, and will most probably keep using it for the next 20 years ;-) If you can afford recompiling every 2 years, you can assume it will keep working for 20 years. > > The easiest solution would be to not port the application but run it > within a DOS emulation box. I am nervous that DOS emulations may not > be available for whatever is windows in 10 years time. But I am quite > confident that Linux emulation forever! > > This brings up the next interesting question (sorry about this)... (c) > If I target a Linux emulation then which Distribution do I choose for > building the application? > > I was going to ask what the advantage of moving from a Borland C > compiler to DJGPP but I guess the answer is that it may not be > possible to get the BC++ environment to work within a future Windows > environment. (d) Are there other advantages? DJGPP uses GCC, and this is the best supported compiler. > > (e) Please could you also let me know about DLGDSN.? I used it quite > extensively during the original design for the application. I can't > work out if a port to Linux has been successful! DLGDSN is included in this port, but I don't use it, so I'm not sure how stable is. For dialogs use "EasyDiag", a lib I wrote. When you design EasyDiag dialogs you don't need to worry about exact coordinates, they are all relative. You say things like "At the right of X", or "Under Y", or "Top left". This makes much more easy to introduce changes in the dialog. Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina |
From: steve d. <dy...@si...> - 2014-09-02 17:46:35
|
Most of these are TV/Linux questions and this may be the wrong place for them. If it is then I apologize. I have labelled each question to make it easier to refer back to them. Please can you explain why there are different TV ports for different Distributions. (a) How much does the TurboVision code have to change between each Distributions or it it just recompiled for each target Linux? (b) If TV has been ported to version x of a Distribution is it safe to assume it will work with all subsequent versions? The easiest solution would be to not port the application but run it within a DOS emulation box. I am nervous that DOS emulations may not be available for whatever is windows in 10 years time. But I am quite confident that Linux emulation forever! This brings up the next interesting question (sorry about this)... (c) If I target a Linux emulation then which Distribution do I choose for building the application? I was going to ask what the advantage of moving from a Borland C compiler to DJGPP but I guess the answer is that it may not be possible to get the BC++ environment to work within a future Windows environment. (d) Are there other advantages? (e) Please could you also let me know about DLGDSN.? I used it quite extensively during the original design for the application. I can't work out if a port to Linux has been successful! Thanks. Steve -- Please respond to dy...@si... |
From: Salvador E. T. <sal...@in...> - 2014-09-01 11:24:37
|
Hi Steve: The "setedit" project, hosted by SourceForge, supports DOS and uses TV. You can get some ideas from its code. The main DOS target is DJGPP. Regards, SET El 31/08/14 07:50, steve dyson escribió: > Thanks for all the feedback. > > The reason for the question is that I developed an order processing > package in C++ using TV under DOS that has been in use for the past 16 > years. The companies that use it do not want to move away from it as > it has proved to be highly stable and reliable (with over 2 million > orders put through it so far). And because these companies use > application 24/7 I do not want the inconvenience of calls for support > in the middle of the night (or any other times)! > > It is my belief that a Linux platform is probably the most stable & > reliable for future-proofing the product. I think the fewer > intermediary steps (like a DOS emulator or a Linux virtual machine > nrunning under Windows-xxxx) the more reliable the platform will be > and the more likely the product will work in systems produced in 5 > years time (I just cannot risk Windows-2020 being so 'clever' that it > will not allow the program to work). > > I am concerned that porting the application to a Linux environment is > going to be non-trivial and I realize that what I end up will still be > a 20 year old application. But it must work reliably!!! > > I was worried that the TV activity had fallen off for several years > but am very grateful for all who have chipped in with advice and opinions. > > I hope these ramblings make sense and give some background to the > question. > > Regards > Steve > -- > Please respond to dy...@si... <mailto:dy...@si...> > -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina |
From: steve d. <dy...@si...> - 2014-08-31 10:51:39
|
Thanks for all the feedback. The reason for the question is that I developed an order processing package in C++ using TV under DOS that has been in use for the past 16 years. The companies that use it do not want to move away from it as it has proved to be highly stable and reliable (with over 2 million orders put through it so far). And because these companies use application 24/7 I do not want the inconvenience of calls for support in the middle of the night (or any other times)! It is my belief that a Linux platform is probably the most stable & reliable for future-proofing the product. I think the fewer intermediary steps (like a DOS emulator or a Linux virtual machine nrunning under Windows-xxxx) the more reliable the platform will be and the more likely the product will work in systems produced in 5 years time (I just cannot risk Windows-2020 being so 'clever' that it will not allow the program to work). I am concerned that porting the application to a Linux environment is going to be non-trivial and I realize that what I end up will still be a 20 year old application. But it must work reliably!!! I was worried that the TV activity had fallen off for several years but am very grateful for all who have chipped in with advice and opinions. I hope these ramblings make sense and give some background to the question. Regards Steve -- Please respond to dy...@si... |
From: Ivan B. <ib...@ad...> - 2014-08-20 13:49:15
|
<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello!<br> <br> <br> <div class="moz-cite-prefix">El 19/08/14 22:11, Lisias escribió:<br> </div> <blockquote cite="mid:53F...@un..." type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <div class="moz-cite-prefix">My Gosh,<br> <br> I completely forgot about this list! :-)<br> <br> It's something like... 20 years? since I signed to it.<br> <br> </div> </blockquote> Yeah! Amazing isn't it? IT'S ALIVE IT'S ALIVE!!!! :-)<br> <br> <br> <blockquote cite="mid:53F...@un..." type="cite"> <div class="moz-cite-prefix"> On 14.08.19 15:35, steve dyson wrote:<br> </div> <blockquote cite="mid:CAG...@ma..." type="cite"> <div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">I need to port a CPP TurboVision business application from MS-DOS to Linux as it is becoming harder an harder to configure the newer versions of windows to provide a correct environment for the program to run in (and I cannot guarantee even newer versions of Windows will support legacy code).</span> <div> <font face="arial, sans-serif"><br> </font></div> <div><font face="arial, sans-serif">The application originally ran in a pure MS-DOS environment using a LittleBigLan network. I have ported it to run under Windows 98 and then under Windows XP using a Linux based file server.<br> </font></div> </div> </blockquote> On the short run, did you tried DOSBOX or, better yet, Virtual BOX? The former is faster, but the latter is far more accurate (but somewhat resource hogger, you will need a virtualization enabled processor, as i3).<br> <br> </blockquote> Yeah, trying emulation/virtualization first seems like the right thing to do, much less work than porting it.<br> I recommend trying this things in this order until one works:<br> - DOSEmu + FreeDOS.<br> - DOSBOX (does it come with FreeDOS? I guess so...).<br> - Virt-Manager + FreeDOS (uses libvirt with QEMU-KVM or you can use QEMU without KVM acceleration too).<br> - VirtualBox + FreeDOS.<br> <br> <br> <br> <blockquote cite="mid:53F...@un..." type="cite"> <blockquote cite="mid:CAG...@ma..." type="cite"> <div dir="ltr"> <div><font face="arial, sans-serif"> </font> <div><span style="font-family:arial,sans-serif;font-size:13px">Is there a preferred flavour of Linux (Debian/Red Hat/etc) that I should choose and which port of TV would be most stable? Should I use 32 bit or 64 bit target (and is there much difference in the performance)? Is there a lists of Gotchas or potential problems that I should be mindful off?</span> <div> <span style="font-family:arial,sans-serif;font-size:13px"><br> </span></div> </div> </div> </div> </blockquote> A Linux Distro is almost as a religion - you will need to live it in order to taste it. My personal distro of choice is OpenSUSE. I like it very much, YAST2 saves a huge amount of time while administering the box.<br> <br> </blockquote> Oh no! Don't listen to this guy, Debian is the best of course!!! (now waiting for the Red Hat fanatic....).<br> You may find precompiled Debian packages though, or compile ones your self, but its been a long time since I last tested them; I saw Salvador touching the scripts a bit so maybe he adapted them to current Debian stable (Wheezy).<br> <br> TVision and SETEdit work equally well in 32 and 64 bits, but you may find that porting your application to 32bits is easier as a first step...<br> If you are doing heavy math, then the 64 bits results could be a bit different to the 32 or 16 bits ones because SSE instructions doesn't have excess precision or something like that... so thats something to have in mind too.<br> You can tell the compiler to use SSE in 32 bits easily after you ported the application to see the differences in the results before porting to 64 bits.<br> <br> <br> Hope this helps, bye!<br> <br> <br> <pre class="moz-signature" cols="72">-- Ivan Baldo - <a class="moz-txt-link-abbreviated" href="mailto:ib...@ad...">ib...@ad...</a> - <a class="moz-txt-link-freetext" href="http://ibaldo.codigolibre.net/">http://ibaldo.codigolibre.net/</a> >From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: <a class="moz-txt-link-abbreviated" href="mailto:ib...@co...">ib...@co...</a> - <a class="moz-txt-link-freetext" href="http://go.to/ibaldo">http://go.to/ibaldo</a> </pre> </body> </html> |
From: Salvador E. T. <sal...@in...> - 2014-08-20 13:14:12
|
Hi! El 19/08/14 22:11, Lisias escribió: > My Gosh, > > I completely forgot about this list! :-) > > It's something like... 20 years? since I signed to it. > > On 14.08.19 15:35, steve dyson wrote: >> I need to port a CPP TurboVision business application from MS-DOS to >> Linux as it is becoming harder an harder to configure the newer >> versions of windows to provide a correct environment for the program >> to run in (and I cannot guarantee even newer versions of Windows will >> support legacy code). >> >> The application originally ran in a pure MS-DOS environment using a >> LittleBigLan network. I have ported it to run under Windows 98 and >> then under Windows XP using a Linux based file server. > On the short run, did you tried DOSBOX or, better yet, Virtual BOX? > The former is faster, but the latter is far more accurate (but > somewhat resource hogger, you will need a virtualization enabled > processor, as i3). Another option: if you really prefer Windows you can create native Win32 applications using TV. Various screen drivers are available, and you can use various compilers (mingw, cygwin, BC++, MSVC, Watcom). But Linux target is much more stable. > >> Is there a preferred flavour of Linux (Debian/Red Hat/etc) that I >> should choose and which port of TV would be most stable? Should I use >> 32 bit or 64 bit target (and is there much difference in the >> performance)? Is there a lists of Gotchas or potential problems that >> I should be mindful off? >> > A Linux Distro is almost as a religion - you will need to live it in > order to taste it. My personal distro of choice is OpenSUSE. I like it > very much, YAST2 saves a huge amount of time while administering the box. I agree, this is a question of taste. I use Debian GNU/Linux, since v1.3. I always use the stable version. > I can't give any opinion about the TV version to use, it's too much > time since I played with it for the last time - sorry. I suggest using the CVS trunk, just do a CVS check-out. If you can't access CVS try this: http://tvision.sourceforge.net/snap.html > Stick with 32 bits as much as you can. 64 bits programs uses twice the > memory for pointers and memory addresses, it's just a waste of code > space unless you are dealing with an so huge amount of data that a > 2ˆ32 address space can't hold it. I agree, TV applications won't get any advantage when compiled for a 64 bits target, and you could hit a bug. About gotchas: Linux console isn't well maintained, you'll get better results running TV applications from the graphic environment (will run as a native X application). Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina |
From: Lisias <li...@un...> - 2014-08-20 02:46:02
|
Nah. Just 15 years... :-) -- Lisias On 14.08.19 22:11, Lisias wrote: > My Gosh, > > I completely forgot about this list! :-) > > It's something like... 20 years? since I signed to it. |
From: Lisias <li...@un...> - 2014-08-20 01:25:06
|
My Gosh, I completely forgot about this list! :-) It's something like... 20 years? since I signed to it. On 14.08.19 15:35, steve dyson wrote: > I need to port a CPP TurboVision business application from MS-DOS to > Linux as it is becoming harder an harder to configure the newer > versions of windows to provide a correct environment for the program > to run in (and I cannot guarantee even newer versions of Windows will > support legacy code). > > The application originally ran in a pure MS-DOS environment using a > LittleBigLan network. I have ported it to run under Windows 98 and > then under Windows XP using a Linux based file server. On the short run, did you tried DOSBOX or, better yet, Virtual BOX? The former is faster, but the latter is far more accurate (but somewhat resource hogger, you will need a virtualization enabled processor, as i3). > Is there a preferred flavour of Linux (Debian/Red Hat/etc) that I > should choose and which port of TV would be most stable? Should I use > 32 bit or 64 bit target (and is there much difference in the > performance)? Is there a lists of Gotchas or potential problems that I > should be mindful off? > A Linux Distro is almost as a religion - you will need to live it in order to taste it. My personal distro of choice is OpenSUSE. I like it very much, YAST2 saves a huge amount of time while administering the box. I can't give any opinion about the TV version to use, it's too much time since I played with it for the last time - sorry. Stick with 32 bits as much as you can. 64 bits programs uses twice the memory for pointers and memory addresses, it's just a waste of code space unless you are dealing with an so huge amount of data that a 2^32 address space can't hold it. If 4 G of ram is enough to you, stay away from 64 bits programs. :-) You can do 64 bits math in a 32 bits address space targeted program, anyway. What compiler did you use on your MS-DOS box? Did you tried GCC over mingw or cygwin? -- Lisias |
From: steve d. <dy...@si...> - 2014-08-19 18:36:34
|
I need to port a CPP TurboVision business application from MS-DOS to Linux as it is becoming harder an harder to configure the newer versions of windows to provide a correct environment for the program to run in (and I cannot guarantee even newer versions of Windows will support legacy code). The application originally ran in a pure MS-DOS environment using a LittleBigLan network. I have ported it to run under Windows 98 and then under Windows XP using a Linux based file server. Is there a preferred flavour of Linux (Debian/Red Hat/etc) that I should choose and which port of TV would be most stable? Should I use 32 bit or 64 bit target (and is there much difference in the performance)? Is there a lists of Gotchas or potential problems that I should be mindful off? Thanks in advance. Steve Dyson -- Please respond to dy...@si... |
From: Michael R. <mic...@fr...> - 2008-09-08 18:44:46
|
Salvador Eduardo Tropea schrieb: > Why inside winnt? Dunno, I did feel redirected into this folder by the readme. > Can you try the one in the root of the project? > (Makefile.nmk) it reuses the BC++ makefile. Ok. >> Can you tell me how to build one of the examples? Is there a sample >> makefile for VC++ 8.0? > > Please try the main .nmk. Done that with a fresh copy, worked. Have the librhtv.lib again, now in \makes. (This time only the 'no public symbols found' warning again, the other one not). > I think this is what the other makefile compiles. The makefile in \winnt creates the example. Thanks so far. :) Regards, -mr |
From: Salvador E. T. <sal...@in...> - 2008-09-08 15:54:22
|
On 08/09/08 11:12, Michael Reichenbach wrote: > Cool, project seams alive. :) > > Salvador Eduardo Tropea schrieb: > >> I don't know much about VC versions ... >> > > Me neither, only the version I am using. There is a history of versions, > number x.x and corespondent Vistual Studio name. > http://en.wikipedia.org/wiki/Visual_C%2B%2B > > >> You can try a CVS snapshot: >> >> http://tvision.sourceforge.net/snap.html >> > > Done. > > >> I never had direct access to it. >> > > Microsoft platform sdk is free in price. > Yes, but last time I checked it needed W2k or newer, last Windows I installed was 98SE ... > Also Visual Studio 2005 Express Edition (VC++ 8.0) and Visual Studio > 2008 Express Edition (VC++ 9.0) are free in price. Rich in features. > Imho worth to try and use. > http://www.microsoft.com/express/2005/ > > Only disadvantages: > - obviously them like you to buy a paid version (besides free > registration no nagscreen) > - it's from ms, if this is important for you > > >> If you get errors you can post them and we could try to solve the >> issues. >> > > nmake -f Makefile.nmk clean doesn't work probable because the line is to > long. (Sorry, I can't provide any solutions, maybe deleting the whole > folder instant.) > > > > > (used > nmake -f Makefile.nmk all > inside the winnt folder, Why inside winnt? Can you try the one in the root of the project? (Makefile.nmk) it reuses the BC++ makefile. > started visual studio 2005 command promt before) > > > > I could build libtv.lib (some warnings, see blow) with the cvs snapshot > you gave to me. > > > Yet I haven't build an example. The readme says 'How do I compile the > demo? Is compiled by the makefile, the name is tvex.exe.'. But it hasn't > build tvex.exe, even if I removed the # before SRC7 = > ./examples/tutorial and SRC3 = ./ > I think this is what the other makefile compiles. > Can you tell me how to build one of the examples? Is there a sample > makefile for VC++ 8.0? > Please try the main .nmk. Regard, SET -- _______________________________________________________________ Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI-Electrónica e Informática Tel: (+54 11) 4724 6315 Colectora de Av. General Paz 5445 San Martín - B1650KNA Casilla de Correo 157 FAX: (+54 11) 4754 5194 Buenos Aires * Argentina http://www.inti.gob.ar/ |
From: Michael R. <mic...@fr...> - 2008-09-08 14:12:52
|
Cool, project seams alive. :) Salvador Eduardo Tropea schrieb: > I don't know much about VC versions ... Me neither, only the version I am using. There is a history of versions, number x.x and corespondent Vistual Studio name. http://en.wikipedia.org/wiki/Visual_C%2B%2B > You can try a CVS snapshot: > > http://tvision.sourceforge.net/snap.html Done. > I never had direct access to it. Microsoft platform sdk is free in price. Also Visual Studio 2005 Express Edition (VC++ 8.0) and Visual Studio 2008 Express Edition (VC++ 9.0) are free in price. Rich in features. Imho worth to try and use. http://www.microsoft.com/express/2005/ Only disadvantages: - obviously them like you to buy a paid version (besides free registration no nagscreen) - it's from ms, if this is important for you > If you get errors you can post them and we could try to solve the > issues. nmake -f Makefile.nmk clean doesn't work probable because the line is to long. (Sorry, I can't provide any solutions, maybe deleting the whole folder instant.) (used nmake -f Makefile.nmk all inside the winnt folder, started visual studio 2005 command promt before) I could build libtv.lib (some warnings, see blow) with the cvs snapshot you gave to me. Yet I haven't build an example. The readme says 'How do I compile the demo? Is compiled by the makefile, the name is tvex.exe.'. But it hasn't build tvex.exe, even if I removed the # before SRC7 = ./examples/tutorial and SRC3 = ./ Can you tell me how to build one of the examples? Is there a sample makefile for VC++ 8.0? No errors, so far only warnings. Everywhere this one: cl /nologo -c -O2 -I./include -I../include -D_WIN32 /GR- /GX- /EHsc /Tp. ./classes/unix\unixdis.cc -Foobj_ms/unixdis.o cl : Command line warning D9035 : option 'GX-' has been deprecated and will be r emoved in a future release cl : Command line warning D9036 : use 'EHs-c-' instead of 'GX-' unixdis.cc cl /nologo -c -O2 -I./include -I../include -D_WIN32 /GR- /GX- /EHsc /Tp. ./classes/unix\unixkey.cc -Foobj_ms/unixkey.o cl : Command line warning D9035 : option 'GX-' has been deprecated and will be r emoved in a future release I've combined and exchanged /GR- with the new EHs-c-. Then I did run into a lot of cl /nologo -c -O2 -I./include -I../include -D_WIN32 /GR- /EHs-c- /EHsc / Tp../classes/qnx4\qnx4scr.cc -Foobj_ms/qnx4scr.o cl : Command line warning D9025 : overriding '/EHs-' with '/EHs' cl : Command line warning D9025 : overriding '/EHc-' with '/EHc' combined again.... This is the new makefile with less warnings: http://nopaste.com/p/aHrQqRgRT (warning, this was just reading and luck, tbh I have not much clue, better someone else is looking into this) With the new makefile there are only a few warning left, all about the same topic. xtermmouse.o : warning LNK4221: no public symbols found; archive member will be inaccessible xtermkey.o : warning LNK4221: no public symbols found; archive member will be in accessible xtermdis.o : warning LNK4221: no public symbols found; archive member will be in accessible x11src.o : warning LNK4221: no public symbols found; archive member will be inac cessible x11mouse.o : warning LNK4221: no public symbols found; archive member will be in accessible x11key.o : warning LNK4221: no public symbols found; archive member will be inac cessible x11dis.o : warning LNK4221: no public symbols found; archive member will be inac cessible wingrscr.o : warning LNK4221: no public symbols found; archive member will be in accessible wingrmouse.o : warning LNK4221: no public symbols found; archive member will be inaccessible wingrkey.o : warning LNK4221: no public symbols found; archive member will be in accessible wingrdis.o : warning LNK4221: no public symbols found; archive member will be in accessible unixscr.o : warning LNK4221: no public symbols found; archive member will be ina ccessible unixmouse.o : warning LNK4221: no public symbols found; archive member will be i naccessible unixkey.o : warning LNK4221: no public symbols found; archive member will be ina ccessible unixdis.o : warning LNK4221: no public symbols found; archive member will be ina ccessible sescreen.o : warning LNK4221: no public symbols found; archive member will be in accessible screen.o : warning LNK4221: no public symbols found; archive member will be inac cessible rhscreen.o : warning LNK4221: no public symbols found; archive member will be in accessible qnxscr.o : warning LNK4221: no public symbols found; archive member will be inac cessible qnxkey.o : warning LNK4221: no public symbols found; archive member will be inac cessible qnxdis.o : warning LNK4221: no public symbols found; archive member will be inac cessible qnx4scr.o : warning LNK4221: no public symbols found; archive member will be ina ccessible qnx4key.o : warning LNK4221: no public symbols found; archive member will be ina ccessible qnx4dis.o : warning LNK4221: no public symbols found; archive member will be ina ccessible linuxscr.o : warning LNK4221: no public symbols found; archive member will be in accessible linuxmouse.o : warning LNK4221: no public symbols found; archive member will be inaccessible linuxkey.o : warning LNK4221: no public symbols found; archive member will be in accessible linuxdis.o : warning LNK4221: no public symbols found; archive member will be in accessible dosscr.o : warning LNK4221: no public symbols found; archive member will be inac cessible dosmouse.o : warning LNK4221: no public symbols found; archive member will be in accessible doskey.o : warning LNK4221: no public symbols found; archive member will be inac cessible dosdis.o : warning LNK4221: no public symbols found; archive member will be inac cessible |
From: Mike G. <mi...@ma...> - 2008-09-08 13:35:52
|
Hello, Michael! MR> I am pretty curios about this project. MR> Did you get tv to compile with Visual C++ 8.0 (VS 05) (or VC++ 9.0, CS MR> VS08)? MR> Is there an updated makefile? TVision has been compiled by me using VS2005 without any problem. As for VS2008 you need to check if it still works, because many standard C/C++ (POSIX) function names and functions was declared by VS2005 as deprecated on the score of security and ISO C++ conformance, so VS2008 could or could not contain these standard function names and functions. With best regards, Mike Gorchak. E-mail: mi...@ma... |
From: Salvador E. T. <sal...@in...> - 2008-09-08 12:49:29
|
Hi! On 08/09/08 09:40, Michael Reichenbach wrote: > I am pretty curios about this project. > > Did you get tv to compile with Visual C++ 8.0 (VS 05) (or VC++ 9.0, CS > VS08)? > I don't know much about VC versions ... > Is there an updated makefile? > You can try a CVS snapshot: http://tvision.sourceforge.net/snap.html If you get errors you can post them and we could try to solve the issues. Is a little bit slow process but that's the way used to get it compiled with a new version of VC++, I never had direct access to it. Regards, SET -- _______________________________________________________________ Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI-Electrónica e Informática Tel: (+54 11) 4724 6315 Colectora de Av. General Paz 5445 San Martín - B1650KNA Casilla de Correo 157 FAX: (+54 11) 4754 5194 Buenos Aires * Argentina http://www.inti.gob.ar/ |
From: Michael R. <mic...@fr...> - 2008-09-08 12:40:31
|
Hi! I am pretty curios about this project. Did you get tv to compile with Visual C++ 8.0 (VS 05) (or VC++ 9.0, CS VS08)? Is there an updated makefile? Regards, -mr |
From: Salvador E. T. <sal...@in...> - 2006-11-29 12:39:30
|
On 28/11/06 15:34, Dennis Smallwood wrote: >I am wondering about the TVision ability to browse NTFS partitions. I seem >to be able to list the files that are below 2GB in file size, but files more >that 2GB are not displayed. Is this a limitation of 32 bits calls? > >Has anyone been successful in getting this to work? Would the libraries have >to change to include this ability? How? Is this a feature request? > > Don't know. Take a look at classes/tfilelis.cc You'll find void TFileList::readDirectory( const char *aWildCard ) in a section that says "// Linux, BC++/Win32 and CygWin". It uses stat and S_ISREG: if (stat(gl.gl_pathv[i], &s) == 0 && S_ISREG(s.st_mode)) I don't have NTFS so I can't test it. Regards, SET |
From: Dennis S. <dsm...@ho...> - 2006-11-28 18:34:36
|
I am wondering about the TVision ability to browse NTFS partitions. I seem to be able to list the files that are below 2GB in file size, but files more that 2GB are not displayed. Is this a limitation of 32 bits calls? Has anyone been successful in getting this to work? Would the libraries have to change to include this ability? How? Is this a feature request? _________________________________________________________________ Fixing up the home? Live Search can help http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmemailtaglinenov06&FORM=WLMTAG |
From: Salvador E. T. <sal...@in...> - 2006-11-17 13:43:24
|
Hi All! I uploaded a source tarball and .deb packages for: Debian GNU/Linux 3.1 (Sarge) x86/SPARC and Ubuntu 6.10 (Edgy) x86. Regards, SET P.D. Thanks to Juan Pablo for the Ubuntu packages. |
From: Salvador E. T. <sal...@in...> - 2006-03-06 12:57:59
|
On 28/02/06 16:51, Petr B=EChan wrote: >Is there any reason why TGroup::~TGroup() doesn't call shutDown()? I'd >post it as bug, but it's so obvious that more likely there is some >really good reason that I don't see (wrong chaining of destructors with >some non-gcc compilers? I don't have too much experience with >portability in obscure environments, just gcc on linux and mingw). By >looking into other TV clones on the net it may be legacy from the >original borland source, but you said you don't aim to be 100% >compatible and besides changing it shouldn't bring any incompatibility. > =20 > >I know TV from ancient times when I worked in pascal. Recently I needed >to code UI for console applications so I looked for c++ counterpart to >TV I already knew, found this and did what I remembered as correct: >{ TDialog *dlg; > TProgram::deskTop->execView(dlg); > delete dlg; } >After coding 4 dialogs I thought that it's time to wonder if I have >memory management right, and of course I found that each dialog instance= >uses ~4kB memory which is not returned. And after little searching I >found that the correct way is to call CLY_destroy(dlg) instead of >standard c++ way of using destructors. > =20 > Yes. >Even Borland manual for destructor TGroup.done() (for pascal, I don't >have one for c++ TV) says "Hides the group using Hide, disposes of each >subview in the group, and finally calls the Done destructor inherited >from TView" in the description of TGroup destructor. As simple fix I >added the call to shutDown() into ~TView() and ~TGroup and the basic >dialogs now work as I expected (I didn't have lot of time to test it yet= >- it just compiles, runs and valgrind reports no leaks in views). I can >get a patch together if you are interested, after fixing rest of >shutDown()'s. And testing it a bit. > =20 > The need for destroy is because you could share the same objects between = different "containers", you could also have static items in a collection = (making destroy incorrect). In general: you need to use destroy when you need to delete an object=20 and what it contains, some times you don't want to destroy the contained = objects. SET --=20 Salvador Eduardo Tropea (SET). (Electronics Engineer) Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Alternative e-mail: se...@co... se...@ie...=20 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013 |
From: <pet...@se...> - 2006-02-28 19:52:09
|
Is there any reason why TGroup::~TGroup() doesn't call shutDown()? I'd post it as bug, but it's so obvious that more likely there is some really good reason that I don't see (wrong chaining of destructors with some non-gcc compilers? I don't have too much experience with portability in obscure environments, just gcc on linux and mingw). By looking into other TV clones on the net it may be legacy from the original borland source, but you said you don't aim to be 100% compatible and besides changing it shouldn't bring any incompatibility. I know TV from ancient times when I worked in pascal. Recently I needed to code UI for console applications so I looked for c++ counterpart to TV I already knew, found this and did what I remembered as correct: { TDialog *dlg; TProgram::deskTop->execView(dlg); delete dlg; } After coding 4 dialogs I thought that it's time to wonder if I have memory management right, and of course I found that each dialog instance uses ~4kB memory which is not returned. And after little searching I found that the correct way is to call CLY_destroy(dlg) instead of standard c++ way of using destructors. Even Borland manual for destructor TGroup.done() (for pascal, I don't have one for c++ TV) says "Hides the group using Hide, disposes of each subview in the group, and finally calls the Done destructor inherited from TView" in the description of TGroup destructor. As simple fix I added the call to shutDown() into ~TView() and ~TGroup and the basic dialogs now work as I expected (I didn't have lot of time to test it yet - it just compiles, runs and valgrind reports no leaks in views). I can get a patch together if you are interested, after fixing rest of shutDown()'s. And testing it a bit. |
From: Salvador E. T. <sal...@in...> - 2005-07-29 15:30:23
|
Eddie wrote: > >Ad. 1. I will try, but give me an advise, how to do it or give me diff-file >format description. Sorry bothering, but I never wrote diff-file. > > Just use the diff tool (GNU diff Cygwin and DJGPP have it). The -u option is good for humans. If you are using CVS: cvs -z3 diff -u classes/tframe.cc SET -- Salvador Eduardo Tropea (SET). (Electronics Engineer) Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Alternative e-mail: se...@co... se...@ie... Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013 |
From: Eddie <one...@te...> - 2005-07-29 14:36:33
|
My "bug" is fixed. "Bug" reason: after I've insert TWindow, TWindow owner looses focus active flag. Fix: ... insert( ... ) // TWindow setState( sfActine, True ); // Wait until it closes And everything is fine. Until it works I will not change it. But thanks for advises. -----Original Message----- From: Salvador Eduardo Tropea [mailto:sal...@in...] Sent: Friday, July 29, 2005 3:51 PM To: Eddie Cc: tvi...@li... Subject: Re: Dialog frame bug/response problem Eddie wrote: >I've created a dialog (TDlg1 -> TDialog) which runs another one (TDlg2 >-> >TDialog) when a button is pressed. Button command is catch in >TDlg1::handleEvent. > > To see examples where that's implemented take a look at setedit. The setedit/edkeys.cc file implements a set of dialogs that calls other dialogs. >When the second one comes up (TDlg2 -> TDialog) and when user press a >button a window comes (TWnd -> TWindow) up. > > Without closing the dialogs? >The window is inserted like this (in TDlg2::handleEvent): >getAppPtr()->desktop->insert( pkWnd ); > >And I wait until it's closed, using this: > > [snip] > >Second dialog (TDlg2) frame becomes single lined (something like dlg is >dragged, but frame color is black). > > Because it doesn't have the focus anymore. >When I close TWnd. >Second dialog buttons (TDlg2 has only button controls) are working. The >frame is as I wrote above. I can't move it. But I can close it. > >The first dialog frame is untouched. > >Set please tell me why is it happening? > > You are inserting a normal window from a modal window, it doesn't have any sense. You should do all using windows or dialogs, this mix is invalid (other don't). Just imagine Windows opening a window from one of those dialogs that blocks the whole UI. SET -- Salvador Eduardo Tropea (SET). (Electronics Engineer) Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Alternative e-mail: se...@co... se...@ie... Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013 |
From: Eddie <one...@te...> - 2005-07-29 14:35:43
|
> Hmmm .... is quite hard to process things like it: > 1) You should send a diff and not a replacement. > 2) You are breaking the original indentation. > 3) That's incomplete, you are using ASCII 0xF without hooking to the code > page stuff. It means your icon looks like a random char on other > platforms. > 4) You are not providing a way to enable/diable it. > 5) You are using static_cast, I don't know if all the compiler we support > have this feature. Additionally it needs extra info not always generated > (on purpose to reduce binary size). > 6) You are using bool (not used in other place of the lib). > 7) The character you used (sun/star) isn't available in all consoles and > is reduced to the same ASCII than the black square. Both are reduced to *. > I'll incorporate it but with some changes and will see the result. Ad. 1. I will try, but give me an advise, how to do it or give me diff-file format description. Sorry bothering, but I never wrote diff-file. Ad. 2. Yes I know but it's strange I search a little before I wrote the code to check if it's already written. Nothing found. I check DosNavigator pascal sources and there also nothing found. I searched for tv.2 pascal sources but, not found. So I run BP7 ide and wrote the code being careful on this to code acted identically as I saw it in ide. I think it should be added by tv authors. I do not know why do they skip this part of code. Ad.3, 5, 6, 7. Sorry I wasn't thinking about (platforms) porting stuff. I wrote it to use it in VC. > The CVS snapshot contains it. Nice. Thanks. |
From: Salvador E. T. <sal...@in...> - 2005-07-29 13:51:28
|
Eddie wrote: >I've created a dialog (TDlg1 -> TDialog) which runs another one (TDlg2 -> >TDialog) when a button is pressed. Button command is catch in >TDlg1::handleEvent. > > To see examples where that's implemented take a look at setedit. The setedit/edkeys.cc file implements a set of dialogs that calls other dialogs. >When the second one comes up (TDlg2 -> TDialog) and when user press a button >a window comes (TWnd -> TWindow) up. > > Without closing the dialogs? >The window is inserted like this (in TDlg2::handleEvent): >getAppPtr()->desktop->insert( pkWnd ); > >And I wait until it's closed, using this: > > [snip] > >Second dialog (TDlg2) frame becomes single lined (something like dlg is >dragged, but frame color is black). > > Because it doesn't have the focus anymore. >When I close TWnd. >Second dialog buttons (TDlg2 has only button controls) are working. The >frame is as I wrote above. I can't move it. But I can close it. > >The first dialog frame is untouched. > >Set please tell me why is it happening? > > You are inserting a normal window from a modal window, it doesn't have any sense. You should do all using windows or dialogs, this mix is invalid (other don't). Just imagine Windows opening a window from one of those dialogs that blocks the whole UI. SET -- Salvador Eduardo Tropea (SET). (Electronics Engineer) Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Alternative e-mail: se...@co... se...@ie... Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013 |