Feature planning for v3.0

[Dovyski]

This issue is aimed to keep track of the features/changes planned to land on Flixel Community v3.0.

Feature/Change	Author	Complexity
Moving classes into folders: core (FlxBasic, FlxObject), graphics (FlxSprite, FlxText), etc (#194) Added in ca946ab	@WingEraser	Minor
Make Flixel GPU accelerated (#90) WIP in #219	@Dovyski	_Major_
Organize FlxG and FlxU a tad better (#142) Forum post about it.	@IQAndreas	Minor
Add math vector methods to FlxPoint (or create FlxVector) (#188)	@Dovyski	Minor
Add more colors to FlxG (or preferably, FlxColor) (#141)	@IQAndreas	Minor
Add FlxRandom seeded random generator (#197) Added in 8bad64f	@IQAndreas	Minor
Move static constants on path following from FlxObject to FlxPath (#112) WIP in #218	@IQAndreas	Minor
Merge a part of Flixel Power Tools into code tree (#163)	@IQAndreas	_Major_
Rename and add FlxDebugger functions (discussions) WIP in #217	@IQAndreas	Minor
Improve plugin system (#121) WIP in 79450d8	@WingEraser	Medium/Major
Create tutorials for Flixel Community website (issue #3 on flixelcommunity.github.com)	@Dovyski	Minor

After adding an entry to the table, please, post a comment discussing it.

[IQAndreas]

Nice table! Thanks for filling everything in.

Shall I copy over some of the discussion as well, or should we just continue from where we left off?

[IQAndreas]

Merge a part of Flixel Power Tools into code tree (#163)

As for this one, I was thinking primarily of these classes, as they would compliment #141 and #142:

• FlxColor
• FlxMath

But others can of course come in as well if they fit in better as part of the core rather than plugin.

[WingEraser]

If you don't mind, I can take #142 as well while I'm refactoring the classes.
EDIT: also #141

[IQAndreas]

If you don't mind, I can take #142 as well while I'm refactoring the classes.

Aw, I was actually looking forward to doing those. 😛 If it's alright that I do those, I had some plans on how to group the "deprecated redirect" methods.

But I do think, if we move everything into packages, since it affects so many files, that should be done before any other changes so as to avoid merge conflicts. Do you have an IDE where you just drag and drop the classes to their new locations, or do you need to do that work manually?

[WingEraser]

I got FDT4 which should work out. I'll let you handle the #141 and #142. I'm going to start this weekend with a folder structure and put it in a separated issue.

[IQAndreas]

Just a quick check first, we already talked about the cons of some of these proposed v2.58 features by email, but is there anyone that is adamantly against any of the changes or feel they should not be used?

[Dovyski]

Shall I copy over some of the discussion as well, or should we just continue from where we left off?

Let's continue from where we left off.

is there anyone that is adamantly against any of the changes or feel they should not be used?

I'm ok with all changes! Of course I would like to discuss some things, such as which parts of Flixel Power Tools should be merged, which new singletons to create (e.g. FlxM, etc), etc, but all that can be done as we move to the implementation of each task.

[Dovyski]

I can take #90 to start working on Stage3D support for Flixel. It will take a lot of experimentation and prototipation. Anyone else interested on this particular issue?

[WingEraser]

I can take #90 to start working on Stage3D support for Flixel. It will take a lot of experimentation and prototipation. Anyone else interested on this particular issue?

I will join, but only for the thinking part. Can't start with this yet until next year, when I got more free time.

[IQAndreas]

Of course I would like to discuss some things, such as which parts of Flixel Power Tools should be merged, which new singletons to create (e.g. FlxM, etc), etc.

Excellent. I have already started on said discussion in #142 (comment), just chime in there. Or should I create a separate issue for FlxMath and another for FlxColor?

[IQAndreas]

On a related topic, now that we have a stable release that is publicly available, shall we change the main (default) branch displayed in the repository to master? (currently, it is dev)

[Dovyski]

I will join, but only for the thinking part. Can't start with this yet until next year, when I got more free time.

Great! I will post my ideas on #90, we can discuss everything there.

Or should I create a separate issue for FlxMath and another for FlxColor

Let's use the already open issue, it's easier to follow the discussion.

About the main branch displayed in the repository, I totally agree about using master. I thought I was the only one seeing dev as default =P

[FlixelCommunityBot]

Flixel v3.00 (CHANGELOG)

TODO: Insert description of this release

Repository changes

Change main package from org.flixel to just flixel (#194)
Organize Flixel's classes into several, more logically organized packages (#194)
Rename FlxAnim to FlxAnimation (#205)

New Features

New plugin system based on FlxSignals (#121)

Improvements

Example improvement (#0)

Performance Improvements

Example performance improvement (#0)

Bugfixes

Example bug fix (#0)