A nicer server list.
The entrace into ember should be streamlined a bit. There should be a notion of "selected server". This should be the last server you logged into, and should be persisted somewhere in the config. The flow of the login should go:
1) Server Check ( do I have a "set" server ), if so display login widget ( and optionally pre-fetch stored user/password and fill them ) that includes the servername information. If there is no set server, display a sever selection.
2) The login widget should promenantly display somewhere the server it's setup for. There should be a button that should activate the "server selection" widget.
3) The process should proceed with the login and continue as it does now.
Blueprint information
- Status:
- Complete
- Approver:
- Erik Ogenvik
- Priority:
- Low
- Drafter:
- Sean Ryan
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Erik Ogenvik
- Completed by
- Erik Ogenvik
Related branches
Related bugs
Sprints
Whiteboard
More usability would surely be needed. As you say, in most cases people will connect to the same server. The widgets shown at startup could sure need some more helpful texts.
However, I'm thinking that in the long run we would probably also want to support a way of starting up Ember into different "modes". I.e. if you are a content creator, you would probably want to start it up in a mode where you get easy access to the asset manager and the model editor and other widgets which are suited for editing media, while if you start it up as a regular user you probably want to just connect to a server.
Further, we want Ember to be a general client which can support many different game types (at least that's the plan). While we now use the example world of Mason, it should be possible to start it up in a different game world mode. That would perhaps involve using a different skin, showing just a subselection of servers from the meta server (only those running a specific game type) and so on. I've though about perhaps using a scheme similar to the init scripts on linux (but with lua scripts), but I'm not so sure that's needed. However, we need some kind of mechanism for allowing different config files to be loaded depending on the game mode. That is however something for a different blueprint. This would be a nice addition anyway.
2012-02-14: The metaserver-ng is now has the concept of attributes ( arbitrary ), and will soon have a method of extending the listreq functionality ( https:/
