|
|
Are you trying to migrate an OS/2 application to Windows ?
|
Porting software from one platform to another is like translating from German to French. You have to know both the original, to understand what it is trying to accomplish, and you
have to know how to express that in terms of the target.
If your OS/2 application has been coded to the native platform interfaces, you're talking about a lot of work. If you still have the original programmers available, think about how
much time it will take to retrain them on Windows. Typical Windows training courses will tell them how to call an API, how to set up a Graphics Device Context. They know all that.
They just need somebody to help them map that knowledge to a different set of API's. Sure, they can do that on their own - they're no idiots, are they ? But it might just be more
cost-effective to hire somebody to get them up to speed fast.
Even if your OS/2 application has been coded using the Open Class Library (OCL) that comes with IBM's VisualAge for OS/2 V3.x, you will have some "native" code in there.
Important pieces are missing from OCL: file handling, printing, threads, semaphores ... Typically, this platform-dependent code will represent only a small portion of your code, but
it could be where you spend the most time - unless you get somebody to come in, do the conversion, and move out again. With the hard work done, your people can go from there.
In just about every case, this formula is much more cost-effective.
Of course, given all the above, it should come as no surprise that we are able to handle the entire conversion for you, for example if you had the original application developed for you by outside contractors.
|
