Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ardent.UUCP!jkh From: jkh@ardent.UUCP Newsgroups: comp.windows.x Subject: storage scheme for text widgets Message-ID: <8807052356.AA00142@scrod.ardent.com> Date: 5 Jul 88 23:55:57 GMT Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 13 The way memory is allocated and manipulated for string source text widgets begins to lose rapidly as the amount of text manipulated grows. For example, open a compose window with xmh and use M-I to insert a reasonably large file (like /etc/termcap). Go back to the top and insert a few characters. chomp chomp. I haven't had occasion to use disk source widgets yet, so I don't know if they're a significant win in this regard (though there will always be situations where paging from a file is impractical). Anyway.. This isn't so much a flame as it is a question. Is anyone working on a different storage mechanism for string source widgets? It seems a pity to provide a widget that lends itself so well to general editing and then make it impractical to do so. Jordan