alan@cogswell.Jpl.Nasa.Gov (Alan S. Mazer) (08/16/90)
In article <4119@trantor.harris-atd.com>, chuck@trantor.harris-atd.com (Chuck Musciano) writes: [examples of sophisticated GUIDE applications deleted] > In a recent post to the OPEN LOOK mailing list, someone was trying to > get two canvases to align in a certain way in a window. He had obviously > worked at this for some time, and then took the time to post and wait for > a reply. If he had used GUIDE, the problem would have been solved in under > ten seconds or so. That's the power of GUIDE. (Yes, I'm back. I have this compulsion to present the other side.) More scenarios. A programmer here was trying to write an application where as the user traversed a walking menu the program would pass information to another process, and then use the results of that process to create lower levels of the menu tree. They learned GUIDE (not a trivial task) and then tried for days to get this thing working. Then because I had been using SunView for years and XView for a while too, we worked on it together. We never got it. Since the basic purpose of the project was to evaluate GUIDE, we never got around to implementing it directly in XView. But I don't think we would have had a problem. If you want to do basic things and not waste time on layout and such, and if you have the time to learn GUIDE, GUIDE should be terrific. But if you want to do something weird, it seems better to do it at the lower level and not take the time to learn GUIDE and then have to work around it. Another person here just wanted to create a simple demo program. Something like a panel with button and a canvas. They decided to use GUIDE, too. They eventually called up with a question which showed that for what they were trying to do things were getting much too complicated. Turned out the non- GUIDE code to do what they wanted was about 10 lines and very simple. They could have learned to do what GUIDE did using vanilla XView in much less time. Clearly some people are getting great results from GUIDE, and for a product in its first release, that says a lot for Sun. But it doesn't seem to fit well into all application areas. -- Alan # My aptitude test in high school suggested that ..!ames!elroy!alan # I should become a forest ranger. Take my alan@elroy.jpl.nasa.gov # opinions on computers with a grain of salt.
chiu@efi.com (Chan Chiu) (09/06/90)
Does anyone know if Guide also works with sunview ? I know it works with XView. /CC
fgreco@govt.shearson.COM (Frank Greco) (09/06/90)
>Does anyone know if Guide also works with sunview ?
Guide is built with XView code, as mentioned in the MIT X Conference last year,
so the answer is.....no.emike@cpg.trs.reuter.com (E. Mike Durbin) (09/12/90)
In article <9009061417.AA02660@islanders.>, fgreco@govt.shearson.COM (Frank Greco) writes: |> >Does anyone know if Guide also works with sunview ? |> |> Guide is built with XView code, as mentioned in the MIT X Conference last year, |> so the answer is.....no. Actually, the Beta version of Developer's Guide came with gxv (guide to XView), gnt (guide to NtN) and gsv (guide to Sun View). The GUIDE INTERFACE LANGUAGE is independent of any windowing system. However, because Sun wants everyone to convert to XView, the gsv part never got out. The answer is it could (you could write a gsv, how about a g2motif), but it dosn't -------------- E. Mike Durbin Rich/Reuters Trading Room Systems emike@cpg.trs.reuter.com or uunet!richsun!emike
watson@spot.Eng.Sun.COM (Robert Watson) (09/19/90)
In article <998@richsun.cpg.trs.reuter.com> emike@cpg.trs.reuter.com (E. Mike Durbin) writes: >Actually, the Beta version of Developer's Guide came with gxv (guide to >XView), gnt >(guide to NtN) and gsv (guide to Sun View). The GUIDE INTERFACE >LANGUAGE is independent >of any windowing system. This is true. >However, because Sun wants everyone to convert to XView, the >gsv part never got out. While what you say is true, it's not quite that straight forward. Gsv was developed at a time when Sun was considering making the Openlook version of Sunview(SOL) available to developers. Because of cost considerations it was decided to throw the eggs into the XView basket, this has resulted in the vast improvements you may have seen in Openwindows Version2. As gsv produced SOL code not regular Sunview we cancelled the project. >The answer is it could (you could write a gsv, how about a g2motif), but >it dosn't We are developing code generators for our OpenLook toolkits, I seriously doubt that you'll be seeing a g2motif from here :-) Robert Watson Mananger, OpenWindows Developer's Guide Sun Microsystems. Mountain View, CA.
cflatter@ZIA.AOC.NRAO.EDU (Chris Flatters) (09/19/90)
>>The answer is it could (you could write a gsv, how about a g2motif), but >>it dosn't > >We are developing code generators for our OpenLook toolkits, I >seriously doubt that you'll be seeing a g2motif from here :-) It is probably worth pointing out that dev/GUIDE deals with OPEN LOOK UI components. A UIMS capable of producing OSF/Motif code (even via an intermediate description language) would have to deal with Motif UI components, which are somewhat different. You would also need a different intermediate language (UIL?) to describe them. Chris Flatters