#WHAP! I'd like to See
5 messages in this thread
Hi Jim,
Have you any plans with Whap! so you could use CIS commands to follow
threads and go back through your captured message base? For instance I wanted
to RP a thread to refresh my memory on the subject being discussed. The parent
message was captured earlier in the week and is either now a .BAK file or
somewhere in the APPENDed file, I'd like to have either a command window to
issue the RP or other CIS like commands or some other way to use the CIS
commands with View! Also there has to be another way figured out to MARK
messages after doing a QSN. The way now is quite tedious. One more thing how
about being able to set the sections in the forume to read once and then having
to change them if you want to NOT enter a specific section, instead of having
to set them each session? Also would be nice to use SHIFT as a qualifier key
with UP and DOWN cursor arrows to move to the top or the bottom of a message,
instead of holding the key down. Other than that I can't think of anything else
(at the moment) and I like WHAP!
Chris
Chris,
I have no plans to support threading. What it would take is an external
program that would take 2 .msg files and put them in threaded order. If
someone wants to write that and upload it you won't hear any complaints from
me!
As you've probably noticed, when you do a CAT of the libraries, it is
also set up in a "sessions" fashion. If someone want to write an external
program that merges them together I, again, would not complain. The is a MUCH
esier task than trying to rethread the messages.
Best,
-jcs-
Just add that ARexx interface and see what nifty goodies the users come up
with. 🙂
-larry
Larry,
For instance?
Best,
-jcs-
Jim,
Any number of things, probably many more than you or I could think of. I had
in mind a program along the lines of the one you mentioned, that could be
called by Arexx. Whap could pass it certain data 'on the fly', and the Arexx
part of the connection could make intelligent (guided by the user) decisions on
whether to add it to a thread or not. Automated operation would be another
plus… decisions could be made 'on the fly', say for example the decision to
download a file upon 'seeing' it for the first time, based perhaps on keywords,
which lib it's in, or even based on who uploaded it. File names could trigger
an action, causing the file to end up in a more appropriate directory, or to be
processed in a certain way, or both. (ARC comes imediately to mind, but it
could be any sort of processing).
-larry