Hi Ian, Yep, you know us 'creative types' :-D
I also wrote a TCL.LIGHT a long time ago that was more similar to your program. It would allow people to only look at files they had access to via a 'allowed files' screen and disallowed all DELETE commands. These people had no access to the real TCL, so I did this so they could play without getting dangerous or looking up the CEO's salary! I no longer have the code for TCL.LIGHT. It faded away about a decade ago and got obsoleted in an upgrade. Take care Allen -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ian McGowan Sent: Monday, August 30, 2004 12:53 To: '[EMAIL PROTECTED]' Subject: RE: [U2] Unclassified:[UV] How are the TCL "dot commands" impleme nted? Seems like every pick programmer has written their own TCL replacement :-) Mine is at: http://www.pickwiki.com/cgi-bin/wiki.pl?TclStack Though it seems like a lot of trouble if the only problem is ".S" leaving null items in the VOC. Wouldn't a cron job, or something in the login script that checks for and removes the entry be easier? Ian > -----Original Message----- > From: Allen E. Elwood (CA) [mailto:[EMAIL PROTECTED] > Sent: Monday, August 30, 2004 9:51 AM > To: [EMAIL PROTECTED] > Subject: RE: [U2] Unclassified:[UV] How are the TCL "dot > commands" implemented? > > > At ROI systems they wanted to create their own TCL.MGR > program which was just a shell that would PERFORM the > commands entered. If you were so inclined, you could create > your own TCL.MGR that would be invoked when people signed on, > or when people exited the menu. > > ROI added a .EX command that would exit their TCL.MGR and > then you could still use the U2 tcl manager. (ROI runs on U2). > > I have my own tcl manager, that is really a word processor > that allows me to store ALL of my commands, from forever ago, > in a full screen (with insert and overwrite and cut and > paste, etc) so all I have to do is to page down to a command > entered YEARS ago, and I can recreate that "one time only" > report that a user said "they'd never want again". Until > they changed their minds, that is :-) > > So I don't even have any dot commands in mine. Just arrow > down to the statement and hit return, and a window is brought > up with options to run the command, or maybe launch a > screen.build and use the name supplied, etc. > > Allen E. Elwood > Senior Programmer Analyst > Direct (818) 361-5251 > Fax (818) 361-5251 > Cell (818) 359-8162 > Home (818) 361-7217 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > HENDERSON MICHAEL MR > Sent: Sunday, August 29, 2004 16:15 > To: [EMAIL PROTECTED] > Subject: [U2] Unclassified:[UV] How are the TCL "dot > commands" implemented? > > > Hi, > > I feel I ought to know this, but I can't find it in the > UniVerse Internals course books, so can someone please > enlighten me how are the UniVerse TCL "dot commands" implemented? > > Actually it's really only ".S" that concerns me, because I'd > like to put a wrapper round it. > > Problem: Someone enters ".S" at TCL, instead of ".X" or ".D" > (finger trouble), or ".S <paragraph name>" > Result: A PAragraph is automatically created and saved into > the VOC, with an ID of "" > > Now, having a entry in the VOC with a 'null' ID has some > nasty side-effects, at least here. > > So, I'd like to be able to intercept a ".S" on its own and > 'head it off at the pass' > > Help, anyone? > > > Thanks > > > Mike > ------- > u2-users mailing list > [EMAIL PROTECTED] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
