YaST Development August 2008

yast-devel@lists.opensuse.org

23 participants
30 discussions

[yast-devel] buttons buttons buttons
by Martin Schmidkunz 24 Oct '08

24 Oct '08

Hi, when testing openSUSE 11.1/SLES 11 I came across a rather curious situation: many modules have already switched their label from Abort/OK(Accept, Finish...) to the style guide compliant Cancel/OK label. However in every case there is a third, inactive "Back" button included. This doesn't make sense as there is nothing to go back and the dialog is just an overview. I suppose this is due to many of you using wizard.ycp as base template for creating your module. What do you think about using the button box (http://lizards.opensuse.org/2008/08/28/button-order-in-yast-trying-to-make-…) instead of the buttons of wizard.ycp? In my opinion this would have the following advantages: * consistent button order in pop ups and in the module * user would not need to deal with an inactive button * button order in YaST would be consistent with the desktop used by the user What do you think about that issue? 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: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 6

[yast-devel] use ALog::Item
by Martin Vidner 09 Sep '08

09 Sep '08

Dear hackers, you are all admins of your own workstations, I believe. Have you ever wondered what YaST did to your system? Or even what *you* did to your system a week or a month ago? Please have a look at your y2log now: sudo less /var/log/YaST2/y2log The information is (mostly) there, but it is buried in piles and heaps of debugging information. So yes, as if you did not have enough features to implement already, I am asking you for more. But the users will love it. Please take one (or all) of your modules and put in log messages using the API below. Presumably they are already there, using y2milestone. ALog stands for Admin's log, to remind you who the reader is. ALog::Item("/etc/ntp.conf: added 'server ntp.example.org'") ALog::Item("enabled /etd/init.d/ntp") ALog::Item("started /etd/init.d/ntp") ALog::CommitPopup() will lead to ALog::Note("set up ntp from local server") A prototype is in SVN already: http://svn.opensuse.org/svn/yast/trunk/yast2/library/log/src/ALog.ycp The interface is not set in stone (yet). Please comment and let's find a design that is useful and easy to use. Open questions: - actual log format References: - https://keeper.novell.com/sxkeeper/feature/303700?contenttype=text/html - https://keeper.novell.com/sxkeeper/feature/100386?contenttype=text/html - related log in zypp: http://lists.opensuse.org/zypp-devel/2008-07/msg00043.html -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 14

[yast-devel] Button Order
by Stefan Hundhammer 04 Sep '08

04 Sep '08

Fate #303446 covers a long-standing request: Support both GNOME and KDE button orders in YaST2. The UI now provides a new widget called ButtonBox that handles that in an abstract way. What we need to do now is to use that widget whereever appropriate. In many cases, this will be as simple as replacing `HBox( `PushButton(`id(`ok ), _( "&OK" ) ), `PushButton(`id(`cancel), _( "&Cancel" ) ) ) with `ButtonBox( `PushButton(`id(`ok ), _( "&OK" ) ), `PushButton(`id(`cancel), _( "&Cancel" ) ) ) More information at http://en.opensuse.org/YaST/Development/Misc/Button_Order [Any follow-up discussions please on yast-devel] CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] yast style guide effective
by Martin Schmidkunz 02 Sep '08

02 Sep '08

Hi everybody, finally the YaST style guide is finished and effective immediately! See: http://en.opensuse.org/YaST/Style_Guide So please take a look at your modules and polish them :-) As far as I can see the main issues are: * table with buttons http://en.opensuse.org/YaST/Style_Guide#Table_with_Buttons * using check boxes to enable/disable things * to make ConfirmAbort look like http://en.opensuse.org/Image:Ysg_discarding_changes.png * replacing "Abort" label with "Cancel" in wizardycp Thanks a lot to everyone contributing to the style guide! Especially to Lukas and Bubli! 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: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] [Fwd: INFRA: svn.opensuse.org maintenance]
by Lukas Ocilka 29 Aug '08

29 Aug '08

FYI, Peter Poemel today at 01:58 AM wrote: (forwarded mail) Bye Lukas

1 0

[yast-devel] $Y2_BUTTON_ORDER and friends
by Lukas Ocilka 27 Aug '08

27 Aug '08

Hi, It seems we have some new (?) variable(s) in YaST and it took me a while to implement something similar in UI::GetDisplayInfo just because of button orders in Popup YCP module. Is there any more info about these variables? Thx Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

2 2

[yast-devel] YCP built-in "getenv" enabled
by Lukas Ocilka 27 Aug '08

27 Aug '08

Hi, I've just enabled built-in getenv (implemented by juhliarik) in yast2-core (2.17.9). This means at least two things: * You no longer need to use hacks to read environment variables. * Some modules are in conflict with this new standard built-in. Here, see the list of files that mention "getenv", please, change them: include/ca-management/commandline.ycp include/ca-management/util.ycp include/inetd/dialogs.ycp include/inetd/routines.ycp modules/AddOnCreator.ycp (just a comment that getenv should be used) Thx() && Bye() Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] Installation::sourcedir
by Stanislav Visnovsky 25 Aug '08

25 Aug '08

Hi! I'm hacking installation and I've just found out that the variable in $subj is rather strange. It has a default value which is never changed, but seems to be considered as the path to the installation source (susetags repo). But, as the value is a default from SLES9 times, it is just a nice path. So, if you are using the value in the code, I suggest to review if the usage is the one you expect. Or maybe I'm just missing something... Stano -- 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] Yast improvment idea?
by Birger Kollstrand 25 Aug '08

25 Aug '08

Hi, I just want to air an idea regarding Yast. We are using SLES and openSUSE in the company as our main Linux offering.Yast is the keys to why we use those in stead of anything else. But it's no supprise that most of our newcommers have never used Linux before (We are a 90% SW company and still....) Yast is then a very good starting point for them. One thing that is an obstacle is that not all services that Yast can provide are easily visible and this is where my ide comes inn. would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed. When clicking on one of the ubinstalled server/services then Yast would ask to install the needed yast packages. I think this would greatly help newcommers to find their way around all the possibilities that are present. If there is anyone else who thinks this might be usefull, then I'll add it as an improvement suggestion. cu / birger.... Devoteam Telecom Norway AS -- 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] patch disk usage (was: repodata.c - clarification)
by Roberto Mannai 23 Aug '08

23 Aug '08

Oops, forwarding to the right mailing list IMHO... ---------- Forwarded message ---------- From: Roberto Mannai <robermann(a)gmail.com> Date: Fri, Aug 22, 2008 at 11:32 PM Subject: [yast-devel] patch disk usage (was: repodata.c - clarification) To: Stanislav Visnovsky <visnov(a)suse.cz> Cc: zypp-devel(a)opensuse.org Hi Stano > I believe zypp-devel is the proper mailing list for this. Yes, thank you, they clared the question. I append the patch, trying to resolve the enhancement in: https://bugzilla.novell.com/show_bug.cgi?id=399239 - "YaST's software installation modules should show disk space modification". It adds the string " - Installing x MB" or " - Removing x MB" to the tooltip on the "Free space" column (in the disk usage widget) . The disk usage variation will work for the same packages that change the disk usage bar; the zypp-devel mailing list pointed out that the repositories with disk usage attribute are those soddisfying the command: dumpsolv /var/cache/zypp/solv/MYREPO/solv | grep diskusage Here the patch, feel free to change (or throw away :)): Index: qt/src/QY2DiskUsageList.cc =================================================================== --- qt/src/QY2DiskUsageList.cc (revision 50308) +++ qt/src/QY2DiskUsageList.cc (working copy) @@ -229,9 +229,20 @@ if ( nameCol() >= 0 ) setText( nameCol(), name() ); if ( deviceNameCol() >= 0 ) setText( deviceNameCol(), deviceName() ); } + - if ( usedSizeCol() < 0 ) - setToolTip( freeSizeCol(), _( "Used %1" ).arg( usedSize().form( 0, 1, true ).c_str() ) ); + if ( usedSizeCol() < 0 ) { + QString message = _( "Used %1" ).arg( usedSize().form( 0, 1, true ).c_str()); + + if(deltaSize() > 0){ + message = message + _( " - Installing %1" ).arg( deltaSize().form( 0, 1, true ).c_str() ); + + } else if(deltaSize() < 0){ + message = message + _( " - Removing %1" ).arg( deltaSize().form( 0, 1, true ).c_str() ); + + } + setToolTip( freeSizeCol(), message); + } } Index: qt/src/QY2DiskUsageList.h =================================================================== --- qt/src/QY2DiskUsageList.h (revision 50308) +++ qt/src/QY2DiskUsageList.h (working copy) @@ -132,6 +132,13 @@ * is the default implementation. **/ virtual FSize freeSize() const; + + /** + * The delta partition space, after installation / removal. + * Derived classes may choose to reimplement this method. + * Default implementation returns 0. + **/ + virtual FSize deltaSize() const { return 0; } /** * The currently used percentage ( 0..100 ) of this partition. Index: qt-pkg/src/YQPkgDiskUsageList.cc =================================================================== --- qt-pkg/src/YQPkgDiskUsageList.cc (revision 50323) +++ qt-pkg/src/YQPkgDiskUsageList.cc (working copy) @@ -114,9 +114,16 @@ const ZyppPartitionDu & partitionDu = *it; YQPkgDiskUsageListItem * item = _items[ QString::fromUtf8(partitionDu.dir.c_str()) ]; - if ( item ) - item->updateDuData( partitionDu ); - else + if ( item ) { + int usedBefore = item->usedSize(); + item->updateDuData( partitionDu ); + int usedAfter = item->usedSize(); + int usedDelta= usedAfter - usedBefore; + if (usedDelta != 0){ + item->setDeltaSize(usedDelta); + } + + } else yuiError() << "No entry for mount point " << partitionDu.dir << endl; } @@ -258,6 +265,7 @@ , _partitionDu( partitionDu ) , _pkgDiskUsageList( parent ) { + _deltaSize = 0; yuiDebug() << "disk usage list entry for " << partitionDu.dir << endl; } @@ -268,8 +276,20 @@ return FSize( _partitionDu.pkg_size, FSize::K ); } +void +YQPkgDiskUsageListItem::setDeltaSize(FSize aDelta) +{ + _deltaSize += aDelta; +} FSize +YQPkgDiskUsageListItem::deltaSize() const +{ + return _deltaSize; +} + + +FSize YQPkgDiskUsageListItem::totalSize() const { return FSize( _partitionDu.total_size, FSize::K ); Index: qt-pkg/src/YQPkgDiskUsageList.h =================================================================== --- qt-pkg/src/YQPkgDiskUsageList.h (revision 50323) +++ qt-pkg/src/YQPkgDiskUsageList.h (working copy) @@ -234,6 +234,19 @@ * Reimplemented from QY2DiskUsageListItem. **/ virtual FSize totalSize() const; + + /** + * The delta partition space, after installation / removal. + * + * Reimplemented from QY2DiskUsageListItem. + **/ + virtual FSize deltaSize() const; + + /** + * Set delta partition space, after marking packages for installation / removal. + * + **/ + virtual void setDeltaSize(FSize aSize) ; /** * The name to display for this partition ( the mount point ). @@ -263,6 +276,7 @@ ZyppPartitionDu _partitionDu; YQPkgDiskUsageList * _pkgDiskUsageList; + FSize _deltaSize; }; Best regards Roberto Mannai -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development August 2008