(This email is more stream of thought - go to the bottom to see an idea that everyone might like)
> http://todesbaum.dyndns.org/freenet/new-splitfile-request/ This is very very cool indeed, and better than I expected it to be. But I do have some high-level issues with this approach, all of which I think can be solved without wasting any of your efforts so far: - Each individual download requires an entire browser window. This isn't in-keeping with the way browsers normally work. I think there is a good risk that users will be confused as to whether the download will continue if they close the window. - Frames will piss off lynx users (although I kinda like that idea) - One could argue that this is the kind of information an expert would love to see, but it might be too much for a newbie. - On a more asthetic note, I think that the block-boxes could be much smaller, each box is basically conveying one of 3 states, and I don't think we need 24X24 pixels to do this. 16X16 or 8X8 might be better, and would make more effective use of screen real-estate. I completely understand the problem with the progress-bar not moving, and that being discouraging for users. I guess, right now I am thinking about an approach where: The user has the option of the interface as currently outlined, or they can simply opt for a normal download, where an infolet provides them with progress information. It should be relatively straight-forward to share code between this screen and the infolet to save duplication of effort. Another idea, which on thinking about it, might be more attractive to you guys, is to pop open a borderless window which conveys this information, but tries to look at-least something like a normal download window that the user will be familiar with (similar size etc). Ian. -- Ian Clarke ian@[freenetproject.org|locut.us|cematics.com] Latest Project http://cematics.com/kanzi Personal Homepage http://locut.us/
msg05890/pgp00000.pgp
Description: PGP signature
