Qt-interest Archive, June 2007
Re: MFC migration
Message 1 in thread
> Given this situation, how would you suggest I approach the migration? I
You have to rewrite everything from the beginning. Mfc is not really a
Gui-programming-library, but a "I want to, but I can't"...
These SendMessages are probably a Signal/Slot mission... repaint the dialogs
with the designer, re-use all algorithms, if possible. 1,5 Mios lines are not
that much I think. Not if it is created with a "wizard" ;-)
--
[ signature omitted ]
Message 2 in thread
Hi,
maybe the MFC migration solution of Trolltech could be interesting
for you - see:
http://trolltech.com/products/qt/addon/solutions/catalog/4/Windows/qtwinmigrate/
Best Regards,
Christian
--
[ signature omitted ]
Message 3 in thread
The first question is whether you should migrate the code at all.
It may be more cost effective to hack the existing system rather than
replace it.
How much time, money and talent do you have available? What's wrong with
the existing system and its development environment? How bad is it? What
'brick walls' are you up against? Are there any components that can be
salvaged? How has the system's environment changed since it was built:
the development environment, developers and system administration staff,
the system's server and client operating systems, the hardware and
networks it runs on, the people that use it, and so on? As well as
taking over management of the system, will you need to add new
functionality, remove functionality, change the GUI, change workflow,
change developers and/or integrate with new systems or users?
There's lots of discussion of software migration in books like The
Mythical Man Month and Refactoring (Martin Fowler). The bottom line is
that a lot of the investment in any system (and pretty much all its
asset value) is in its algorithms, interfaces and workflows -- rather
than the code itself.
Having said that -- if you do write a new version of the system, make
sure you first do a completely new requirements analysis (or 'planning
game' or whatever you call it) and work backwards from that.
Do NOT (necessarily) accept existing ways of working, either for the
system or its developers.
Good luck!
Sam Dutton
SAM DUTTON
SENIOR SITE DEVELOPER
200 GRAY'S INN ROAD
LONDON
WC1X 8XZ
UNITED KINGDOM
T +44 (0)20 7430 4496
F
E SAM.DUTTON@xxxxxxxxx
WWW.ITN.CO.UK
________________________________
From: Shawn Badger [mailto:shawnbadger@xxxxxxxxx]
Sent: Thursday 31 May 2007 17:51
To: qt-interest@xxxxxxxxxxxxx
Subject: MFC migration
I recently discovered the glorious Qt library, and just want to say how
much I enjoy using it.
I started work on a fairly large commercial project recently (approx.
1.5 million lines of code) which is, to my misfortune, written in MFC.
I want to migrate it over to Qt, but I'm a little nervous because the
code is not organized very well. In fact, it's really bad - cluttered
with SendMessage calls, and many other poor quality design decisions;
very little modularity.
Given this situation, how would you suggest I approach the migration? I
was reading about the migration library, and I'm thinking that it won't
help me too much because we don't have many windows that don't depend on
some SendMessage from somewhere.
Any suggestions? Has anyone been through a similar experience?
Thanks,
Shawn
Please Note:
Any views or opinions are solely those of the author and do not necessarily represent
those of Independent Television News Limited unless specifically stated.
This email and any files attached are confidential and intended solely for the use of the individual
or entity to which they are addressed.
If you have received this email in error, please notify postmaster@xxxxxxxxx
Please note that to ensure regulatory compliance and for the protection of our clients and business,
we may monitor and read messages sent to and from our systems.
Thank You.
