Zugg Software :: View topic - Capturing Information To Place into Interactive Database

Apprentice Joined: 10 May 2011 Posts: 111

Recentcomms:

Sorcerer Joined: 15 Apr 2011 Posts: 809

Looks like a case issue - there are no posts from nova, only Nova. Just change your condition to (%upper(%i.name) = %upper($wantedname)). Converting them both to uppercase removes any case sensitivity.

Apprentice Joined: 10 May 2011 Posts: 111

Hey guys,

Bringing this one back to see if it can help me with my current project.

For the SWR that I'm on, we have several ways of communication.

Wizard Joined: 22 Mar 2007 Posts: 2320

The database itself does not need to be sorted, just the output. This should be easy enough to do in a single database. In fact, the database you have already set up and the 'commsfrom' alias is almost everything that you need for this. The 'commsfrom' alias already displays the messages in time order. The only things that may be missing are the triggers to put the other formats of comms into the database, and the trigger to insert the MXP for the clickable link. Do you need help with the other triggers to put comms into the database? It will probably be easiest to write a separate trigger for each style of comms output, but the code should be similar to the trigger you already have.

You need a trigger to capture and modify the line that you want to insert the clickable link in. I'm not sure what lines you want the link to show up in, so I will assume for now that it will be lines like "Bob says 'blah'". This will make it easy, because it guarantees that the name has at least one entry in the database (the message this is triggering on Smile

) I will assume the name of the window you want the output in is named Comms. The trigger should look something like this (untested!):

Apprentice Joined: 10 May 2011 Posts: 111

Hey Rahab, thanks for the quick response! Pretty much anywhere I see the name would be good, as I'd like to be able to click on their name if someone mentions them and bring up what that person has said. Going to start to work on this and see how far I get without bugging ya'll. =)

Wizard Joined: 22 Mar 2007 Posts: 2320

To get get the clickable link everywhere the name appears in mud text, you will need a stringlist of the names in the comms database. Add this line to all triggers which are adding comms to @messagelog:

Apprentice Joined: 10 May 2011 Posts: 111

Ah, gotcha. Thank you!

Having a bit of an issue sorting this out.. I think I'm using too many ~'s. Can you help me sort out this symbol jumble?

Apprentice Joined: 10 May 2011 Posts: 111

NVM, Got it.

Sorcerer Joined: 15 Apr 2011 Posts: 809

You can just use %q for a word boundary, it's equivalent to \b in regex.

Apprentice Joined: 10 May 2011 Posts: 111

Ah, thanks Daern.

Okay, I've got the majority of it figured out. Having issues capturing say triggers, however, as there are so many variations possible.

Apprentice Joined: 10 May 2011 Posts: 111

Wizard Joined: 22 Mar 2007 Posts: 2320

Oh, darn, I think the problem with the trigger is that it is putting it into a loop. I'll think about that some more.

Is there a specific list of adverbs that can be used in the says, besides 'coarsely', or can people use any adverb phrase they want? Do the adverbs always end in 'ly'? If people can add any adverb phrase they want and they don't have any identifying features (like all ending in 'ly'), it will be difficult to separate the charactar name/description from the adverbs. Other than the adverbs, it is actually fairly straightforward.

Another alternative for capturing says would be to only capture those whose names are already in the database. You could add new names into @lognames to ensure that you start capturing their says messages. The pattern for this would be:

Wizard Joined: 22 Mar 2007 Posts: 2320

On second thought, it might be practical if you deliberately eliminate messages from "A masked being" and other unidentifiable figures.

Apprentice Joined: 10 May 2011 Posts: 111

Wizard Joined: 22 Mar 2007 Posts: 2320

Those are regular expressions. They should work if you set the Triggers to be regular expression triggers.

In fact if you actually have a list of the tones, then you can do it perfectly, without including the tones in the names. Just put all of the tones into a stringlist variable named @tones. Here is a pair of zscript patterns that I think should match all of the say variations you list:

Apprentice Joined: 10 May 2011 Posts: 111

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, there is a way to grab that by a trigger. Unfortunately that list gives the adjectival forms of the words. It looks like if you set the tone to "happy", the say will come out "happily". So simply grabbing the list won't be enough--you need to change those forms into the adverbial form. It might be possible to automate this conversion, as well, except for a few odd cases.

The trigger would need to be a regular expression trigger. The pattern would be:

Apprentice Joined: 10 May 2011 Posts: 111

Before you posted, I did some screwing around and came up with this:

Apprentice Joined: 10 May 2011 Posts: 111

Also, I don't have the slightest clue how to work on that conversion, other than the capitalized letters.

Wizard Joined: 22 Mar 2007 Posts: 2320

The question marks mean "zero or one of the thing immediately preceding". In each case, the thing immediately preceding is contained in a set of parentheses. Basically, by putting in the question marks, it means that the second, third, and fourth number/word pair are optional and might not appear. [edit]Note that this was a regular expression trigger pattern, so the trigger would have to be marked as a regular expression trigger. There isn't any good way to do the equivalent for a zscript pattern in this case.[/edit]

I'll try to remember to give some code for the adj/adv conversion when I get home.

Wizard Joined: 22 Mar 2007 Posts: 2320

Okay, let's see. Here is a snippet of code to convert an adjective, $adj, into an adverb, $adv. I have actually tested it, and it even works on spry. Very Happy

Apprentice Joined: 10 May 2011 Posts: 111

I'm getting the fired but did not compile error.

Wizard Joined: 22 Mar 2007 Posts: 2320

The snippet I gave works on a single word at a time, held in the variable $adj, and puts the single resulting adverb into $adv. The @tones variable is an entire list of adjectives. You need to loop through the adjectives one at a time, put each one through my conversion code, store all the resulting adverbs, and at the end stuff all the adverbs back into @tones. One way of doing the loop would be:

Apprentice Joined: 10 May 2011 Posts: 111

Wizard Joined: 22 Mar 2007 Posts: 2320

You didn't take @//LotjShared/Comms/tones out of the #SWITCH command.

No, you don't need to specify a full path to get to a variable in a shared module. A simple @tones will usually suffice if you have only one variable with that name.