CompuServe Thread

#WPCorp & Amiga

12 messages in this thread
#47430From: May 8, 1989 2:42 PM
OK, things are looking up, the decision has been made. As of today (8 May 1989) WordPerfect Corporation will continue to do new development on WordPerfect for the Amiga. Three programmers will be working on both maintaining version 4.1 and Library, and additionally they will be working on a future version of WordPerfect. Due to these limited resources, development will procede at a slower pace. No attempt will be made to do a 6.0 product for the time being. However, features will be added to the current product to move it in that direction. Currently, the first priority is to complete the maintanence update of 4.1. This should take less than a month. Next, development will be done on the new version. The current plans are not complete, but here are some of the ideas: – 4.2 file format – Print preview – Sort – Document comments – ARexx support – Non-interactive spell checking – Better scroll bar support – Other 4.2 & 5.0 enhancements (dependant on demand & time) We can now move forward and get back to doing some real work on the Amiga. Please let me know of any opinions you have on the next version of WordPerfect. We have not totally ruled out graphics support, it is something we are considering, but with the limited resources it is hard to justify. We will, of course be looking at fixing the anomalies of 4.1 (scroll bars) along with adding the new features. // \X/ Lynn
#47479From: SyndesisMay 8, 1989 6:59 PM
It's important to remember that a lot of people online don't know what they're talking about. I think this applies to WPCorp in several ways. First, many people online have little or no understanding of the cost of support and development. WPCorp does, so don't apologize for your decision. Second, I don't think the apparent demand for WYSIWYG word processors applies to Word Perfect. (I can't understand why it's an issue with many other word processors, frankly.) I think maintenance of 4.2 would be fine. It's file compatibility with other PCs that really drives WP sales, I think. Don't bother developing 5.0 or 6.0 for us until they're solid on other machines. I think it's good that your Amiga programmers will be working with programmers for other machines. I think the "I (heart) Amiga" club types should view this as a plus, not a minus. They'll spread the word about what's good and bad with the Amiga, which certainly beats no press at all. Also, Commodore's PR about "units sold" is subject to interpretation. One million what? A500s with joysticks? Finally, your cutbacks in Amiga development will be an educational process for many Amigaheads – so there's still hope.
#47567From: May 9, 1989 10:45 AM
Syndesis, Thanks, I hope we're right. :-> // \X/ Lynn
#49562From: Stephen MacKenzieMay 21, 1989 1:24 AM
I'm very disappointed to learn WP won't do a full 5.0 release for Amiga. However, I'll continue to use WP where it makes the most sense, primarily in academic work requiring footnotes, indexes, table of contents, thesaurus, etc.–things no Desktop Publishing program supports. WP is the only word processor on the Amiga at present that does all this with full freedom of page formatting (i.e., intermixing multiple column formats on a page or in a document). I don't particularly care about picture support–I'm not using your program for artwork preparation. However, I do care about WYSIWYG (the reason WP was first invented), color, and font support. Here's why: 1) I use excellence! (another word processor) to prepare 35mm slides. With color and fonts, it's much faster than Aegis' Video Titler, and uses a fraction of the disk space. With color and font support, I could use WP instead. Yes, I would prefer a single program that does all the text things I want to do, instead of having to remember options from multiple programs. 2) For general writing, I set up a page that is one screen in size, two columns wide, and using a font I designed to get maximum information on a single screen. WP and TOPAZ-80 won't let me get as much data on screen at a time. That's important–otherwise we'd all still be using 40-column TV-format screens. I've put off purchasing a DTP program–I was hoping WP would come out with a version that would combine its excellent document features with fonts. Desktop publishing programs can make pretty output–but can they intersperse automatically-numbered footnotes at the bottom of each page and produce a correctly-numbered index and table of contents at the same time? I don't know of any. I'm going to miss having WP 5.0. I thought WP was dedicated enough to its product to make it work on EVERY machine, and I thought that Amiga passing the 1,000,000 production mark would insure we'd be included. I guess not, and I suspect WP will begin to lose market share as a result. Anyway, thanks for being honest with us.
#49636From: Ethan SolomitaMay 21, 1989 5:16 PM
Lynn, maybe you could use Amiga fonts for on-screen displays, not printouts, in order to create a WYSIWIG display. If someone selects 12 cpi instead of 10, switch to a smaller height font on screen. That shouldn't be too difficult. If you do do that, it should really be an option and not forced down peoples' throats. — Ethan
#49769From: May 22, 1989 5:21 PM
Stephen, We never said that we will not be doing WP 5.0 for the Amiga. What we said was 'we aren't doing 5.0 for the Amiga right now'. Besides, things are rarely ever completely set in cement until they actually happen (or not happen as the case may be). We're still talking about various options we have at this point. The one that is in cement is that the resources we have to do any project is somewhat limited. So, it is felt that moving slowly toward 5.0 by adding 4.2 features (and other things that don't require that major portions of WP be rewritten) is the best option (given the resource limitations), so that is what we are doing. I do appreciate your input, and like all that I've been receiving lately I am saving a copy of it. // \X/ Lynn
#50682From: RICH MEDVEDMay 27, 1989 1:54 PM
Lynn, one thing I'd really like to see is: When printing a program from within WP, have the print screen come up active. You don't know how amny times I've entered a 'g' in my document when trying to send a {G}o to the printer.
#51087From: Ethan SolomitaMay 29, 1989 5:53 PM
Seconded! When I press shift-F7, the window should be activated, at least the first time when its initially loaded. — Ethan
#51304From: RICH MEDVEDMay 31, 1989 1:16 AM
The strange thing is that I seem to remember one of the versions working that way. Is it just bad recall or did they change it around twice?
#51202From: May 30, 1989 12:26 PM
Rich, Problem is, most people don't want it to come up active. They want to be able to go on editing (or whatever) while the thing prints. I suppose we could add an option to have it come active everytime you send a print job (would that fill your needs?) // \X/ Lynn
#51305From: RICH MEDVEDMay 31, 1989 1:27 AM
You could make it part of the installation. However, you might check on that here. Seems that if a window opens in the front, and it's a new activity that you've purposely started, that you'd like that task to be active. At the store I manage, Computer Quest in WA, that that is a common objection. Let's see what the traffic here has to say, Lynn. Those of you that use your printer set for single sheet, do you prefer to have the print window open active, so all you have to do is hit the "G" key, or is it nicer the way it presently works? One other comment, Lynn. Presently, you need to grab the mouse whether you want to issue a {G}o OR continue editing, i.e. got to hit the "G" with the mouse or hit the depth gadget to get your doc window to the front. With an active Print window, you'd only need to track down the rodent to bring the doc window back to the front – for us single sheet users that'd mean only 2% of the time. BTW, I have customers looking for a bug fix to work with 1.3 since the first of the year – keeps slipping. Expected release date? Last I had was prior to the end of May.
#51344From: May 31, 1989 1:53 PM
Rich, Actually you don't have to "grab the mouse whether yo want to issue a {G}o OR continue editing". I have my WP doc windows open on the bottom of the screen (yes, interlace) so that when print comes up it's not in the way. Actually we didn't want the Print window to open up in front, but couldn't figure a legal way to prevent that (anyone else know how?). I prefer a solution with the maximum flexibility…which is why I proposed some kind of setup option (we could make it default your way if the vote goes that way). Another possibility would be to have print come active anytime it needs a "G" (although I'm opposed to this one, but it could be a Print setup option). I'm not aware of anything in the shipping version of WP that doesn't work with 1.3, but I may be wrong, please let me know what you're referring to. // \X/ Lynn