@lotherio said in A new platform?:
But it seems we're focused on re-inventing the wheel when web interface already has gadgets/wickets/platforms/extra/etc that could be made to work in a web frame along side a window client for the RP side that is the typical RP oriented things for the mush to work. There are tons of apps/gadgets/gizmos out there that could take a web frame and make it just as clunky as MUDlet, with options of control.
I looked into that very extensively when designing Ares and you're missing a few very critical points here:
-
It's a giant PITA to install and get all the moving parts working together. I mean, have you looked at the "Zero to MUX" thread lately? Just getting TinyMUX and MediaWiki installed is hideous. Throw in a forum and a ticket system and a Discord chat server and a Google calendar and whatnot on top of that? And then when some update happens and one piece stops playing nice with your system? Good luck.
-
People don't want to go to six different places to get the information for the game. They don't want to have to create six different logins. (And you might think single sign on would work but no - not gonna happen.)
-
We don't really need all that complexity. MUSH mail and bb posts are pretty simple. We don't need a whole email system or forum software.
So yes, we're reinventing the wheel to an extent - but only a small, simple wagon wheel and for good reasons.
Is it saving any work, becoming easier? Or is it just adding more options that equate to more work?
It really depends on what you want. Using Ares with FS3 can be installed and configured without touching a single line of Ruby code. Installing community plugins (which will include several other skill systems) may take a few code tweaks, but the instructions tell you exactly which lines of code to change to plug them in. So if that meets your needs, then yes - it absolutely saves work even though there's a GUI involved.
But for new code? Of course it's going to be more work to do ASCII+GUI as opposed to just ASCII or just GUI. But we're kinda stuck with that as long as we're forced to design hybrid systems that support both interfaces.
@arkandel said in A new platform?:
lthough my preference is for something that generally looks like a traditional MUSH client (an input line at the bottom, a main window for poses) with all of the additional UI elements added to it(a Hangouts-like chat list on a retractable sidebar on the right that you can hide, tabs for 'channels', etc) or on demand. Do I want to send you a mail? I right click on your name, pick that from a context menu and do so.
Yeah that all sounds great, but here we run into some practical issues. We want to have a game server that:
- Is easy to install with very little technical experience.
- Is easily extensible for whatever custom systems a game wants to add on.
- Supports a hybrid interface with multiple inputs.
- Has a really kick-butt user interface with all kinds of fancy UI elements.
Many of those goals are mutually-exclusive. The fancier you make something, the more complex it gets. The more moving parts you add, the harder it is to install. And so forth.
I think we have to be a bit realistic with our expectations.