Re: re: Mr. Project DB
Mikael Hallendal <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.mr-project.user |
|---|---|
| Message-ID | <[email protected]> |
tor 2002-09-05 klockan 20.40 skrev info: > ... as I think to "publish" is a new concept seen from the user > perspective. > But you are right that seen from the programmers perspective it is quite > similar to "save". True, and it's the user perspective that I want to keep in focus at this point of the discussion. Sorry for getting back in my developer role :) > You are right here too: I just wanted to make clear where my suggestions > come from. My general experience with Linux people (KDE or Gnome) is that > they say: "It is good as it is because it is this way since ever, so it must > be good and therefore we dont need to change it" I can only speak for GNOME and in GNOME 2.0 we have worked very hard on changing our UI to be more user friendly and usability is currently very high on the priority list in GNOME. One problem is that lots of people (especially advanced users) doesn't like changes. And for every change a project like GNOME or KDE make they will be in for endless discussions about it. It's much easier to start fresh and do large changes than to change existing projects. > Just look at the crap email clients (from a user perspective) the Open > Source community produced for the last 20 years. Well, the Unix-like systems are only now starting to get to the desktop. In the past they have been focused against advanced users, and reading your mail in mutt or gnus (emacs-client) is often more efficient than reading them in Evolution (which I guess is the one you are referring to here). > Then there had to be Microsoft to introduce new concepts, and users loved > it, and open source programmers started to copy the concepts. > > But Open Source programmers "very rarely" introduce new user interface > concepts or make software more easy usable. They just dont get it even > when I explain then the advantages of new concepts. As said above, I wouldn't say this is something that has to do with Open Source programmers. Rather programmers on Unix-like systems (which mostly have been the same). Now there are _LOTS_ of Open Source/Free Software programmers that are aiming at getting there free systems to the end user and the desktop. And thus will also aim for getting a more easily used approach. > As every task is owned by a person, only the owner can edit it. So no > collision can happen as described by you. The person can break a task > into subtasks and make more detailed plans from a big task it was > assigned as beeing responsible for it and it accepted beeing > responsible for it. Great, this is the kind of discussion that I would like at this point. This solution would solve the issues I raised, is this a solution that makes the software easy to work with at the same time? Again, thanks for your input, it's greatly appreciated. Regards, Mikael Hallendal -- Mikael Hallendal [email protected] CodeFactory AB http://www.codefactory.se/ Office: +46 (0)8 587 583 05 Cell: +46 (0)709 718 918