Board index » cppbuilder » Migrating from a Dos app

Migrating from a Dos app


2004-01-06 11:38:21 PM
cppbuilder41
I have an old Dos app written in Borland C++ 3.1.
I really need to update this app to a windows app. The app does not have a
lot of visual user interface but instead has a lot of detailed file
manipulation under the covers.
I am trying to determine the best way to migrate this app to a windows app.
One of my problems is that in recent years the majority (90 %)of my
development has been in Delphi but to rewrite all the code in Delphi would
be a major effort.
Can someone give me an idea of the level of effort involved in updating a
Dos app written with Borland C++ version 3.1 to a Windows app using the
latest Borland C++ (version ???).
Any advice?
Any white papers / articles?
Thanks for any help, Joe
 
 

Re:Migrating from a Dos app

Hi Joe:
Assuming that you are not accesing directly to the hardware (that's illegal
in Win32) you can select between
several frameworks that will help you. The runner-ends are:
- (Borland C++ 5.x | Borland C++ 5.5 | Visual C++ | Gcc ) + OWL/OWLNext: OWL
it's great!, also OWLNext includes the latest development (like support for
Linux). However Borland has abandoned OWL in favor of VCL but OWL community
still work on this frameworks. It's easy to learn and Borland C++5.x can
be purchased in ebay, and other sites for $100 bucks (80 euros, go Bush, go,
keep spending all my savings!!!).
- Borland C++ Builder + VCL: The BEST RAD around, but will be discountinued
in favor of wxWindow, which address the multiplataform development. .NET
(the new framework proposed by MS) it's 'inspired' in VCL (since VCL
creators now work for MS).
- ( Borland C++ 5.5 | Visual C++ | Gcc |Intel C++) + wxWindows: The
wxWindows frameworks it's stable, and mature. It allow to develop app. for
multiple
plataforms. The new CBX includes wxWindows as prefered framework (but also
support others). It will be a very good choice when Borland launches CBX2
and includes a RAD for it (in few months).
- Visual C++ + MFC: MFC it's more poor that OWL, but users base it's large.
MFC 1.0 for DOS its abandoned, MFC 2.0 for 16 bits its abandoned, MFC x.x
(dont remember current version) for Win32 its currently working but will be
abandoned in favor of .NET framework.
My recomendations : OWLNext or wxWindows (when fully usuable).
Saludos
Sebastian
----- Original Message -----
From: "Joe Pettit" < XXXX@XXXXX.COM >
Newsgroups: borland.public.cpp.borlandcpp
Sent: Tuesday, January 06, 2004 12:38 PM
Subject: Migrating from a Dos app
Quote
I have an old Dos app written in Borland C++ 3.1.
I really need to update this app to a windows app. The app does not have
a
lot of visual user interface but instead has a lot of detailed file
manipulation under the covers.

I am trying to determine the best way to migrate this app to a windows
app.
One of my problems is that in recent years the majority (90 %)of my
development has been in Delphi but to rewrite all the code in Delphi would
be a major effort.

Can someone give me an idea of the level of effort involved in updating a
Dos app written with Borland C++ version 3.1 to a Windows app using the
latest Borland C++ (version ???).
Any advice?
Any white papers / articles?

Thanks for any help, Joe


 

Re:Migrating from a Dos app

Hi Joe,
I have written an application generator that allows developers to
build applications for in just a fraction of the time it used to take.
The generator has two major parts: A UI generator which is written in
Delphi and produces Delphi forms that work in a Delphi framework that
makes all the forms work together.
The second part of the system is a backend generator for MS SQL
Server.
It occurs to me that you may wish to leverage you knowledge of Delphi
while at the same time use a tool that does virtually all the work for
you.
In order to demonstrate the my generator to developers, I am issuing a
promotion:
The Promotion will cost you nothing. All you have to do is send me the
T-SQL scripts necessary to create your tables and to define the
indexes and foreign key relationships or I can create them for you
from what ever information you have. My generator will do the job, and
I will deliver the finished and fully functional UI.exe along with a
finished and fully functional SQL Server back end which contains a
robust security system and a comprehensive data dictionary, completely
free of charge.
The benefits of this system are as follows:
1. The system generates true Client Server and Multi Tier
applications.
2. There is Zero Coding for common functionality such as;
Adds, Updates, and Deletes,
Creating application wide unique Ids for each record,
Maintaining an Audit trail for each table,
Posting to the general ledger,
Rolling down changes to dependent tables,
Cascading deletes,
Transactions and rollbacks,
Calling validation and business rule stored procedures,
Calling post processing stored procedures,
Importing and revalidating data,
Security,
Spell checking, language translation and more.
3. There is zero work of any kind for generation of data entry screens
and their lookups.
4. The back end is completely independent from the front end. You can
hit the database with any application or user interface and still be
sure that you have complete security and valid data.
5. Easy navigation through out the application. The generated user
interface is a familiar modern metaphor with a navigation tree on top
or at the side and data entry screens at the bottom. Also, the
generated user interface remembers customizations to each data entry
screen. This allows you to make sweeping changes to the interface, and
regenerate all data entry screens, without loosing your
customizations.
6. Consistent look and feel via OOP Inheritance and code generators.
7. Major changes in look and functionality are made in one place only,
and ripple down to all affected parts of the system without programmer
intervention. Again, this was accomplished with OOP inheritance and
also with code generators.
8. Users to have the ability to create queries and reports on the fly.
And the ability to save and reload those queries and reports in many
formats including Excel and HTML.
9. Users to have complete flexibility in customizing the look and feel
of the system. The extent to which each user can customize the
interface must be seen to be believed. This high level of
customizability creates a high degree of user acceptance.
10. Logical use of hot keys and local popup menus allow for easy mouse
free operation, permitting the user to keep his or her hands on the
keyboard, if the user so desires.
11. All custom code added to generated data entry screens and
generated backend code persists after regeneration.
12. Comes with a business rule generator
13. Comes with a data import utility
14. Comes with a data revalidation utility to use when you change your
business rules.
You get all this without programming.
Please let me know how I can help,
Best, John
XXXX@XXXXX.COM
 

{smallsort}

Re:Migrating from a Dos app

Joe Pettit wrote:
Quote
I have an old Dos app written in Borland C++ 3.1.
I really need to update this app to a windows app. The app does not have a
lot of visual user interface but instead has a lot of detailed file
manipulation under the covers.
The easiest is to make it a console app. Then it will look and work
just like the DOS app.
The biggest thing to watch for in migrating from DOS to Win32 is that
"int" becomes 32bits instead of 16, so any structures made with "int"
will be the wrong size.
Also, any MAKE_FP and "far" prefixes can be removed.
If you are looking to update the look (for "political" reasons) to
GUI, then you could use the Resource Workshop that came with 3.1 to
design your forms. The code to run a simple form isn't all that hard.
There are example Win programs that came with 3.1 that show the
basics. That part hasn't changed much over the years.
The free command line compiler will compile the old Resouce Workshop
file just fine, and your converted code will compile and link into a
32bit Win App (either console or GUI).
 

Re:Migrating from a Dos app

On Tue, 6 Jan 2004 10:38:21 -0500, "Joe Pettit" < XXXX@XXXXX.COM >
wrote:
Quote
I have an old Dos app written in Borland C++ 3.1.
I really need to update this app to a windows app. The app does not have a
lot of visual user interface but instead has a lot of detailed file
manipulation under the covers.

I am trying to determine the best way to migrate this app to a windows app.
One of my problems is that in recent years the majority (90 %)of my
development has been in Delphi but to rewrite all the code in Delphi would
be a major effort.

Can someone give me an idea of the level of effort involved in updating a
Dos app written with Borland C++ version 3.1 to a Windows app using the
latest Borland C++ (version ???).
Any advice?
Any white papers / articles?

Thanks for any help, Joe

If it is not too hard you could stick your file manipulation code in a
c/c++ dll and give it a c interface, then write a little Delphi
program to call it.
HTH,
Jeff
Jeff Kish