Are there other issues in Phil's presentation?
yes many but we:
1. should not try to catch all at once
2. not panic
3. not negate them :D
4. not neglect them :)
5. accept them and
6. select what’s best for the project to deal with first with the resources we have
Deep breath…. :)
Here is some of what I think would be smart on our part:
1. yes, SUnit comes first so the IDE reaches conceptual completeness <- that’s great for morale and historic for Helios
2. Being sure that users who hate vi aren not disregarded by Helios, on the contrary, Helios delivers love for them too
3. The basic smalltalk workflow* should be navigable and do a better job in removing barriers on the creativity flow. Ideally in one keystroke for each step (I should elaborate on this with an usability review, video or a hangout would be better for this and email sucks for explaining this... in this stage at least)
Doing my best here:
*basic smalltalk workflow:
inspect in one keystroke
select a class name wherever and browse in one keystroke
select a word and find implementors, senders, symbols and strings in one keystroke
debug in one keystroke
from the debugger jump to any of the previous actions in one keystroke
same from an inspector
What if we need one extra keystroke? I know it sounds like is not a big deal, but in usability terms, in the cognitive load for the user in creative flow is like the difference between free and making email or facebook cost only 1$ per post. Whole different story. We want to remove barriers to create things with Amber so we want to remove those barriers. Let’s find them and then talk how we deal with them. If we make Amber pre-cognitive, we’ll increase the chances of touching hearts. If we do that, things are limitless
--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/d/optout.
Locked
-- 