| Newsgroups |
gmane.comp.web.galeon.devel |
| Message-ID |
<[email protected]> |
>Even if the usability of galeon x.y where x <= 1 was not as good as what
>we have in galeon 2, it was not very bad. I would say that in cases it
>was even better (but in most it was a bit worse).
>
I think galeon 2 usability is, in general, improved really really lot. Not
so much like the code did, but still there is a big difference.
>My first target is me. I want a browser that I can use comfortably.
>It is better if some other people like it, but that's secondary.
I'm happy you are confirming my impression.
This means our targets are very very different :(
>
>If you mean the user styleshet that could be set in the prefs dialog, I
>could agree that it didn't need space in the UI, but the functionality
>was useful. Again, it could help accessibility (making fonts always big
>enough and acoiding stupid colors).
Yeah I was talking of this. The funcionality can be useful as I said, but
done that way is just crack.
>But would a way to enable gestures make her work harder? Probably not a
>lot harder.
>
>And that feature would make some other people work easier. And maybe
>some day your gf will try it and like it.
Many prefs will make her work harder.
>
>I think that we agree that cool features are good when they don't get in
>the way of people's work (and don't add too much work for the poor
>developers).
>
>The difference is that you are sometimes too much conservative with the
>interface (too much of Seth's HIG). OTOH, I think the HIG is good when
>not abused. We need to read the HIG as a recommendation and apply it
>with common sense.
>
>What does this means in this case? The HIG says that you should put the
>"Preferences" menu item in the edit menu. That's very good for most apps
>because in most apps you don't change the prefs very often.
>
>But it seems to be common to change the prefs of a web browser. If you
>don't believe it, just look at the people complaining. I already know
>that the people reading and posting to this list is not representative
>of your user target, but they are representative of current galeon's
>users.
>
>What was galeon1 solution: we had a menu called "Settings" with some
>preferences that were often changed and the "Preferences" menu item.
>That was good for many users and I doubt that it made harder using
>galeon to your girlfriend or any other user of your target.
Not only my gf. This made galeon harder to use for me to, because a very
common item was misplaced comparing it to other applications.
>>
>> So now I tried to define who I target, let's try to delimit better the
>field
>> defining who I dont target. I dont target most of you reading my mail
:)
>
>That's good. But I think you should at least keep the people reading
>this list in mind when designing the UI. Even if they are not you first
>target they should be kept in mind when possible.
>
>Screwing your current user base is not a very good idea ;-)
>
Maybe, but I'm not working on galeon to have many users ...
Marco
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf