1 Nov 11:03
Re: goals vs requirements
Ralf Engels <ralf-engels <at> gmx.de>
2003-11-01 10:03:23 GMT
2003-11-01 10:03:23 GMT
Hi, Again I had some answers that I want to comment: Ed is giving some good cases for modularity. I just want to point one thing out: minimal interface. Having a small (but complete) interface is the corner-stone of a modular development. This is currently not the case. The PlaylistManager alone has around 30 functions, sends four events and has it's fingers all over the place. I tried to change this and belive me it is extremly hard. Please try this too so that you can see for yourself why I wanted a structured development process. This is not about re-writing the code. This is about finding out what needs to be fixed. Kristian is writing about two different points. First about the metadata issue. Kristian, I am totally agains saving meta-data in a playlist item. As we found out (via the requirements) we only need to determine the meta-data in very special cases. Again I encourag you to write a working design in the requirements document, a simple text file or in comments. Please feel free to change what you like, but GOD DAMN DO IT. I can't understand the current design and every sentence you are writing is confusing me more. What exactly does the music-catalog do? Please write it down or you will be the only person that can write code for this. Another point is the work-split between player and playlist. current: getNextSong getPreviousSong -- player-playlist(Continue reading)
RSS Feed