Op vr, 05-05-2006 te 17:45 -0400, schreef Youness Alaoui: > On Fri, 05 May 2006 16:09:00 -0400, Karel Demeyer <[EMAIL PROTECTED]> > wrote: > > > Op vr, 05-05-2006 te 21:34 +0200, schreef Karel Demeyer: > [CUT] > >> > > > I pressed "Send" too quickly :) I read this first before replying on > > the comments above though. > > > am I just sleepy or I can't figure out what you're trying to say... ;)
Well, I first replied on what you typed above, and pressed send while I intended to answer this in teh other mail too :). > > >> > I 99% agree, you really did a great job on this! kudos > >> > my few comments : why enable sound in account menu ? yes it is account > >> > option, but I don't see it in there.. > > For that reason and because creating yet another menu would be overkill. > > I guess you want more stuff in this menu ... > >> > I would also think that an "Options" or "Tools" menu would be usefull > >> > (enable sound in there as well as access to prefs window + any often > >> > modified preferences) > > wat often modified preferences ? My first draft added "dp in cl" in the > > view menu but one pf the usability ppl said "it's crack" and indeed, it > > is. You don't change it that often. In finitis you could add the > > "where is the psm showed" stuffin the view menu .. but again that's not > > for tools, and you don't want to change that alot ;). What rests ? I > > don't have an idea what prefs you'd want to see in a menu. The sound > > one is the only one I could think of as it's something you might change > > a lot, like changing your status. We could have a cool plugin that for > > example sets sounds muted dpending on the state btw ;) > > > first, sounds per state is in the TODO already, but I thought of it as an > additional checkbox in the custom states only (to avoid yet another option > in the prefs window, those who want the feature just have to create a > custom state "away-nosound" with no automessage, no nick change...) > often modified.. humm, I would say plugins, skins, access to preferences > window, enable sounds.. humm.. webcam settings... it's already enough, but > we could think of others, maybe mainly stuff we want people to *see*, I > mean joe average won't go in the prefs window and see what we got, but he > might look in the menus and if he sees in the menu a "Enable super cool > feature X", he might click on it.. I remember now that we should have took > a look at official client menus, which we forgot to do (don't know if you > did it under the hood) skins are just an "appeareance" option. A lot of applications put some way to configure their skins in their meus to make it easy discoverable, because they think skins are cool. But, in fact, like 90% of our users will still only use the default skin. Those who want to tweak stuff willgo into the preferences screen and find a skin settings button (should be fully incorporated in the window itself though ;)) over there. So for like 90% of our users, it's filling the menus and making it more difficult to find what they want to do. Again, I'm willing to add this to thge powertools plugin. Same for webcam settings. Most users only set this up once, and when tehy first want to send webcam they'll be presented with this window anyway, so they set it once and they'll never need a menu item for it again. If they *do* want to change the device, a "preferences" menu-item will guide them imo. It' not like they won't discover we have webcam-posibilities as we have items for 'm in the Actions menus. I did look at the official client though it's kind of a usability nightmare (and this is not only because of the bloat). It was a 7.5 version anyway. > here's what it has : > .... > ok, I deleted it, I think the mail program will word wrap it and it will > screw the whole design.. take a look at it instead at : > http://kakaroto.homelinux.net/amsn/msn_menus.txt > (file is also attached) > anyways, I can't remember what I was saying... > look at those menus, tehre are some stuff in there that we can and SHOULD > use in our own menus.. like report bug/send feedback in help menu (just a > small example), This might go in our help, I'm fine with that :) > so take a look at those.. you'll notice it's an msn 8.0 > beta menu, and that I cut/abbreviated/rephrased some of the long named > items.. cause I GOT BORED at doing that!!! np :) > also, about contextual menus, they are weird, the menu depend on who you > clicked on (they seem to exist 'non-IM' contacts.. wtf.. maybe it's some > kind of adress book where you add people name, email, phone numbers, etc.. > keep them on the server without the other user having a passport, as a > internet addressbook.. but I'm not sure), so you can have a menu for a non > im contact, a different one for a msn contact, differnt for offline/online > contacts, and different if it's yourself (if you have your own user in > your contact list, the right click won't allow you to block/unblock... the > items are not there at all) ... anyways, I do not have the patience to > copy each of the different contextual menus I see there... :D. we don't have non-im persons anyway. and if we had, I think we better keep allmost the same menu and grey out some stuff. THe first group's actions could be changeble though as we already do it then for the acitons we have now and I think it's good to keep it that way fter I discussion I had last night on #openusability. > > > >> > Also, optional, but what do you think of (as a new feature) a > >> "Windows" > >> > menu ? with the list of all opened windows/contains.. might be > >> usefull.. > >> > since it needs new code, maybe if it's accepted, do the design and > >> keep it > >> > in the wiki until we implement the code for it. > > I don't think this would enhance usability. A "Windows" menu is found > > in MDI's (multiple document interfaces), this type of programs is not > > very liked by usability crowd ( "The use of MDI is discouraged, as they > > have a number of inherent usability problems" ). > > You coujld say aMSN is kind of a MDI prog as we 'work' on multiple > > chats. But, there's no such an art of adding menu-titles. We already > > have 5 now with my proposal, you propose 2 more. Maybe we do have to > > add 'm, but I think we better don't. In fact allmost all modern > > desktops have a "windows listing" somewhere in a panel, also called the > > "taskbar" in windows. Most modrn windowmanagers support grouping of all > > windows of 1 application. In other words, 99% of our users will already > > have this functionality on their desktop! It's like hte same reason why > > a clock on, a website is crack ;). Those 1% are likely geeks and if > > they want it they can add it to powertools ;) > > well, it's not an MDI, but yeah, I understand what you mean, the idea > sounded like a good one since I use a WM without any taskbar so I didn't > hink about that.. forget it then! :) you are likely a geek ;) > > >> > > >> > you also pointed out something interesting when talking about some > >> stuff > >> > that needs to be moved to prefs window.. how about a redesign of the > >> prefs > >> > window :p yes, it WILL be redesigned.. but in time only.. also, we'd > >> need > >> > someone to take it where Alvaro left on the new prefs window, I think > >> he > >> > has the API finished, but only needs to code the items to apepar in > >> the > >> > prefs window.. > >> > post-0.96 > > > > I'm wanting to do a design of a clean preferences window, but beware, > > this will mean a lot of preferences would be added to this window byb a > > plugin so it's not in the way of "normal"' users. > > > > it seems I'm still sleepy as I don't get it... OK, in the future, I might want to make a proposal design for a clean preferences window. But "cleaninng it up" means removing a lot of preferences, that could be re-added to that same window (not in the plugin's prefs window) by a "advanced prefs" plugin or something. Karel. > > KKRT > > >> > > >> > > >> > > >> > -- > >> > KaKaRoTo > >> > > >> > > >> > ------------------------------------------------------- > >> > 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 > >> > > >> > >> > >> > >> ------------------------------------------------------- > >> 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 > >> > > > > > > > > ------------------------------------------------------- > > 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 > > > > -- > KaKaRoTo ------------------------------------------------------- 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
