Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!olivea!apple!fernwood!portal!cup.portal.com!Lee_Robert_Willis From: Lee_Robert_Willis@cup.portal.com Newsgroups: comp.sys.amiga.programmer Subject: Re: HYPER FUNCTIONALITY Message-ID: <41791@cup.portal.com> Date: 28 Apr 91 22:12:11 GMT References: <1991Apr25.073105.23324@agate.berkeley.edu> <1991Apr28.010519.14364@zorch.SF-Bay.ORG> Organization: The Portal System (TM) Lines: 37 I w >re: Hyper-functionality - > >I remember reading a SIGGRAPH article a few years back which >discussed writing applications as two cooperating co-programs: >a user-interface (client); and a 'nuts-and-bolts' (server) program. ... >If this paradigm (good word) was followed, and if software publishers >were sufficently motivated, they could include in the purchase package >the source code for the GUI program, and a programmers guide on >how to interface to the server. > >This allows owners to rewrite the GUI (how many times have >you wanted to do that?) without threatening the author's >profit margin. (He hasn't given away any secrets, since >all the good stuff is safely tucked away in the 'nuts-and-bolts'. > >And with the server interface fully documented, other parties >can build on to this application to write composite applications. > >(It's not dynamic linking, but I think its do-able with a lot >less fuss.) On second thought, all of the above could be accomplished without 'cooperating coprograms' simply by moving all the 'nuts and bolts' into a library. It's even more a lot less fuss. I really like this concept. It's implementable with current Amiga technology, doesn't require any new standards be written, and allows the purchaser of a software package to fully utilize the power of the package. (Assuming he can program) Lee Lee_Robert_Willis@cup.portal.com