Re: [Freesynd-devel] The Icon and other stuff

Hi,

Why making a 0.7.1? I'm not against it but do we have something that worths
a release?
Or is it just that you want to accelerate the number of release (which is
fine by me)?

About the list of functionnalities, it's the other name for roadmap.
The current todo list has tasks like "Correct identification of object
types during mission load, includes vehicles, static objects".
This may be something we have to do but it's a bit too specific. It doesn't
help in seeing what has to be done globally to finish the game.
There should be something more like "implement trains animation" or
"implement music variations".

We could also look at the different missions. Is every mission playable?
what need to be done in each mission so it can be played?

So first : what do we put in 0.7.1?

Benoit


2013/3/29 Bohdan Stelmakh <cha...@ma...>

> Hi,
>
> > Should we add an icon ?
> > Isn't there already an icon? There's an icon directory in the trunk. I
> > thought someone did the work a time ago, adding an icon for the different
> > platforms (apple, unix and windows).
>  This icon is directly copied from syndicate's logo - very bad thing. We
> need to
> have our own.
>
> > I don't like that google code style
> > guide promots short functions < 40 lines - I don't want to follow that
> rule,
> > I will continue to write funcions as large as I think they should be.
> > Well, I can't force you if you don't want, it's a free world. But I do
> > believe that shorter methods help in understanding the code specially if
> > method calls are well organized and method names are well chosen. This
> rule
> > is commonly adopted now and you will see it in many code analysis tool.
>  For me, its harder to understand such code, as it needs jumping to see
> what is under
> function and then go to previous and then again start thinking about
> function
> I was looking at. I acknowledge that if I would be looking at code first
> time
> I would have basic idea what it does faster, but in order to know code
> more deeply,
> it would take more time then large function not broken into single use
> functions,
> due to jumping to look at those functions. Due to objective programming we
> already
> create single use(call) functions and now we should be splitting those
> into smaller
> chunks just to give someone ability of fast "first look" at code, but with
> hard
> "deep look" at code... It is common for me to see people smoking tobacco
> based
> products, should I start smoking?...
>  The complexity human is capable to understand is always dependent on its
> size,
> abilities and knowledge and will of person.
>  You think that you decrease size of code to understand, but have you
> counted
> lines, before and after shortening, of all code?
>  What about "abilities and knowledge and will of person", is there same
> static
> condition like "< 40 lines" for those, that will require us to base our
> code
> on it? Just consider this, no need to answer.
>
>  Be realistic there are 2 of us and random contributers from time to time.
> When
> I'm not willing to implement something I review code, my, then yours, then
> all.
> Simplifying logic, removing old unused/never used(prototype code),
> optimizing,
> adding comments, completing, fix something, there is so much to do.
>  0.7 was released after almost a year, 0.7.1 - April?, 0.7.? - when? I'm
> not
> enthusiastic about coding, as all simple stuff we have already written and
> now
> the hard part to code remains. If we will not be doing what is actually
> needed the 1.0 will be released in 2020 or never.
>
> > Do we need a lot of changes to release 0.7.1? What needs to be done? I'm
> > confused.
> > To me, the only reason of a 0.7.1 release was that you wanted to finish
> > something that you thought was not complete when we released 0.7
> ("Although
> > we can release it now, I will continue improving directional pathfinding
> > later."). Other than that, I don't see other important subjects that need
> > to be released right now.
>  I have no idea how to improve dir. pathfinding for peds. I will probably
> use
> normal pathfinding there, as it can reach required location, but there is
> a problem
> with Z coordinate.
>  I thought we will fix style and fix some code, actually we didn't discuss
> 0.7.1
> roadmap.
>
> > But I agree, we need to make a list of functionnalities that need to be
> > implemented to finish the game. The current todo list is a bit too
> > code-oriented.
>  Oh - no, not again. We discussed it in past and I don't remember good
> results.
> How without code we will have features? Or you are refering to, how
> required
> feature should work, how implement it?
>
> --
> Bohdan Stelmakh (chamel)
>
>
> ------------------------------------------------------------------------------
> Own the Future-Intel(R) Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest. Compete
> for recognition, cash, and the chance to get your game on Steam.
> $5K grand prize plus 10 genre and skill prizes. Submit your demo
> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
> _______________________________________________
> Freesynd-devel mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freesynd-devel
>