Comments on: Inform 7 Development: Implementing Single-Keyword Conversations

By: Keyword Interface for Conversation Package « The Quern

Keyword Interface for Conversation Package « The Quern — Sat, 27 Feb 2010 15:54:43 +0000

[...] Interface extension with Eric Eve’s Conversation Package system for conversations (part 1 and part 2), I’ve packaged up the interface code as an extension and submitted it to the archive, so it [...]

By: Matt Wigdahl

Matt Wigdahl — Fri, 19 Feb 2010 18:09:33 +0000

I’ve just updated the code in this article to correct a formatting issue that caused the problem Strainer pointed out above. I’m going to add documentation for the extension and then submit to the archive on Wednesday of next week.

By: Matt Wigdahl

Matt Wigdahl — Fri, 19 Feb 2010 04:16:48 +0000

Wow! You really went the extra mile on this! I’ll be happy to take a look, and will clean this up for a formal extension as soon as I can. I’ll be out of town this weekend so it won’t be immediate, but I will try to have it polished up and ready to go by the middle of next week.

Thanks again!

By: Strainer

Strainer — Fri, 19 Feb 2010 02:40:30 +0000

Hello Matt!

Great work you did on this extension, is there already a version we could use? I have put one together already, only extending one part of your code:

Rule for printing the name of something (called item) when listing suggested topics:
let output be indexed text;
now output is the printed name of item;
let kw be indexed text;
now kw is the keyword of item;
if kw is “”:
change kw to word number ( the number of words in output ) in output;
repeat with wordcounter running from 1 to the number of words in output:
say “[if wordcounter > 1] [end if]“;
if word number wordcounter in output matches the regular expression “\b(?i)[kw]“:
say “[to][word number wordcounter in output][x]“;
else:
say “[word number wordcounter in output]“;
otherwise:
repeat with wordcounter running from 1 to the number of words in output:
say “[if wordcounter > 1] [end if]“;
if word number wordcounter in output matches the regular expression “\b(?i)[kw]“:
say “[to][word number wordcounter in output][x]“;
else:
say “[word number wordcounter in output]“.

With your code as it was, topics and things which already had keywords weren’t printed, with this version this works now. I have put together all your suggestions (the modifications you did to Conversation Suggestions are already part of the new Version 3 of the extension).

As far as I tested it, everything worked fine. I must say that I have mostly tested this with German language, but it should work with English just fine. I have put your name as author, as it wasn’t my work, but I was eager to try this out. I hope you don’t mind that.

Here is the link to the plugin:

http://www.mediafire.com/?myxatmomint

Would be happy if you could take a look at this.

Thanks for your effort.

Strainer

By: baluev

baluev — Sat, 26 Dec 2009 23:07:07 +0000

I want to quote your post in my blog. It can?
And you et an account on Twitter?

By: Matt Wigdahl

Matt Wigdahl — Wed, 23 Dec 2009 19:32:48 +0000

Thanks! Yes, I will package it up once I clean it to the point where it’s generic enough to work. I agree that it makes the most sense to do it that way.

By: Eric Eve

Eric Eve — Wed, 23 Dec 2009 19:20:02 +0000

More good stuff here!

I’ve incorporated your change to “To say nothing specific” in the next version of Conversation Suggestions (since it fixes a problem I spotted to). Might it be worth packaging up the rest into an extension of your own (e.g. Keyword Conversation)? I think it makes better sense to put it all in new extension rather than trying to incorporate it into an existing one. I could try to knock up something on the basis of your code, but since it is all your code it may be more appropriate for you to release an extension in your own name.

– Eric