[Scribus] Thus is has been with Scribus.
Mon Feb 4 10:43:03 CET 2008
> In reality it doesn't matter what the UI looks like, simply because the ones who
> use it will become accustomed to it over time. It seems as though many programs
> have 'all of the same problems', and this is because all UI's are based on the
> "fundamentals" of program layout and not on "how does the user actually use it".
OK, but for an app such as Scribus, how would you design the UI to
reflect how it's actually used ?
And there's a chicken and egg issue here as the way the user actually
uses the software at the moment is coloured the present and historic
UIs. The real question is perhaps,
"If you were designing a ui for somebody who had never touched a
computer, where would you start to best meet their needs ?"
Or is this hopelessly naive given how few people start from that initial
And do you make an app quick to learn by using conventional common
controls, or do you make the ideal user interface for the job, which
most user will not want to engage with initially ?
This isn't a new dilemma in the GUI environment. It seems analogous to
the lack of uptake of powerful but cryptic tools like APL whose syntax
scared off most users.
John Beardmore, MSc EDM (Open), B.A. Chem (Oxon), CMIOSH, AIEMA, MEI
Managing Director, T4 Sustainability Limited. http://www.T4sLtd.co.uk/
Carbon Trust Consultant: Energy Audit, Carbon Footprint, Design Advice
Energy Efficiency Accreditation Scheme Registered Assessor
P:0845 4561332 F:0870 0522417 M:07785 563116 Skype:t4sustainability
More information about the scribus