Saving TABS/CRLF's from text widget. Best Way?
in [TCL]
|
From: GizmoGorilla on 10 Feb 2010 07:49 On 2010-02-09 3:55 PM, Bryan Oakley wrote: [8<] > I don't mean to sound preachy, but it sounds like you're making a > beginners mistake of premature optimization. Don't worry about > compression until it actually proves to be a problem. Otherwise you'll > spend way too much time on something that just doesn't matter. ....comments appreciated, and I will try to be more precise next time... Yes you're right that in this day, space is cheap & abundant, but that is not always the case. I'm developing this software to be run on an old, slow, Solaris networked server where space is not as abundant and cpu speed is not blazing. This, I have no control over. The text widget will be used to link a user comment to a record in a db, of which there may be 10's of 000's of records so Im trying to be efficient given my constraints. I will take the posted comments into consideration. Thanks. Norm [GG]
From: Will Duquette on 10 Feb 2010 10:29 On Feb 10, 4:49 am, GizmoGorilla <gizmogori...(a)hotmail.com> wrote: > On 2010-02-09 3:55 PM, Bryan Oakley wrote: > > [8<] > > > I don't mean to sound preachy, but it sounds like you're making a > > beginners mistake of premature optimization. Don't worry about > > compression until it actually proves to be a problem. Otherwise you'll > > spend way too much time on something that just doesn't matter. > > ...comments appreciated, and I will try to be more precise next > time... > > Yes you're right that in this day, space is cheap & abundant, > but that is not always the case. I'm developing this software > to be run on an old, slow, Solaris networked server where space > is not as abundant and cpu speed is not blazing. This, I have > no control over. The text widget will be used to link a > user comment to a record in a db, of which there may be 10's > of 000's of records so Im trying to be efficient given my > constraints. I will take the posted comments into > consideration. Thanks. > > Norm [GG] OK; but man, it's been a long time since I've worried about the space taken up by *text*. What kind of database are you using? Will
From: GizmoGorilla on 10 Feb 2010 13:00 [8<] > OK; but man, it's been a long time since I've worried about the space > taken up by *text*. > > What kind of database are you using? Everything is custom made here using a simple flat file system. SQL would be nicer but this is what I have to work with. The DB is used to track about 1000 students per semester for equipment assignment and account related issues. Each student could potentially have a couple dozen entries in a semester, each entry with a comment field... Thanks again for your input. Norm
From: drscrypt on 11 Feb 2010 10:07 GizmoGorilla wrote: > widget, WYSIWYG. So perhaps when I save, for example... > > (users view) > some text tab to here > \n > \n > \n > \n > > ...it could be saved as... > > (data view) > some text [5x\t] tab to here > [4x\n] > This would remove the spaces inserted by the tabs, and remove > the blank lines, So my data now uses 2 lines, not 5. Do you realize by doing that you are actually increasing your file size and not compressing it in any way? > string length "\n\n\n\n" 4 > string length "\[5x\\n\]" 6 Especially with tabs, where you are more likely to have one here and there, or 2-3 in consecutive order, you are increasing the size of the file not to mention the extra processing that you must do at load/unload. Plus how many 1x commands are you planning to define? I would suggest to either trim tabs/newlines away if they are multiples, or leave things as is. DrS
From: GizmoGorilla on 12 Feb 2010 07:32
On 10.02.11 7:07, drscrypt(a)gmail.com wrote: > Do you realize by doing that you are actually increasing your file size > and not compressing it in any way? [8<] > > I would suggest to either trim tabs/newlines away if they are multiples, > or leave things as is. Yea, I do realize that, and in retrospect, a little more thought should have been exercised prior my to posting. :( I will leave things as they are for now. Once the software goes live I'll see how it performs... Thanks for the feedback... Norm |