Eldritch Eschaton wrote:
So how exactly do you go about that? There's no guide to all of the little micro-changes made to make it easy to backport logic. So do you just plug something back in, see what breaks, and go from there?
Well, for example, if you look at postures.t
, you'll see it uses one of the new elements that you found (roomTitle), in lines like this:
That would be roomName in adv3. One of the key changes is the use of a single 'vocab' property intead of 'vocabWords'. And you can see some of those differences reflected in the templates
. And that can help you figure out what to look for in some cases.
Eldritch Eschaton wrote:
If this is the direction it was going, I see why TADS sort of dropped off the radar compared to Inform. Consider me a sad TADS 2 veteran.
Keep in mind, adv3 is still very powerful on its own. You really don't need
anything that adv3lite does. And if you do find something interesting, like the rules module or something, those are usually easier to backport to adv3 because they are are using intrinsic aspects or are using bits of the overall libraries (system or otherwise) that weren't changed.Side Topic / For What It's Worth:
As far as the "direction it was going", adv3lite in TADS and usage of TADS vs Inform are entirely orthogonal, I believe.
Consider that Inform has a wider ecosystem overall. Its web-based solutions are much easier to use and deploy with, widening the audiences you can reach. (I just did a series of blog posts using Inform 7 and the web-based interpreters. That's something I could not have done as easily in TADS.) And Inform has an IDE approach that is functional across operating systems and one that, at least arguably, has the least cognitive friction. Inform, in my opinion, simply out-competed its parser-based alternatives.
CYOA-style, or choice-based, alternatives are (to me) orthogonal to the TADS / Hugo / Inform ecosystem. But they are clearly gaining in popularity and seeing a lot of innovation and, I would argue, often have an easier learning curve.
So combined with that, it's likely that not too many parser-based alternatives are going to ultimately command much attention. You're probably going to have one that "rules the roost" and sees the most engagement. That happens to be Inform and, again, I feel that's because it ultimately out-competed its friendly competitors. It innovated more broadly and, importantly, made that innovation consumable by varying skill levels. (I suppose in that one sense, that's where adv3lite faltered in terms of helping TADS gain traction, which is what my quoted/referenced posts earlier were about.)
I personally greatly enjoy programming in TADS. But if I were writing a game that I wanted to distribute as widely as possible and as easily as possible to as many people as possible, while having the widest possible community support, TADS would not be my first choice.