Re: Has anyone written a word wrap routine for text?

Path: emory!swrinde!cs.utexas.edu!uunet!ddssuprs!lpc From: lpc@ddssuprs.uucp (Luis P Caamano) Newsgroups: comp.databases.informix Keywords: informix Message-ID: <1992Jan28.135249.34720@ddssuprs.uucp> Date: 28 Jan 92 13:52:49 GMT References: <1604@das13.snide.com> <1992Jan25.020930.25632@ddssuprs.uucp> <1613@das13.snide.com> Organization: Dickens Data Systems, Inc. In article <1613@das13.snide.com> dave@das13.snide.com (Dave Snyder) writes: >In article <1992Jan25.020930.25632@ddssuprs.uucp>, lpc@ddssuprs.uucp (Luis P Caamano) writes: >> What I really want is to have a table called 'lines' with two >> fields, one the document id (the join) and the other one is >> the line field. Then I'll define a 6 lines array field on the form >> with a max program array of let's say 300. That would give me a 300 >> lines memo pad. Then I use my input array on the field and then >> you'll have a efficient memo field. If the user only types one >> line then I'll have only one record on the lines table. It's here >> where I want a wordwrap feature. As you might guess what I want >> is the wordwrap feature implemented on a another kind of input >> array command or the WORDWRAP feature with scrolling capabilities >> on a VARCHAR field. Get the idea? > >We used to do that, it worked quite well until someone wanted to write How did you do THAT? I guess that was the original question. What is "THAT" in your sentence? The lines table with an input array, the wordwrap feature on an input array, or the "scrollable" wordrap field. >damn near a book describing each piece of equipment and 300 lines >wasn't enough. Now we use TEXT blobs with Micro Emacs (with emacs wordwrap >turned on), and also BYTE blobs with Word Perfect. These two solutions >work like a charm. > >Remember! TEXT and BYTE blobs require Informix-ONLINE. > I won't write an application that depends on Informix-ONLINE, not even 4.00 unless it's an special application. My accounting system don't even use any of the 4.00 features so it can run on .03 much less TEXT and BYTE blobs. Of course you can write your app so it checks what it's running on, and use features accordingly (sometimes you have to) but that's not exactly what we're talking about. -- --------------------------------------------------------------------------- Luis P. Caamano | Support Services Engineer | uunet!ddssuprs!lpc Dickens Data Systems, Norcross GA | (404) 242-5991 --------------------------------------------------------------------------- If you think you know something, you'll stop learning. -myself