a95
Subj : Re: Migrating from a Dos app
To   : borland.public.cpp.borlandcpp
From : "Sebastian Ledesma" <labo(no_sp@m)solidyne1.com>
Date : Tue Jan 06 2004 02:35 pm

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" <joep@i-f-s.com>
Newsgroups: borland.public.cpp.borlandcpp
Sent: Tuesday, January 06, 2004 12:38 PM
Subject: Migrating from a Dos app


> 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
>
>

.

0