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
Hi everybody,
the results of the hard disk configuration survey are available at
http://en.opensuse.org/UX#View_results_of_previous_surveys
Big thanks to all of you who took the time in participating!
Your answers were very helpful!
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
Hi,
I plan to create branches in the yast and zypp repositores as soon
as RC1 is announced.
That will mean trunk will be open for 11.1 development. But do not
forget to apply 11.0 fixes both to trunk and the branch until 11.0
is released.
Here is the proposed text for the branch docs:
http://en.opensuse.org/YaST/Development/SVN_branches
Development Branches
openSUSE 11.1
URL: http://svn.opensuse.org/svn/yast/trunk/
Version: 2.17.*
Note: We use trunk for the development.
SLE 10 SP3
URL: http://svn.opensuse.org/svn/yast/branches/SuSE-SLE-10-SP3-Branch/
Version: 2.13.* (continues on the previous version line 2.13)
Important: Submit new features and fixes to trunk as well
Note: We use this branch for SLE 10 SP3 development
Maintenance Branches
openSUSE 11.0
URL: http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-11_0-Branch/
Version: 2.16.*
Note: Only shipstoppers now, maintenance updates then.
They must be approved by FIXME
SLE 10 SP2
URL: http://svn.opensuse.org/svn/yast/branches/SuSE-SLE-10-SP2-Branch/
Version: 2.13.X.* ('x' means the last version before SLE-10-SP3 branch was created)
Note: Every patch must be approved by hmuelle
Note: Do not forget to merge the fixes not only to the trunk but also to SP3.
--
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
present: kkaempf, visnov, jsrain, dmacvicar
* scope of the call: look into concrete opportunities for YaST and
follow with concrete actions and scenarios.
* autodriver installation: dmacvicar looking into integrating
recommended hardware packages to applications.
(FATE 303677)
* packagekit lock API: kkaempf suggest proposing this API into packagekit.
use case: Be able to say 'no, I dont want this' when PackageKit pops
up asking to install a driver.
Developer use case: I am following the source repo for this driver and
I do not want the package.
* shaas should be exploring CIM sw-mgmt in windows to find out about the
model.
* kkaempf has been writing cmpiswig, writing providers in scripting
languages. together with ws-man bindngs, the scripting stack is mostly
complete.
* arvin request on swig and libstorage, how to export structs into ycp
space is worth looking (http://en.opensuse.org/YaST/What_Sucks)
* visnov: looked into django. AI: write-down impression
http://www.djangoproject.com/ (Django is a high-level Python Web framework
that encourages rapid development and clean, pragmatic design.)
* topic: zypper/libzypp plugin interface, hooks. scripting languages.
worth exploring
* visnov: yast bindings use 4 pkbindings functions:
- available, installed, install package, and other. (Package.ycp) that
should be ported to packagekit
(would remove libzypp dependency)
- looking dbus support for ycp
* AI: satsolver-tools testcases for other parsers (kkaempf done
updateinfo and content)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Prague YaST2 team meeting 2008-05-27
====================================
Present: jkupec, jreidinger, jsrain, jsuchome, juhliarik, kmachalkova,
locilka, lslezak, mvidner
Absent: mzugec
Minutes: juhliarik
New branches (mvidner):
----------------------
- Martin plans to create branches (SP3, 11.1) in the yast and zypp repositores
as soon as RC1 is announced.
zypper/libzypp:
--------------
- PoolQuery::setVersion() has been added to be able to search by version
(and to be able to support all that was supported in the old zypp locks)
(jkupec)
- zypper now sets the new 'ignoreAlreadyRecommended' solver flag - false
for dist-upgrade and a new 'install-new-recommends' command, true for
all other commands. This solves the problem of "'zypper in foo', foo not
found, but i will install a bunch of other packages if you want" :O)
(jkupec bnc #389694)
- simple "(X/Y)" for "installing Xth of Y packages" counter added to zypper's
output (jkupec bnc #240588)
- added convertor for converting old locks to new (jreidinger)
- there is a problem with time consuming searching of locks if a lock contains
an unknown attribute (the query ignores such attributes and can return a lot
more packages than intened). We need to find a way how to at least log such
cases, currently we are not able to tell whether the attribute is known or
not. (jreidinger)
Add-On Creator (jsuchome):
-------------------------
- enable reading patterns if they are stored in one file (bnc#393515)
- updated to support latest version of pattern metadata
- added sysconfig variables to handle compressing the metadata
Misc:
-----
- In 2nd stage without automatic configuration, internet test couldn't be
performed as no URL for downloading release notes has been defined. A new
function has been added to Product module (Product::ReadProduct) to read
available product and its attributes on the installed system and in 2nd
stage, which is now used in YCP script testing internet connection.
(kmachalkova - bnc #390738)
- With libyui and ncurses, it is not possible to create dialogs beforehand on
the stack and open/close them only when needed. It may result in the
situation where topmost dialog cannot be closed at all. Thus, any pop-up
dialog should be created on demand only. (kmachalkova - bnc #384368)
- Creating backup of /etc/pam.d/ during upgrade to openSUSE 11.0 (locilka -
bnc #393066)
- Currently impossible to build YaST documentation for openSUSE 11.0 due
to several package-splits, and moved or renamed docu-files. (locilka, mvidner)
- locking packages for PPC64 (lslezak - bnc #336678)
- The product creator doesn't support more pattern definitions in one file.
Will be fixed after 11.0.(lslezak)
- OES2 + SP2 doesn't work (mvidner)
- solved problem with editing boot section for lilo (juhliarik)
- Image Creator (part of yast2-product-creator) is updated. it supports
current version of kiwi e.g. added support for profiles (jsuchome)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi,
I am trying to install RC1 on my old notebook. A change compared to
10.3 is that I get a kernel panic before linuxrc comes up.
http://en.opensuse.org/Installation_with_Little_Memory
says to use _tmpfs=0 which does help (although
http://en.opensuse.org/Linuxrc says _TmpFS is "No longer supported")
But as it says, the system is indeed extremely slow and little
memory is left. I am somehow disappointed because I was hoping that
the refactored zypp would actually free some memory. Are there any
other tricks I could try?
--
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
Hi!
I compiled YaST and one yast module (yast2-iscsi-client as an example
that it works) on Fedora Core 9:
http://mzugec.blogspot.com/2008/05/research-of-possibility-running-yast.html
This is of course only first step to make it really usable or really
cross-distribution upstreamed tool.
I compiled also libzypp/zypper and do some tests to compare their speed
(installation source is local CD):
[root@dhcp24 ~]# time echo "y"|yum install rpmlint
Loaded plugins: refresh-packagekit
fedora | 2.4 kB 00:00
updates | 2.3 kB 00:00
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package rpmlint.noarch 0:0.82-3.fc9 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
rpmlint noarch 0.82-3.fc9 fedora
178 k
Transaction Summary
=============================================================================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 178 k
Is this ok [y/N]: Downloading Packages:
(1/1): rpmlint-0.82-3.fc9.noarch.rpm | 178 kB 00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: rpmlint ######################### [1/1]
Installed: rpmlint.noarch 0:0.82-3.fc9
Complete!
real 0m15.552s
user 0m9.794s
sys 0m3.801s
And after uninstalling the same with zypper:
[root@dhcp24 ~]# time zypper -n in rpmlint
Reading installed packages...
The following NEW package is going to be installed:
rpmlint
Overall download size: 178.0 K. After the operation, additional 178.0 K
will be used.
Continue? [YES/no]: yes
Downloading package rpmlint-0.82-3.fc9.noarch (1/1), 178.0 K (178.0 K
unpacked)
Installing: rpmlint-0.82-3.fc9 [done]
real 0m4.922s
user 0m1.561s
sys 0m2.610s
That's great for us, isn't it? ;-)
Bye,
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
Hello,
trying to compile yast-$SUBJ package I have following error message:
YCP.cc:15:33: error: ycp-ui/YUIComponent.h: No such file or directory
On 10.3 that file was part of yast2-core-devel. But now (11.0) I can't
found it. I suppose it should be in libyui package, but no success ...
Anybody knows? ;-)
Thanks,
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
Hi!
This is just a reminder, that the text freeze for openSUSE 11.0 strings in
YaST is on Monday, April 21st, 10:00 AM.
After the text freeze, string changes are only allowed, if the original
message is so bad that translators do not have a chance to get it right.
String additions due to bug fixes or because of missing _("tagging") are
allowed.
Typos and other cosmetical things will be fixed with overloads in en_GB.po and
en_US.po files.
Jiri
--
Regards,
Jiri Srain
YaST Team Leader
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz
Lihovarska 1060/12 tel: +420 284 028 959
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz