Who is working on what?

[z80_fr]

Is there a place where we could find who is working on what?

Jesper, have you setup something?

I ask that because I think it will be nice to know if for example I would lke to work on the battery status indicator. If someone already work on it, I'll loose my time on writting thing that are already existing.

I'm not at the point where I'll be able to be efficient because I've only started to read part of the code writen until now.
But when I'll feel confident to start writting and publishing code, then I'll like to know what subject I can work on without loosing time and energy.

[nilrog]

For now i'm just trying to fix a working flasher on OSX and if possible also Linux. But I have currently a large lack of spare time

[Jesper Hansen]

Developent is a bit chaotic at the moment, but it will be better as we find a way to distribute info about what we're working on.

[z80_fr]

I actualy read the code and try to understand how things works.

This afternoon I thought about other way for PREV and NEiXT song while playing a song.
But for the moment I've not the knowledge for modifying the code of Ypod.

[Botosu]

Can I suggest this approach ?

http://www.myplace.nu/mp3/yabbse/index.php?topic=3223.0
Problem and Solution.
 
We'll need one person (or 2) to collect the code and integrate it.
Always the final release will be made by Jesper.

[MIC]

Is there a place where we could find who is working on what?

For my part:
I have stopped working on the SVN code, because of lacking design/development rules. I'm not happy with the way development goes at the moment, neither with the results.
For now, I working on my own code version since my design requirements seems to be different from other developers.

Of course, bug fixes and other important code changes will go into the SVN code version.

[z80_fr]

Is there a place where we could find who is working on what?

For my part:
I have stopped working on the SVN code, because of lacking design/development rules. I'm not happy with the way development goes at the moment, neither with the results.

Humm.... that's why I asked for information about that.

For now, I working on my own code version since my design requirements seems to be different from other developers.

Of course, bug fixes and other important code changes will go into the SVN code version.

And are your design requirement are secret?
If not can I (we) have more information about what you are looking for?
(maybe could interest us and/or give idea)

[MIC]

They are not secret.
My priorities at the moment are power managment, bug removal, minimal code size and basic functionality, like ID3 tag, M3U playlist support, skin/theme support and user interface handling.

The actual codes already needs 50% of the flash space, and the code is not what I would call stable. So features like a spectrum analyzer are nice to have, but this is lowest priority for me.

Also I would design the GUI of the player after the rule: "Less is sometimes more." (free translated from German).

[z80_fr]

They are not secret.
My priorities at the moment are power managment, bug removal, minimal code size and basic functionality, like ID3 tag, M3U playlist support, skin/theme support and user interface handling.

Those functionality meet my wish

The actual codes already needs 50% of the flash space, and the code is not what I would call stable. So features like a spectrum analyzer are nice to have, but this is lowest priority for me.

I agree with you that spectrum analyzer to me look like nice tool but not usefull yet.

Also I would design the GUI of the player after the rule: "Less is sometimes more." (free translated from German).

Once again I agree. The best GUI is the most simple and intuitive.

Maybe we should open a new topic to discuss about the GUI and how we would like it to be and try to  select the best idea in every part of the GUI.
We also have to define the way of coding, I mean rules to follow when coding "module". That's if we decide to work as a team.

Or maybe people like more to work on their side?  I don't really know how dev's work on this forum since I've not been active member on this forum until the release of Ypod.

[ToS]

Really, I think it´s Jespers previlige to decide on how work should be distributed and how the s/w should be designed, I hope he takes help from the forum to solve tasks and find solutions to design issues. I Would prefer that we posts code solutions and Jesper uses copy/paste to implement the best solutions, cause I think the quality of the code might suffer if more than a couple of people get write access in the SVN.

As to MIC´s less is more approach to the GUI... no lets go wild and crazy...   I would like an implementation where we have a config file at the SD card that describes what text or icons should be used for what info... That way MIC could have his simple gui with text, and I could have my shiny progress bar and funky battery icon  

eg.

config.ini
battery_icon=on
battery_icon_xy=10,10
battery100%=batt_icon100.bmy
battery75%=batt_icon75.bmy
battery50%=batt_icon50.bmy
battery25%=batt_icon25.bmy
battery0%=batt_icon0.bmy
#battery_icon=off
#battery_text="%d.%d Volt",10,10

/ToS

[Jesper Hansen]

It's sad to hear you feel that way about it MIC, but I can understand that it happens.
Development is, intendedly, a bit loose until we've got some more basic features in and got used to SVN.  Assigning a specific developer to add a next and prev menu item, and updating a web-page or something that he's working on this, which is about 1 minutes work, is just silly and impossible. Later, we can then tighten it up and look at more (and larger) specific tasks. We can then also take advantage of the branches in SVN so we don't affect the main codeline.

I think we've had  a lot of functionality added during the latest week (although it's only in the repository right now, and not released), but we've got the player screen shined up, which was a requirement from some people, it shows ID3 tags (the code YOU sent me), it has a volume bar, realtime spectrum analyzer (about 10-20 lines of code only), next/prev song and in addition to that, I have working M3U playlist code.
I don't know about unstability, the player works 100% for me.

But, I was thinking of how releases should be handled. To make sure we have solid releases, only tested and working code should be committed to the repository. I will then, every few days (at the moment) make a public release.
Later, we probably need to set specific release dates, and list the features that will go into that release, then focus on those.

There is no immediate need for code (size) optimization. We have about 70 kB for further expansion and that is a LOT, considering that all base driver functionality is already there.
What I see as a feature we need to look at very soon is how the skin/themes can be handled in an effective and flexible way. Each individual user can then choose to design their UI as simple as they want.


Any views on this are welcome and I appreciate any feedback or ideas on how we can best take advantage of our resources.

[Jesper Hansen]

I created a new thread specifically for discussing the skin/themes.
Please keep this thread on the topic about how to handle development.

[nilrog]

Jesper, could you set up a mailinglist that we could subscribe to for commits to the repository so it is easy to keep up with changes? Just a simple hook in svn that sends the commit log message and a list of files that was touched in the commit. I'm interrested in what is currently going on but I haven't got all the time needed right now to check the repository commit log to see what happens.

[ToS]

Oh, no need for oldschool mail lists when we have SVN, lets try to stick to the forum as the way to communicate...

In explorer, select the folder level in your local copy of the repository where you want to view changes...
TurtoiseSVN->Check for modifications, now click the button check repository, and hey. better than any email, you can see wich files you have updated local, what files that are updated in the repository... And now.. Select a file that has changed with right click, select compare with working copy... And now you really see what has changed...

/ToS

[MIC]

It's sad to hear you feel that way about it MIC, but I can understand that it happens.

Jesper, there is nothing sad in what I said, it was just a statement of my actual thoughts and opinion 
But at the moment I don't know what else I could do. I will take up work on the official code as soon as we have some sort of development coordination.