0.5.5 is nearing completion, new website is going to be uploaded pending release, totally revamping the core from scratch to start working on BT++ 1.0 (nothing too advanced, faster load times, more sleek gui, fixing some bugs here and there, and keeping the interface simple). If any of you have suggestions for BT++ Future Development, you may post your ideas or contact me at keenan@olypen.com
Regards,
Cody Morrison
BT++ Project Admin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are a couple of things you could fix with BitTorrent++ .
1. Remove the need to hash files when the client is started.
2. It should be possible to see log information for, preferably for each torrent, but at least a global log.
3. On HTTP requests to the tracker you need to support compression (I'm not sure about this, but I got a bad feeling).
4. When disk is full, the torrent should be paused.
5. When the Transfer view is shown, BT++ uses way to much CPU time. If you're able to go back to the Log view, the CPU usage is dropped. This is especially present when having lots of torrents running...
6. When reaching some kind of limit of open files, BT++ shows a python log window with some errors, and BT++ is usually just dead.
That is what I remember now. I can't scare you away by giving you too many errors at first either... ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey Guys,
0.5.5 is nearing completion, new website is going to be uploaded pending release, totally revamping the core from scratch to start working on BT++ 1.0 (nothing too advanced, faster load times, more sleek gui, fixing some bugs here and there, and keeping the interface simple). If any of you have suggestions for BT++ Future Development, you may post your ideas or contact me at keenan@olypen.com
Regards,
Cody Morrison
BT++ Project Admin
Thats good to hear I've been eagerly awaiting the netxt release of BT++.
Also i'd like to say i've tried many Bt clients and so far BT++ is the only one that seems to work well for me.
So thank you, good job and please keep up the good work.
There are a couple of things you could fix with BitTorrent++ .
1. Remove the need to hash files when the client is started.
2. It should be possible to see log information for, preferably for each torrent, but at least a global log.
3. On HTTP requests to the tracker you need to support compression (I'm not sure about this, but I got a bad feeling).
4. When disk is full, the torrent should be paused.
5. When the Transfer view is shown, BT++ uses way to much CPU time. If you're able to go back to the Log view, the CPU usage is dropped. This is especially present when having lots of torrents running...
6. When reaching some kind of limit of open files, BT++ shows a python log window with some errors, and BT++ is usually just dead.
That is what I remember now. I can't scare you away by giving you too many errors at first either... ;)
What is the status of BT++ 0.5.5?
Roughly how many percent is done?
Is anyone still using BT++?
Annoying.
what about allowing to resume/stop more than one torrent at a time ? now I have to stop resume them one by one...