FIFE forums

FIFE Development => Framework development => Topic started by: prock on March 29, 2012, 04:53:41 pm

Title: Prioritizing our time/efforts
Post by: prock on March 29, 2012, 04:53:41 pm
Hi All,

As you know I'm trying to get a list of priorities together for the direction of FIFE.  I'd like to have these discussions throughout the summer, have the milestones set out, and be able to start on some major components by the time GSoC is complete this year (or even before if possible).  I have placed a bunch of our ideas from the FIFE 1.0 meeting we had as well as a bunch of existing tickets into a document on the wiki available here (http://wiki.fifengine.net/PrioritizedTasks).  Please review it and add any items you want for consideration there.

What I'd like to do in this thread is gather the high priority major component items for FIFE 1.0.  These are items that we MUST include in 1.0 and cannot be left out under any circumstance and they are a major chunk of work.  Once we have a list of high priority items we can begin breaking them down into a logical sequence of implementation which will be used to help derive our milestones.  The rest of the tasks will hopefully fall in there somewhere.

Here is an example of a list (in no particular order)

I just threw that list together off the top of my head...  What do you guys think?
Title: Re: Prioritizing our time/efforts
Post by: prock on March 30, 2012, 09:57:02 pm
Also if you guys have some ideas floating around in your head on how we can improve FIFE please add them to the correct section on the Prioritized Tasks (http://wiki.fifengine.net/PrioritizedTasks) list on the Wiki.. It can be anything at all no matter how crazy it might seem.  Lets get all these ideas out there.  Continue to think about priority though as it would be nice to have this hammered out soon.
Title: Re: Prioritizing our time/efforts
Post by: Nihathrael on April 03, 2012, 03:25:11 pm
Here's a list from the top of my head going through the list at the wiki:
Number 1-10:
(Yep, it is that important :P)

11 and following (no order):

Basically none of the features here http://wiki.fifengine.net/PrioritizedTasks#New_and_required_features_for_FIFE_1.0 are required by Unknown Horizons. I'd rather focus on improving the other stuff.

Cheers
Title: Re: Prioritizing our time/efforts
Post by: chewie on April 03, 2012, 03:26:09 pm
As FIFE 1.0 is a really big and important milestone it should IMO include these things: (no order, prolly not complete yet :D)


My main thought about it is that there be less "Oh, FIFE can't do XY" statements from outside spectators and instead more "Wow, I had no idea FIFE can do that" statements. 8)

Very important task IMO:

Unification of FIFE-object management aspects. ATM there are things which are managed by FIFE and retrievable by the client (e.g. images, instances, layers, maps, cameras etc..) and there are things which are not managed by FIFE, instead each client implements (should implement) a small manager on it's own. From the top of my head those FIFE-objects are:


I bet there are some more, and the general idea why this is bad: there is this pending owner ship problem between python & c++. With a proper fife.engine.get(manager, component, id) system, this could be adressed althogether and clients won't attempt to store fife-objects on their own (and therefore prolly introduce problems in their code if not done correctly) and instead only have to store the means on how to get the fife-object (e.g. layer.getInstance(instance_id))

Some ideas into this direction are the current implementation of the ImageManager, the pending thoughts about SceneManager, FontManager etc.
Title: Re: Prioritizing our time/efforts
Post by: prock on May 25, 2012, 03:14:59 pm
I'm going to add a couple more topics to the priority list... 
Title: Re: Prioritizing our time/efforts
Post by: prock on June 08, 2012, 11:38:36 am
Also on the priority list is attracting new developers.  We have a lot of tasks to do, time to start actively recruiting.  I'd like to get the coding standards worked out, the API changes applied, source code documented, and the website and wiki up to speed before actively recruiting.  The project has been in a bit disarray for some time so it's time to tighten things up a bit.  A process that I'm not looking forward to but needs to be done regardless.