September 2008

[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(… [View More]

4 6

[yast-devel] Proposition: Input domain in static network configuration
by Arthur Rodrigo Sawazachi Valadares 03 Sep '08

03 Sep '08

Hi, I wanted to propose a patch for linuxrc (initially) to allow the user to set search domain on static network configuration (DHCP already pulls this info from server, but in the future we could also allow the user to input extra domains). This would allow the user to type simple hostnames instead of fully qualified hostnames for NFS, FTP, etc throughout the installation. Any comments and suggestions are welcome =) Thank you, Arthur V. -- To unsubscribe, e-mail: yast-devel+unsubscribe(… [View More]

1 0

[yast-devel] Hackweek: Unified Installation Progress
by Stanislav Visnovsky 02 Sep '08

02 Sep '08

Hi Hackers! So, Hackweek III is over and here is the result of my work - a grand unified installation progress. Global progress =============== The basic idea is that the progress consists "stages" - during a new install, there are 3: disk preparation, image deployment and package installation. Before the first client using the unified progress, the stages need to be set up, e.g. : list< map<string,any> > stages = [ $[ "name" : "disk", "description": _("Preparing … [View More]disks..."), "value" : Mode::update() ? 0 : 120, // 2 minutes, who needs more? ;-) "units" : `sec, ], $[ "name" : "images", "description": _("Deploying Images..."), "value" : ImageInstallation::TotalSize() / 1024, // kilobytes "units" : `kb, ], $[ "name" : "packages", "description": _("Installing Packages..."), // here, we do a hack, because until images are deployed, we cannot determine how many // packages will be really installed additionally "value" : (PackageSlideShow::total_size_to_install - ImageInstallation::TotalSize()) / 1024 , // kilobytes "units" : `kb, ], ]; SlideShow::Setup( stages ); The function will calculate the partitioning of the unified progress based on estimate of a needed time. A stage can provide the estimate of time or an amount of data to be transferred (the constants used are based on assumption of 15 min install time and that the data are downloaded and written to disk). The logic is no rocket science as the only goal for a progress bar is to have it move somewhat regularly. A client using the new unified progress will do basically 2 things: 1) calls SlideShow::MoveToStage( stage-id ) - this will move the global progress to a proper position for start of the stage and updates also the label ("description" entry in the map) 2) calls regularly SlideShow::StageProgress( new_percent, new_label ) - new_percent is the progress inside of the current stage, the library will recompute this to get a global progress percents. - if new_label is nil, label is not updated. More functionality ================== The SlideShow dialog contains the following functionality: - global progress (see above) - subprogress for the current action (e.g. download a package, format disk, ...) - installation log - slide show support - optional package table - release notes viewer See the SlideShow API how to handle those. Implementation Notes ==================== During the hacking, I've splitted the old SlideShow module into 3: - Slides.ycp - handling of slide loading from the installation medium - SlideShow.ycp - generic API for the unified installation progress - PackageSlideShow - code specific for handling package installation, e.g. CDs, summary table, .... Attached are the complete new modules as diffs do not make much sense. Next, there is updated control.xml with a new installation client inst_prepareprogress which sets up the stages for normal installation. The rest are diffs for adapting to new APIs. Influenced code is in yast2-installation, yast2-packager and yast2-storage I've tested the code on modified alpha2 - new installation, update and also on running system. Qt and ncurses. Stano [View Less]

2 3

[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 … [View More]

3 2

[yast-devel] Re: [zypp-devel] Enabled distupgrade of the SAT solver
by Stefan Schubert 02 Sep '08

02 Sep '08

Cristian Rodríguez schrieb: > Stefan Schubert escribió: > >> Hi, >> I have enabled the distupgrade of the SAT solver. In order to use the old >> distupgrade you can set the environment variable ZYPP_NO_SAT_UPDATE. >> But this should be used as fallback only :-) >> >> This variable will can be used until the old distupgrade mechanism will >> be removed from libzypp. >> I will send an EMAIL when this happens. >> > > Will be … [View More]

1 0

[yast-devel] Enabled distupgrade of the SAT solver
by Stefan Schubert 02 Sep '08

02 Sep '08

Hi, I have enabled the distupgrade of the SAT solver. In order to use the old distupgrade you can set the environment variable ZYPP_NO_SAT_UPDATE. But this should be used as fallback only :-) This variable will can be used until the old distupgrade mechanism will be removed from libzypp. I will send an EMAIL when this happens. Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 … [View More]

1 0

Main

Development

Information

Community

Social Media

Other

YaST Development