- openSUSE UX

Re: [opensuse-factory] Re: [opensuse-ux] Liberation fonts as default
by Bernhard Walle 22 Jun '07

22 Jun '07

* Stephan Kulow <coolo(a)novell.com> [2007-06-17 14:21]: > Am Saturday 16 June 2007 schrieb Stephan Binner: > > On Thursday 14 June 2007 06:02:29 Mohammad Bhuyan wrote: > > > I was thinking if the future distributions install them as default fonts > > > in Desktop and apps, then it will look good out of the box. > > > > What's wrong with DejaVu? Why has the default desktop to use MS metrics? I > > see sense for using it in office documents but desktop/application > > interfaces? > Because web sites are layout for these metrics. And web sites are an important > part of today's desktops. And what's the exact releationship between the desktop font and the default font in the browser? Thanks, Bernhard -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

1 0

Liberation fonts as default
by Mohammad Bhuyan 17 Jun '07

17 Jun '07

Hi all, Just installed Liberations Fonts (Red Hat) and changed KDE Desktop fonts to use them. I am not using sub pixel hinting and don't plan to use them due to MS patent over it. Now that there is an open replacement for MS fonts to distribute freely (I assume that is the point of Liberation fonts), I was thinking if the future distributions install them as default fonts in Desktop and apps, then it will look good out of the box. We must acknowledge the ubiquity of the proprietary Microsoft fonts. Lots of rants on the net is about people complaining how linux desktop looked ugly out of the box. gfx aside, I am sure we all know that the text in the screens is one key contribution to the user experience. Regards, -- Soyuz -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

4 5

Re: [opensuse-ux] Re: syntax versus semantics in UI
by Martin Schmidkunz 08 Jun '07

08 Jun '07

Am 06.06.2007, 19:48 Uhr, schrieb Juergen Weigert <jw(a)suse.de>: > This is another good example for Johannes' problem: Yes, but although we have different semantics represented by the same syntax it is obvious for the user what to do :-) This semantics/syntax thing makes sense for me, when the user is hindered to accomplish a task the most easiest way or if the user is in danger of making errors because he doesn`t know what to do. Cu, Martin -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

1 0

apparmor yast redesign - updated
by David Drewelow 06 Jun '07

06 Jun '07

http://en.opensuse.org/YaST/AppArmor/UI-Redesign This is probably the final version of the reporting forms redesign. Any feedback would be appreciated. Thanks, -David -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

3 5

Re: apparmor yast redesign - updated
by David Drewelow 06 Jun '07

06 Jun '07

Dominic Reynolds wrote: > Form: > > o Running Reports - Setting Filters - Profile Filters > > Whats the difference in behavior for "Select Access Type" and "Filter by > Mode"? They have the same options in the form. > > Also should we consider the present and future scope of mediation for AA? > > Currently we have: > * files (r,w,l,m,Px,px,Ux,ux,ix) > * POSIX capabilities > > Coming: > * network access controls (soonish - maybe 10.3) > * IPC controls (hopefully code11) > * rlimits (hopefully code11) > > With that scope in mind is it worth breaking the filter types into > individual tabs? Or does that make things too complex? > Hmm. Good point. That's going to be a nightmare for configuration. I was thinking of the NetDomain controls as separate, but obviously they're not. I think Tabs are the way to go here. More later. > o View Archived Reports - Choosing Reports > > This is mostly just enhancement request - in the table where we list the > file name and date time for existing reports. Would it be worthwhile to > do a little pre-processing to make the output list: > > --------------------------------------- > Report Type Date > > Audit Report 2007-05-14 13:45 > --------------------------------------- > > Not a huge deal really. > Believe it or not, not easy to do. It's a table, and you could do an ugly workaround of inserting spaces into item data, but I think that this is an issue with yast's record display. > > o Creating a Report > > For this form would it be usefull to use the tabbed UI again? Maybe > > -------------------------------------- > General/Recipients/Archiving > > General: > Name > Shcedule > > Recipients: > Email config > > Archiving: > Export type > Archive Locations > ------------------------------------ > > The QT form looks ok - but I've found the ncurses version (from previous > versions of aa) very hard to use. > Ah, I'll look into this. I didn't even think of Tabs, because it's a (relatively) simple form, but that's a good idea. More later... > Thanks for getting this redesign together - looks good. > > > -dom > Thanks, Dom. -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

1 0

Re: syntax versus semantics in UI
by Martin Schmidkunz 06 Jun '07

06 Jun '07

Hi Johannes, hi all, Please don apologize for long answers. Although it took me some time to read it and more time to answer, I found it quite interesting to read and I think, you got many good points :-) > mixing syntax with semantics I was aware of the difference between syntax and semantics, I only doubt whether this difference is also clear to the user or to be more exact: at which experience level is the user able to distinguish between syntax and semantics? I would like to give you an answer on that, but I don't know it by myself :-( "What is really interesting" should definitly not be hidden. That's totally correct :-) The point is that "what is interesting" is different for each user group. Maybe we should start thinking about different design for our different user groups? I think the syntax vs. semantics discussion and your notion of the usability test showed also that we need to take care of the workflow to clean up the semantics side of life. One word regarding the term "consistency": when I talk about consistency I want to express that it is important that items that have the same semantics must look the same to avoid user confusion. I want to work on both, the consistency and the workflow side, but up to now I don't have a mandate for this. It is on my to do list to discuss this issue, but I am afraid I won't have any resources for this before autumn :-( The light switches vs. fire alarm buttons is an excellent example. If you look closely at the fire alarms you will also notice that putting a red frame around the button is not sufficient to protect it from misuses: usually it is hidden behind glass and you have an additional explanation message. Which can be taken as a proof, that different semantics have to be explained to the user. Kind regards, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

4 4

Very Disappointed
by member greenarrow1 01 Jun '07

01 Jun '07

After reading today about Novell just giving Microsoft advanced data on virtualization that us developers create without the possibility of other SUSE developers seeing it beforehand has turned me entirely against Novell, and SUSE. What Open Source stands for and my belief in freedom for software is why I was further developing the virtual desktop With the new kernel version which support virtual desktops and my working with it I have just completely deleted all I have done which was pointed towards SUSE because I do not want work I do to fall into the hands of Microsoft and being patented under their operating system. The reason why Microsoft pulled their virtual desktop is because they cannot get it to work and now I really believe that is one of their main reasons to team up with Novell to steal our ideas and place it within proprietary code. I will not do work that is going to benefit any company that restricts what one can do on their computer. I am sorry to say this as I have been with SUSE from 8.1 and watched it develop to what it is today but will not stand by and watch a monopolistic company like Microsoft ruin us or take over SUSE with Novell's help. And, please do not flame me as I was once a developer for Microsoft so I do know their inner workings. George greenarrow1 InNetInvestigations-Forensic SuSe 10.2/TriStar/Apache GoBoLinux -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

2 1

Re: [Fwd: [opensuse-ux] UI redesign - AppArmor reporting]
by Martin Schmidkunz 25 May '07

25 May '07

Hi, > I'm looking for suggestions and feedback about the apparmor reporting > UI. The plan is to completely redo the report > scheduling form (the "start" page of the reporting module). That sounds like a cool idea! I think that for doing proper suggestions for redesigning the apparmor reporting module one of us within the UX-team needs the time, to understand the functions of the current module. I will ask for resources on our next team meeting on Wednesday evening (CET time) and let you know afterwards. Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

1 0

syntax versus semantics in UI
by Johannes Meixner 25 May '07

25 May '07

Hello, I have a general question if there exist solutions how to show semantics regarding user input via UI. I know how to show syntax regarding user input via UI, e.g.: - show several checkboxes for several binary (on/off) values which can be set "on" or "off" independent of each other - show radio buttons for several binary (on/off) values where only one of them can be "on" - show a list of predefined values if only this values are correct input - show a text input field for an arbitrary input value I don't know how to show semantics regarding user input via UI. Example: a) for one kind of input values the user is free to choose what he likes because any choice would work b) for other kind of input values the user is not free to choose what he likes because only the right choice would work Is there a solution how to show this kind of semantics regarding user input via the UI? Simple real-world examples are: 1) Password input: A password is an arbitrary input value so that a text input field is shown in the UI. But the semantics is different if - a new password is to be set => case a) above - the system asks the user for his password => case b) above 2) Printer specific option settings: Specify the printing resolution versus specify the media size: Both values can be choosen from a list of possible values e.g. Resolution: 300dpi, 600dpi, 1200dpi (the supported resolutions of the printer driver) Media Size: A4, A5, Letter, Legal (the supported media sizes of the printer driver) The syntax is the same for resolution and media size but the semantics is different because - any choice of the resolution works => case a) above - only the media size which is actually in the printer works => case b) above You might think that this is no UX/UI problem at all because it is obvious for any normal user if the semantics is of type a) or b). This is true for my simple examples above but in general it isn't, see this snippet from a mail: -------------------------------------------------------------- > > Why did you acitvate the filtering when you want to set up > > a raw queue? Filtering is exactly the opposite of "raw". ... > Reading this setting in the YAST module, I thought it was > more a choice: do you want the filtering done on the > server side or on the client side. It is a choice but it is not a choice where you are free to select whatever you like - it is a choice where you must choose the right setting which works in your particular environment. -------------------------------------------------------------- In the YaST printer config we have two checkboxes [ ] Share Printer [ ] Do Local Filtering where the first one is of type a) but the second one is type b) but there is nothing in the UI which indicates this difference and this difference is no longer obvious to any normal user. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

3 6

Request for icons for updater applet
by Joerg Kress 25 May '07

25 May '07

Hello everyone! NOTE: Cross-posted as this involves both teams, IMHO. We have a need for icons for the updater applet for both GNOME and KDE. The current icons have certain limitations in areas of usability and accessibility. Please refer to bug 246157 [1] for an example. I have made some proposals in the wiki [2]. One might also check the parent page [3], which also holds the current icons. Currently we have 4 icons, based on a blue dot with a small label on the bottom right. Each label indicates a certain state: * Red: Error occured * Yellow: Updates available * Striped(Yellow/Black): Checking for Updates * Green: No updates We want to have another state: "Applying Updates", which could be merged with "Checking for updates" into "Updater working/Busy" So, UX teams should verify which states need distinguishing from a usability perspective and artworkers should then find a usable and accessible solution. Links: [1]: https://bugzilla.novell.com/show_bug.cgi?id=246157 [2]: http://en.opensuse.org/Updater_applet/Icon_proposals [3]: http://en.opensuse.org/Updater_Applet Thanks in advance! Josh -- Jörg Kreß <jkress(a)suse.de> YaST2 Development _________________________________________________________________ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-ux+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ux+help(a)opensuse.org

6 8