DevelopmentPlans/2.6.0 - Revision history

Blast at 22:26, 14 June 2015

2015-06-14T22:26:41Z

← Older revision		Revision as of 22:26, 14 June 2015
Line 56:		Line 56:
	## Generic server-controlled marker and hunt system.		## Generic server-controlled marker and hunt system.
	## Use BZID for all saved user identifiers not names.		## Use BZID for all saved user identifiers not names.

			==Misc==

			# Clean up platform code. For instance:
			## Make the ResInfo class also contain a depth value so that Windows doesn't have to have it's own custom Resolution class, and then sort based on the ResInfo items instead of platform specific sorting methods (Windows and Linux platform code have their own very similar methods).
			## Make the Linux platform code build again (which may be solved by just doing the ResInfo change). Note that SDL is the normal platform for Linux systems, so the 'Linux' platform code is for Linux systems without SDL.

	[[Category:Development Plans]]		[[Category:Development Plans]]

Alezakos: Add page to the Development Plans category

2013-06-06T10:41:13Z

Add page to the Development Plans category

← Older revision		Revision as of 10:41, 6 June 2013
Line 56:		Line 56:
	## Generic server-controlled marker and hunt system.		## Generic server-controlled marker and hunt system.
	## Use BZID for all saved user identifiers not names.		## Use BZID for all saved user identifiers not names.

			[[Category:Development Plans]]

Blast: /* Features */

2013-04-28T17:08:37Z

Features

← Older revision		Revision as of 17:08, 28 April 2013
Line 16:		Line 16:

	# Add new UI elements		# Add new UI elements
	## Dialogs		## [[DevelopmentPlans/Dialogs\|Dialogs]]
	### Modal dialogs are featured front and center, and require being dismissed by the user. They support hotkeys, server-specified buttons, or freeform menu items. Keyboard, mouse (including clicking items), and joystick interaction is supported.		### Modal dialogs are featured front and center, and require being dismissed by the user. They support hotkeys, server-specified buttons, or freeform menu items. Keyboard, mouse (including clicking items), and joystick interaction is supported.
	### Unobtrusive dialogs show up as smaller semi-transparent boxes towards the edge of the screen and support only hotkeys (keyboard, mouse button, joystick button) for interaction.		### Unobtrusive dialogs show up as smaller semi-transparent boxes towards the edge of the screen and support only hotkeys (keyboard, mouse button, joystick button) for interaction.

Blast: /* Goals */

2013-04-28T15:34:14Z

Goals

← Older revision		Revision as of 15:34, 28 April 2013
Line 4:		Line 4:

	==Goals==		==Goals==

			This list covers the major goals of this release, and the features related to each goal.

	* Tutorial Mode (1.1.1, 1.1.2, 4.1, 4.2, 4.3, 5.1, 5.2, 5.3, 6.1, 6.2, 6.3, 7.1, 7.2)		* Tutorial Mode (1.1.1, 1.1.2, 4.1, 4.2, 4.3, 5.1, 5.2, 5.3, 6.1, 6.2, 6.3, 7.1, 7.2)

Blast at 15:31, 28 April 2013

2013-04-28T15:31:25Z

@@ Line 31: / Line 31: @@
 ## BZDB controlled attributes
 ## Mesh bases/teleporters
 # Server Side Players
 ## Server-side shot path tracking
@@ Line 40: / Line 45: @@
 ##* Locale
 ## Implement MsgAllow from 2.99.x (or should this be part of the per-player name/value pair system?)

Blast: /* Overview */

2013-04-28T14:47:11Z

Overview

← Older revision		Revision as of 14:47, 28 April 2013
Line 1:		Line 1:
	==Overview==		==Overview==

	2.6.0 will be a new ~~major~~ release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving the flexibility of the user interface.		2.6.0 will be a new breaking release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving the flexibility of the user interface.

	==Goals==		==Goals==

Blast: Created page with "==Overview== 2.6.0 will be a new major release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving t..."

2013-04-28T14:27:00Z

Created page with "==Overview== 2.6.0 will be a new major release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving t..."

New page

==Overview==

2.6.0 will be a new major release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving the flexibility of the user interface.

==Goals==

* Tutorial Mode (1.1.1, 1.1.2, 4.1, 4.2, 4.3, 5.1, 5.2, 5.3, 6.1, 6.2, 6.3, 7.1, 7.2)
* Easier polling system (1.1.2, 2.1, 2.2)
* Useful MOTD (1.1.1, 3.1, 3.2)
* Better localized messages (4.1, 4.2, 4.3, 5.1, 7.1)
* Additional mapping features (5.1, 5.2, 5.3)

==Features==

# Add new UI elements
## Dialogs
### Modal dialogs are featured front and center, and require being dismissed by the user. They support hotkeys, server-specified buttons, or freeform menu items. Keyboard, mouse (including clicking items), and joystick interaction is supported.
### Unobtrusive dialogs show up as smaller semi-transparent boxes towards the edge of the screen and support only hotkeys (keyboard, mouse button, joystick button) for interaction.
# Revamp the poll system
## Add an actual message type to the protocol for the poll system (MsgPoll and MsgVote, perhaps, or just build it with generic dialog message types)
## Add an unobtrusive dialog for polls with support for both the old style /vote command and polling/dialog key bindings.
# Revamp the MOTD
## Update client MOTD code to send the client version and other system information (operating system and similar) to the server. The MOTD server would then use this information to send appropriate MOTD entries.
## Have the MOTD code detect when there is a new MOTD and pop up a modal dialog. Include a MOTD menu item for later access.
# Font system and language support
## New font system (FTGL or similar)
## Add the additional fonts and better translations from 2.99.x.
## Send the client locale to the server so that the server could localize messages sent to the client
# Map features
## Text object (from 2.99.x)
## BZDB controlled attributes
## Mesh bases/teleporters
# Server Side Players
## Server-side shot path tracking
## Shared client logic library used in both the client and server.
## Ability to spawn and control SSPs from a plugin.
# Other
## Add a per-player name/value pair system. This would be used for data like:
##* Motto
##* Locale
## Implement MsgAllow from 2.99.x (or should this be part of the per-player name/value pair system?)