February 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] printer module redesign
by Martin Schmidkunz 05 Feb '08

05 Feb '08

Hi everyone, as some of you may know it is now almost a year since we first try to think (again) about a redesign of the printer module. And now we are ready to present you a first release candidate :-) You find it on: http://en.opensuse.org/YaST/Development/Printer_Enhancement#Release_Candida… I am very happy with it as it cleans up the kerfuffle the current module shows at present: * the depth of workflow was reduced from 9 levels to 3 * overall number of screens was reduced from over 30 to 10 * technical short wording was replaced by explanatory wording, which is easy to comprehend * dialog layout which also confused expert users was replaced by simple, meaningful layout (or to put it into more poetic words: the user was released from his dungeon :-)) At this point I would like to thank: * Michal Zugec for putting the UI redesign on the agenda (and especially in autumn when everyone already forgot about it) * Johannes Meixner for his endless time, patience and comments * everyone on the lists for their comments and participation I am looking forward to your comments! Have a nice weekend, 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

12 32

[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] Transactional upgrades using the filesystem
by Duncan Mac-Vicar P. 04 Feb '08

04 Feb '08

We have some features open for rollbacks on upgrades. Give a look at this: "There is no ideal software, it always has bugs. Minor, major or security issues will always exist and modern operating systems need to deal with this fact. What if any software which user installs had a capability to rollback to previously known successful point and operation itself would take no time? What if developer or user has a tool which could checkpoint operating system and capability to revert changes in no time? This is possible if we will marry two great technologies: ZFS and Debian APT <http://www.nexenta.org/os/TransactionalZFSUpgrades>. Both technologies now part of Nexenta Operating System which is core foundation for its derivative distributions. Meet apt-clone <http://www.nexenta.org/os/AptCloneMan>. The tool which integrates with the NexentaCP system, keeps track of upgrade checkpoints and allows to create/destroy/edit checkpoints by request." http://osnews.com/story/19180/Transactional_Debian_Upgrades_with_ZFS_on_Nex… -- 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] style guide meeting canceled
by Martin Schmidkunz 04 Feb '08

04 Feb '08

Hi everyone, I am sorry, but due to my current work with the printer module I was not able to prepare anything for the style guide meeting tomorrow. So as long as anyother doesn't want to jump in (topic would be "pop ups") I say we cancel the meeting and see us on Tuesday next week. 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] any inst_ldap-client?
by Jordi Massaguer Pla 01 Feb '08

01 Feb '08

Is there any inst_ldap-client we could use for a custom installation? We would like to set up the ldap without going into the inst_user.ycp. The problem we are in now is that inst_user trys to show the add new user dialog, and we do not want this to be shown, even when we accept the default ldap configuration. Right now we are patching inst_user.ycp but I understand this is not the way. Any pointers? thanx jordi -- 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 9

[yast-devel] Czech YaST2 team (Prague) meeting 2008-30.1
by Michal Zugec 01 Feb '08

01 Feb '08

Czech YaST2 team (Prague) meeting 2008-01-09 ============================================ Present: jkupec, jsrain, jsuchome, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec Absent: - Minutes: mzugec Next minutes: jkupec libzypp ------- MediaCurl: full support of .curlrc syntax has been added in order to read proxy authentication data correctly kerberos -------- There is support to obtain kerberos-related informations from dns-server (Fate 301812). users ----- Module was rewritten to use CWMTab (#279959) There are plans to move users module to first stage during installation. Implementation fo this is in progress. ncurses ------- Ncurses package manager failed to close all open dialogs on exit, causing installation to be unable to proceed or crash completely (bug #354712) Busy indicator implementation in ncurses was rewritten to make use of the main UI idle loop. So it now needs threads instead of alarms, because only re-entrant functions can be called safely from signal handlers. Yet the implementation is not perfect (bug #355562) controlcenter -------------- YaST team together with usability team works on redesign of Control Center. We like systemsettings from KDE4. installation ------------ Desktop selection - checkboxes are away. See next alpha. installation sources -------------------- There is new possible installation source - USB stick. SP2 migration ------------- The migration is in stage when should work and you can test it. https://wiki.innerweb.novell.com/index.php/SLE10_SP2_Migration printer ------- netcat is not required, just recommended. In case it's not installed, all dialogs (buttons) that runs scripts required netcat are disabled. iSCSI initiator --------------- yast2-iscsi-client in SP2 now uses upstream-like syntax on iscsiadm output (backward-compatibility patch against upstream was removed). -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0