> > I find it somewhat disheartening that the only way out, given in the talk > anyway, is to assemble a UI team that has full control over the interface > design and doesn't come from either the user or developer camps. That's not > something I see happening for Leo anytime soon; the project just isn't at > that scale. Still, I enjoyed the talk and the thinking it's stirred up in > me. >
Concerning an UI team, I wouldn't be disheartened, because Leo isn't at the scale of Blender. Imo it's not a UI team per se that's needed. If you consider such a team just as an enbodyment or incarnation of special set of qualities, even a single developer at times can put on different 'hats' and (try to) approach his project once as user and once as a developer. I know, that's not easy; but at least we all know how it feels to be a newbie when we try out new stuff (or try to absorb PyQt). I don't know if you've also seen the second and third video in the series http://www.youtube.com/watch?v=yIedljapuz0 http://www.youtube.com/watch?v=UWacQrEcMHk There Andrew Price discusses usability points that can be applied almost unchanged to Leo. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
