Op zaterdag 6 mei 2006 13:09, schreef Karel Demeyer: > Op vr, 05-05-2006 te 21:20 +0200, schreef Harry Vennik:
[CUT] > > > [OFF] amsn versioncontrol -> in about window > > > This was removes because it's not very much used anyway and only > > > populates screen real-estate. whe a user checks the version he/she has > > > in the about window, he/she should be able to check for the latest > > > release in there too. > > > > 100% true. > > > > > [OFF] minimise instead of close -> in preferences > > > This is something only set once. From usability point of view it's > > > even wrong to minimise a window (to the tray) when the close button is > > > used as this should do the same as the "close" entry in the main menu. > > > Though, this is an often requested feature, so it should be kept, and > > > it's place is in the preferences window. > > > > I do not agree 100% here, but I think you're close. The tray icon should > > be regarded as a separate window. Pressing the close button or close in > > the main menu should both only close the window they're in, the main > > window in this case. > > This metaphor would mean the tray icon is our "main window" as closing > this closes the whole app. I can't agree on this. > A notification are is meant to have icons notifying a user of something > from the OS or another app, not to have a main app window in it. > The system tray is a place where apps can reside to show they are still there, although there even if there is no window on the desktop. The icon will also show the current state of the app in most cases. For aMSN (and most other IM) it represents the current status of the user, for a sound mixer app it will show if sound is muted or not, a network connection monitor will show if network is up-and-running (and signal level in case of a wireless network), an e-mail client will show if there is any new mail, etc.... > > There should also be a 'Quit' or 'Exit' item appended to the first menu > > that will terminate aMSN, and thus make the trayicon disappear too. > > [CUT] > > > > > > ===Account=== > > > Log in as ... > > > Log in > > > Log out > > > --- > > > Change Nickname ... > > > My Status > > > > --- > > > Go to Inbox > > > My profile > > > --- > > > view received files > > > show events history > > > --- > > > Enable sounds > > > Plugins > > > Prefs > > > --- > > > Close > > > > - Okay, as said already, I'd add a last item named either 'Quit' or > > 'Exit'. - Also I've got my doubts about the 'show events history' item. > > Further down in this e-mail I'll tell why. > > - 'Enable sounds', 'Plugins' and 'Preferences' should not be here... I'll > > pick them up later. > > [CUT] > > > ===Contacts=== > > > add a contact ... > > > remove a contact ... - 1 > > > Contact properties - 1 > > > --- > > > New group > > > Rename group - 4 > > > Remove group - 4 > > > --- > > > view chat history - 1, 2 > > > view webcam sessions - 1, 2 > > > --- > > > save contactlist - 3 > > > load saved contactlist - 3 > > > > Okay, this could be cleaner. > > I marked the menu items with the numbers of the remarks. > > > > 1. Here are also many items that apply to one specific contact, so it > > makes no sense to keep them here. Just have them in the context menu. > > "context menu only" = not done > You won that ;-) But please think of the implications that should have on other things in our GUI to reach maximum usability, as we discussed. [For the others in here: In a private discussion on MSN I told Karel that it only makes sense to include contact-specific items in the menus if the user can select a contact in the CL (maybe allow selecting multiple at once) and then choose the item from the menu. Currently a separate list of contacts pops up after choosing the menu-item, which I think of as a usability nightmare.] > > 2. Here I see two history related items, while another history related > > item is in the 'Account'-menu (events log). This doesn't feel good... But > > what I say now it is also contrary to my previous remark, because the > > events log does not belong in a context menu for a contact too.... Btw. I > > do understand why you put these two here and the events log in 'Account', > > but to me it feels bad not to have all history stuff in one place. Yeah, > > complex thing.... Okay, I'll leave the final conclusion to others. Either > > have all history stuff together, or keep event log in 'Account'and have > > these 2 in the context menu only. > > "context menu only" = not done > > > 3. Maybe these should be in the 'Account' menu??? > > They are about contacts, most naturally to have 'm in this menu if this > menu exists. > The contact list is a property of the account. Actions that affect the list, and not individual contacts should therefore be in the 'Account' menu. Actions that apply to a selected contact (or a set of selected contacts) should be in a 'Contact' menu (yes, I think naming it in sigular instead of plural would be best) > > 4. These apply to a group, so right clicking the group header should > > popup a context menu with these options, and having then in here makes > > not much sense, > > "context menu only" = not done > > > 5. Hmmm, two items left.... Renaming this menu (e.g. 'Tools') and adding > > the 'Enable sounds', 'Plugins' and 'Preferences' would be nice. > > > > > ===Help=== > > > contents > > > --- > > > FAQ > > > online help > > > --- > > > about aMSN > > > > This one is okay ;-) > > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Amsn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
