Hi Sebastian,
I feel your pain :)
we are aiming to focus Pharo 4 in “modularisation and tools”, to enhance what
we have currently.
Now… one of the biggest problems we have is that people is so used to the old
tools that they don’t even realise that we can do a lot better. And most
possible
Thanks for bringing this up.
Yes, we should care about usability.
And I agree that usability is attainable as long as you approach it with
consistent discipline. It's similar to designing code: you start asking
questions, figure out what the right questions are, and then stick to it.
I like
Our engineering bias make us think too literally some times.
Let's stay scientific but use the designer hat instead of the mathematician hat.
I know is for the web, but don't you have the feeling that you can design an
experiment in a way that will converge to the same usability principles?
As somebody coming from the HCI side, rather than the software engineering
/ programming language side, I too value usability. But, it seems to me
that you first do the major changes and then slowly hone to get usability
right. I find lots of small little usability bugs in Pharo 3.0 but I assume
Hi Sebastian,
I think you read my mail too literally :).
We do not disagree. My comment about Don't make me think is that what
applies for the web is not quite the same as for a programming environment.
For example, on the web, it is more profitable to assume that everyone is a
newcomer, while
On 03 Jan 2014, at 12:56, J.F. Rick s...@je77.com wrote:
As somebody coming from the HCI side, rather than the software engineering /
programming language side, I too value usability. But, it seems to me that
you first do the major changes and then slowly hone to get usability right. I
Sebastian wrote
Cheap idea for us:
Good idea for a bit later, and for the new parts.
We already have a number of well-known problems for new users.
If we don’t eliminate them first, we’re not going to find much new
issues. They will be hidden behind:
- no discoverable way of creating classes
I felt we didn't disagree but wanted open that line of conversation because it
sounds heathy :D
I agree the tests for our tool aren't going to be the same as for many web
sites/apps. One thing is to try to create a great experience for woman buying
shoes in the web and another is computer
If that's the case the UI curators should decide what are those 3 priority
issues
We can jump to these:
7. Don't panic by overwhelming issues. Discuss with colleagues or publish in a
private wiki for the team or something
8. Decide what are the 3 most blocking entry barriers and show that to
