console capability?

Forum where anything UOX3-related goes - including, but not limited to: newbie-support, ideas, general questions, comments, etc and-so-forth.
Post Reply
punt
VIP
Posts: 244
Joined: Wed Mar 24, 2004 7:46 pm
Has thanked: 0
Been thanked: 9 times

console capability?

Post by punt »

Currently the console command is limited to single character entries (for the most part).

What should the console capabiity be? What should one be able to do from the console? The current capability? specifiing specific files?
User avatar
Xuri
Site Admin
Posts: 3704
Joined: Mon Jun 02, 2003 9:11 am
Location: Norway
Has thanked: 48 times
Been thanked: 8 times
Contact:

Post by Xuri »

You mean changing (parts) of the uox.ini configuration from the console directly (like the file-paths)?
-= Ho Eyo He Hum =-
punt
VIP
Posts: 244
Joined: Wed Mar 24, 2004 7:46 pm
Has thanked: 0
Been thanked: 9 times

Post by punt »

Well, not what I was thinking, but is that something that should be allowed?

I was thinking like specifying a single js file, or data file that could be reloaded.

But really looking for a "requirement" list of what should the console provide.
Command wise at least.
User avatar
Xuri
Site Admin
Posts: 3704
Joined: Mon Jun 02, 2003 9:11 am
Location: Norway
Has thanked: 48 times
Been thanked: 8 times
Contact:

Post by Xuri »

Ah. That would actually be quite useful. It already takes a few seconds to reload the JS files, and when people start adding custom script I can imagine it can take quite some time to reload it all at the same time.

And I guess the same would apply to the DFNs; Being allowed to reload a single file would be useful indeed.

As for other stuff the console should provide...I'm not sure. Perhaps we should take a look at the consoles of the other available Emus and see if they do anything interesting there which might be useful for UOX3 as well =)
-= Ho Eyo He Hum =-
giwo
Developer
Posts: 1780
Joined: Fri Jun 18, 2004 4:17 pm
Location: California
Has thanked: 0
Been thanked: 0

Post by giwo »

It is my opinion that the console should be as simple to use as possible, allowing even the newest of users to quickly figure out (via prompts and responses to actions) how to do things (IE the security notice telling them how to disable security ).

Having said that, I am also very much for versatility. While it is always a difficult balance to have versatility and ease of use, it can be done, with careful planning and implementation.

Loading single files at a time and being able to specify which file to load dynamically would be very nice. It would also save us some characters currently used up by the quick-keys method so we can make that option more versatile (or perhaps even allow for users to map their own quick-keys).

I'd say Xuri has a good thought of checking out how other console-based emu's tackle the same issue, then proceed as we feel so inclined.
Scott
punt
VIP
Posts: 244
Joined: Wed Mar 24, 2004 7:46 pm
Has thanked: 0
Been thanked: 9 times

Post by punt »

giwo wrote:It is my opinion that the console should be as simple to use as possible, allowing even the newest of users to quickly figure out (via prompts and responses to actions) how to do things (IE the security notice telling them how to disable security ).

Having said that, I am also very much for versatility. While it is always a difficult balance to have versatility and ease of use, it can be done, with careful planning and implementation.

Loading single files at a time and being able to specify which file to load dynamically would be very nice. It would also save us some characters currently used up by the quick-keys method so we can make that option more versatile (or perhaps even allow for users to map their own quick-keys).

I'd say Xuri has a good thought of checking out how other console-based emu's tackle the same issue, then proceed as we feel so inclined.
Agree on all statements. Clearly I wanted to understand the capability, after that the question is determining how to expose that capability (which goes to the simple/intuative).

As for the other emu's, a great idea, but I will take a page from other uox dev's, and state I don't have the time to : 1. examine the code of them, 2. setup to run them, 3. Determine what is applicable or not.

Refactoring several aspects of UOX3, embedding NSPR, undoing other approachs, and enhancing it at the same time is keeping me gainfully ocuppied.

Was just curious of the options as I look at this (relates to my other Coders question on threads or processes), that one doesn't have to limit to a single keystroke once the console is moved out of the criticial path.
User avatar
Xuri
Site Admin
Posts: 3704
Joined: Mon Jun 02, 2003 9:11 am
Location: Norway
Has thanked: 48 times
Been thanked: 8 times
Contact:

Post by Xuri »

Hm. I've checked out a few other emus (Wolfpack, Lonewolf, UOXClassic, Nox Wizzard, POL, RunUO, Method) - most of which are UOX-related emus, but still..

None of the ones I checked out have a more "advanced" console than UOX3 currently has, as far as I could see. I failed to find any features in any of them which UOX3 doesn't already have, and many of them have nothing more than the same console menu that UOX3 0.70.x had, if even that..

EDIT: Found a copy of Sphere 55i - not the latest version of Sphere, but..
Sphere has a console which has a seperate area in the bottom for typing in, which allows writing stuff without being interupted by the console scrolling I guess hm. Also has an interesting "Hear all that is said"-option, which prints all speech in the console.

EDIT2: Forgot to mention something that RunUO does. If it starts up with no accounts, you're asked to create an admin account there and then, through the console. That's useful. Expanded idea for UOX3; Do both this AND have a seperate option in the menu where the admin can add new accounts in general?
-= Ho Eyo He Hum =-
Post Reply