Home > Archive > Clipper > September 2005 > Need a menu system
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Need a menu system
|
|
| Scott Coffey 2005-09-12, 6:55 pm |
|
I have a client running Summer '87 code in a POS application. They
are using IBM's old FDO product (Fixed Disk Organizer) as their menu
system.
Since I moved them out of the DOS environment and into Windows (98 SE)
the FDO application will sometimes crash. This happens when they
minimize the FDO application and do some processing under Windows and
then restore the application. It's not a show stopper, but it is a
PITA.
What is a good replacement for the FDO menu system? I'm not a great
Clipper programmer but I am able to maintain their code, so writing
one from scratch would be an option although I'm thinking that a
decent menu system should exist out there somewhere. A small memory
footprint would be a plus. Any suggestions?
Thanks,
Scott
| |
| LHSoft@gmail.com 2005-09-12, 6:55 pm |
| Scott,
Have a look at Traybar, can be found at:
http://www.nimation.nl/traybar/
Lasse
Scott Coffey wrote:
> I have a client running Summer '87 code in a POS application. They
> are using IBM's old FDO product (Fixed Disk Organizer) as their menu
> system.
>
> Since I moved them out of the DOS environment and into Windows (98 SE)
> the FDO application will sometimes crash. This happens when they
> minimize the FDO application and do some processing under Windows and
> then restore the application. It's not a show stopper, but it is a
> PITA.
>
> What is a good replacement for the FDO menu system? I'm not a great
> Clipper programmer but I am able to maintain their code, so writing
> one from scratch would be an option although I'm thinking that a
> decent menu system should exist out there somewhere. A small memory
> footprint would be a plus. Any suggestions?
>
> Thanks,
> Scott
| |
| E. Fridman 2005-09-12, 6:55 pm |
| Scott,
May be I missing something but what is wrong with Windows shortcuts?
| |
| Scott Coffey 2005-09-13, 6:55 pm |
| On 12 Sep 2005 15:30:20 -0700, "E. Fridman" <pm771.am@gmail.com>
wrote:
>Scott,
>
>May be I missing something but what is wrong with Windows shortcuts?
I guess you're missing something. ;-)
I said I moved the application to the Windows OS (from a DOS
environment). It's still a Clipper Summer '87 application that is
menu driven. I need a replacement for the FDO menu system.
| |
| Scott Coffey 2005-09-13, 6:55 pm |
| On 12 Sep 2005 14:00:33 -0700, LHSoft@gmail.com wrote:
>Scott,
>
>Have a look at Traybar, can be found at:
>
>http://www.nimation.nl/traybar/
>
>Lasse
OK, I guess I wasn't clear here. I moved the application to Windows
as the host OS (from DRDOS as the host OS), but it is still a Clipper
application running Summer '87 code in a DOS box under 98SE. What I
need is a Clipper menu system... not a Windows menu system.
Scott
[color=darkred]
>Scott Coffey wrote:
| |
|
|
| AUGE_OHR 2005-09-13, 6:55 pm |
| hi,
> I have a client running Summer '87 code in a POS application. They
> are using IBM's old FDO product (Fixed Disk Organizer) as their menu
> system.
if i remember right FDO was only a ROM based BATch System
> Since I moved them out of the DOS environment and into Windows (98 SE)
> the FDO application will sometimes crash. This happens when they
did you "start" Win98 also from FDO ?
> minimize the FDO application and do some processing under Windows
> and then restore the application.
and than they start other Application with FDO ?
if yes ...
greetings by OHR
Jimmy
| |
|
|
Scott;
>
> I guess you're missing something. ;-)
>
> I said I moved the application to the Windows OS (from a DOS
> environment). It's still a Clipper Summer '87 application that is
> menu driven. I need a replacement for the FDO menu system.
I, and apparently others, are not clear on this. Perhaps the issue is your
definition of "application."
You have a application that consists of a single EXE that you want to call
from a DOS menu system? Why? If it is a single EXE, then either create a
shortcut on the desktop or put it on the regular Window Start menu (or
both). It doesn't matter if the EXE is a DOS program or a Windows program.
Or, you have an application that consists of multiple EXE's that are each
called from a DOS menu system which makes it appear to be one EXE to the
user? This is more complex. It would be better to compile all the code into
one EXE. If that is not feasible, you could create a desktop folder, and put
shortcuts to all the EXEs into that. Granted it wouldn't seem like they were
using the same application as it did with the DOS menu system.
Perhaps I still don't understand?
--
Regards,
James Bott
Intellitech
San Diego, California, USA
http://ourworld.compuserve.com/homepages/jbott
| |
| Stephen Quinn 2005-09-14, 6:55 pm |
| Scott
Check to see if GrumpMenu is on the OASIS.
Another alternative is to create an app with a picklist() (Grumpfish) of apps
you want to swap out to.
IIRC there's also a couple of different menu classes/functions in Grumpfish.
HTH
Steve
| |
| Scott Coffey 2005-09-14, 6:55 pm |
| On Tue, 13 Sep 2005 17:21:01 -0700, "James"
<jbottREMOVE@compuserve.com> wrote:
>
>Scott;
>
>
>I, and apparently others, are not clear on this. Perhaps the issue is your
>definition of "application."
I guess so. ;-)
I am responsible for a POS *system*. In addition to the main cash
register program there are programs for physical inventories, managing
price changes, timeclock functions, etc. etc. It's a full blown
system written solely in Clipper Summer '87 but running under Windows
98SE. It previously ran under DRDOS, but I needed to move it to
Windows in order to take advantage of things like high speed DSL lines
and newer versions of credit card verification programs. You enter
the system by clicking an icon on the desktop. From there it runs in
a full screen DOS box.
The system is driven by menus created using the FDO program. The
first menu looks like:
1. Cash Register Menu
2. Manager's Menu
3. Credit Card Menu
4. VIP Customer Menu
etc.
If you took menu option 1, it would look like:
1. Cash Register Program
2. End of Day Closeout
3. Receive Daily Files from Office
4. Receive New Pricing File
etc.
As you can see, menus call other menus which do different functions. I
want to replace this old, non-supported FDO menu system with something
that will work properly under Windows. I was hoping for a native
Clipper (supporting Summer '87 compiler) solution but any menu system
that could be used by Clipper Summer '87 applications would do fine.
I would simply stick with the FDO system, but as I mentioned it's
starting to sometimes crash since moving from DRDOS as the host OS to
Windows 98SE as the host OS.
Scott
| |
| Scott Coffey 2005-09-14, 6:55 pm |
| On 13 Sep 2005 14:33:41 -0700, "E. Fridman" <pm771.am@gmail.com>
wrote:
>Have you already looked at Oasis
>(http://www.the-oasis.net/ftpmaster....nt=ftpgenrl.htm) ?
I did, but nothing jumped out at me. I was hoping someone here could
give some insight.
Aren't most complete applications menu driven? If so, do people write
them from scratch or is there a menu generator or what-have-you out
there that works well with Clipper applications?
Excuse my ignorance. I'm a RPG programmer specializing in the IBM
midrange series of systems. I was brought kicking and screaming into
supporting this Clipper application.
| |
| Scott Coffey 2005-09-14, 6:55 pm |
| On Wed, 14 Sep 2005 00:23:40 +0200, "AUGE_OHR"
<AUGE_OHR_NOSPAM_@CSI.COM> wrote:
>hi,
>
>
>if i remember right FDO was only a ROM based BATch System
It's a menu system written long ago by IBM. It allows you to create a
menu system by "filling in the blanks" so to speak. You can have a
menu option perform DOS command, including calling other programs
(like Clipper programs).
>
>did you "start" Win98 also from FDO ?
No. Win98 is the host OS for a Clipper based POS system. To start
the system you click in icon on the Window 98 desktop which then opens
a full screen DOS box and then loads the FDO menu system.
I'm surprised you've never heard of it. A Google search would only
turn up references from the Y2K patch provided a few years back, but
here's a blurb from one of the patch providers:
"Although it is a rather old-fashioned application, I still consider
IBM's Fixed Disk Organizer (FDO) one of the easiest to use and most
elegant menu programs. Even when using Windows or a different OS, I
still make a DOS startup with FDO for old games and applications.
Maybe there are other users who think likewise and want to continue
using FDO."
I'm not finding it very "elegant" though. <g>
| |
| Scott Coffey 2005-09-14, 6:55 pm |
| On Wed, 14 Sep 2005 08:00:04 GMT, "Stephen Quinn"
<steveq@NOSPAMintegritynet.com.au> wrote:
>Scott
>
>Check to see if GrumpMenu is on the OASIS.
>Another alternative is to create an app with a picklist() (Grumpfish) of apps
>you want to swap out to.
>IIRC there's also a couple of different menu classes/functions in Grumpfish.
>
>HTH
>Steve
>
I found a .zip file called grump406, but it was pretty much Gr to
me. I was able to view the .ng file with Norton Guide Reader, but it
didn't tell me much.
Keep in mind that I'm an extreme Clipper lightweight. I was hoping
for some off-the-shelf menu system for dummies. ;-)
| |
| AUGE_OHR 2005-09-14, 6:55 pm |
| hi,
next try :
> It's a full blown system written solely in Clipper Summer '87 but running
> under Windows 98SE. It previously ran under DRDOS, but I needed to
> move it to Windows in order to take advantage of things like high speed
> DSL lines and newer versions of credit card verification programs.
did you test test it ? are you using a Lib for S87 to "control" COM Ports ?
how do you want to get DSL to COM(1-8) ?
> As you can see, menus call other menus which do different functions. I
> want to replace this old, non-supported FDO menu system with something
> that will work properly under Windows.
FDO is only a BATch menu system to run one of the menuitem.
you have to look inside how it calls the Cl*pper Programm. ( can be
parameters or different Application )
>I was hoping for a native Clipper (supporting Summer '87 compiler)
>solution but any menu system that could be used by Clipper Summer '87
>applications would do fine.
use PROMPT / MENU TO :
PROCEDURE MAINMENU
PRIVAT nChoice := 2 // S87 do not have LOCAL
SET WRAP ON
SET MESSAGE TO 23 CENTER
@ 6, 10 PROMPT "Add" MESSAGE "New Acct"
@ 7, 10 PROMPT "Edit" MESSAGE "Change Acct"
@ 9, 10 PROMPT "Quit" MESSAGE "Return to DOS"
MENU TO nChoice
//
DO CASE
CASE nChoice = 0
QUIT
CASE nChoice = 1
NewAccount()
CASE nChoice = 2
ChangeAccount()
CASE nChoice = 3
QUIT
ENDCASE
RETURN
> I would simply stick with the FDO system, but as I mentioned it's
> starting to sometimes crash since moving from DRDOS as the host OS to
> Windows 98SE as the host OS.
have a look at your Windows System Monitor. you will see that 16-bit DOS
application like Cl*pper S87 will take 100% CPU ...
it is time to recompile you S87 Source with a 32-bit compiler/linker to use
it
in a "multitasking / multiuser" environment.
greetings by OHR
Jimmy
| |
| AUGE_OHR 2005-09-14, 6:55 pm |
| hi,
> "Although it is a rather old-fashioned application, I still consider
> IBM's Fixed Disk Organizer (FDO) one of the easiest to use and most
> elegant menu programs.
in old days i use Xtree or Norton Command.
just one more :
did User try to call more than one FDO menuitem when using Win98 ?
if YES : is your application "network ready" ?
greetings by OHR
Jimmy
| |
| LHSoft@gmail.com 2005-09-14, 6:55 pm |
| Scott,
I'm not sure if I still get your problem correct., Sounds like the
system runs a bunch of different EXE files from the menu. If that's the
case, have a look at www.magee.com their automenu system will still
work in a windows dos-box.
The only other alternative I see (maybe I still don't understand your
problem) is to try to analyze the program and compile all those EXE's
into one exe using Clipper's native MENU commands. It might be that you
also need to switch linker from Plink to Blinker, to make it fit into
the dos memory of 640kb. If you have all the source, and there is no
extremely fancy lib's involved, it shouln't be that hard to make the
changes.
Regards,
Lasse
| |
| J. Webb 2005-09-14, 9:55 pm |
| I had a very similar situation years ago with my POS app. I moved from
MS-DOS 6.2 running PowerLAN (and Later Lantastic) to Win98. I was
using an old early Menu program written by ACR. I have three
programs:1. POS Register program, 2. End-of-day Closeout and 3. Update
Price files. I just bit the bullet and created three windows shortcuts
and placed them on the left side of the screen. The users had a little
trouble learning to use the mouse but it ended up being a solid
solution. Later on I integrated all three prgs into the register
program.
One major issue I had to deal with in Windows was the program sometimes
got minimized on the taskbar. The users would not see it and try to
execute it again which would cause errors. I ended up modifying the
errorsys to trap a logfile.dbf opened in exclusive mode to not allow
them to open more than move copy of the program at a time. Another
irritation was the users would sometime accidentally delete the
shortcut or even rename them.
Except for a few problems like those...It works pretty well.
However, I'm about 80 percent complete with a rewrite using Xharbour.
It makes converting to a Touch Screen app. very simple.
Good Luck.
LHSoft@gmail.com wrote:
> Scott,
>
> I'm not sure if I still get your problem correct., Sounds like the
> system runs a bunch of different EXE files from the menu. If that's the
> case, have a look at www.magee.com their automenu system will still
> work in a windows dos-box.
>
> The only other alternative I see (maybe I still don't understand your
> problem) is to try to analyze the program and compile all those EXE's
> into one exe using Clipper's native MENU commands. It might be that you
> also need to switch linker from Plink to Blinker, to make it fit into
> the dos memory of 640kb. If you have all the source, and there is no
> extremely fancy lib's involved, it shouln't be that hard to make the
> changes.
>
> Regards,
>
> Lasse
| |
| pete@nospam.demon.co.uk 2005-09-15, 3:55 am |
| In article <dg9rj9$rau$02$1@news.t-online.com>
AUGE_OHR_NOSPAM_@CSI.COM "AUGE_OHR" writes:
[..]
>
> use PROMPT / MENU TO :
I was wondering when somebody was going to suggest the obvious
starting point <g>
[..]
> have a look at your Windows System Monitor. you will see that 16-bit DOS
> application like Cl*pper S87 will take 100% CPU ...
Go to The Oasis and look for "nice"; this is a tiny TSR I wrote a
few years ago to overcome this very problem. It monitors
keyboard polling and releases a time slice to W9x and CPU usage
drops to 2-3%
Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."
| |
|
| "Scott Coffey" <none@noemail.com> wrote in message
news:4rqgi156hns7l83ujpba8a3pq252lfqfbk@
4ax.com...
> On Wed, 14 Sep 2005 00:23:40 +0200, "AUGE_OHR"
> <AUGE_OHR_NOSPAM_@CSI.COM> wrote:
>
>
> It's a menu system written long ago by IBM. It allows you to create a
> menu system by "filling in the blanks" so to speak. You can have a
> menu option perform DOS command, including calling other programs
> (like Clipper programs).
>
>
> No. Win98 is the host OS for a Clipper based POS system. To start
> the system you click in icon on the Window 98 desktop which then opens
> a full screen DOS box and then loads the FDO menu system.
>
> I'm surprised you've never heard of it. A Google search would only
> turn up references from the Y2K patch provided a few years back, but
> here's a blurb from one of the patch providers:
>
> "Although it is a rather old-fashioned application, I still consider
> IBM's Fixed Disk Organizer (FDO) one of the easiest to use and most
> elegant menu programs. Even when using Windows or a different OS, I
> still make a DOS startup with FDO for old games and applications.
> Maybe there are other users who think likewise and want to continue
> using FDO."
>
> I'm not finding it very "elegant" though. <g>
what is the internal structure of your fdo?
how are you starting your menu system?
is your fdo monolithic [app + data] file?
is there main app [fdo.exe or fdo.com] running separate menu definition data
file?
is menu definition file simple text file describing items and hierarchy, or
is some pre-compiled binary coded file?
do you need fdo tools to create menus, or you may use any external [text]
editor?
anyway, you could very easily replace a fdo with pure batch file [.bat],
containing a series of "choice" and "goto" dos statements.
using norton's "be.exe" [batch enhancer], you may have the same result, but
additionaly having drawn real colored menu frames on screen.
| |
| Scott Coffey 2005-09-15, 6:55 pm |
| On 14 Sep 2005 17:04:10 -0700, "J. Webb" <webbsoft2@hotmail.com>
wrote:
>I had a very similar situation years ago with my POS app. I moved from
>MS-DOS 6.2 running PowerLAN (and Later Lantastic) to Win98. I was
>using an old early Menu program written by ACR. I have three
>programs:1. POS Register program, 2. End-of-day Closeout and 3. Update
>Price files. I just bit the bullet and created three windows shortcuts
>and placed them on the left side of the screen. The users had a little
>trouble learning to use the mouse but it ended up being a solid
>solution. Later on I integrated all three prgs into the register
>program.
Problem is, I currently have 27 different menu items that are active
and of course more could be added in the future so Windows shortcuts
aren't really an option.
| |
| Scott Coffey 2005-09-15, 6:55 pm |
| On Wed, 14 Sep 2005 20:53:21 +0200, "AUGE_OHR"
<AUGE_OHR_NOSPAM_@CSI.COM> wrote:
>hi,
>
>next try :
>
>
>did you test test it ? are you using a Lib for S87 to "control" COM Ports ?
>how do you want to get DSL to COM(1-8) ?
Yes, everything is working fine except for the occasional crash of the
FDO menu program.
>
>FDO is only a BATch menu system to run one of the menuitem.
>you have to look inside how it calls the Cl*pper Programm. ( can be
>parameters or different Application )
>
>
>use PROMPT / MENU TO :
>
>PROCEDURE MAINMENU
>PRIVAT nChoice := 2 // S87 do not have LOCAL
> SET WRAP ON
> SET MESSAGE TO 23 CENTER
> @ 6, 10 PROMPT "Add" MESSAGE "New Acct"
> @ 7, 10 PROMPT "Edit" MESSAGE "Change Acct"
> @ 9, 10 PROMPT "Quit" MESSAGE "Return to DOS"
> MENU TO nChoice
> //
> DO CASE
> CASE nChoice = 0
> QUIT
> CASE nChoice = 1
> NewAccount()
> CASE nChoice = 2
> ChangeAccount()
> CASE nChoice = 3
> QUIT
> ENDCASE
>RETURN
OK, now were getting to the meat of this thing. Are you suggesting
that I write the menus myself? I realized from the start that this
was an option but:
1. I'm a novice Clipper programmer, so writing it from scratch might
take more time than I would be comfortable with, from a billing
standpoint.
2. I hate to reinvent the wheel. I just assumed that someone had
written a "fill in the blanks" menu system for Clipper programs.
Of course it might be so trivial to do menus (I've never tried) that
no one bothered to write a utility. That's why I'm hoping the Clipper
experts could advise me.
>
>have a look at your Windows System Monitor. you will see that 16-bit DOS
>application like Cl*pper S87 will take 100% CPU ...
>
>it is time to recompile you S87 Source with a 32-bit compiler/linker to use
>it
>in a "multitasking / multiuser" environment.
I agree Jimmy, but first things first. I'm in the "if it ain't broke
don't fix it" mode for now.
| |
| Scott Coffey 2005-09-15, 6:55 pm |
| On Thu, 15 Sep 2005 05:48:56 +0000 (UTC), pete@nospam.demon.co.uk
wrote:
>In article <dg9rj9$rau$02$1@news.t-online.com>
> AUGE_OHR_NOSPAM_@CSI.COM "AUGE_OHR" writes:
>[..]
>
>I was wondering when somebody was going to suggest the obvious
>starting point <g>
Hi Pete.
So is this what I should be doing? Should I write the menus myself? I
just assumed that something as common as menus would be addressed by
some pre-written utility. Since I'm an RPG programmer for the IBM
midrange platform, I'm used to having menu systems available to me
where there is a standard menu layout and I simply fill in the blanks
to get menu item descriptions along with the associated programs that
are called when the option is taken. The FDO utility was very similar
in concept.
Scott
| |
| Scott Coffey 2005-09-15, 6:55 pm |
| On 14 Sep 2005 12:46:32 -0700, LHSoft@gmail.com wrote:
>Scott,
>
>I'm not sure if I still get your problem correct., Sounds like the
>system runs a bunch of different EXE files from the menu. If that's the
>case, have a look at www.magee.com their automenu system will still
>work in a windows dos-box.
>
>The only other alternative I see (maybe I still don't understand your
>problem) is to try to analyze the program and compile all those EXE's
>into one exe using Clipper's native MENU commands. It might be that you
>also need to switch linker from Plink to Blinker, to make it fit into
>the dos memory of 640kb. If you have all the source, and there is no
>extremely fancy lib's involved, it shouln't be that hard to make the
>changes.
>
>Regards,
>
>Lasse
Thanks for the link Lasse. That product looks very promising and I've
sent an e-mail to them to see if they have a demo I could try.
Scott
| |
|
| "Scott Coffey" <none@noemail.com> wrote in message
news:8o1ji1pr5ikfphlherl31ru6kj76jr7rku@
4ax.com...
> On 14 Sep 2005 17:04:10 -0700, "J. Webb" <webbsoft2@hotmail.com>
> wrote:
>
>
> Problem is, I currently have 27 different menu items that are active
> and of course more could be added in the future so Windows shortcuts
> aren't really an option.
if the quantity is the only thing making you problem on win menu system, it
is easy [win98 example]:
you may make menu *tree* not just a *bunch* of shortcuts.
on folder \windows, there is folder "start menu"
this "start menu" folder may contain .lnk files, or other subfolders.
investigate it, each subfolder will represent another menu subtree, without
any limit in nesting deep.
so, you may very easily represnt you fdo menu with windows menu system, just
having folders for tree and .lnk files for action items, representing "real"
shortcuts.
| |
| pete@nospam.demon.co.uk 2005-09-16, 3:55 am |
| In article <qa2ji1lo9e11o5plrra9qaupjv2i414122@4ax.com>
none@noemail.com "Scott Coffey" writes:
> Hi Pete.
>
> So is this what I should be doing? Should I write the menus myself?
Hi Scott,
That is where I would start -- it doesn't really take that much
effort to set up a few "@ y,x PROMPT 'blah blah'" entries, a
"MENU TO var" and a CASE block. It's adequate unless you need to
do some background task(s) concurrently -- e.g. to default to a
particular choice after a defined timeout.
> I just assumed that something as common as menus would be addressed by
> some pre-written utility. Since I'm an RPG programmer for the IBM
> midrange platform, I'm used to having menu systems available to me
> where there is a standard menu layout and I simply fill in the blanks
> to get menu item descriptions along with the associated programs that
> are called when the option is taken. The FDO utility was very similar
> in concept.
>
> Scott
There might be a menu generator program at The Oasis that someome
has written -- I've never looked. Maybe someone else knows?
Cheers,
Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."
| |
| Scott Coffey 2005-09-16, 6:55 pm |
| On Thu, 15 Sep 2005 17:12:57 +0200, "sali" <sali@euroherc.hr> wrote:
>"Scott Coffey" <none@noemail.com> wrote in message
> news:8o1ji1pr5ikfphlherl31ru6kj76jr7rku@
4ax.com...
>
>if the quantity is the only thing making you problem on win menu system, it
>is easy [win98 example]:
>you may make menu *tree* not just a *bunch* of shortcuts.
>on folder \windows, there is folder "start menu"
>this "start menu" folder may contain .lnk files, or other subfolders.
>investigate it, each subfolder will represent another menu subtree, without
>any limit in nesting deep.
>so, you may very easily represnt you fdo menu with windows menu system, just
>having folders for tree and .lnk files for action items, representing "real"
>shortcuts.
Wow. This was one of those "can't see the forest for the trees" kind
of things. Of *course* I can use the Windows menu system.
This customer is very conservative and doesn't like the idea of his
employees (store clerks) "playing around" in Windows, so the concept
of using a pure DOS menu system and simply staying in that system
until time to turn off their computer for the day was appealing to
him. But since returning to Windows was always very easy (it was just
another menu option) and because they have now been under the Windows
OS for six months with no major catastrophes, I think I can sell the
concept of having all of their POS functions as simple Windows Start
Menu shortcuts.
Thanks sali. It was obvious but I needed someone to rub my face in
it. <g>
BTW, I spent about 30 minutes converting the first couple of menus and
it looks great.
| |
|
|
Scott Coffey;
[color=darkred]
Although this would be a good solution, from the age of the programs I fear
you may run into lots of public and private variables that could be a real
nightmare when all the applications are combined into one. I would say there
is a high probability that this is going to happen.
Regards,
James
| |
| tom knauf 2005-09-19, 6:55 pm |
| Hi,
we use WINU from www.bardon.com. You just have to enter the calls ("xxx.bat,
yyy.exe") your old menusystem does.
A good "designer" is included. There is an accesscontrol (its main
purpose), timeouts, ....
We put 25 old clipper programs in a menu tree like this.
Yes its for windows 9x.
HTH
Tom
"Scott Coffey" <none@noemail.com> schrieb im Newsbeitrag
news:fg4bi1t05l4jg7apod5s9gvqvqj6ht8ff3@
4ax.com...
>
> I have a client running Summer '87 code in a POS application. They
> are using IBM's old FDO product (Fixed Disk Organizer) as their menu
> system.
>
> Since I moved them out of the DOS environment and into Windows (98 SE)
> the FDO application will sometimes crash. This happens when they
> minimize the FDO application and do some processing under Windows and
> then restore the application. It's not a show stopper, but it is a
> PITA.
>
> What is a good replacement for the FDO menu system? I'm not a great
> Clipper programmer but I am able to maintain their code, so writing
> one from scratch would be an option although I'm thinking that a
> decent menu system should exist out there somewhere. A small memory
> footprint would be a plus. Any suggestions?
>
> Thanks,
> Scott
| |
| Scott Coffey 2005-09-20, 6:55 pm |
| On Mon, 19 Sep 2005 17:58:17 +0200, "tom knauf" <hbgmail@pdtgmbh.de>
wrote:
>Hi,
>
>we use WINU from www.bardon.com. You just have to enter the calls ("xxx.bat,
>yyy.exe") your old menusystem does.
>A good "designer" is included. There is an accesscontrol (its main
>purpose), timeouts, ....
>
>We put 25 old clipper programs in a menu tree like this.
>Yes its for windows 9x.
>
>
>HTH
>Tom
That looks promising Tom. Thanks for the reply.
|
|
|
|
|