Improve the syntax highlighter by also highlighting words based on what they mean to the compiler. We could have different colors for objects, rulebooks, kinds, variables, properties, etc.

The semantic analysis would have to be done by NI, producing a markup file for the IDEs to read.

Dynamic object creation has been frequently requested, but we
have resisted because it would have to be a Glulx-only feature. Jesse McGrew's
Dynamic Objects extension offers some of these features, but would be
stronger if there were some kind of internal table or routine to look up the
data types of properties, global variables, and rulebook variables at runtime.

Add a check-box next to the documentation search box that would search only the code snippets in the documentation, and not the main text. Searches for 'in' would become useful, as well as many other English phrases that are also I7 code.

It would be nice to have two-way relations that also have an attached value for weighted relationships of some kind; or three-way relations. (These are essentially the same thing, only with different formal properties and kinds of terms.)

In the case of specific objects or simple variables, allow for the use of possessive pronouns to reference properties, so "the location's description" would be a natural language synonym for "the description of the location."

A way to bookmark one's place in the Source text panel so that one
can quickly jump back to it. We propose to allow the user to set bookmarks in
the source, with shortcuts to jump back to the most-recently set; the bookmarks
would also be visible in the contents view of the source, and could be deleted
again.

Currently, printing the name of something in bracketed text (like [the orange] or [the list of round fruits]) marks it as mentioned, preventing it from appearing later-- except if this occurs within the room description itself. It would be nice if this worked within room descriptions, so workarounds like Mentioned In Room Description by Ron Newcomb are no longer necessary.

It would be great if users could leave feedback and reviews of extensions indicating which ones were especially useful. This would be a good tip for other authors and also provide some encouragement to extensions creators who do a good job.

At present, neither the Windows IDE nor the GNOME Linux IDE allows the user to write a project entirely in Inform 6, though both IDEs can package a pre-compiled Inform 6 project with metadata. I'd like to see this feature, already present in the Mac OS X IDE, implemented across the board.

The ability to define a null token in a list of alternatives in
Understand grammar, to match the existing ability to make a word optional
in a phrase definition. For example,

Understand "google for/-- [text] in/on [library computer]" as consulting
it about (with nouns reversed).

which could match "GOOGLE FOO ON COMPUTER" or "GOOGLE FOR FOO ON COMPUTER".

While there are other ways to achieve this effect, by defining new grammar
tokens, allowing "--" would be quicker and more legible.

The IDE should keep a timestamp of the last time it saved the source text. Then, when the IDE is foregrounded, it should check the story.ni file's modification time. If the file was updated more recently than the IDE saved, the IDE should silently "revert" to the newer contents.

This would allow the user to have the file open in an external editor, save, switch to the IDE, and compile.

(This is the preferred behavior for Mac text editors. See TextWrangler/BBEdit, for example.)

Authors have repeatedly asked for more control over the styles used in
the game. At a minimum, some way for arbitrary colour changes to be allowed -
this is the one area where Glk/Glulx is behind the Z-Machine.

In addition to "it is completely impossible", it should be possible to say that something is a reasonable option but that the parser should never guess it on its own (so that the parser doesn't solve puzzles for us).

Extensions should be accessible through a repository, like an apt repository.

Inform 7 should automatically download and install any extensions it needs but doesn't have, while keeping all old versions accessible.

In action descriptions, the terms "applying to one visible thing" is misleading -- what's really meant is that the thing is *in scope*, and often it isn't visible at all, especially if we're talking about something that is placed in scope at a distance, like a conversation topic.