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,
as you might have noticed I just committed quite some changes to the
ldap-server module in trunk. This is the result of the work I have been
doing recently in a local git (git-svn) tree.
The changes are an almost complete redesign of the ldap-server agent,
YaST-API and parts of the GUI (more to come). I needed to do that to
make yast2-ldap-server support a new configuration mechanism of
OpenLDAP that allows the server to be mananged completely via LDAP (as
a result of that, no restarts are needed and config changes are
effective immediately).
I am not completely done with the changes yet, but the module is now in
a state that it can be built again as an RPM and it creates a valid
running OpenLDAP configuration (most of the times ;) ). Some things
however do not yet work.
The biggest missing/broken thing is the YaPI interface that some other
YaST Modules (samba, mail, dns and dhcp) use to access the OpenLDAP
configuration (add Schema, change Database-Indexes). I hope to have
that fixed or offer a different way to access the functionality really
soon now and will keep you updated in case that some changes are
required in those modules.
Other non working things are:
- AutoYaST support
- Some of the options offered in the GUI don't hit the configuration
database yet
- Documentation is lacking
- Some feature available in the old module might currently be missing.
- The module itself has still quite a lot of rough edges
--
regards,
Ralf
PS: Sorry for the big amount of commit traffic but I wanted to keep the
history intact (using git-svn dcommit).
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Prague YaST Team Meeting 2008-06-24
===================================
Present: jkupec, jreidinger, jsrain, juhliarik, jsuchome,
kmachalkova, locilka, lslezak, mvidner, mzugec
Product Creator
---------------
Support for multiple patterns in one file has been added to the product
creator module.
Yast Documentation
------------------
Documentation for Yast in openSUSE-11.0 is available at
http://forgeftp.novell.com/yast/doc/SL11.0/
Other Distributions
-------------------
http://mvidner.blogspot.com/search/label/cultural%20exchangehttp://en.opensuse.org/GNOME/Projects/Lived_in_Project
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi,
I have now reworked the 'YaST as a Service' wiki page[1] to better
explain the architectural concept and the concrete implementation
proposal.
This project does not intend to supersede other projects (Make YaST
Independent of YCP, Using CIM from YaST modules, YaST DBus Service, YaST
PackageKit Service, YaST Web User Interface) but intends to show how a
combination of them can lead to a next-gen YaST architecture.
Klaus
---
[1] http://en.opensuse.org/YaST/Research/YaaS
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi,
if you get the error "multiple target patterns"
(when making the documentation in core),
it is because "make" gets confused when a file name contains
colons.
1) please get yast2-devtools-2.17.0+:
Mon Jun 9 11:29:04 CEST 2008 - mvidner(a)suse.cz
- ydoc.xsl: don't break on builtins in namespaces.
2) rm html/*::*
3) if (2) does not help, then make clean, or otherwise make sure
that the "id" attribute in the *.xml docs does not contain colons.
Sorry for the trouble.
--
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,
Maybe a stupid question ;) but could we reuse the code we actually have
for Qt user interface and link it with 'QxtWeb Module'?
http://docs.libqxt.org/group__QxtWeb.html
QxtWeb provides tools for creating event-driven web services using Qt.
The general usage pattern is as follows:
* Create a QxtAbstractWebSessionManager object, such as
QxtHttpSessionManager, for each protocol that can interface to the
service.
* If using QxtHttpSessionManager, select a connector plugin, such as
QxtHttpServerConnector.
* Register a QxtAbstractWebService factory. The factory is invoked
each time a new session is created and returns a service object
for that session. QxtWebServiceDirectory allows you to register
multiple services and selects between them based on the path.
* Invoke QxtAbstractWebSessionManager::start() to begin accepting
connections.
Could any Qt guru review that, please :)?
Thx
Lukas
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d)
-----------------------------------------------------------------
Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
Hi everyone,
please find a new version of the YaST style guide draft at:
http://en.opensuse.org/Image:Ysg2.pdf
The goal is to have a developer friendly style guide which ensures the
greatest possible consistency between various modules and various
environments.
The time line for the style guide is to discuss it the next two weeks
and to have an executable style guide by the end of the YaST workshop.
I would like to ask and encourage you again to discuss it!
What do you like?
What do you dislike?
What is missing?
Just to come up with some points of discussion:
* button labeling: OK/Cancel instead of Apply/Accept/Abort/... and
Next/Back/Cancel/Finish in a wizard/add workflow
I know OK/Cancel is not 100% correct but with these two labels we are
consistent to GNOME HIG and KDE
http://library.gnome.org/devel/hig-book/stable/windows-utility.html.en#expl…http://developer.kde.org/documentation/standards/kde/style/dialogs/index.ht…
* Progress dialogs
I propose to skip the cancel button because I made the experience that
in many cases the cancel button does not work
* Number of steps in a wizard
I propose to skip the display of "Step XX of XX" because the number of
steps can not predicted in every module
* colons
In accordance to GNOME
(http://library.gnome.org/devel/hig-book/stable/controls-option-menus.html.en)
and KDE style guide
(http://developer.kde.org/documentation/standards/kde/style/basics/labels.ht…)
I propose to use colons with the label of a combo box
And of course there might be many more issues worth to be discussed :-)
The style guide is based on the style guide in the wiki
(http://en.opensuse.org/YaST/Style_Guide) developed by Lukas and me and
when we agreed on one version it will be published in the openSUSE wiki
again.
Looking forward to your opinions!
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
Hello,
this is a preliminary schedule, also published on the wiki:
http://en.opensuse.org/YaST/Events/Workshop_Nuremberg_2008#Schedule
* Monday: 11:30 Arrival from Prague, 12:00 Opening&Lunch
* Tuesday: 12:00 Lunch, 13:00 5+5 minutes each team
* Wednesday: 12:00 Lunch, 13:00 5+5 minutes each team, 15:00 Outdoor event, 18:00 Dinner
* Thursday: 12:00 Lunch, 13:00 5+5 minutes each team
* Friday: 12:00 Lunch, 13:00 Wrapup, 15:00 Departure (to Prague)
Not much is planned as most of the time should be spent by ... hacking :-)
Thanks
Michal
On Fri, 13 Jun 2008, Michal Švec wrote:
>
> Hi all,
>
> first of all I'd like to thank you for the hard work on openSUSE 11.0,
> it's definitely going to be a great release!
>
> Having said that I'm pleased to announce YaST Workshop 2008, taking place
> in Nuremberg, June 30 to July 4.
>
> The main goal is to move YaST further, both in terms of functionality, but
> also higher flexibility and more openness. We want to give developers a
> chance to work on something new, something we often neglected for some
> time, something cool and also have fun with that.
>
> The details about the workshop can be found here:
> http://en.opensuse.org/YaST/Events/Workshop_Nuremberg_2008
>
> As it is supposed to be a team work, I'd like to encourage you to have a
> look at the ideas, enlist yourself at those you would like to work on and
> use the time until the workshop to look around the topics and learn new
> things, possibly using your ITO. The list of ideas is not closed so
> anybody can expand the list with further ideas.
>
> Also, the event is not closed, if you would like to work with a collegue
> from a different team or department on the project, feel free to invite
> him to take a part (and let us know in order to prepare the logistics).
>
> I strongly believe this would be fun and useful as well and I'm looking
> forward to it.
>
> Thanks
> Michal
>
Hi all,
first of all I'd like to thank you for the hard work on openSUSE 11.0,
it's definitely going to be a great release!
Having said that I'm pleased to announce YaST Workshop 2008, taking place
in Nuremberg, June 30 to July 4.
The main goal is to move YaST further, both in terms of functionality, but
also higher flexibility and more openness. We want to give developers a
chance to work on something new, something we often neglected for some
time, something cool and also have fun with that.
The details about the workshop can be found here:
http://en.opensuse.org/YaST/Events/Workshop_Nuremberg_2008
As it is supposed to be a team work, I'd like to encourage you to have a
look at the ideas, enlist yourself at those you would like to work on and
use the time until the workshop to look around the topics and learn new
things, possibly using your ITO. The list of ideas is not closed so
anybody can expand the list with further ideas.
Also, if you would like to work with a collegue from a different team or
department on the project, feel free to invite him to take a part (and let
us know in order to prepare the logistics).
I strongly believe this would be fun and useful as well and I'm looking
forward to it.
Thanks
Michal
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi!
I have looked through the projects, which have at least one participants, here
is the summary:
Make Building YaST Documentation Easier (Better)
Lukas Ocilka
Make YaST Independent of YCP
Jozef Uhliarik
Make YaST more IPv6 compatible
Michal Zugec
Using CIM from YaST Modules
Jan Kupec
YaST Interface for Webpin
Katarina Machalkova
Willing Mentors: Lukas Ocilka, Martin Vidner
YaST on other Distributions
Michal Zugec
Martin Vidner
YaST PolicyKit configuration module
Jiri Suchomel
YaST PolicyKit integration
Josef Reidinger
Ladislav Slezak
Jiri Suchomel
YaST Style Guide
Lukas Ocilka
YaST web user interface
Jiri Srain
Stefan Schubert
Michal Zugec
Jozef Uhliarik
CVS for config files
Stefan Hundhammer
signals and slots for zypp
Stefan Schubert
Michael Andres
YaST Libzypp Module
Stefan Schubert
Stefan Hundhammer
Michael Andres
mod-ui module
J. Daniel Schmidt
Stefan Hundhammer
Thomas Goettlicher
Gabriele Mohr
(K)Desktop Integration for plug'n'play hardware
Thomas Goettlicher
Stefan Haas
Installation in IPv6 Environment
Steffen Winterfeldt
Hubert Mantel
If you have selected more projects, please, pick up one which you want to work
on (and consider the interest shown by others). It will be possible to move
to another project during the workshop (provided the team agrees), the
selection is about choosing project you start with.
One of the rules is that there must be at least two participants of each
project. If you are alone, please, try to convince someone join you, or move
to another project.
Thanks in advance!
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
