Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!ucla-cs!zen!ucbvax!hplabs!hp-pcd!uoregon!jessen From: jessen@uoregon.UUCP (Bob) Newsgroups: comp.sys.mac Subject: Info desired on mac interface generators... Message-ID: <364@uoregon.UUCP> Date: Sat, 1-Aug-87 19:47:11 EDT Article-I.D.: uoregon.364 Posted: Sat Aug 1 19:47:11 1987 Date-Received: Sun, 2-Aug-87 11:06:13 EDT Reply-To: jessen@uoregon.UUCP (Bob) Distribution: na Organization: University of Oregon, Computer Science, Eugene OR Lines: 29 I too am interested in finding information about MacExpress, MacApp, and any other extended programming environments for Mac Software development.(in reference to George Lippert's posting). I am especially interested in the following with respect to these sort of products: i) How does a developer "edit" or create a given interface. (i.e. do you edit graphically, textually, or by some other means..I know that some system gives you a typical Mac-style interface and then you express how yours differs from this prototypical interface. How are these differences expressed and what are the alternative approaches?) ii) What kind of code these products produce (do they produce, for example, Lightspeed C code to be included in your project or do they generate target machine code) iii) How does a programmer tie in the functionality of the software into the generated interface. (i.e. what is the interface between the interface and the code produced by the programmer) iv) What elements of a Mac interface do they assist you with? Do they handle things like menus,windows,alert boxes, dialog boxes, etc.? v) are they built around any existing programming environment (such as Lightspeed C) or are they stand-alone products that interface with other products. Any information provided along these lines would be greatly appreciated. I am especially interested in hearing from users of these products. How have these products helped you and where do you see pitfalls in them.