Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!eru!luth!sunic!liuida!slaka!micke From: micke@slaka.sirius.se (Mikael Karlsson) Newsgroups: comp.sys.amiga Subject: Snap Release II Message-ID: <4564.AA4564@slaka.sirius.se> Date: 22 Nov 89 00:05:36 GMT Followup-To: comp.sys.amiga Lines: 52 Keywords: Expires: Ok folks, what would you like to see in the next release of Snap? Here are some suggestions and thoughts. o Saving graphics. Important. Does anyone have a good iff.library? If not, how about some nice example code? o Prepending and appending characters is a common request. Very important! But how should it work? Should the text be modified before it's put in the clipboard or should the prepending and appending happen at insert-time? _clipboard_ | | TxED ------------> | Hello | "Hello"< | |------------> TxED/Snap Snap ---Modify---> | >Hello | |___________| _clipboard_ | | | |------------> TxED "Hello" "Hello"- TxED/Snap -------> | Hello | | |---Modify---> Snap ">Hello" |___________| How to select modified vs. original text? Remember that it's possible to select any qualifier to use with Snap. There's no "spare" qualifier to use for modified Snaps. Would it be enough with an extra insert key? How to select what to prepend and append? I've considered environment variables (SnapPrepend & SnapAppend). o Converting to a handler and a loader with some help texts. Not critical but it would be nice to get it done. o Recognizing text with an extra blank line between the rows (e.g. Browser). Shouldn't be too hard as long as there's a row above or below to sync with. Any other ways of checking this? Peter? o Compileability(:-) with Lattice. No big deal. o Recognizing proportional fonts. Probably not useful. Tell me what you think. So, tell me what you think. Any other ideas? Mikael Karlsson, Lovsattersvagen 10, S-585 98 LINKOPING, SWEDEN micke@slaka.UUCP, micke@slaka.sirius.se {mcvax,munnari,seismo}!enea!liuida!slaka!micke C86.M-KARLSSON@LINUS.liu.se