Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!bbn!rochester!ritcv!cci632!ccicpg!leo!harald From: harald@leo.UUCP ( Harald Milne) Newsgroups: comp.sys.amiga Subject: Re: Cloning a Mac Summary: Bravo! Keywords: Let's not thank you. Message-ID: <3051@leo.UUCP> Date: 12 May 88 08:50:29 GMT References: <52787@sun.uucp> Organization: CCI CPD (Advanced Development), Irvine CA Lines: 38 In article <52787@sun.uucp>, cmcmanis%pepper@Sun.COM (Chuck McManis) writes: > Several people have called for cloning certain aspects of the Macintosh > `paradigm' here and frankly I am a bit amused by it. So am I. > Rather than ask "How can we do this Mac thing on the Amiga?" ask instead > "How can we solve the problem that this Mac things solves better?" A > case in point is user interfaces. Yes! Yes! Isn't that why we are here? > Consider the following random thoughts ... > Some things you and I do to/with computers that could use this system ... > Want to edit a file? Kick a TextFile progenitor and it pops out a raw > text file Object. Drop the text file Object into an editor and change > its contents and properties (like it's name). Drop the Text File Object > on to the Compiler Object, if it understands the Text file (it has the > "C" property, although it could be a "Modula 2" property) it burps > out and Object Code object and maybe a TextFile errors object. Kick > the "NewObject" generator again and tell it has the property of an > executable. Now Drop that object, the ObjectCode Objects, and some > LibraryObjects into a LinkObject. It burps out a the ExecutableObject > again but now it does something useful. Even better, recognize the file type, ala the BSD file command. Handle all aspects of this type as appropriate. Remove all notions of compilers, linkers and such drudgery. This is the object, do what is supposed to be done! Oooh. I like it! Object oriented OS! -- Work: Computer Consoles Inc. (CCI), Advanced Development Group (ADG) Irvine, CA (RISCy business!) UUCP: uunet!ccicpg!leo!harald