[ANN] Dialog Tool 2.0-beta-18

Authoring Dialog
,
201

For me, the button I use most is “bless (this one knot in particular)”, so that I can have unblessed changes up higher in the Skein.

1 Like
202

Work in progress of what’s coming next:

SCR-20260530-jhip-3
SCR-20260530-jhip-33424×3774 1.42 MB

We’ve got nodes and arrows!

1 Like
203

This came out so good, but it depends on the Dialog 1c/01, so I’ll release as soon as that hits (and I update the homebrew formula).

204

2.0-beta-17a

What’s New?

  • New navigation graph for exploring all knots
  • Several new keyboard accelerators
  • Jump drop-down menu is now fully keyboard navigable
  • The return of “Bless This Knot” (vs. “Bless All Changes”)
  • Replay All is now significantly faster
  • Jump menu is now fully keyboard navigable
  • Show network error modal immediately on server disconnect
  • Capture and report dgdebug startup errors
  • Remove use of pseudo-tty, make use of dgdebug --format ansi, for improved stability

SCR-20260530-tqen-2

3 Likes
205

Who has tried this on Windows? It’s sounding like it will run on Windows now!

206

New in Dialog Tool 2.0-beta-18

Now generates installers for Windows and Linux.

Accessibility improvements - icons to supplement colors, better ARIA control descriptions.

Network error modal no longer is displayed when the Skein is shutdown properly (via the Quit command).

Navigation graph and transcript both scroll to active knot when a count (new or error) is clicked in the status counts.

Installers?

Yes, you should be able to install on Windows by downloading the new .msi installer:

https://github.com/hlship/dialog-tool/releases/download/2.0-beta-18/dgt-2.0-beta-18-windows.msi

There’s also an installer file for Linux:

https://github.com/hlship/dialog-tool/releases/download/2.0-beta-18/dgt-2.0-beta-18-linux.deb

Full instructions are on the Dialog Tool home page:

https://github.com/hlship/dialog-tool#installing

Please if you can, try these out and report back!

What’s Next? What’s Left?

The Skein is looking very solid at this point. The only major feature left is handling single character input. There may also be some road bumps due to expected changes in how dgdebug outputs ANSI sequences for colors and fonts.

But I’m not the only user; please check it out and give feedback here or by adding issues on the GitHub home page.

There are a few issues for dgt in general, the most prominent of which is supporting varied sources by target.

I’m really happy with what I’ve created here, especially with the late addition of the navigation graph.

1 Like
207

Are you currently using --tag-lines to detect line versus character input?

208

I hadn’t noticed your mentioning of screen readers until just now; beta-18 should be more accessible than prior releases, but I’m far from expert on these issues. I’ll be looking forward to your feedback!

209

No, that’s the next thing to implement.

210

I could use a small sample that uses single character input, to test against.

211

Oh, sure thing.

(program entry point)
	First I'm going to print some text, then ask for line input.
	(get input $Words)
	You said "(no space)
	(exhaust) { *($Word is one of $Words) $Word }
	(no space)"! (par)
	Now I'm going to print some more text, then ask for single key input.
	(get key $Key)
	You pressed the "(no space) (print key $Key) (no space)" key! (par)
	Now I'm going to ask for line input again.
	(get input $)
	Goodbye!

(print key @\s) SPACE
(print key @\n) ENTER
(print key @\b) BACKSPACE
(print key @\u/@\d/@\l/@\r) arrow
(print key $Key) (uppercase) $Key