Hi everyone,Thanks again for your comments. After some thought, I'm starting to think that the best choice would be putting less attention to BeOS similarity than before. I will be mostly commenting on Waldemar's posts, since my thoughts are quite similar to what DarkWyrm suggested, no comment from my side is needed.
Waldemar Kornewald wrote:
About showing the file list, I still disagree. If we can work around bad packages automatically we don't need to inspect them. Nobody does this under Windows, so why should we?
I don't think Windows is a good argument, since many of their approaches are far from being intuitive and useful. My thoughts of this are quite simple - I don't like the idea to decrease user freedom (since knowing what the system does _is_ freedom) just because complexity would rise a bit. Even though we aim for normal, desktop users, I think we should not tighten our area of vision too much. I know a few people that are neither developers nor complete computer newbies that find such information interesting. I just can't imagine them running the package builder, or some other application, to get this info. The same goes for me, as I have the very same thoughts as DarkWyrm.
IMO, one additional button put in the right place won't make normal users waste time or feel uncomfortable. I simply think the pros of such addition overwhelm the cons.
BTW, one other minor improvement suggestion: "Begin" is basically like "OK" and I think more obvious labels shouldbe used. What do you think about renaming "Begin" to "Install"?
This seems a good idea. Although the old approach is still quite good, since we decided already that the window tab should include "Install: Package name". With this addition, "Begin" also sounds fair, since the user knows that pressing the button will "begin the installation of Package name".
Just a quick note for Łukasz: I think that our installer should be able to recognize such "bad" packages and not allow for selecting a target folder (but only avolume).
I agree. This would then end the issue of volume and path separation.
The pop-up field could be replaced with a BStringView when there is only one option, so you could easily recognize when multiple options are available (if that's your concern).
The same here - I also agree.Anyway, right now I think that a UI similar to the one proposed by Waldemar can prove to be a good choice. First, the issue of the "Show files" button should be resolved though...
-- Best regards, Łukasz 'Sil2100' Zemczak