January 2008 - YaST Development - openSUSE Mailing Lists

[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