From owner-freebsd-hackers  Mon Sep 16 20:50:38 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA05101
          for hackers-outgoing; Mon, 16 Sep 1996 20:50:38 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA05096
          for <hackers@freebsd.org>; Mon, 16 Sep 1996 20:50:32 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id UAA02458; Mon, 16 Sep 1996 20:50:29 -0700 (PDT)
To: "Sean J. Schluntz" <schluntz@gromit.pinpt.com>
cc: hackers@freebsd.org
Subject: Re: Question on Porting Windows software to X 
In-reply-to: Your message of "Mon, 16 Sep 1996 09:33:42 PDT."
             <2.2.32.19960916163342.0091e7c8@wallace.pinpt.com> 
Date: Mon, 16 Sep 1996 20:50:29 -0700
Message-ID: <2456.842932229@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Looking at a larger word processing application for windows (16bit not 32)
> like Word 6, WordPerfict 6 or WordStar.  What do would you all think the
> difficulty level and approximate time would be required to port this app to
> X if you had the full sources for the orriginal application.

Well, having done that exact thing for Lotus's AmiPro word processor,
I can say that it's hard.  Even harder if the codebase in question is
a legacy from some pure-windows shop.  Were that the case, you'd almost
certainly want to use a transition tool like Willows or Wind/U.  That might
at least hold X at arm's length while you grappled with the OS dependant bits.

						Jordan