Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What do we want in 0.7? #277

Closed
pathunstrom opened this issue May 20, 2019 · 15 comments
Closed

What do we want in 0.7? #277

pathunstrom opened this issue May 20, 2019 · 15 comments
Labels
discussion Issues that more just discussing than specific flaws or features wishlist

Comments

@pathunstrom
Copy link
Collaborator

0.6 is coming to a close, which means we need to start discussing our next release. Since there's a lot more stakeholders this time around, I'm making an explicit issue here to discuss this. This discussion will become the basis for the 0.7 project board.

If you're suggesting a topic, please put it in a separate message, and everyone who cares can vote up or vote down with a reaction.

Discussion can go between suggestions. I'll try to keep this OP up to date with all of the suggestions.

@pathunstrom pathunstrom added discussion Issues that more just discussing than specific flaws or features wishlist labels May 20, 2019
@pathunstrom
Copy link
Collaborator Author

Suggestion: Really focus on documentation

@pathunstrom
Copy link
Collaborator Author

pathunstrom commented May 20, 2019

Suggestion: Rebuild renderer to handle new rendering contexts and make layering #276 a thing.

(Edit by @astronouth7303: This will enable future work for text #146 and canvas sprites)

@AstraLuma
Copy link
Member

Suggestion: Sound

@AstraLuma
Copy link
Member

AstraLuma commented May 20, 2019

Suggestion: Resource revamp #147

(This is kind of a prerequisite for the sound and render context work.)

@AstraLuma
Copy link
Member

AstraLuma commented May 20, 2019

Suggestion: Regions and Physics feature #121

This would allow you to describe the physical shape of your sprite (probably just square and circle to start with), and do collisions based on it.

@AstraLuma
Copy link
Member

AstraLuma commented May 20, 2019

Suggestion: Behavior Trees and Finite State Machines.

(I'm including this because it's been discussed as a feature, but I'm personally of the opinion we've got bigger fish to fry.)

@AstraLuma
Copy link
Member

AstraLuma commented May 20, 2019

Suggestion: Subsprites and Camera-attached sprites.

Roughly, making a sprite that's a child of a sprite or a camera meaningful.

This pretty much depends on #128 / #229 .

@AstraLuma
Copy link
Member

Suggestion: Stacking scene rendering with alpha backgrounds. #143

@AstraLuma
Copy link
Member

Suggestion: Gamepad support

@AstraLuma
Copy link
Member

AstraLuma commented May 21, 2019

Suggestion: Actions feature

This is an abstraction layer to translate raw input events into semantically meaningful actions. Also, handles different input modes.

@nbraud
Copy link
Contributor

nbraud commented May 31, 2019

Regions and Physics feature

@astronouth7303 What do you mean by Regions there?
In any case, I would be pretty keen on having a stab at a declarative-ish thing for specifying dynamics.

@AstraLuma
Copy link
Member

AstraLuma commented Jul 7, 2019

Ok, so here's what I'm seeing based on this:

  • Docs
  • Resource/asset rewrite
  • Sound
  • A physics systems (all @nbraud's doing)

@pathunstrom
Copy link
Collaborator Author

How long do you think a prototype of your imagining for resources/assets be?

Since Sound is going to need to lean on it somehow.

@AstraLuma
Copy link
Member

I've already done the initial prototypes. Need to round it out into a data model integrated with the ppb system.

@AstraLuma
Copy link
Member

Closing in favor of https://github.com/orgs/ppb/projects/7

@AstraLuma AstraLuma pinned this issue Sep 30, 2019
@nbraud nbraud unpinned this issue Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Issues that more just discussing than specific flaws or features wishlist
Projects
None yet
Development

No branches or pull requests

3 participants