Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!gatech!udel!haven!uflorida!serc.cis.ufl.edu!mfi From: mfi@serc.cis.ufl.edu (Mark Interrante) Newsgroups: comp.sys.next Subject: Re: call for built in IB documenter Message-ID: <27533@uflorida.cis.ufl.EDU> Date: 20 Mar 91 19:26:01 GMT References: <68871@brunix.UUCP> <69158@brunix.UUCP> <1991Mar20.165430.2364@data.com> Sender: news@uflorida.cis.ufl.EDU Reply-To: mfi@serc.cis.ufl.edu (Mark Interrante) Organization: UF CIS Department Lines: 35 In article cnh5730@maraba.tamu.edu writes: >In article <1991Mar20.165430.2364@data.com> smb@data.com (Steven M. Boker) writes: > Those at NeXT who > are reading this should take note. Implementing Ronalds idea would > be a boon to the more-than-casual developer. > >Why not write an IBdocument.app and implement Ronald's idea your self? >Your app could interface with IB seamlessly if you implement the app using >NeXT's "services" paradigm. I am more interested in what other developers think should be included in upcoming versions of IB. It seems that additional interface/data structure classes can be easily incorporated into IB so that is no longer an issue for IB-only development. Possible areas: 1. configuration support tools (multiuser) 2. an integrated graphical compiler/debugging tools. (ala mac/PC tools) of course this need not be part of IB per se. 3. I would like the ability to double click on just about anything in IB and have it open up or at least have an inspector popup. 4. ? This is one tool that NeXT has the lead in, what do others want included to help maintain that lead? ----------------------------------------------------------------------------- mark Interrante Software Engineering Research Center mfi@beach.cis.ufl.edu CIS Department, University of Florida 32611 ----------------------------------------------------------------------------- Quote from a west Texas farmer "status quo is Latin for the mess we're in."