home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.windows.x:15689 comp.windows.x.motif:5849
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!swrinde!ctcvax.ccf.swri.edu!trident!mark
- From: mark@trident.datasys.swri.edu (Mark D. Collier)
- Newsgroups: comp.windows.x,comp.windows.x.motif
- Subject: Using GUI builders (TeleUse in particular)
- Message-ID: <121@trident.datasys.swri.edu>
- Date: 26 Aug 92 22:00:27 GMT
- Followup-To: comp.windows.x
- Organization: Southwest Research Institute, San Antonio, Texas
- Lines: 29
-
- I am planning to develop a very sophisticated, highly interactive
- Motif application. I have been using X/Motif for several years and
- have been using internal tools to simplify user interface develop-
- ment. For this new project, I am being strongly encouraged to use
- TeleUse. My questions are:
-
- 1) How well do these GUI builders really work in terms of
- developing a non-prototype product?
-
- 2) Can I really divide the user interface, application code,
- and yet make them talk together in an elegant fashion?
-
- 3) How is TeleUse as compared to other GUI builders. Does
- its billing as a UIMS (as opposed to a VDT) really mean
- anything?
-
- 4) Would you use TeleUse to develop TeleUse? My application
- is a display/GUI builder which focuses on output-driven
- COTS/custom widget (like DataViews, SAMMI, SL-GMS, etc).
-
- All opinions are welcome and encouraged. If I get enough input I
- will summarize the responses.
-
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Mark D. Collier Southwest Research Institute
- Senior Research Analyst Automation and Data Systems Division
- Voice: (512) 522-3437 Data Systems Department
- FAX: (512) 522-5499 Software Engineering Section
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-