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