Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!apple!claris!wombat From: wombat@claris.com (Scott Lindsey) Newsgroups: comp.sys.apple Subject: Re: New Beagle Software... Keywords: Anglophobia, Freedman, robin, pantheism Message-ID: Date: 31 Dec 89 23:28:49 GMT References: <14341.chatter.infoapple@pro-beagle> Sender: wombat@claris.com Organization: Claris Corporation, Santa Clara, CA Lines: 44 In-reply-to: mmunz@pro-beagle.cts.COM's message of 19 Dec 89 06:25:27 GMT Subversive: Nancy Reagan In article <14341.chatter.infoapple@pro-beagle> mmunz@pro-beagle.cts.COM (Mark Munz) writes: > Yes, there are some problems still with the dictionaries. But I would > like to give you some of the inside scoop. When Beagle Bros got > MultiScribe, we got ourselves a mess. Sorry folks, Styleware didn't > do a good job keeping source code updated with object code and the like. StyleWare didn't do that lousy a job -- Claris did. Claris was never very interested in any of the StyleWare product line except for GSWorks. Clar didn't ask for source until all of the programmers and equipment had been moved to California, continuing development on AWGS. At that point, the StyleWare office had been thrown to the four winds. The source Beagle finally got was culled from various programmers' hard drives, and included a few post-production bug fixes. > We've been cleaning it up since we've got it and trying to fix problems > along the way. The dictionary problems and compatibility with AW 3.0 > are both on our list of things to work on. One thing I'm curious about, and I hope you don't consider this inappropriate for the public forum (switch to email if you do), is why Beagle took so long from accepting the source to the first complaint? If they'd tried a build immediately, they probably could've gotten more leverage in the deal/support from Claris on the deal. One thing I mentioned to some people in marketing at Claris was the possibility of letting Beagle get the AWGS spell checker code, as of version 1.1. It is based on the code used in MSGS and has been pounded on quite a bit since 1.0v2 (which hadn't changed since 1.0) I fixed bugs both in StyleWare's code and in Proximity's. The main practical problems would be that the source is in MPW, not APW and that there might be some interfacing problems going back to MSGS from AWGS. However, it's my belief that that would still be easier than what Beagle would have to do otherwise (or is it too late now?). > >From what I see, I don't think StyleWare would have ever updated > MultiScribe GS.. or maybe that's could never have? StyleWare could have, probably would have. Claris couldn't have, probably wouldn't have tried. Scott Lindsey |"Cold and misty morning. I heard a warning borne in the air Claris Corp. | About an age of power when no one had an hour to spare" ames!claris!wombat| DISCLAIMER: These are not the opinions of Claris, Apple, wombat@claris.com | StyleWare, the author, or anyone else living or Dead.