I’ve been using it for development with 10.2 (or indeed whatever the bleeding-edge version of Inform is at any given time). The stated purpose is to allow people to develop for whatever version they like. @Dannii said we should discuss the future of this branch. Practically nobody else is using i…

[image] Zed Lopez: be in directory instead of flat-file format (a new v11 feature) I’ll write more about this difference later. Right now, my plain is to, as soon as I can, I hope tonight or tomorrow night update the extensions to directory format run my smoketester to see which work for th…

I should say that I think the Glk Foundations (ie, the incorporation of Glulx Entry Points into the core kits) is complete, but it’s waiting for Graham to give it a final review and then merge it. Once that’s done we can look at getting the Glk extensions ready for v11.

While I agree with most of what @Zed is saying, I think “essentially beyond redemption” is too extreme a description of the now-“development” branch, so I’d be sad it if was just deleted entirely. I’ve been considering it a collection of incomplete “works in progress” which I might pick up and try …

[image] Nathanael Nerode: I think “essentially beyond redemption” is too extreme a description of the now-“development” branch, so I’d be sad it if was just deleted entirely. I’m not suggesting getting rid of it; I just don’t think it’s worth pursuing trying to get it to a point of being fit …

IMO I see the master/development branch as a scratchpad for people working on extensions. Which is why renaming it to development makes so much sense, we really should have thought of doing that when we first added the I7 release branches. But I do think it should primarily be for people to primaril…

OK, I’m going to be very explicit on why I think the minor compatbility work does belong in the dev branch. (Though it belongs in other places too.) I’m doing dev work on my extension. My extension, or the code I’m using to test my extension, needs to depend on another extension by someone else. …

One of the reasons why I don’t think inform-git updates should be in dev is that the original extension’s developer may want to work on their own updates, but perhaps they’re still using 10.1 or 6M62. I’d like for the dev branch to be somewhere they can come back to at any time and have their extens…

[image] Dannii: Also note that the idea of a global extensions folder will be going away in future Inform releases. The intent is that only .materials/Extensions will be considered. But you could still copy everything into that folder… At risk of pedantry (a risk I valiantly brave daily), I’l…

In fact, I specifically requested and got the ability to add an additional --nest from Graham Nelson because it’s necessary for my extension development workflow. I’m preparing a patch to the Linux IDE which allows it to be added in the IDE, and I’m already using the patched version. Bluntly, if t…

One of the reasons why I don’t think inform-git updates should be in dev is that the original extension’s developer may want to work on their own updates, but perhaps they’re still using 10.1 or 6M62. I’d like for the dev branch to be somewhere they can come back to at any time and have their exten…

The Interactive Fiction Community Forum

Future of the "development" branch on friends-of-i7

Authoring Inform 7