On 1/16/07, Nick LaForge <[EMAIL PROTECTED]> wrote:
> Things like good font support and accessibility. Things
> like theming. Cut and paste. Drag and drop. Shared caches for themes
> and configuration. Standardized (and good!) open/save dialogs. MIME
> databases. Icons. Cairo integration.
Silliness. Meaning transcends appearance. I would use tcl/tk.
Again, though, who am I to stop you?
I have blossomed this into an irrelevant debate, and for this I am
sorry. I hope the important things can be done instead.
We want to make this intuitive and easy to use. But consider the
audience. Who is going to be analyzing PCI signals? For this
purpose, aesthetics are useful only as clues that make it easier to
use the program.
Has anyone written any code for this yet?
I recommend this book to anyone who designs anything:
http://www.amazon.com/Design-Everyday-Things-Donald-Norman/dp/0465067107/sr=8-1/qid=1168964534/ref=pd_bbs_sr_1/002-4137434-1839212?ie=UTF8&s=books
--
Timothy Miller
http://www.cse.ohio-state.edu/~millerti
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
