userfriendliness

Is the benefit for organizations and companies in general efficiency, effectiveness, userfriendliness, etc worthy intentions?

HCI research and the common good Erik Stolterman 2006

Is the benefit for organizations and companies in general efficiency, effectiveness, userfriendliness, etc worthy intentions?

Archive 2006-06-01 Erik Stolterman 2006

Notable among these are (1) vast improvements in the ratio of price to performance in integrated circuit design and manufacturing; (2) improvements in userfriendliness and the automation of complex procedures; (3) enhanced interoperability among multi-vendor systems; and (4) universal access to computer networks by both wireless and land-line connections.

Npr Reengineering Through Information Technology A ITY National Archives 1994

One of the things that i've always come to appreciate with Firefox is userfriendliness.

unknown title 2009

Enjoy the userfriendliness of a Web interface today!

Planet ActiveState 2009

Redmine modules: no namespacing issue split: source code links are automatically available on each applicaton page, instead of the module page gitolite modules: no namespacing issue split: easier to find projects (git. kde.org/APPNAME. git instead of git. kde.org/SOMEMODULE. git) git modules: projects can keep their interdependencies, module-wide libraries and so on less server space split: moving a project (eg. to unmaintained) moves its whole history user workflow modules: keeps a sense of community by having a whole module kept together increases passive testing of trunk (more people to notice if the build's broken) lower barrier to hacking on other projects in the module easier to refactor a module [rare] less downloading & disk space for those who want entire modules split: less downloading & disk space for people who only want a small part of a module easier to get started on one little app? easier to avoid being exposed to unstable versions of other projects [I think that's a bit selfish though] comments: kdesrc-build, build-tool and mr make it easy to handle large numbers of repos, although there's still room for improvement on userfriendliness. releases modules: closer to what we have with svn??

KDE TechBase - Recent changes [en] 2010

Redmine modules: no namespacing issue split: source code links are automatically available on each applicaton page, instead of the module page gitolite modules: no namespacing issue split: easier to find projects (git. kde.org/APPNAME. git instead of git. kde.org/SOMEMODULE. git) git modules: projects can keep their interdependencies, module-wide libraries and so on less server space split: moving a project (eg. to unmaintained) moves its whole history user workflow modules: keeps a sense of community by having a whole module kept together increases passive testing of trunk (more people to notice if the build's broken) lower barrier to hacking on other projects in the module easier to refactor a module [rare] less downloading & disk space for those who want entire modules split: less downloading & disk space for people who only want a small part of a module easier to get started on one little app? easier to avoid being exposed to unstable versions of other projects [I think that's a bit selfish though] comments: kdesrc-build, build-tool and mr make it easy to handle large numbers of repos, although there's still room for improvement on userfriendliness.

KDE TechBase - Recent changes [en] 2010