 |
|
You are not logged in.
Hi.
I've been a long time musikCube user and I love it. I've introduced it to all my friends and they are using it now because of it's speed and simplicity.
I think it's great that developers are working on mC2 but in the mean time someone should address the bugs on the current 1.0 branch. Not to mention that the website still displays the final version from 2006.
I'm volunteering here to work on a series of maintenance releases every two months or so. I think that whatever I can release in those two months should be better than having the same version in the website and the same errors reported over an over.
This is what I have planed:
* Keep working on my code base which is based on the original 1.0 release at SourceForge.
* Incorporate all the bug fixes that have been provided by the community. I've seen several on this forum.
* Fix as much bugs as I can from this list: http://www.musikcube.com/punbb/viewtopic.php?id=1299
* Incorporate small feature request from that list. Those that don't require a complete rewrite of the source to have them implemented.
* Release 1.0.x versions until one of those can be called musikCube 1.1.
If all of you are comfortable with me intruding, I already have fixed a crashing bug on the dock bar and added a global hotkey for the quick search in the version I'm using now.
Cheers.
Offline
Hi!
Jooles was the lastest guy who fight with the mC1 code 
. He has made some patched EXEs whoch can be found here.
The bugs from my list are also in the new bugtracker trac.
The most annoying bugs are the "Reset View bug" and the bugged tag-writting.
Last edited by DocTriv (2008-03-03 05:20:36)
Offline
Hello jcarrascal,
You're more than welcome to maintain 1.0 if you'd like. I'd recommend using my personal repository located here:
http://svn.clangen.org/musikCube/
I spent a good 2-3 weeks cleaning up the code base, renaming files, classes, structures, adding namespaces, etc to help make things a little easier to figure out. There were also a couple other developers who organized the source tree into a more sane arrangement, and improved the build process overall.
This source base requires Visual Studio 2005.
If you're interested let me know, and I can set you up with commit access on the repository.
Offline
Hi DocTriv and avatar3d.
That's excellent. I can port my modifications to your code base and start working on top of it.
Offline
Great. If you get to a point where you'd like to check in some changes give me an email at: casey at musikcube dot com.
Offline
Just so the community is informed... I've been granted commit access for the 1.0 branch and that I'll be working on bug fixing and hopefully release a 1.1 version in the following months.
Thanks Casey.
Offline
Awesome. That's great news and good to hear. I look forward to seeing your work.
Thanks for your interest in the project.
Offline
I look forward to this too 
Offline
Sounds great indeed! If you need testers and feedback, call us.
Offline
Does Casey's latest repository linked above includes the changes Jooles made?
And are actual plugin still compatible with newer builds (I think I read somewhere they are not anymore)?
Offline
Yes, they seem to have the "Smart Previous" song fix by Jooles. I don't know if it's compatible with other plugins but if not that's another bug to fix.
Offline
Some plugins are, some aren't. The plugin API changed slightly for the 1.0 release and broke some of them. But between 1.0 and the bugfix releases, there has been no change to the plugin system, so anything that works (or not) in 1.0 will be the same in 1.01. Trouble is, many of the broken plugins have no source code available.
Offline
I know the previous developers setup a "trac" issue tracking system at https://opensvn.csie.org/traccgi/musikCubeReloaded, but it appears to go up and down, and is always slow. I've setup a trac instance on my personal server for the new maintenance brach, available here:
http://musikcube.clangen.org
Feel free to use it, or not, but it should always be available.
Offline
Can we migrate the bug reports ("tickets") from "musikCubeReloaded" to your trac installation?
There are at least some download options.
Offline
Okay, the old tickets and wiki have been migrated over to the new site. If you previously registered a user account you may need to re-register.
Offline
Nice!
I made an account there, updated probably all now outdated links to the old trac/source location in the forum and also edited the old trac wiki (maybe it can be closed/deleted).
Now I have to get to know how to make a query about all changes in the tickets - my RSS feed did not mention me about jcarrascal's discoveries regarding the genre tag writing bug.
Last edited by DocTriv (2008-03-03 06:06:49)
Offline
Anything new from the bugfix release? Builds to test?
Offline
I make some changes to both musikcube and mc2 tracs wiki to add links.
In the changelog on trunk of musikcube we can read :
1.1a
- bugfix: read/write MP3 ID3 tags (0 interpreted as empty) [core_mp3]
But there is also all Jooles works ?
Offline
It was said that Jooles' changes are included there, but I don't know exactly.
(A binary build is not available yet?)
Offline
Nice to see someone is working on it. I'll try the new builds one they get available. I hope bug #12 gets fixed as this is crucial to me 
Offline
Really it is a very good news for us. Hopefully we will get this version soon. I want to know more about the tracking system. Please let me know.
Offline
Sadly until I can save up the few hundred pounds I need for a new computer I still can't do any work on mC2. It *will* come I just don't know when...
Offline
