I've been considering this on and off for a while, and I decided I might as well put it out there.
People are talking a lot about the future of MUSHclient and the future of MUDs themselves (even the future of operating systems) and when I consider it, there's this big, obvious question in my mind. Why isn't there a client as good as MUSHclient for Linux?
I've been looking in to the development of Mudlet(http://www.mudlet.org) and I hate it. I'm not knocking any of those devs or the work they've done, I'm just saying that the client is fundamentally different than MUSH and it's interface and functionality do not suit -my- needs.
Yes, MUSHclient runs (well) on top of Wine. So, if you are running a Linux operating system, it's totally feasible to use MUSHclient. However, that's about as much involvement as the Wine option allows for.
I would really like to be involved in the development of MUSH, but I'm not going to start running a Windows box any time soon, and where the hell do you even find MSVC 6.0 nowadays?
There are a lot of things in MUSH I think could be improved upon, extended, etc, regardless of which operating system it is running/developed on. Reconfiguration of the GUI, (triggers/aliases/etc), improving use of STL, extending GUI displays and script functions (wxwidgets/wxlua anyone?), modularity, etc.
I'm considering how much work it would be to fork MUSH and port it to Linux (I develop on Debian primarily.) I also want to know how such a project could be synchronized to the continued development of MUSH on windows. In other words, I'm trying to decide if I'll be writing a brand new client inspired/based-off of MUSHclient, for the Linux operating system, or if the current client could feasibly be split into a separate build for Nix.
What do you guys think about this? Twisol, you up for some practice coding? :D |