Wouldn't it be good if all variants had the latest UI and were available in the same place? See here for some vague musings on the topic.
Variant Project
Collapse
X
-
That might be true, although a completely unmaintained variant probably won't.
I think the idea is to make it really easy to share some of the new features (Nintendo DS support, menu scrolling code, new ncurses features, better colors, etc) between maintained variants (including Vanilla).
I imagine this would help someone update variants with a minimum of work, so that someone who doesn't really want to spend much time on X variant can still keep it current.
P.S. Nick, I responded on your blog also!Comment
-
d_m, your reply to Nick's blog post sparked something in my head... "abstract stuff out"? Why not upgrade to C++, if making such a radical change in the architecture to begin with?
You read the scroll labeled NOBIMUS UPSCOTI...
You are surrounded by a stasis field!
The tengu tries to teleport, but fails!Comment
-
One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
I'd say no to that, as I'd rather not see Angband get embroiled in Microsoft software patent disputes.
Java might be nice, especially in view of Android being based on it... However Java for desktops is slooooowwww. Oh sure, the actual code may run faster than compiled C, but the JVM is seriously huge. It is absolute overkill for a text based game.
And languages like Python, while they may be cross-platform, are not really cross-platform enough for many Windows users.
That being said, I can think of very good reasons to switch to something other than C. Especially for anyone writing a multiplayer network version. *cough*bufferoverflow*cough*Comment
-
What does this mean? My day job is Python development for a Windows platform. The interpreter installs trivially as do the vast majority of third-party libraries. If you want something to hand to other users, py2exe makes standalone executables just fine.Comment
-
Oh... I hadn't heard of py2exe. Scratch what I said then.Comment
-
To be perfectly honest, I've started a straight port of Angband to Python before. It's not hard so much as really time consuming and boring (Angband is around 150,000 lines of C). Also once you're rewriting Angband the temptation to drastically improve on it is hard to resist.
I think moving toward a "more modern" language would obviously aid future development. Although at that point only future Angband variants (or those which were rewritten in language X) would even benefit. So in the short term it wouldn't address Nick's concern at all.
I think this exposes an existing tension in the Angband Vanilla/Variant ecosystem.Comment
-
Yeah, I'm very much looking at something evolutionary, and easy.
Yes indeed, but often the tension is a good thing. The last thing I would want to see is all the variants becoming a bland mush - I'm trying to focus on features that are just an annoyance if you don't have them, rather than being part of the feel of the individual variant.I think this exposes an existing tension in the Angband Vanilla/Variant ecosystem.One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
So are you imagining FA/O as being the base for this? Are there any major UI features V or other variants have that you'd want? Would this start as a term-XXX.c standardization?Yes indeed, but often the tension is a good thing. The last thing I would want to see is all the variants becoming a bland mush - I'm trying to focus on features that are just an annoyance if you don't have them, rather than being part of the feel of the individual variant.
I feel like the term-XXX files are currently the easiest to port, and what is really needed is a level of abstraction that V doesn't currently have (a way to effectively wrap all the term_out() calls and so forth). Maybe FA has this?
EDIT: I also worry about the discussion bifurcation that your blog is causing
Comment
-
Probably, yes, yes, not really. I have updated the FA low-level code to the latest (or at least a recent) version of V two or three times; Jeff is currently going through the same thing for NPP. At the moment a number of things in V are more advanced than FA, and there are several things which are better (or at least different - opinions may varySo are you imagining FA/O as being the base for this? Are there any major UI features V or other variants have that you'd want? Would this start as a term-XXX.c standardization?
I feel like the term-XXX files are currently the easiest to port, and what is really needed is a level of abstraction that V doesn't currently have (a way to effectively wrap all the term_out() calls and so forth). Maybe FA has this?
) in FA than V. My thought is that the simplest thing is to start with FA and see what evolves - with the first thing to do being to align with V as much as possible.
I'm actually fairly happy with the main-xxx files as they are - although I think there's a whole nother conversation to have about what OSs we need ports for.
Yes. I started the blog because I didn't want to rabbit on here too much about peripheral stuff, but I don't know how good an idea it was really.I also worry about the discussion bifurcation that your blog is causing
One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
I seem to recall that you have solved the "description too long to fit in an 80x24 terminal without scrolling" problem in a way that V should adopt.
Definitely let me know if you make progress on this idea, have patches you'd like committed to V to help align it better, or have specific suggestions on what to change. My time to work on Angband is somewhat sporadic but I'm definitely interested.Comment
Comment