February 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] New ncurses package selector
by Katarina Machalkova 19 Feb '08

19 Feb '08

Hi yast hackers let me share some preliminary results of my hackweek project with you. I've decided to improve the layout of ncurses package selector in order to give it a better structure and make it more user friendly. Some featured changes: * New menus. Though I did no extensive card-sorting study, I tried to group menu items together according to their common functionality. For example, all dependency related actions (check deps now, verify system etc.) are now in submenu of its own: http://users.suse.cz/~kmachalkova/pkger-deps.png * More visible filters Package filters (patterns, RPM groups, langs, repositories, searching) are no longer hidden in a popup menu, but have a panel of its own: http://users.suse.cz/~kmachalkova/pkger-main.png The upper left pane is the filter itself, the lower left one is its description (well, not yet, "Some text here" is a placeholder) * Reorganized package table The order of columns in pkg table has changed, so the most important entries (status, pkg name and its summary) are visible at all times, while those that users do not need to see so often (version, pkg size) shifted to the right and user can scroll the table to see them. In the future (thanks, Lukas for the idea) I'd like to make this configurable and let user choose which table columns (s)he wants to see. * Wizard-like bottom line With left-most help http://users.suse.cz/~kmachalkova/pkger-help.png and Cancel/OK aligned to the right. I'm developing the stuff in my /tmp/bubli/ncurses-pkg svn branch, but don't try it at home ;-) because it's pretty dumb and does in fact nothing so far. It only looks 'nice' (or at least, hopefully) better than before. The original NCPackageSelector super-class has ~4000 lines of code, so I'm trying to break it into little pieces (subclasses) and moving the things around esp. event handling is quite a big deal I just wanted to give you the idea, how it looks like and I'm open to your comments and suggestions. frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

5 8

[yast-devel] UI::SetModulename
by Duncan Mac-Vicar Prett 19 Feb '08

19 Feb '08

packager module does not compile against latest core, pkg-bindings, anyone has idea where to look? (i commented it to make it work, but why is it failing?) What is the replacement for that function? ProductLicense.ycp:18 [Interpreter] Symbol 'UI::SetModulename' does not exist. cheers Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 3

[yast-devel] extra-packages
by Stephan Kulow 19 Feb '08

19 Feb '08

Hi, I discussed this in Prague with some of you, but I left it uncommited for a while: I changed the file format of extra-packages to be readable by a C preprocessor, so we can express architecture specifics. Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] updating the yast slideshow package for SLED10 SP2
by Karl Eichwalder 18 Feb '08

18 Feb '08

I'd like to update the yast slide-show package for SLED10 (SP2). What's the right SVN server and branch, please? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Why YAST is too VAST
by Klaus Kaempf 15 Feb '08

15 Feb '08

"Then, either integrate all the KDE Control Center desktop/theme/artwork elements into YAST or - my preferred option - lose the Control Center duplicates from YAST... but don't have both! YAST is excellent for handling hardware but by overloading it with all these other functions, its developers have created a monster. YAST has become too VAST (Very Awkward Setup Tool)." http://www.raiden.net/?cat=2&aid=376 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

10 11

[yast-devel] Warning: new libzypp ahead
by Stephan Kulow 15 Feb '08

15 Feb '08

Hi, We're going to submit new libzypp into Factory today. zypp:svn already has a "ported" version of yast2-ncurses-pkg and yast2-qt-pkg - and I'll polish these today. But we need the full stack of new yast packages developed during hackweek in Factory too - e.g. yast2-core, yast2, yast2-installation, they all changed incompatible without libzypp's fault :) Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] Translation fixes
by Michal Svec 13 Feb '08

13 Feb '08

Hi, I ran check_ycp through the repo and fixed the missing translations where it seemed appropriate. Please have a look at the attached patch, if there are no complaints I'd commit it later today. You could do the test youself via 'y2tool check_ycp' or the script I used (attached), it reports much more, besides translations :) I left out ca-management, as it contains quite a lot of those and I was not sure which are on purpose. Thanks, Michal

4 4

[yast-devel] redesign of printer module redesign
by Martin Schmidkunz 12 Feb '08

12 Feb '08

Hi everybody, a quite wise CUPS expert once said "exchange dungeons by trees" and that was an inspiration for me to take your feedback and make another series of mock ups: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Release_Candida… What do you think about it? The first feedbacks revealed a great sense of confusion about the amount and design of information presented in the overview. Thats why the space acquired by help was used for an overview. (Help as such will not be dropped it will move to a button within the navigation area :-)) One thought was to hide "print via network", "sharing" and "CUPS autoconfig" under a "Settings" category, but this idea was dropped as the word "Settings" as such is quite meaningless. We also exchange "Remote Access" with "Share Printers" as this might be easier to understand. I am looking forward to your comments, 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: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 26

[yast-devel] style guide meeting on 19th february
by Martin Schmidkunz 11 Feb '08

11 Feb '08

Hi, as there is hackweek this week this means that there will be no meetings. Therefore the next YaST style guide meeting is scheduled for Tuesday, 19th February 2008, 16:00 CET until 17:00 CET on "styleguide" channel on irc.freenode.org World times for this meeting: http://www.timeanddate.com/worldclock/fixedtime.html?day=19&month=2&year=20… The agenda will be pop up dialogs and maybe we will have time for message boxes as well. First ideas about these topics can be found at: http://en.opensuse.org/YaST/Style_Guide/Dialogs We are looking forward to you, Martin und Eva -- 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: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

Re: [opensuse-ux] Re: [yast-devel] printer module redesign
by Johannes Meixner 06 Feb '08

06 Feb '08

Hello, On Feb 5 21:29 Rajko M. wrote (shortened): > On Tuesday 05 February 2008 02:21:28 am Lukas Ocilka wrote: > > I'm afraid that there are more than just two people :) I also rather do > > like more in one dialog than four tabs. > > I know there is more, but someone has to say that :-) Having both local queues and remote queues in one single overview and have them nevertheless strictly separated is the fundamental "message" which must be made obvious to the user because this tells him in one single overview what the printing stuff is all about. Mix up local queues and remote queues in one list might look better on the first glance for those who don't know what the printing stuff is all about but it doesn't help them to deal with it. It does even confuse them because they will not be made aware of the crucial distinction between local queues and remote queues and what one can do with each of them. Provide local queues and remote queues on two different screens (e.g. via two tabs or whatever the usability experts like) might look better on the first glance for those who don't know what the printing stuff is all about but it makes it harder for them to deal with it. When only the local queues are shown by default it is no longer obvious when there exist already remote queues which are ready to be used for printing in the network. Users might then start to set up local queues when they like to print in the network but the [Add] button is the wrong way for printing in the network with CUPS. By the way: The word "printer" becomes meaningless when "queue" is not used. When "printer" can mean both the device and its queue, the meaning of "printer" is degenerated to "thingy regarding printing". This does not provide real information so that it is meaningless. It does not mean that we must use "queue" in the dialogs. But it does mean that we can no longer use "printer" when we mean the device. Therefore we should use strictly "device" when we talk about the piece of hardware and we can use "printer" or "configuration" or whatever else fits - except "device" - when we mean the queue. The wording "printer" for queue and "device" for the hardware is even consistent with the wording in CUPS. As a small exercise think about the differences regarding the meaning behind the following terms: - local queue for a directly connected device - local queue for a local device - local queue for a remote device - remote queue for a directly connected device - remote queue for a local device - remote queue for a remote device > ... Johannes has some ideas that IMHO are more promissing, than currently > discussed UI design. Look at one of threads "printer module". The text > included in line with buttons can explain what buttons can't. http://lists.opensuse.org/opensuse-ux/2007-05/msg00075.html http://lists.opensuse.org/opensuse-ux/2007-05/msg00087.html Unfortunately any further discussion is futile because descriptive texts for buttons was already rejected. Instead we have exhaustive discussions about button names... Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1