jordan%lvvm6.span@SDS.SDSC.EDU (RICH) (03/25/89)
> From: Andy Tefft (814) 862-6728" <ART100%PSUVM.BITNET@CUNYVM.CUNY.EDU> > > How come nobody's ever thought of putting binscii or executioner > code inside shrinkit or any other archive program? It would be great > if Andy and Dave could work something up. This way, you would be able > to use ShrinkIT to handle the entire file, even if in BinSCII format, > and BinSCII could still be a separate program (since it would still > be useful, for example to convert TO text). Or is space too tight > in Shrinkit (that's what I figure)? Andy has mentioned that ShrinkIt is now capable of becoming a standard for Apple ][ use. Now, if BinSCII/Executioner capability can be added without sacrifice to ShrinkIt, that would be fine. But if ShrinkIt _does_ become a new standard (replacing or supplementing BLU) a large fraction (perhaps a majority) of its users will not be on a text-passing network with character munging IBMs and such in the transmission paths, but on information services like GEnie, ALPE, CompuServe, and various BBSes that do not require files to be encoded. For all those people the added code would be so much dead weight. And if it cost speed or other features to incorporate, would it be worth it? (Admittedly a ShrinkIt style interface for BinSCII would be rather nice :-) Rich <jordan%lvva.span@sds.sdsc.edu> <jordan%lvva.span@sdsc.bitnet> BIX: richjordan (Rarely there) GEnie: BARRACUDA