For fear of joining something that I will regret at a later date On 12/14/05, Michael Sweet <[EMAIL PROTECTED]> wrote:
> > 2) The same with print to file. > > Actually, I like what KDE does - "Print to File" is just another printer > in the list. This feels, to me, a very developer centric way of looking at it. Is it Joel who talks about abstracting away to nothing? I think so, but I can't find it on his site. Basically developers think things like "Well, printing to a file is done the same way as printing to a printer, so we can have a file option in the printer list", but thats not how users think. I don't know where I'd put a Print to File option, but I'd like it as a seperate entity instead. I'm wondering out loud now, if it could be linked to the other file operations (such as open, save, etc.) , because its really an operation that results in a file, rather than an operation that operates on the printer. But suggesting that would be something that I'll be shot down in flames for. iain _______________________________________________ Usability mailing list [email protected] http://mail.gnome.org/mailman/listinfo/usability
