Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!mips!swrinde!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!cam-cl!news From: nbvs@cl.cam.ac.uk (Nicko van Someren) Newsgroups: comp.sys.acorn Subject: Re: invoking editors/draw/etc from other app.s Keywords: editors, RAMtransfer Message-ID: <1991Apr11.104904.15710@cl.cam.ac.uk> Date: 11 Apr 91 10:49:04 GMT References: Reply-To: nbvs@cl.cam.ac.uk (Nicko van Someren) Organization: U of Cambridge Comp Lab, UK Lines: 62 In article jwil1@cs.aukuni.ac.nz (JasonCarlyle Williams ) writes: >OK, guys... You have recently been discussion the idea of invoking editors >(Edit, Draw, etc.) from within another App. along the lines that the editor >will pass you back the file when finished with it... >It's actually nigh on impossible to do this with current app.s (i.e. Edit >would probably have to be re-written to handle this special case) Complete rot! It would need very little change indeed. In fact I have implemented most of what needs doing by use of the txtedit library in C release 3. It is very simple. >How about a sort of RAM filing system for this? >When you want to do a transfer, you "save" your file to the RAMFS, which >automatically (dynamically) 'creates' a disc just for that one file. I think this will need much more work. The existing filing systems know nothing of the WIMP ( as this would require) - and why should they? >This has several dinky features: > >Wimp$Scrap could automatically be channeled through this dynamic RAMdisc >(though not a RAMdisc that pleb users can 'see' on the desktop) if enough >RAM exists for the transfer. Then, Wimp$Scraps will be equivalent to RAM >transfers when the RAM is available. Sounds like you want a pipe. I guess that would be handy. >Extra twiddly bits could be given to the FS when you save a file to it: >e.g. *SAVE file to RAMFS > *Run file (to invoke !Edit on it) > (And set 'twiddly bit' "return the file to me") The last one needs contact with the WIMP. Further more the second one will create a NEW COPY of edit. A message would use the existing copy. >Then when user clicks 'save' in Edit, it saves back to this RAMFS and >the RAMFS sends you a DataLoad request or similar to get you to re-load the >file for your own usage again. This is either cumbersome (you have to go menu, dialogue, OK) or need as much rewrite as before. >This could work, Any reason for the conditional there ? > and it would also work with any application regardless >of whether it actually had been written with this system in mind. A fair point... >(That should give you something to think about/winge about/ignore, anyway) >The Master of the Arcane Use messages, that is what they are there for! Nicko +-----------------------------------------------------------------------------+ | Nicko van Someren, nbvs@cl.cam.ac.uk, (44) 223 358707 or (44) 860 498903 | +-----------------------------------------------------------------------------+