January 2008 - YaST Development - openSUSE Mailing Lists

[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] 3 questions about yast....
by Roberto Angelino 28 Feb '08

28 Feb '08

OK. First some background: My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script. Here are the 3 questions they have (for sles10 version): 1) After yast completes installation (i.e., post-install), the fstab is created. What yast module makes this call? It has to be in yast2-installation, but I can't find the connection between the installation and yast2-storage where WriteFstab() lives. 2) How does yast determine what the source partition to mount is? 3) bootloader_finish.ycp breaks the install at the end. They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do? Thanks -robert -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

6 10

[yast-devel] Progress::New() can be called recursively now
by Ladislav Slezak 05 Feb '08

05 Feb '08

Hi all, I changed the internals of Progress:: module to support multiple (nested) invocations of Progress::New() function. The change has been submitted in yast2-2.16.22. Here are some details about my change. Introduction ------------ So what's the change is about? Imagine two yast modules which use Progress:: in their Write() function. Now you would like to use these two modules in your client and display a progress in your Write() function. The problem is that the there will be displayed two independent progresses (from 0% to 100%), one for each Write() call and that's not what user expects - progress 100% doesn't mean that the work is finished! So the usual solution is to disable Progress:: before calling another Write(), but the details about the nested progress are lost. The new functionality allows you to create a "parent progress" which has two stages. The progress values will be recalculated so that the first Write() call will display progress from 0% to 50% the second one from 50% to 100%. The level is "unlimited", the first Write() can call another nested two Write() functions which will be recalculated to 0%-25% and to 25%-50%, and so on... Why it was changed? ------------------- I wanted to fix bug #352007. The package callbacks now use Progress:: module and many yast clients already use Progress:: at start and starting the package manager is usually one step in their progress (e.g. online_update, sw_single). Now the progress bar displays correct (recalculated) values for the package manager steps. This allows us to build new modules on top of others without loosing details in Read() and Write() functions. If you do not want to display some details you can still hide them using Progress::set(false). Internals of Progress:: ----------------------- Progress:: has now an internal stack with progress state, Progress::New() checks if there is already a progress running, if there is no progress it behaves as it did in the past. When there is already a progress running then Progress::New() pushes the current state to the stack and all progress values are recalculated according to the previous states. (In this case the stages are not displayed, they are part of the parent stage.) Progress::Finish() pops the state from the stack so the previous internal state is set back. Examples -------- There are some examples in SVN, see yast2/library/wizard/doc/examples/progress_*.ycp files, I think this is the best way to learn how it works and how to use the new feature... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 5

[yast-devel] sl 11.0: instsys & translations
by Steffen Winterfeldt 30 Jan '08

30 Jan '08

Hi, for sl 11.0 we're splitting language dependent parts off the instsys and loading only the language we need. This way the instsys size reduces from about 70MB in sl 10.3 to currently about 55MB. And, to save space on the media, the common parts of the instsys and rescue system are moved into a separate image, too. So, why am I telling all this? Beacause, in short, it means the instsys consist now of several parts. And because I've just submitted a new installation-images package that activates all those changes. This means you find in the /boot/<arch>/ directory on the media a lot of files like 'root.de', 'root.cs' etc. The important bit is the new 'config' file there. It describes what image files linuxrc will load. If you are testing installations and want to replace/add just some files to the instsys, you can edit that config file and add another instsys part. This might sometimes be easier than the old way of unpacking/repacking the instsys. I'm aware that Lukas has not yet completed (at least I think he has not) support for this in yast. But linuxrc does support it. So everything should be ok as long as you select the language at the boot loader/in linuxrc. Steffen -- 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] Re: [y2-maint] disabling MDNS during installation
by Lukas Ocilka 29 Jan '08

29 Jan '08

Schlomo Schapiro napsal(a): > Hi, > > can you please take a look at > > https://bugzilla.novell.com/show_bug.cgi?id=349467 > > The issue is about disabling MDNS during the installation as many sites use a > .local DNS domain. > > Steffen Winterfeldt was so kind to add support to linuxrc for disabling mdns in > the installation initrd, could you please add support to disable it also in the > installed system ? > > Thanks a lot, > Schlomo Schapiro Hi, I'm afraid you have used a wrong mailing-list. Please, use yast-devel(a)opensuse.org Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

1 0

[yast-devel] selecting an additional pattern during installation
by Jordi Massaguer Pla 29 Jan '08

29 Jan '08

Hi all, I've just created the page http://en.opensuse.org/Select_additional_pattern that explains a way of selecting an additional pattern during the installation. This has been used in order to let the user select between different installation modes, that were: - client - server - standalone when the user selects the client, the client pattern is selected; when the user selects the server, the server one is selected; and the same for the standalone. Then, this pattern is stored in Packages::additional_pattern variable. This way, we can use all-in-one DVD instead of having one DVD and three addon CDs. This module, that presents the options using a GUI, needs of a modification on the module/Packages.ycp, so that it adds the previously selected pattern (the one in Packages::additional_pattern (we added this variable, too) ). Comments will be very welcome, greetings, -- Jordi Massaguer i Pla openTrends Solucions i Sistemes, S.L. Torre Llacuna C/Llacuna 166, 10º 1ª A 08018 Barcelona Phone: (+34) 93 320 84 14 Fax: (+34) 93 300 35 27 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] create translation for a new yast module
by Jordi Massaguer Pla 28 Jan '08

28 Jan '08

Hi all! When creating a new YaST module, how do I create the po and mo files needed for its translation? Is there any tool or I have to create it by hand copying the po file from another module? greetings, -- Jordi Massaguer i Pla openTrends Solucions i Sistemes, S.L. Torre Llacuna C/Llacuna 166, 10º 1ª A 08018 Barcelona Phone: (+34) 93 320 84 14 Fax: (+34) 93 300 35 27 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] yast style guide meeting tuesday 29th january 16:00 CET
by Martin Schmidkunz 28 Jan '08

28 Jan '08

Hi, some of you suggested that the official yast channel is not appropriate for discussing style guide issues in an undisturbed manner, so we will meet in the "styleguide" channel on irc.freenode.org The meeting is scheduled for Tuesday, 29th January 2008, 16:00 CET until 17:00 CET. World times for this meeting: http://www.timeanddate.com/worldclock/fixedtime.html?day=29&month=1&year=20… The agenda will be the other full-screen dialogs: # Progress Dialogs (initializing, reading and writing...) # Dialog with Tabs # Tree Widget Dialog # Summary Dialog # Installation Proposal I think we can handle them quite shortly as it is mostly about: does it make sense how it is written down in: 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

[yast-devel] replace yast2/NetworkDevices by yast2/NetworkInterfaces
by Michal Zugec 25 Jan '08

25 Jan '08

Hi all, in yast2 package (version 2.16.23) I replaced deprecated NetworkDevices module by new one - NetworkInterfaces. First reason is just cometic - the name "Interfaces" is more close to it's real functionality. Second reason is some incompatible internal changes (device type is recognized not only by configuration name, but also by INTERFACETYPE option, ...) Affected packages are: dhcp-server, devtools, dns-server, firstboot, heartbeat, mail , nis-server, ntp-client, users. I changed them in svn or asked maintainers to do it, changed packages are not submited into autobuild. Please test your packages (manually and with testsuites) and submit them into autobuild. I didn't changed ipsec package, it seems to be no more used one, right? Thank you, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- 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] results of yast style guide meeting on 22th january 2008
by Martin Schmidkunz 24 Jan '08

24 Jan '08

Hi everybody, at the end of the e-mail you will find a summary of results from the YaST style guide meeting on 22th January. The only issue which was not discussed directly is the filter issue (last paragraph) within the overview dialog. AFAIK filters in overview dialogs are only used in the user/groups management dialog. Currently the filter and the filter selection are separated, but Jiri found a very nice way to get rid of this separation (see Bug 279959). If you have any comments on the results of our style guide meeting, please let me know. For the next meeting on Tuesday, 29th January, 16 CET, we can take a look at the other full-screen dialogs: # Progress Dialogs (initializing, reading and writing...) # Dialog with Tabs # Tree Widget Dialog # Summary Dialog # Installation Proposal I think we can handle them quite shortly as it is mostly about: does it make sense how it is written down in: http://en.opensuse.org/YaST/Style_Guide/Dialogs Thanks for the discussion and your comments last Tuesday! Cu, Martin Properties of a common dialog * Help text is displayed via a help push button aligned on the left side. A click on the button opens the help text in a new window. On the right side the module dialog is displayed. * All navigation buttons are located at the bottom line of the common dialog. * By clicking the "x" in the window decoration the dialog closes. If the user changed something a warning pop up is display and has to be confirmed. Technically this means: UI WM_CLOSE button must be handled as "cancel/abort/close" * YaST modules should use the wizard.ycp (framework) * Unnecessary buttons (e.g. next in a one screen dialog) should be disabled Properties of an overview dialog * The heading consist of module name + "Configuration" if the dialog is used for hardware and services configuration * The items should be displayed in a table * If detailed information is necessary it is provided by a rich text field at the bottom of the table. The conten of the rich text field changes when the user changes the item in the table. * To configure the items within the table a set of three push buttons with the labels "Add", "Edit", "Delete" is used. These three push buttons are aligned at the left bottom. * To provide "expert options" or other settings like "set default" align the corresponding push button on the right. Try to avoid menu buttons or combo boxes as they hide their content from the user. * An additional line of buttons between the buttons at the bottom of the table and the navigation buttons should be avoided * If filtering is needed use the space above the table. The current filter is displayed as a text label on the left side, the "Set Filter" combo box is aligned on the right. -- 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

[yast-devel] Sending signals to background process
by Kevin James 22 Jan '08

22 Jan '08

Hi, I've been working on a YaST module for a while now, and one of the things I needed to do was monitor a dd process running in the background, to provide a progress bar. Part of this involved sending Signal 10 (SIGUSR1) to dd to get it to print out the current progress - in doing this I added a function to ag_background called SigSubprocess, which is effectively a copy of the KillSubprocess function but it takes a parameter and sends that parameter as the signal to the background process. e.g. SCR::Execute(.background.sig, 10); I've included the patch here - is it possible to get this into the main source tree? I'm sure it would be useful in other circumstances... Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com

2 1

[yast-devel] basis for yast style guide discussion at 16:00 (CET)
by Martin Schmidkunz 22 Jan '08

22 Jan '08

Hi, if you want to take a look at the basis of the style guide discussion at 16:00 (CET), please go to: http://en.opensuse.org/YaST/Style_Guide/Dialogs and look at the "Full-screen Dialogs"- section. Please note that these are just some basic notes and not already the final status. 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

1 0

[yast-devel] BusyIndicator
by Thomas Goettlicher 17 Jan '08

17 Jan '08

Hi Katarina, hi Martin, could you proof read the BusyIndicator code, please? The widget has some limitation because of the timer stuff: - Only one BusyIndicator widget works at the same time because only one signalhandler can listen to the alarm event. I decided to connect the last created instance of the BusyIndicator what results that only one BusyIndicator shows progress. - The widget cannot work together with a UserInput widget because UserInput blocks while waiting for keystrokes and the alarm signal is not delivered. The result is that the BusyIndicator doesn't show progress. There is a simple workaround: If a TimeoutUserInput widget is used in a loop instead of a UserInput widget everything works fine. Maybe there is a solution to avoid these limitations using threads. As far as I know the ncurses-ui doesn't use threads right now. Please let me know your opinion about the BusyIndicator widget and whether there are any issues I can fix. Thanks a lot. Thomas -- 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] netcat required by yast-core
by Roman Drahtmueller 17 Jan '08

17 Jan '08

Hi, just briefly, why does yast-core require netcat? Thanks, Roman. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] better framework for module interaction?
by Duncan Mac-Vicar Prett 17 Jan '08

17 Jan '08

feature #302961: Integrated Software Management Application, which means basically integrate the repository editor with the package management application makes me think we are missing something in the YaST framework which I saw recently in the Android platform. Android separates each view in an activity. Each Activy chains with others (to generate a workflow) by generating Intents, and Activities can filter and respond to Intents too. (http://code.google.com/android/intro/anatomy.html) The idea is, if you wrte an application, and you need to edit a contact, or to select an geo-address. Your application don't care how you do it. It is not hardcoded. The activity generates an intent of "edit contact", or "select point in earth" and other activities will be launched, which of course registered ther capabilities. This allow the workflows to perform the tasks by selecting 1) the best 2) the user prefered, component to do the job. I think YaST is in the need of something similar, where modules could launch sub activities without knowing much about them. At least this would solve problems like integrating launching other modules from a module, and also would allow modules to be easily replaced and avoid all the hardcoding. What do you think? Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 7

[yast-devel] ABI again
by Martin Vidner 17 Jan '08

17 Jan '08

> URL: http://svn.opensuse.org/viewcvs/yast?rev=43683&view=rev > Log: > consistent constness > > Modified: > trunk/core/libyui/src/YCheckBox.h > trunk/core/libyui/src/YCheckBoxFrame.cc > trunk/core/libyui/src/YCheckBoxFrame.h ... > Modified: trunk/core/libyui/src/YCheckBox.h > URL: http://svn.opensuse.org/viewcvs/yast/trunk/core/libyui/src/YCheckBox.h?rev=… > ============================================================================== > --- trunk/core/libyui/src/YCheckBox.h (original) > +++ trunk/core/libyui/src/YCheckBox.h Wed Jan 16 18:39:06 2008 > @@ -173,7 +173,7 @@ > * > * Reimplemented from YWidget. > **/ > - virtual string shortcutString() { return label(); } > + virtual string shortcutString() const { return label(); } > > /** > * Set the string of this widget that holds the keyboard shortcut. This too is a change in the ABI. Please do not forget to add dependencies to the spec file. yast2-$UI.spec: Requires: yast2-core >= $NEWCORE Recently I saw a bug where a user updated only yast2-core by mistake but not the UIs and it started crashing too. It would be prevented by yast2-core.spec: Conflicts: yast2-$UI < $NEWUI (for all UIs) but I am reluctant about that one. -- 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

4 4

[yast-devel] BusyIndicator
by Martin Vidner 15 Jan '08

15 Jan '08

On Thu, Jan 10, 2008 at 04:07:46PM -0000, tgoettlicher(a)svn.opensuse.org wrote: > Author: tgoettlicher > Date: Thu Jan 10 17:07:46 2008 > New Revision: 43537 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=43537&view=rev > Log: > added BusyIndicator widget (fate #302559) Hi, Thomas has asked me for a review of the implementation, here it is: We are adding a new widget. In general, we need - documentation http://forgeftp.novell.com/yast/doc/SL10.3/tdg/Book-UIReference.html OK, it is there - implementation for all 3 UIs I see only qt. What about the rest? - proper dependencies because the ABI changes See below > Added: > trunk/core/libyui/doc/examples/BusyIndicator.ycp > trunk/core/libyui/src/YBusyIndicator.cc > trunk/core/libyui/src/YBusyIndicator.h > Modified: > trunk/core/VERSION > trunk/core/libyui/src/Makefile.am > trunk/core/libyui/src/YCPDialogParser.cc > trunk/core/libyui/src/YCPDialogParser.h > trunk/core/libyui/src/YUISymbols.h > trunk/core/libyui/src/YWidgetFactory.h > trunk/core/package/yast2-core.changes > ... > Added: trunk/core/libyui/doc/examples/BusyIndicator.ycp > URL: http://svn.opensuse.org/viewcvs/yast/trunk/core/libyui/doc/examples/BusyInd… > ============================================================================== > --- trunk/core/libyui/doc/examples/BusyIndicator.ycp (added) > +++ trunk/core/libyui/doc/examples/BusyIndicator.ycp Thu Jan 10 17:07:46 2008 > @@ -0,0 +1,33 @@ > +// Simple ProgressBar example BusyIndicator > +{ > + integer timeout = 1001; // in milliseconds > + > + UI::OpenDialog( > + `VBox( > + `BusyIndicator(`id(`busy), "Sample busy indicator", timeout ), > + `PushButton(`id(`alive), "send &tick"), > + `PushButton(`id(`query), "&query"), > + `Right(`PushButton(`id(`close), "&Close" ) ) > + ) > + ); > + > + > + while ( true ) > + { > + symbol button = (symbol) UI::UserInput(); > + > + if ( button == `alive ) > + { > + UI::ChangeWidget(`id(`busy), `Alive, true); > + UI::ChangeWidget(`id(`busy), `Timeout, 999); > + } > + else if ( button == `query ) > + { > + UI::ChangeWidget(`id(`busy), `Label, sformat("timeout: %1, alive: %2",UI::QueryWidget(`id(`busy), `Timeout), UI::QueryWidget(`id(`busy), `Alive))); > + } > + else if ( button == `close ) > + break; > + } > + > + UI::CloseDialog(); > +} > > Added: trunk/core/libyui/src/YBusyIndicator.cc > URL: http://svn.opensuse.org/viewcvs/yast/trunk/core/libyui/src/YBusyIndicator.c… > ============================================================================== > --- trunk/core/libyui/src/YBusyIndicator.cc (added) > +++ trunk/core/libyui/src/YBusyIndicator.cc Thu Jan 10 17:07:46 2008 > +const YPropertySet & > +YBusyIndicator::propertySet() > +{ > + static YPropertySet propSet; > + > + if ( propSet.isEmpty() ) > + { > + /* > + * @property integer Timeout timeout until busy indicator changes to stalled state in ms > + * @property bool Alive busy indicator is in alive or stalled state > + * @property string Label caption above the busy indicator > + */ > + propSet.add( YProperty( YUIProperty_Timeout, YIntegerProperty ) ); > + propSet.add( YProperty( YUIProperty_Alive, YBoolProperty ) ); > + propSet.add( YProperty( YUIProperty_Label, YStringProperty ) ); > + propSet.add( YWidget::propertySet() ); > + } > + > + return propSet; > +} > Added: trunk/core/libyui/src/YBusyIndicator.h > URL: http://svn.opensuse.org/viewcvs/yast/trunk/core/libyui/src/YBusyIndicator.h… > ============================================================================== > --- trunk/core/libyui/src/YBusyIndicator.h (added) > +++ trunk/core/libyui/src/YBusyIndicator.h Thu Jan 10 17:07:46 2008 > + /** > + * Return the current timout value. in milliseconds > + **/ > + int timeout() const; > + > Modified: trunk/core/libyui/src/YCPDialogParser.cc > URL: http://svn.opensuse.org/viewcvs/yast/trunk/core/libyui/src/YCPDialogParser.… > ============================================================================== > --- trunk/core/libyui/src/YCPDialogParser.cc (original) > +++ trunk/core/libyui/src/YCPDialogParser.cc Thu Jan 10 17:07:46 2008 > @@ -80,6 +80,7 @@ > #include "YTree.h" > #include "YWizard.h" > #include "YTimezoneSelector.h" > +#include "YBusyIndicator.h" > > using std::string; > > @@ -262,6 +263,7 @@ > else if ( s == YUIWidget_VSquash ) w = parseSquash ( p, opt, term, ol, n, false, true ); > else if ( s == YUIWidget_VStretch ) w = parseSpacing ( p, opt, term, ol, n, YD_VERT, true ); > else if ( s == YUIWidget_VWeight ) w = parseWeight ( p, opt, term, ol, n, YD_VERT ); > + else if ( s == YUIWidget_BusyIndicator ) w = parseBusyIndicator ( p, opt, term, ol, n ); > > // Special widgets - may or may not be supported by the specific UI. > // The YCP application should ask for presence of such a widget with Has???Widget() prior to creating one. > @@ -2198,6 +2200,9 @@ > * value will be 100. If you omit the optional parameter <tt>progress</tt>, the > * progress bar will set to 0 initially. > * > + * If you don't know the number of total steps you might want to use the > + * BusyIndicator widget instead of ProgressBar. > + * > **/ > > YWidget * > @@ -3307,6 +3312,54 @@ > return selector; > } > > +/** > + * @widget Busy Indicator BusyIndicator (make -C core/libyui/doc and see the generated docs to proofread it) > + * @short Graphical busy indicator > + * @class YBusyIndicator > + * @arg string label the label describing the bar > + * @optarg integer timeout the timout until busy indicator changes to stalled state s/timout/timeout/ in milliseconds, 1000ms by default > + * @usage `BusyIndicator(`id(`busy), "background action", 2000 ), > + * @example BusyIndicator.ycp > + * > + * @description > + * > + * A busy indicator is a bar with a label that gives feedback to the user that > + * a task is in progress and the user has to wait. It is similar to a progress bar. > + * The difference is that a busy indicator can be used when the total number of > + * steps is not known before the action starts. You have to send keep alive messages > + * by setting alive to true every now and then, otherwise the busy indicator will > + * change to stalled state. > + * > + **/ > Modified: trunk/core/libyui/src/YWidgetFactory.h > URL: http://svn.opensuse.org/viewcvs/yast/trunk/core/libyui/src/YWidgetFactory.h… > ============================================================================== > --- trunk/core/libyui/src/YWidgetFactory.h (original) > +++ trunk/core/libyui/src/YWidgetFactory.h Thu Jan 10 17:07:46 2008 > @@ -56,6 +56,7 @@ > class YTableHeader; > class YTimeField; > class YTree; > +class YBusyIndicator; > > > > @@ -102,6 +103,7 @@ > virtual YTable * createTable ( YWidget * parent, YTableHeader * header ) = 0; > virtual YProgressBar * createProgressBar ( YWidget * parent, const string & label, int maxValue = 100 ) = 0; > virtual YRichText * createRichText ( YWidget * parent, const string & text = string(), bool plainTextMode = false ) = 0; > + virtual YBusyIndicator * createBusyIndicator ( YWidget * parent, const string & label, int timeout = 1000 ) = 0; Adding a virtual method makes a library binary incompatible: http://techbase.kde.org/index.php?title=Policies/Binary_Compatibility_Issue… I see that you use the implementation pointer technique in the widget itself but we probably cannot avoid the ABI change for the factory class. So we have to add proper RPM dependencies. The easiest way should be changing the soname, like this in Makefile.am: -libpy2UI_la_LDFLAGS = -version-info 2:0 +libpy2UI_la_LDFLAGS = -version-info 3:0 -- 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

6 11

[yast-devel] yast style guide meeting tuesday 22th january 16:00 CET
by Martin Schmidkunz 15 Jan '08

15 Jan '08

Hi, in discussions with some developers and during our own work it turned out that it would be nice to have a style guide for YaST modules. In order to get one, Eva and I will prepare single pieces of it, which will be discussed with all interested persons on IRC. That is probably the best method to give as many people as possible the chance to participate in this project. The meeting will take place in the yast channel on irc.freenode.org and it is scheduled for Tuesday, 22th January 2008, 16:00 CET until 17:00 CET. World times for this meeting: http://www.timeanddate.com/worldclock/fixedtime.html?day=22&month=1&year=20… 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

[yast-devel] yast2-ncurses has a status line :)
by Katarina Machalkova 14 Jan '08

14 Jan '08

Hola brave yast hackers! As I kept receiving user complaints that the navigation in yast text-mode UI is a bit clumsy, I took my ITO and decided to do something with it. Here's the first bigger improvement (I hope so): We have many 'cheat-codes' for quick access to push buttons in text-mode in the form of Fxx keys, but: 1) hardly anyone knows about those 2) it is because they are well hidden in a pop-up that appears if F1 key is pressed (real hackers use F1 help key as the very last resort ;-) ) 3) this popup is so confusing that it leaves user even more clueless than (s)he was before (see ttps://bugzilla.novell.com/show_bug.cgi?id=335291) Now ncurses UI has a nice contrast status line where all Fxx cheat codes for current dialog are listed, as you can see in attached screenshot (I used yast2-users module as an example, because it makes quite intensive use of Fxx keys). User has these quick shortcuts in front of his/her eyes at all times and can use them right away without having to open a help popup or to remember that e.g. F10 usually stands for 'Finish'. The only disadvantage is that the status line takes yet another line off the small (and sometimes really crowded) text-mode screen :( Anyway, so far it's just a prototype, I'm thinkin about disabling status line completely should the screen be smaller than e.g. 25 lines ... So, enjoy this improvement and feel free to use Fxx shortcuts in your modules more intensively (hint: add `opt(`key_Fxx) to your widget to make it quickly accesible by selected Fxx key) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

14 34

[yast-devel] extra-packages
by Stephan Kulow 14 Jan '08

14 Jan '08

Hi! I would like to have the format of yast's extra-packages changed, so I can parse it easier in a script. Is there a problem with this? Greetings, Stephan

2 2

[yast-devel] My first ycp dialog :)
by Stephan Kulow 09 Jan '08

09 Jan '08

Hi! I thought prototyping in ycp is easier than creating mockups in gimp, so I coded http://ktown.kde.org/~coolo/yast7.png - but it looks weired - suggestions are welcome ;) Greetings, Stephan

11 29

[yast-devel] Unification of Fxx keys usage
by Katarina Machalkova 08 Jan '08

08 Jan '08

Hi, as the new version of yast2-ncurses that finally contains status line support has been submitted to abuild today, I'd like to ask you, yast hackers and module maintainers, for a favour. This request would be much more useful as a chapter in yast style guide, but as we have no styleguide, I'm using this e-mail channel. It would be really useful if the function keys for particular actions were more or less constant and did not change from module to module. So please check your modules if at least the following Fxx keys are assigned to these actions (i.e. do not assign them to any other action) F1- Help F3 - Add F4 - Edit/Configure/Change F5 - Delete F8 - Back F9 - Abort/Cancel F10 - Next/Finish/Accept/OK Ncurses navigation help also mentions F2 - Info, F6 - Test, F7 -Expert/Advanced, but this would be imho pretty tight requirements, so try to stick to the ones listed above and use the remaining function keys as you wish. Some cases where these rules are currently broken: include/printer/dialogs-cups.ycp: F4 assigned to 'Delete' (use F5) clients/ldap_browser.ycp: F5 assigned to 'Reload' (use e.g. F6) include/bootloader/routines/dialogs_i386.ycp: F8 assigned to 'Cancel' (use F9) Thanks for keeping ncurses UI well-usable :) B. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] libyui throwing exceptions
by Martin Vidner 08 Jan '08

08 Jan '08

> URL: http://svn.opensuse.org/viewcvs/yast?rev=43316&view=rev > Log: > - Fixed crash when running text-mode menu as > non-root user (new libyui throws an exception > if SelectionBox entry is nil) Hi, so I learn that the new libyui throws exceptions in certain cases and some of them are not caught, causing yast to abort. I understand that such cases are errors in libyui usage and fixing the individual cases like this one is fine. Still, YaST should not crash. Shouldn't we revert to the old behavior of graceful degradation where the YCP code gets nil and manages to recover? I suppose that it can be done by one catch somewhere in the UI bindings. (The log should say "libyui usage error, please report in bugzilla, search for 'WidgetItemIsNilException' first") -- 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

4 8

[yast-devel] 11.0 Alpha Yast Installer Font
by Bryen 03 Jan '08

03 Jan '08

This should probably be mentioned over in Factory, but I thought I'd come here straight to the source. :-) I just downloaded the latest Alpha Boot CD to install on my test machine. I see the new, and beautiful green Installer that Coolo mentioned in a previous post. Only problem I have, as a low-vision person, is that its a bit harder to read. I'm not sure if the font size is the same as it was in the old installer or if it is due to the new background contrast. Also, I tried the installer twice, first in 1024 resolution and then in 800 resolution, and both times, the font size remained apparently the same. But text did get cut off along some edges in the 800x600 resolution. I have not tried just standard text mode yet. But low-vision folks shouldn't have to sacrifice the beauty of the new installer. :-) We just need to find a way to manage font size for the installer. Or is there a way to do that currently, and I'm not aware? -- ---Bryen--- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1