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

Plans for more Proofs #5

Open
16 of 23 tasks
SeiferTim opened this issue Jun 24, 2015 · 5 comments
Open
16 of 23 tasks

Plans for more Proofs #5

SeiferTim opened this issue Jun 24, 2015 · 5 comments

Comments

@SeiferTim
Copy link
Member

SeiferTim commented Jun 24, 2015

I think I've come up with most of the Concepts that we need - there might be a few more to add (Nape?)

Here are some ideas for proofs and other topics to cover:

  • Basics:
    • Adding objects
    • Talk about things like Draw order?
    • Explain alive, exists, kill, revive, destroy?
  • Text:
    • Input Text? Is that a thing, or am I imagining it...?
  • Movement:
    • thrust-style movement?
  • Groups:
    • More recycling 'tricks', getFirstAvailable, etc.
    • sort
  • Overlap:
    • Pixel-perfect overlap
    • group overlap
  • Tiling:
    • raycasting
    • tile properties (one-way tiles, etc)
  • Camera:
    • flash
    • fade
    • follow with different kinds of following styles
    • multiple cameras
  • Input:
    • keyboard input
    • mouse input
    • touch/gamepad/swipe?
  • UI:
    • scrollFactor? (might belong in Basics, instead?)
    • buttons
    • talk about flixel-ui?
  • States:
    • switchState
    • substates
@Gama11
Copy link
Member

Gama11 commented Jun 24, 2015

Draw order should definitely be covered - sorting by z, custom sorting functions. Very commonly asked question.

There's FlxInputText in flixel-ui, but it doesn't work that well.

States also needs to cover resetState.

scrollFactor isn't really specific to UI (parallax scrolling, your demo... ;))

@SeiferTim
Copy link
Member Author

scrollFactor probably belongs in camera?

@Gama11
Copy link
Member

Gama11 commented Jun 24, 2015

Yeah.

@Geokureli
Copy link
Member

Geokureli commented Dec 31, 2021

FlxTilemap is incredibly hard to learn. people don't really think to look in the base class and demos don't cover many of the fundamental features. it's such a common feature for newcomers and not everyone learns from stepped tutorials and demos I think snippets should cover or at least mention:

  • how tilemaps are structured
  • loadMapFromCSV, loadMapFromArray, loadMapFromGraphic
  • setTileProperties
  • colliding with a tilemap
  • autotiling

@Geokureli
Copy link
Member

Geokureli commented Apr 28, 2024

  • we need to remove Health as this feature is being deprecated
  • I'd like to redo some of the collision proofs, they don't really showcase the collision system that much, they seem more like tweens
  • Same with Gravity and MaxVelocity, it seems like a tween
  • I'd like to simplify Jumping, and add the current proof as "Variable Jumping"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants