XiXMusicPlayer on Sourceforge

[Zittergie]

Hi all,

at last, I have put up a sourceforge page for XiXMusicPlayer:  http://sourceforge.net/projects/xixmusicplayer/
It are my first steps joining source code with sourceforge and SVN.

Anyone who wants to help this project, and in the process help me to enhance my knowledge about pascal, opensource and svn, is very welcome....

[minesadorada]

Thank you for making this.  Very nice look and functionality.

[Leledumbo]

Aha! Now I can modify the source myself to implement the missing close to tray feature.

[Zittergie]

Leledumbo: that option is already available in the svn-source   

[Leledumbo]

Leledumbo: that option is already available in the svn-source 

Oh, thanks then
Btw, your repository layout seems broken. svn co-ing trunk results in empty directory and when I view it online, the sources are outside of trunk, even under the same directory as branches, tags and trunk itself.

[JD]

I love your work. The fact that it is multi-platform is a very good thing. May I ask where is the svn-source version with the minimize to tray feature?

Thanks,

JD

[Zittergie]

This is all new for me, so if you see any mistakes or have tips, let me know.

To import the SVN use:

Code: [Select]

svn co svn://svn.code.sf.net/p/xixmusicplayer/svn xixmusicplayer
To update the sources:

Code: [Select]

svn update

Not included in the SVN are:
- BASS libraries: http://www.un4seen.com
- BRGABitmap


I would also like to know how to work on the code with more people.  How do you always work with the latest source available if you commit changes with different people.  So I think I will need to read some more about SVN 

[Leledumbo]

This is all new for me, so if you see any mistakes or have tips, let me know.
...
I would also like to know how to work on the code with more people.  How do you always work with the latest source available if you commit changes with different people.  So I think I will need to read some more about SVN 

Yes, you do
Otherwise, it's hard to keep up stable releases (tags), bleeding edge (trunk) and forks (branches) at the same time. Where should people commit? How do you keep the stable version free from breaking changes?

For now, please move the latest source to trunk. Let's assume you never release a stable version. From this trunk, whenever you're ready to release a new stable version, create a tag from the trunk snapshot at that time and exclusively work on that for fixes (possibly merging the fixes commits back to trunk) until you think it's bug free enough to be released.

[Zittergie]

For now, please move the latest source to trunk.

Done.  Thanks.

[jesusr]

Hi, great program, congratulations!

I found some problems on reading and saving tags, I opened a ticket in SF about it and attached a patch for it

[Zittergie]

Thanks,

patch applied.  Help is very appreciated. 

BTW: ordered "Pragmatic Guide To Subversion"

[jesusr]

Thanks.

In the mean time I have fixed a number of bugs and implemented some TODO features:

- Fill Tags from filename sometimes ignores some fields
- Fill tags changes are ignored
- Quick button for filling tags doesn't work or sometimes ignore changes
- Tags changes are not reflected in the tag fields
- Implemented propagating of re-tagging changes back to main form
- Implemented multiple artist selection
- Implemented changing the case on tags: all caps, first letter on each word, first letter on first word

The changes involve some refactoring of the code which allowed to remove many repetitive code on the re-tagging side, and I'm still trying to figure out how to make it reusable and easy to read.

What I would like now is to add a tab for browsing the database in "virtual filesystem" because sometimes files are already orderer and tagging of such files would become easier.

[Zittergie]

I like the idea about the filenavigation in a "virtual filesystem".

Maybe we would need to make an option to choose the Tabs you want to see, because adding too much tabs will make it less comfortable to use.  If you only show the ones you want to use, it will be more easy to navigate.  Maybe a possibility to save these in presets.

[CM630]

I just found three bugs:
1. It won't play files which contain cyrillic letters in WinXP.
2. ID3, v1 tags are not read.
3. Cyrillic ID3 tags are displayed as monkeys (CP1252 instead of CP1251) if they are encoded as ASCII. Encoding shall be performed according system settings (Language for non-unicode programs).

And there is a gread drawback of the File Manager- there is no place where users can paste the path to a folder of a file.

[Zittergie]

When compiled with Lazarus 1.4 it seems fine, but when compiled with svn trunk (1.5) cyrillic and other foreign chars seem to be a problem.
At first I thought it was connected to FindAllFiles, but it will probably be something else.
Haven't looked deeper at it yet. The only Windows Device I have to compile and test is a cheap Windows 8 tablet :-) so all help to spice up the windows version is welcome.