What I'm thinking about for the 1.3.0 release
Posted: 20 Oct 2014, 16:54
This is the list of items I'd like to tackle for a 1.3.0 release (I'll be trying to do releases more along the lines of 1.3.0, 1.3.1, etc. -- quicker releases with smaller features than we've had in the past)
These have been chosen to be quicker-and-safer to implement for a first pass, add what are only optional features (so I shouldn't affect existing users who don't want the features too much), and give me a good look at different parts of the code.
I could go for a 1.2.1 release, but I thought moving from 1.2 to 1.3 would be a good differentiator between the Jerome releases and the Joshua releases.
PRIMARY GOALS
- fix the crash bug with space bar input
- add a "shadowalpha" attribute (value from 0.0 to 1.0, default is what it is now, which I'm guessing is less than 0.5), so you can set how dark the shadow is on counters, cards, and terrain - per item with shadow
- add an "outline" attribute (value will be the width), which will put a (square) black border around the item (counter, terrain, probably cards too)
- add two (optional) URL values (tags or attributes, not sure yet):
- one would activate a new button in the Multiplayer menu, which would launch the machine's web browser to the matchmaking/chat web page for the gamebox
It would probably be labeled something like "Player Match Web Site..."
- the second would activate a new button in the File menu, that would launch the machine's web browser to the website that the publisher would like to provide more info on the game (could be the game's info page, could be the game's store page, could be the rulebook PDF for publishers who wanted to do that).
It would probably be labeled something like "Gamebox: More Info..."
STRETCH GOALS
- (depends on how quickly the above come together) add xoffset and yoffset attributes to stacks, which would control the direction and distance-between-items of any given stack. There would be global attributes (stackxoffset and stackyoffset) and then those could be overriden in a particular stack with xoffset and yoffset). Default would be what they are now, so existing users shouldn't be affected.
- (depends on outline, above) add an "outlinealpha" attribute so you can make that outline translucent (it'd be like a shadow, but it goes around all the sides and has the wide of the outline attribute value). Default would be 1.0 (no translucency; fully opaque)
...
Thoughts?
-- joshua
EDIT: Changed target version number from 1.3.1 to 1.3.0 (because programmers count from 0)
These have been chosen to be quicker-and-safer to implement for a first pass, add what are only optional features (so I shouldn't affect existing users who don't want the features too much), and give me a good look at different parts of the code.
I could go for a 1.2.1 release, but I thought moving from 1.2 to 1.3 would be a good differentiator between the Jerome releases and the Joshua releases.
PRIMARY GOALS
- fix the crash bug with space bar input
- add a "shadowalpha" attribute (value from 0.0 to 1.0, default is what it is now, which I'm guessing is less than 0.5), so you can set how dark the shadow is on counters, cards, and terrain - per item with shadow
- add an "outline" attribute (value will be the width), which will put a (square) black border around the item (counter, terrain, probably cards too)
- add two (optional) URL values (tags or attributes, not sure yet):
- one would activate a new button in the Multiplayer menu, which would launch the machine's web browser to the matchmaking/chat web page for the gamebox
It would probably be labeled something like "Player Match Web Site..."
- the second would activate a new button in the File menu, that would launch the machine's web browser to the website that the publisher would like to provide more info on the game (could be the game's info page, could be the game's store page, could be the rulebook PDF for publishers who wanted to do that).
It would probably be labeled something like "Gamebox: More Info..."
STRETCH GOALS
- (depends on how quickly the above come together) add xoffset and yoffset attributes to stacks, which would control the direction and distance-between-items of any given stack. There would be global attributes (stackxoffset and stackyoffset) and then those could be overriden in a particular stack with xoffset and yoffset). Default would be what they are now, so existing users shouldn't be affected.
- (depends on outline, above) add an "outlinealpha" attribute so you can make that outline translucent (it'd be like a shadow, but it goes around all the sides and has the wide of the outline attribute value). Default would be 1.0 (no translucency; fully opaque)
...
Thoughts?
-- joshua
EDIT: Changed target version number from 1.3.1 to 1.3.0 (because programmers count from 0)