July 3rd, 2002
|
| Apprentice | | Join Date: July 2nd, 2002 Location: Alameda, California
Posts: 6
| |
Quote: Originally posted by tshdos
Some problems that should be looked at
1. Very boring, plain interface. Some may like this, I don't.
>> Subjective- I've tried to avoid some of the horrible garish GUI's I've seen. In actual fact the GUI uses the latest XP common controls.
2. No advanced features. I guess this may be a good thing for some people.
>> Like what? When I conducted an informal survey the #1 feature request (by far) was better downloads. Compare QP's d/l with any other client. It has the best and most robust implementation of swarm downloading.
3. Text in the list (connections) should be replaced by something more descriptive for the average user (ie SOCK_CONNECTED should be replaced with Connected or something )
>> Good point.
4. Connections window should tell you what type of client you are connected to... since it supports 0.6 handshake this would be VERY easy to add.
>> On the to do list.
5. Blank message boxes. I have gotten a couple of errors where the message box had no title or message ???
>> Beta bugs, I'll look at this right away.
6. When you initiate a search it just adds the term to a listbox. It makes no mention of whether it has even acknowledged the request.
>> The latest build has a list edit box which contains pending searches, you can also cancel a search from here.
7. No way to stop a search. Granted that you don't really have any control over the hits coming back, there should be a command to stop adding things to the list.
>>See 6)
8. If you sort the search list while items are coming in, any new items added are not sorted.
>> By design since sorting as hits arrive can dramatically slow down searches that return hundreds or thousands of hits in small groups. Perhaps a compromise to do an option to turn automatic resorting on.
9. Results tab show too little information about a hit. Standard information should be at least filename, size, firewalled host, busy host, host speed. I recommend having those plus host address, client name, file extension and SHA1 hash
>> Meta information is displayed in the tooltip. I will add this to the list view also. As for client speed, I could add this for informational purposes, but in my experience it is pretty much meaningless because so many other factors affect d/l speed.
10. Apparently no ultrapeer support (unconfirmed, but I couldn't get anything from the handshake other than a User-Agent field). This should be a requirement.
>> Under development.
11. Lots of simple text formatting things that should be changed.
12. Bandwidth hog. See 10.
13. The absolute worst problem: Sets itself to automatically startup when you load windows WITHOUT ASKING OR TELLING YOU. There is also no way (that I can tell) to turn it off without manually deleting it. ( Delete it from the Startup folder in the Start Menu ).
>> If this is the worst problem you can think of, it certainly puts the rest of your complaints in perspective  .
Still running some more tests, but I have had it for over a week and already dislike it. But that's just my opinion, try it for yourself 
>> Thanks for the feedback. I'm getting lots of emails from people that love QP.
About the only good thing I see with this client is the charts which are a little better than most, although it is just a commercial control.
>> Woah, a positive comment. Funny thing is I had another guy (as vehement as you) wax lyrical about how much he hated the charts. As for the chart control's origin, I guess you would code everything yourself in assembler
Anyone know how to pronounce the name?
>> I hope you're kidding.
|  |