On Fri, 2010-11-19 at 12:19 +0100, Christoph Noack wrote: > "User's don't give requirements. They provide information". > > If you ask for requirements, you might end up in getting answers that > lead to the same design like it is available today. Only few people > might come up with suggestions what might be better ...
It's true that if you ask users for requirements, the answers will often be based on existing solutions and lots of hidden assumptions. I'm in 2 roles here, designer and potential user. You could assume a risk of what I offer being to too self-centered. On the other hand I have the domain-specific knowledge and experience that is needed. The fun thing is that I have to apply it on itself ;) Also note that much of what I wrote is not about what people have been or are doing, but is about what they should be doing. You really don't need to worry about this leading to a design like it would be available today, already. I'm rather sure there is no open-source solution, yet. I'm not familiar with proprietary solutions that might exist, so no risk of blindly copying them. -- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/ -- E-mail to [email protected] for instructions on how to unsubscribe List archives are available at http://www.libreoffice.org/lists/marketing/ All messages you send to this list will be publicly archived and cannot be deleted
