May 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] icons in modules
by Martin Schmidkunz 16 May '08

16 May '08

Hi, while testing openSUSE 11.0 I noticed, that none of the modules has an icon in the heading. Is that on purpose? Have a lot of fun, 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

4 3

[yast-devel] Bug or missing Packet 11.0
by Günther J. Niederwimmer 16 May '08

16 May '08

Hello, I like to build the YaST2 Module YaSt2-Mail, i have this Error for yast2_ui_pkg? But I can't found this ? techz:/data/BuildServer # ./build_SL110 yast2-mail logging output to /Test/SL-110/build-root/.build.log... techz started "build yast2-mail.spec" at Fri May 16 06:17:28 CEST 2008. Using BUILD_ROOT=/Test/SL-110/build-root Using BUILD_RPMS=/datas2/SUSE/RPMS/OS110/i586:/datas2/SUSE/opensuse/update/11.0:/datas2/SUSE/opensuse/distribution/SL-OSS-factory/inst-source:/datas2/SUSE/opensuse/distribution/SL-OSS-factory/inst-source/suse:/datas2/SUSE/opensuse/distribution/SL-Factory-non-oss/inst-source-extra Using BUILD_ARCH=i586:i486:i386 processing specfile /data/BuildServer/yast2-mail/yast2-mail.spec... init_buildsystem yast2-mail.spec ... expanding package dependencies... expansion error have choice for yast2_ui_pkg needed by yast2-packager: yast2-ncurses-pkg yast2-qt-pkg yast2-gtk have choice for glib2-branding needed by glib2: glib2-branding-upstream glib2-branding-openSUSE -- mit freundlichen Grüßen / best Regards Günther J. Niederwimmer -- 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] Fwd: web based YaST (2)
by mzugec＠suse.cz 15 May '08

15 May '08

Hello, I found very interesting framework: http://excess.org/urwid/ It supports both ncurses and web-based UI! Since we have python bindings we can do some reasearch/propotype. Of course I'm volunteer but not immediately, so if anybody have a time ... ;-) Some example: http://live.excess.org/cgi/calc Bye, Michal -- 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] Czech YaST2 team (Prague) meeting 2008-05-13
by Jiri Srain 15 May '08

15 May '08

Czech YaST2 team (Prague) meeting 2008-05-13 ============================================ Present: jkupec, jreidinger, jsrain, jsuchome, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec Minutes: jsrain Current activity: - everybody is fixing bugs for openSUSE 11.0 - lock API is now available via zypper (jreidinger) - zypepr removelock command now takes also a string argument. Lock callbacks have been implemented to allow interactive lock removal in case of ambiguities (jreidinger) - lock API is now available via Pkg bindings, is being used to lock 64-bit packages on 32-bit PPC (bnc#336678) (lslezak) - 127.0.0.2 problem strikes back (bnc#383336) (kmachalkova) - several crashes of YaST caused by changes in libyui (some warnings in former version now cause exceptions) - link to repo selector from package selector is now optional (bnc#381956) (lslezak) - fixing SDK migration (mvidner)

1 0

[yast-devel] Prague YaST team meeting 2008-05-06
by Josef Reidinger 09 May '08

09 May '08

Prague YaST team meeting 2008-05-06 =================================== Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome, kmachalkova, locilka, lslezak, mzugec Absent: mvidner (holiday) Minutes: jreidinger Next minutes: jsrain libzypp ------- - search now support all features which is in zypper in 10.3 (jkupec) - cleaning immediately downloaded packages (jreidinger) (bug #381311) zypper ------ - smart summary width(jkupec) - smart repository select options (jreidinger) Yast2-network ------------- - 127.0.0.2 bug strikes back #383336 (kmachalkova) - fix in SP2 problem with more than one DNS server definition in /etc/hosts. These were wrongly listed as 'domain' instead of 'search', producing invalid /etc/hosts file. (bnc #376410) Instalation ----------- - add priority and alias to repository (locilka) Command line mode (lslezak) ----------------- - Command line interface doesn't work with ncurses UI when any UI:: call is evaluated (even UI::GetDisplayInfo()). Please check your yast modules in command line mode using ncurses UI ('yast <module> help'). Preferably in Beta2, Mode.ycp and PackageCallbacks.ycp were recently fixed to be CLI compatible Sound Card Configuration ------------------------ - sound card without PCI id added to MODULES_LOADED_ON_BOOT to correct initialize (bnc#331659) pkg_bindings (lslezak) ------------ - implementing persistent locking api (bnc#336678 (lock 64bit packages on ppc32) ) network ------- - instead rewriting line only substitute changed parts in udev rules (mzugec) -- 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] isLayoutStretch
by Ricardo Cruz 09 May '08

09 May '08

Hi there, Would be great if we could make YLayoutBox::isLayoutStretch(YWidget*) public. In fact, what about moving isLayoutStretch to YWidget together with the rest of the layout properties? Thanks, Ricardo -- 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] Selection delay for ComboBox widgets?
by Stefan Hundhammer 05 May '08

05 May '08

https://bugzilla.novell.com/show_bug.cgi?id=382755 shows that it might be useful to add a timeout to the ComboBox widget so it holds back events when many (keyboard) events occur in a short time frame. Our SelectionBox widget and (since some weeks) our tree widget behaves in that way: When you go through multiple items in a short time, only the last event gets delivered, not all the intermediate events. This can make cursor key navigation (or dragging with the mouse) in such a SelectionBox or tree much more useful: When expensive operations are performed at each such event and only the last of those events is meaningful anyway, the intermediate events are not delivered, so they don't have any impact on performance. Example: +------------- | [Item 001] | | Item 002 | | Item 003 | . ... ... . . ... ... . | Item 999 | +------------+ Keeping "cursor down" pressed until "Item 999" is reached would not make UI::UserInput() or UI::WaitForEvent() return for "Item 002", "Item 003", etc.; only for "Item 999". See also http://svn.opensuse.org/svn/yast/trunk/libyui/examples/SelectionBox2.cc for a UI example that allows experimenting with that (use the "notify" and "immediate" check boxes and watch the "value" field as you keep cursor keys pressed in the SelectionBox or drag the mouse there). This behaviour usually useful, but it comes at a cost: An event is always only delivered after the timeout is expired. The Qt UI uses 200 milliseconds (the same as the mouse double click interval), so it's not too bad, but it can make an application appear less responsive. That's what `opt(`immediate) is for for SelectionBox and tree widgets. By default, the 200 millisecond timeout is used (for those widgets, not for everything), but with `opt(`immediate), the events are delivered immediately. But in that case, you will also get events for each of "Item 002", "Item 003", etc. - that's the tradeoff. Now here is the question: Can we safely add this to ComboBox widgets, too? Right now, events are delivered immediately, i.e., it behaves as if `opt(`immediate) were set, too. Should we add the timeout, the default behaviour would change: There would be the 200 millisecond timeout with `opt(`notify). Application developers (YCP hackers) that don't want this behaviour for whatever reason would have to add `opt(`immediate). Another factor are editable ComboBox widgets. I am unsure how they should behave. Remember, with `opt(`notify) you get individual key presses (just like in InputField / TextEntry), and delaying them, too, might result in odd application behaviour (or wouldn't it?). Would we want that timeout behaviour there, too? Or would we just do it for non-editable ComboBox widgets? Opinions? Problems with such a change? Anything I overlooked? CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- 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] openSUSE hard disk configuration survey
by Martin Schmidkunz 05 May '08

05 May '08

Hi! We are currently conducting a survey about hard disk configuration. It is available via http://www.surveymonkey.com/s.aspx?sm=lnZcsBO6PqJ9hjNW01jiyQ_3d_3d or http://en.opensuse.org/UX The survey will be online until 28th May 2008 and the results will be published on openSUSE.org as soon as possible Answering the questions will take less than five minutes. Thank you and have a lot of fun, 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