August 2009 - YaST Development - openSUSE Mailing Lists

Re: [yast-devel] WebYaST Architecture Naming Conventions
by Martin Schmidkunz 18 Aug '09

18 Aug '09

> http://en.opensuse.org/YaST/Web/Architecture/Naming Cool! I took the liberty of adding two UI-related terms there as well: Home: Page with status information, quick links to modules and all modules. All Modules: Page which gives access to all available modules (equals control center in YaST) The idea was to gather terms at one site so we might one day get a nice glossary :-) If you don`t think it`s appropriate: well, it`s a wiki :-) Cu, Martin Martin Schmidkunz User Experience Team martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 Novell® Making IT Work As One™ ------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -------------------------------------

1 0

[yast-devel] WebYaST Architecture Naming Conventions
by Klaus Kaempf 18 Aug '09

18 Aug '09

Hi, the recent mail threads showed some confusion about the different parts of the WebYaST architecture and how to name things. I have now started a 'WebYaST architecture naming' page at http://en.opensuse.org/YaST/Web/Architecture/Naming and tried to define an initial set of terms. I encourage all of you to add and adapt this page as you see fit. Just don't change anything in silence but spread the word on the mailing list. Thanks ! Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- 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] WebYaST: Network CIM Model
by Martin Vidner 17 Aug '09

17 Aug '09

CIM naming ---------- As you can see, the nice names "configs", "devices", "routes", etc. are gone. Welcome to CIM! WORK-IN-PROGRESS: the REST aspect is not covered now, because the way CIM composes the data using subclassed associations makes it hard to figure out, and below are only guesses. A Confusingly Irritating Model :-) note to XML: - I use the usual ruby attributes like type=array/boolean. - Additionally I use <Foo value='80'>HTTP</> to combine CIM enumerations (Value+ValueMap) - CIM is CamelCase. We may want to adapt_it_to_ruby CIM_NetworkPort means "network interface", not a "(TCP/IP )protocol port" (hierarchy: EthernetPort: NetworkPort: LogicalPort: LogicalDevice: EnabledLogicalElement: LogicalElement: ManagedSystemElement: ManagedElement) /NetworkPort/eth0 <EthernetPort>  <DeviceID>eth0</>   <NetworkAddresses> <item>112233445566</> <item>aabbccffeeff</> </> <LinkTechnology value='2'>Ethernet</>  <Capabilities type='array'> <item value='3'>WakeOnLan</> </> <EnabledCapabilities type='array' />  </> LogicalDevice has a m:n Realizes association with Core:PhysicalElement, not sure how to model it in REST <PhysicalElement> <Manufacturer>Realtek Semiconductor Co., Ltd.</> <Model>RTL-8169 Gigabit Ethernet</> ... </> IPProtocolEndpoint: Core:ProtocolEndpoint: <IPProtocolEndpoint> <IPv4Address>1.2.3.4</> <SubnetMask>255.255.255.0</> <AddressOrigin value="4">DHCP</>  </> <IPProtocolEndpoint> <IPv6Address>1:2:3::4</> <PrefixLength>64</> <AddressOrigin value="8">IPv6AutoConfig</> </> interface configuration ----------------------- (IPAssignmentSettingData : SettingData: ManagedElement) /IPAssignmentSettingData/eth0 <IPAssignmentSettingData> <AddressOrigin value='4'>DHCP</> </> /IPAssignmentSettingData/eth0 <StaticIPAssignmentSettingData> <AddressOrigin value='3'>Static</> <IPv4Address>10.20.30.40</> <SubnetMask>255.255.0.0</> <GatewayIPv4Address>10.20.7.254</>  </> (WiFi is too new (Jun 2009): http://www.dmtf.org/standards/published_documents/DSP1088_1.0.0.pdf ) the Association ElementSettingData connects ManagedElement and SettingData (compare NetworkManager's ActiveConnection) <ElementSettingData> <ManagedElement>/IPProtocolEndpoint/1</> <SettingData>/IPAssignmentSettingData/eth0</> <IsDefault value="1">Is Default</>  <IsCurrent value="1">Is Current</> </> TODO! how is all this bound to /NetworkPort/eth0? SAPSAPDependency? ActiveConnection? resolver (DNS client) configuration ----------------------------------- (NETCONFIG_DNS_STATIC_SERVERS) /DNSSettingData <DNSSettingData> <AddressOrigin value='3'>Static</> <DNSServerAddresses type='array'>  <item>10.20.0.2</> <item>10.20.0.8</> </> </> (NETCONFIG_DNS_STATIC_SEARCHLIST) /DNSGeneralSettingData <DNSGeneralSettingData> <AddressOrigin value='3'>Static</> <AppendParentSuffixes type="boolean">true</> <DNSSuffixesToAppend type="array"> <item>suse.cz</> <item>suse.de</> </> </> (BTW it seems that netconfig does not enable dissassociating AddressOrigin for these two) /DNSSettingData <DNSSettingData> <AddressOrigin value='4'>DHCP</> </> /DNSGeneralSettingData <DNSGeneralSettingData> <AddressOrigin value='4'>DHCP</> </> (TODO: Virtual Devices, in case you haven't had enough) -- 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

3 4

[yast-devel] Re: [yast-commit] <web-client> master : app/controllers/system_controller.rb - i18n support
by Josef Reidinger 17 Aug '09

17 Aug '09

On 08/17/2009 03:20 PM, Ladislav Slezak wrote: > ref: refs/heads/master > commit 802dfd6ed000459905a9c222f0fd34e8affc08b3 > Author: Ladislav Slezak <lslezak(a)novell.com> > Date: Mon Aug 17 15:08:09 2009 +0200 > > app/controllers/system_controller.rb - i18n support > --- > .../system/app/controllers/system_controller.rb | 14 ++++++++------ > 1 files changed, 8 insertions(+), 6 deletions(-) > > diff --git a/plugins/system/app/controllers/system_controller.rb b/plugins/system/app/controllers/system_controller.rb > index dc4a01f..8336d58 100644 > --- a/plugins/system/app/controllers/system_controller.rb > +++ b/plugins/system/app/controllers/system_controller.rb > @@ -2,6 +2,8 @@ > class SystemController < ApplicationController > before_filter :login_required > > + include GetText > + Hi, gettext is already included in Action Controller so you don't need include it. Only what should be usefull is initialize to own separated translation file via init_gettext _nameofmodule_ in class. (it is helper and couldn't go to initialize, see e.g. language or timezone module) -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- 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] Re: [yast-commit] <rest-service> master : custom-services rest plugin (originaly services plugin for fate 306696)
by Josef Reidinger 17 Aug '09

17 Aug '09

Hi, few comments On 08/17/2009 10:01 AM, Jiri Suchomel wrote: > ref: refs/heads/master > commit 51c4d88d32d55c56e38a96fd782310e8890e41ea > Author: Jiri Suchomel <jsuchome(a)suse.cz> > Date: Mon Aug 17 10:01:21 2009 +0200 > > custom-services rest plugin (originaly services plugin for fate 306696) > --- > plugins/custom_services/.gitignore | 3 + > plugins/custom_services/MIT-LICENSE | 20 +++++ > plugins/custom_services/README | 7 ++ > plugins/custom_services/Rakefile | 10 +++ > .../app/controllers/custom_services_controller.rb | 54 +++++++++++++ > .../custom_services/app/models/custom_service.rb | 70 ++++++++++++++++ > .../app/views/custom_services/index.html.erb | 1 + > .../app/views/custom_services/index.json.erb | 1 + > .../app/views/custom_services/index.xml.erb | 1 + > .../app/views/custom_services/show.html.erb | 1 + > .../app/views/custom_services/show.json.erb | 1 + > .../app/views/custom_services/show.xml.erb | 1 + > plugins/custom_services/config/rails_parent.rb | 15 ++++ > .../config/resources/custom_services.yml | 2 + > plugins/custom_services/init.rb | 1 + > plugins/custom_services/install.rb | 1 + > .../org.opensuse.yast.modules.yapi.services.policy | 39 +++++++++ > .../package/yast2-webservice-services.changes | 16 ++++ > .../package/yast2-webservice-services.spec | 83 ++++++++++++++++++++ > .../tasks/custom_services_tasks.rake | 6 ++ > .../functional/custom_services_controller_test.rb | 51 ++++++++++++ > plugins/custom_services/test/test_helper.rb | 52 ++++++++++++ > plugins/custom_services/uninstall.rb | 1 + > 23 files changed, 437 insertions(+), 0 deletions(-) > > <snip /> > diff --git a/plugins/custom_services/app/models/custom_service.rb b/plugins/custom_services/app/models/custom_service.rb > new file mode 100644 > index 0000000..26ce7ef > --- /dev/null > +++ b/plugins/custom_services/app/models/custom_service.rb > @@ -0,0 +1,70 @@ > +require 'yast_service' > + > +class CustomService > + > + attr_accessor :name > + attr_accessor :status > + > + def initialize > + end > + > + # services = CustomService.find_all > + def self.find_all This is not much convention for model. I think we should for better readiness use same method as do ActiveRecord...so instead find_all use find(:all) (use all as parameter) > + > + services = [] > + yapi_ret = YastService.Call("YaPI::SERVICES::Read") > + > +Rails.logger.debug "reading YAPI ----------------------------" > + > + if yapi_ret.nil? > + raise "Can't get services list" > + else > + yapi_ret.each do |s| > + service = CustomService.new > + service.name = s["name"] > + service.status = s["status"] > + Rails.logger.debug "service: #{service.inspect}" > + services << service > + end > + end > + services > + end > + > + # load the status of the service > + def self.find(id) > + yapi_ret = YastService.Call("YaPI::SERVICES::Get", id) > + > + raise "Got no data while loading service" if yapi_ret.empty? > + > + service = CustomService.new > + service.name = yapi_ret["name"] > + service.status = yapi_ret["status"] > + > + Rails.logger.debug service.inspect > + service > + end > + > + > + def save(cmd) > + ret = YastService.Call("YaPI::SERVICES::Execute", self.name, cmd) > + > + Rails.logger.debug "Command returns: #{ret.inspect}" > + ret > + end > + > + def to_xml( options = {} ) > + xml = options[:builder] ||= Builder::XmlMarkup.new(options) > + xml.instruct! unless options[:skip_instruct] > + > + xml.service do > + xml.tag!(:name, name ) > + xml.tag!(:status, status, {:type => "integer"} ) > + end > + end > + > + def to_json( options = {} ) > + hash = Hash.from_xml(to_xml()) > + return hash.to_json > + end > + > +end > new file mode 100644 > index 0000000..0f5d8ab > --- /dev/null > +++ b/plugins/custom_services/package/org.opensuse.yast.modules.yapi.services.policy > @@ -0,0 +1,39 @@ > +<?xml version="1.0" encoding="UTF-8"?> > +<!DOCTYPE policyconfig PUBLIC "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN" > + "http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd"> > + > +<policyconfig> > + <vendor>Novell, Inc.</vendor> > + <vendor_url>http://www.novell.com</vendor_url> > + > + <action id="org.opensuse.yast.modules.yapi.services.read"> > + <description>Get list of services.</description> > + <message>System policy prevents the Yast DBus service from reading service list.</message> > + <defaults> > + <allow_any>no</allow_any> > + <allow_inactive>no</allow_inactive> > + <allow_active>auth_admin_keep_session</allow_active> > + </defaults> > + </action> > + > + <action id="org.opensuse.yast.modules.yapi.services.get"> > + <description>Get the information about given service.</description> > + <message>System policy prevents the Yast DBus service from reading service info.</message> > + <defaults> > + <allow_any>no</allow_any> > + <allow_inactive>no</allow_inactive> > + <allow_active>auth_admin_keep_session</allow_active> > + </defaults> > + </action> > + > + <action id="org.opensuse.yast.modules.yapi.services.execute"> > + <description>Starting/stopping services.</description> > + <message>System policy prevents the Yast DBus service from executing service script.</message> > + <defaults> > + <allow_any>no</allow_any> > + <allow_inactive>no</allow_inactive> > + <allow_active>auth_admin_keep_session</allow_active> > + </defaults> > + </action> > +</policyconfig> > + We should unify location of policy files. I as yapi is reachable via dbus and uses policy kit I add it to directly to yast module. Maybe someone (Klaus?) should say where is correct location for this file. -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] Re: [yast-commit] <rest-service> master : custom-services rest plugin (originaly services plugin for fate 306696)
by Jiří Suchomel 17 Aug '09

17 Aug '09

On Monday 17 of August 2009 10:01:21 Jiri Suchomel wrote: > ref: refs/heads/master > commit 51c4d88d32d55c56e38a96fd782310e8890e41ea > Author: Jiri Suchomel <jsuchome(a)suse.cz> > Date: Mon Aug 17 10:01:21 2009 +0200 > > custom-services rest plugin (originaly services plugin for fate 306696) > --- > plugins/custom_services/.gitignore | 3 + > plugins/custom_services/MIT-LICENSE | 20 +++++ > plugins/custom_services/README | 7 ++ > plugins/custom_services/Rakefile | 10 +++ > .../app/controllers/custom_services_controller.rb | 54 +++++++++++++ > .../custom_services/app/models/custom_service.rb | 70 ++++++++++++++++ > .../app/views/custom_services/index.html.erb | 1 + > .../app/views/custom_services/index.json.erb | 1 + > .../app/views/custom_services/index.xml.erb | 1 + > .../app/views/custom_services/show.html.erb | 1 + > .../app/views/custom_services/show.json.erb | 1 + > .../app/views/custom_services/show.xml.erb | 1 + > plugins/custom_services/config/rails_parent.rb | 15 ++++ > .../config/resources/custom_services.yml | 2 + > plugins/custom_services/init.rb | 1 + > plugins/custom_services/install.rb | 1 + > .../org.opensuse.yast.modules.yapi.services.policy | 39 +++++++++ > .../package/yast2-webservice-services.changes | 16 ++++ > .../package/yast2-webservice-services.spec | 83 > ++++++++++++++++++++ .../tasks/custom_services_tasks.rake | > 6 ++ > .../functional/custom_services_controller_test.rb | 51 ++++++++++++ > plugins/custom_services/test/test_helper.rb | 52 ++++++++++++ > plugins/custom_services/uninstall.rb | 1 + > 23 files changed, 437 insertions(+), 0 deletions(-) > ... Hi! I just added new plugin, created from old one by copying and sed-ing... Could you help me to see why tests fail with test_access_index(CustomServicesControllerTest): ActionController::RoutingError: No route matches {:controller=>"custom_services", :action=>"index"} Is it some naming convention problem? Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, 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

3 2

[yast-devel] webYaST: network CIM model summary
by Michal Zugec 17 Aug '09

17 Aug '09

UI mockup --------- http://mschmidkunz.110mb.com/network.html Requirements ------------ There were some requirements: - only "eth" devices (no wireless, no bridges, no vlans) - configure one or none device - no global settings (networkmanager, disable ipv6, dhcp options) - ifup only - device can be configured via DHCP or with address(IPv4 or IPv6) - no "no address" option, no additional addresses, no ifplugd, STARTMODE=onboot by default - nameserver - use "old YaST" options - route - setup only default route (no additional routes, no metrics) The meaning of this module is to set machine to be "connected", accessible via ssh - that's all. For all other, special, "expert" setup is here old YaST CIM model --------- Network is defined in CIM model widely: http://www.wbemsolutions.com/tutorials/CIM/cim-model-net.html But what we need is only about 10-20% of that. It's because there are parameters needed for several network devices, routers, wireless AP, switches, network infrastructure definition, ... We have package "cim-schema" in distribution with some interesting .mof files. Some of them are deprecated! /usr/share/mof/cimv2.19.1/Device/CIM_EthernetPort.mof ethernet device - only interesting is MAC address /usr/share/mof/cimv2.19.1/Device/CIM_NetworkPort.mof almost the same with higher abstraction /usr/share/mof/cimv2.19.1/Network/CIM_IPConfigurationService.mof in the future may be deprecated (but without information what we should use instead of it) network configuration, IP address settings /usr/share/mof/cimv2.19.1/Network/CIM_IPAssignmentSettingData.mof this is equal to our BOOTPROTO parameter /usr/share/mof/cimv2.19.1/Network/CIM_IPProtocolEndpoint.mof don't know difference between this and CIM_IPConfigurationService (but this is more similar to our configurations) /usr/share/mof/cimv2.19.1/Network/CIM_NetworkVLAN.mof VLAN settings (but there are no .mof files for other network types - bridge, bonding, ...) There are also some mof files for DNS (resolv.conf) settings /usr/share/mof/cimv2.19.1/Network/CIM_DNSGeneralSettingData.mof /usr/share/mof/cimv2.19.1/Network/CIM_DNSProtocolEndpoint.mof /usr/share/mof/cimv2.19.1/Network/CIM_DNSSettingData.mof As Klaus suggested, we'll use option names (in rest-api) based on names from CIM model. 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

3 2

[yast-devel] WebYaST daily status, minutes taker schedule
by Klaus Kaempf 17 Aug '09

17 Aug '09

Hi, the WebYaST project page (http://en.opensuse.org/YaST/Web/Project) now contains the schedule for taking the meeting minutes. Klaus -- 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] WebYaST daily status, 14-Aug-2009
by Bjoern Geuken 17 Aug '09

17 Aug '09

kkaempf: - wiki cleanup - task list has some new entrys, look onto it - discuss break build: work in branch first, merge, use test suit and then merge back dmacvicar: - need requirements for custom services - fixed broken build on friday next: - get things to green again - will make Hudson send to Yast commit Schubi: - looked at sinatra and selenium - had some problems with details in sinatra next: - try to solve them today or otherwise will chancel sinatry mschmidkunz: - worked on workflow and ui presentation, license next: - basic system bgeuken: - worked on status module next: - work on status module Martin V.: next: - try to complete model jreidinger: - added rest module basic system setup jsrain: (no update) mzugec: - working with martin - added api devices - asked ideas in mail jsuchome: - broke build - use of Yapi is still unclear lslezak: - worked on webclient - fixed plugin loading -- 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] Re: [yast-commit] <web-client> master : custom-services client
by Josef Reidinger 17 Aug '09

17 Aug '09

On 08/17/2009 10:02 AM, Jiri Suchomel wrote: > ref: refs/heads/master > commit 89703cf8f4b2848c1bfbdb71de8df8414d0f5a96 > Author: Jiri Suchomel <jsuchome(a)suse.cz> > Date: Mon Aug 17 10:02:18 2009 +0200 > > custom-services client > --- > plugins/custom_services/README | 7 ++ > plugins/custom_services/Rakefile | 10 +++ > .../app/controllers/custom_services_controller.rb | 67 ++++++++++++++++++ > .../app/views/custom_services/_result.rhtml | 20 ++++++ > .../app/views/custom_services/index.rhtml | 70 +++++++++++++++++++ > plugins/custom_services/config/rails_parent.rb | 15 ++++ > plugins/custom_services/init.rb | 12 +++ > plugins/custom_services/install.rb | 1 + > .../yast2-webclient-custom-services.changes | 4 + > .../package/yast2-webclient-custom-services.spec | 73 ++++++++++++++++++++ > plugins/custom_services/shortcuts.yml | 8 ++ > .../tasks/custom_services_tasks.rake | 6 ++ > .../custom_services/test/custom_services_test.rb | 8 ++ > .../functional/custom_services_controller_test.rb | 45 ++++++++++++ > plugins/custom_services/test/test_helper.rb | 19 +++++ > plugins/custom_services/uninstall.rb | 1 + > 16 files changed, 366 insertions(+), 0 deletions(-) > > diff --git a/plugins/custom_services/README b/plugins/custom_services/README > new file mode 100644 > index 0000000..afbf229 > --- /dev/null > +++ b/plugins/custom_services/README > @@ -0,0 +1,7 @@ > +Services > +========= > + > +Plugin for hanling custom vendor service. > + > + > +Copyright (c) 2009 Novell, released under the MIT license > diff --git a/plugins/custom_services/Rakefile b/plugins/custom_services/Rakefile > new file mode 100644 > index 0000000..ca63e76 > --- /dev/null > +++ b/plugins/custom_services/Rakefile > @@ -0,0 +1,10 @@ > +require 'rake' > +require 'rake/testtask' > +require 'rake/rdoctask' > +require File.join(File.dirname(__FILE__), 'config', 'rails_parent') > +require File.join(RailsParent.parent, 'config', 'boot') > +require 'tasks/rails' > + > +desc 'Default: run unit tests.' > +task :default => :test > + > diff --git a/plugins/custom_services/app/controllers/custom_services_controller.rb b/plugins/custom_services/app/controllers/custom_services_controller.rb > new file mode 100644 > index 0000000..518bccd > --- /dev/null > +++ b/plugins/custom_services/app/controllers/custom_services_controller.rb > @@ -0,0 +1,67 @@ > +require 'yast/service_resource' > + > +class CustomServicesController < ApplicationController > + before_filter :login_required > + layout 'main' > + > + private > + def client_permissions > + @client = YaST::ServiceResource.proxy_for('org.opensuse.yast.modules.yapi.services') > + unless @client > + flash[:notice] = _("Invalid session, please login again.") > + redirect_to( logout_path ) and return > + end > + @permissions = @client.permissions > + end I recommend using proxy_loader library. That handle properly all stuff with loading proxy and also ensure same behavior for all plugins. It is well documented with examplanation example. > + > + # Initialize GetText and Content-Type. > + init_gettext "yast_webclient_custom_service" # textdomain, options(:charset, :content_type) > + > + public > + > + def initialize > + end > + > + # GET /services > + # GET /services.xml > + def index > + return unless client_permissions > + @services = [] > +logger.debug "-------------------------------- index" > + > + begin > + @services = @client.find(:all) > + rescue ActiveResource::ClientError => e > + flash[:error] = YaST::ServiceResource.error(e) > + end > +logger.debug @services.inspect > + > + respond_to do |format| > + format.html # index.html.erb > + format.xml { render :xml => @services } > + end > + end > + > + def execute > + return unless client_permissions > + @service = @client.find(params[:service_id]) > + > + response = @client.put(params[:service_id], :execute => params[:id]) > + > + # we get a hash with exit, stderr, stdout > + ret = Hash.from_xml(response.body) > + ret = ret["hash"] > + logger.debug "returns #{ret.inspect}" > + > + @result_string = "" > + @result_string << ret["stdout"] if ret["stdout"] > + @result_string << ret["stderr"] if ret["stderr"] > + @error_string = ret["exit"].to_s > + if ret["exit"] == 0 > + @error_string = _("success") > + end > + render(:partial =>'result') > + end > + > + > +end > diff --git a/plugins/custom_services/app/views/custom_services/_result.rhtml b/plugins/custom_services/app/views/custom_services/_result.rhtml > new file mode 100644 > index 0000000..3af3d5f > --- /dev/null > +++ b/plugins/custom_services/app/views/custom_services/_result.rhtml > @@ -0,0 +1,20 @@ > + <div class="box"> > + <div class="table"> > + <img src="images/bg-th-left.gif" width="8" height="7" alt="" class="left" /> > + <img src="images/bg-th-right.gif" width="7" height="7" alt="" class="right" /> > + <table class="listing form" cellpadding="0" cellspacing="0"> > + <tr> > + <th class="full" colspan="2"><%=_("Service Call Result")%></th> > + </tr> > + <tr> > + <td class="first" width="120"><strong><%=_("Result")%></strong></td> > + <td class="last"><%=h @error_string %></td> > + </tr> > + <tr class="bg"> > + <td class="first"><strong><%=_("Description")%></strong></td> > + <td class="last"><%=h @result_string %></td> > + </tr> > + </table> > + <p><a href="services" class="button"><%=_("Back")%></a></p> > + </div> > + </div> > \ No newline at end of file > diff --git a/plugins/custom_services/app/views/custom_services/index.rhtml b/plugins/custom_services/app/views/custom_services/index.rhtml > new file mode 100644 > index 0000000..7498013 > --- /dev/null > +++ b/plugins/custom_services/app/views/custom_services/index.rhtml > @@ -0,0 +1,70 @@ > +<%= javascript_include_tag :defaults %> I think you don't want this, this is helper for AJAX stuff (loads all necessary libs for working AJAX helpers) . Your library I think is included already from template. > + > +<script language="javascript"> > + > + YAHOO.namespace('yuiresult'); > + > + function initResultDialog() { > + var handleCancel = function() { > + this.cancel(); > + } > + > + YAHOO.yuiresult.resultDialog = new YAHOO.widget.Dialog("resultdlg", { > + width: "625px", > + modal: true, > + visible: false, > + fixedcenter: true, > + constraintoviewport: true, > + draggable: true }); > + > + YAHOO.yuiresult.resultDialog.render(); > + } > + > + function showResultDialog() { > + YAHOO.yuiresult.resultDialog.show(); > + } > + > + YAHOO.util.Event.addListener(window, "load", initResultDialog); > +</script> > + We have YAHOO js lib? I think we remove it. At least it should be good if we document what libraries is used in webyast and what should other module use. > + > +<div id="resultdlg"> > +</div> > + > + > +<div class='plugin-icon'><img src='/icons/yast-online_update.png'/></div> > +<div class='plugin-content'> > + > +<h2><%=_("The full name of vendor service here")%></h2> > +<br> > + > +<% if ! @permissions[:execute] %> unless is common in ruby > +<p><%=_("You do not have permission to execute the service. The links are disabled.")%></p> > +<% end %> > + > +<ul> > +<% @services.each do |service| %> > +<li><b><%=h service.name %></b> > + <% [ "start", "stop" ].each do |cmd| > + if @permissions[:execute] %> > + <%= > + link_to_remote cmd, > + :update => "resultdlg", > + :url=>{ :id=> cmd, > + :action => "execute", > + :service_id=> service.name > + } > +# :loading => "Element.show('progress')" > +# :complete => "Element.hide('progress'); showResultDialog();" > + %> > + <% > + else %> > + <span style="color: #BDBDBD"><%="#{cmd}" -%></span> I think we should not use hardcoded style, I think better is send mail to robert and choose some class for this case. > + <% > + end > + end %> > +</li> > +<% end %> > +</ul> > + > +</div> -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

Re: [yast-devel] license presentation
by Martin Schmidkunz 17 Aug '09

17 Aug '09

* Martin Schmidkunz <Martin.Schmidkunz(a)gmx.de> [Aug 13. 2009 15:47]: >> http://en.opensuse.org/YaST/Web/Docu/Navigation#Display_License_after_First… > The license agreement should be before the 'home' page. Before > agreeing to the license, the user must not get to any other page. Yes, I forgot to mention that. The idea was to show how a license could be presented to the user when he runs a module/application for the first time and the application/module would need a special license which has to be accepted. Cu, Martin Martin Schmidkunz User Experience Team martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 Novell® Making IT Work As One™ ------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -------------------------------------

1 0

[yast-devel] Re: [yast-commit] <rest-service> master : add base system plugin
by Duncan Mac-Vicar P. 14 Aug '09

14 Aug '09

On Friday 14 August 2009 15:00:21 Josef Reidinger wrote: > ref: refs/heads/master > commit 98d602c0c74678ffb790482ccd8b493c99ab3740 > Author: Josef Reidinger <jreidinger(a)suse.cz> > Date: Fri Aug 14 15:00:06 2009 +0200 > > add base system plugin plugins/basesystem> rake (in /space/git/suse/yast/rest-service/plugins/basesystem) /usr/bin/ruby -I"lib:test" "/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" /usr/bin/ruby -I"lib:test" "/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" /usr/bin/ruby -I"lib:test" "/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" /usr/bin/ruby -I"lib:lib:test" "/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" "test/performance/browsing_test.rb" ./test/test_helper.rb:2:in `require': no such file to load -- /space/git/suse/yast/rest-service/plugins/basesystem/config/environment (LoadError) from ./test/test_helper.rb:2 from ./test/performance/browsing_test.rb:1:in `require' from ./test/performance/browsing_test.rb:1 from /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5:in `load' from /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5 from /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5:in `each' from /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5 rake aborted! Command failed with status (1): [/usr/bin/ruby -I"lib:lib:test" "/usr/lib64...] -- 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] status modul - xml
by Bjoern Geuken 14 Aug '09

14 Aug '09

Hi, I'm trying to gave the status rest-service a nicer xml format, but I faced some problems by sending the times of the values. Inside a browser the xml- tree looks like that: <status> <metricgroup group_name="memory"> <metric name="memory-used"> <label type="value"> <value dateTime="1250178710">1.4260408320e+09</value> <value dateTime="1250178600">1.4165012480e+09</value> <value dateTime="1250178590">1.4164602880e+09</value> .... But when the webclient fetches the data with @client.find(...), it misses the dateTime attributes: #<YaST::ServiceResource::Proxies::Status:0x7f5c68fd0c98 @prefix_options={}, @attributes={"metricgroup"=>[#<YaST::ServiceResource::Proxies::Status::Metricgroup:0x7f5c68f22288 @prefix_options={}, @attributes={"group_name"=>"memory", "metric"=>[#<YaST::ServiceResource::Proxies::Status::Metricgroup::Metric:0x7f5c68f1fb28 @prefix_options={}, @attributes={"label"=>#<YaST::ServiceResource::Proxies::Status::Metricgroup::Metric::Label:0x7f5c68f1f038 @prefix_options={}, @attributes={"values"=> ["1.4095081472e+09", "1.4097989632e+09", ..... "1.4097973248e+09"], "type"=>"value"}>, "name"=>"memory-used"}>, ... It seems that the last branch of an xml-tree (or elements with content?) can't have any attributes. Is this the expected behaviour or maybe a bug? Björn -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 4

[yast-devel] Re: [yast-commit] <rest-service> master : system - do reboot/shutdown only in 'production' mode
by Klaus Kaempf 14 Aug '09

14 Aug '09

Some remarks inline * Ladislav Slezak <lslezak(a)novell.com> [Aug 13. 2009 19:04]: > --- a/plugins/system/app/models/system.rb > +++ b/plugins/system/app/models/system.rb > @@ -46,11 +46,21 @@ class System > case action > > when :reboot > - Rails.logger.debug 'Rebooting the computer...' > - return computer.Reboot == 0 > + if ENV['RAILS_ENV'] == 'production' > + Rails.logger.debug 'Rebooting the computer...' > + return computer.Reboot == 0 'Reboot' seems to be a function. However according to Ruby naming conventions 'Reboot' is a class (first letter upper case). > + else > + Rails.logger.debug "Skipping reboot in #{ENV['RAILS_ENV']} mode" > + return true > + end The result of the "when :reboot" case is of boolean type. Let the 'reboot' function also return a boolean and drop the comparison with 0 > when :shutdown > - Rails.logger.debug 'Shutting down the computer...' > - return computer.Shutdown == 0 > + if ENV['RAILS_ENV'] == 'production' > + Rails.logger.debug 'Shutting down the computer...' > + return computer.Shutdown == 0 > + else > + Rails.logger.debug "Skipping shutdown in #{ENV['RAILS_ENV']} mode" > + return true > + end The duplication of the production check is not DRY (don't repeat yourself). Also think about moving the check into the 'reboot' resp. 'shutdown' functions, because this is "where the action is". Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- 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] WebYaST daily status, 14-Aug-2009
by Jiri Srain 14 Aug '09

14 Aug '09

WebYaST 14-Aug-2009 =================== Present: kkaempf, dmacvicar, schubi, bgeuken, jsrain, lslezak, mvidner, mzugec, jsuchome, jreidinger Status update ------------- - kkaempf: still working on features and tasks discussions on yast-devel TODO: announce and publish the task list - schubi: added testcased of permissions web-client + code clean-up looking on sinatra, will spend today with it (sinatra is an interface for REST services emulation) - bgeuken: worked on status module TODO: work on the web client - dmacvicar: got testsuite in hudson to blue TODO: clean-up, HTML validation TODO: building in BuildService to have an image - jsuchome: committed some work on services plug-in (and YaPI parts) considering approaches how to go on (discussion on yast-devel) not sure what to be done by Monday, need clarification first - mzugec: proposed REST API for network (discussion on yast-devel) TODO: finalize the discussion, start implementation - mvidner: nothing to be added to what Michal said - jreidinger base sysetm module proposal passed to mailing list TODO: write the rest-service back-end still some technical issues to be resolved - lslezak: improved REST service for reboot/shutdown, added testcases added some safety checks (do not reboot in development/testing mode :-) ) TODO: webclient for reboot/shutdown -- 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 -- 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] WebYaST: Network REST Model v1
by Martin Vidner 14 Aug '09

14 Aug '09

If you wonder why another model for the same, I have started this in parallel to Miso looking at CIM, and intentionally it does not include any CIM yet. Next we will look how it can be made more CIM-like and whether the anticipated resulting complication is too much :) * /network http://mschmidkunz.110mb.com/network.html Everything goes under /network But the network services, including a DHCP *server*, will be outside Basic Config ------------ * /network/devices/ (RO) Devices and interfaces are the same for now. Devices are read only (for physial devices, but see below for virtual). The read-write part are the configs. * /network/devices/1 (RO) interface=eth0 product=MSI 1341 * /network/configs/ (RO) Configs are separated from devices like ifcfg-* (shown here like key-value pairs but xml in fact) * /network/configs/1 (RW) startmode=dhcp4 * /network/configs/2 bootproto=static ipaddr=1.2.3.4/24 * /network/configs/3 startmode=dhcp4 wireless_essid=HomeWiFi wireless_key=HomeSweetHome * /network/configs/4 startmode=dhcp4 wireless_essid=WorkWiFi wireless_wpa_psk=HomeSweetHome In the above form, configs are not associated with devices and it works like in NetworkManager, a call like /network/devices/1/configure?config=/network/configs/42 is needed. But a config can get another attribute, "device" that makes it the default config for a device, and it works like our ifcfg (where "device" is in the filename) For simplicity, the UI can hide the device-config separation and always edit the single config for a device. * /network/devices/1/current-config (RO) (current_config? TODO style) ipaddr=1.2.3.4/24 This distinguishes the config, which can specify the IP or say DHCP from the current-config, which always specifies the IP (or does not exist). Think /etc versus "ip" output. * /network/routes/ * /network/routes/default (RW) <route> <via>1.2.3.4</> ("ip r" keyword) <route> * /network/resolver (RW) <nameservers> <nameserver>1.2.3.4</> <nameserver>1.2.3.42</> </> <searches> <search>example.com</> <search>example.net</> </> (use-dhcp ?) * /network/resolver/current-config (RO) Like with the devices, this shows the config even if /network/resolver says DHCP * /network/hostname (RW) hostname=trikolka domain=suse.cz fqdn=trikolka.suse.cz (dhcp??) Virtual Devices --------------- (This is for the future, included here just to show that the API accomodates them) For virtual devices (special interfaces not based on hardware devices - bridge, bonding, vlan) is sysconfig configuration splitted into device and configuration parts. /network/configs stays the same and /network/devices becomes writable (details to be worked out but the REST paths are unchanged from the basic config) bridge ------ ifcfg-br0 STARTMODE='auto' BOOTPROTO='dhcp' BRIDGE='yes' BRIDGE_PORTS='eth0 eth1' BRIDGE_PORTPRIORITIES='50 20' * /network/devices/1 interface=br0 bridge='yes' bridge_ports='eth0 eth1' bridge_portpriorities='50 20' * /network/configs/1 bootproto='dhcp' VLAN ---- ifcfg-vlan3 STARTMODE=onboot ETHERDEVICE=eth0 IPADDR=192.168.3.27/24 * /network/devices/1 interface=vlan3 etherdevice=eth0 # /network/devices/10 * /network/configs/1 ipaddr=192.168.3.27/24 bonding ------- ifcfg-bond0 STARTMODE='onboot' BOOTPROTO='static' IPADDR='192.168.0.1/24' BONDING_MASTER='yes' BONDING_SLAVE_0='eth0' BONDING_SLAVE_1='eth1' BONDING_MODULE_OPTS='mode=1' # backup mode * /network/devices/1 interface=bond0 bonding_master='yes' bonding_slave_0='eth0' # /network/devices/10 bonding_slave_1='eth1' # /network/devices/11 bonding_module_opts='mode=1' # backup mode * /network/configs/1 ipaddr='192.168.0.1/24' -- 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

4 7

[yast-devel] Exporting users during installation
by Leonardo L. P. da Mata 13 Aug '09

13 Aug '09

Hello, I need to clone the installation information to be used with autoyast. there is a module called AutoinstClone that can export this information, it reads the Profile::current data and exports this information using XML::YCPToXMLFile module. This profile contains an entry for users, but this entry only contains the root user, if i create one user called "leonardo" during the installation it doesn't appear in this profile. Does anyone knows how to export the information about this initial user created during installation? i need to create this autoyast file automatic, i really need to do it during the installation process without user interference. Thank you -- Leonardo Luiz Padovani da Mata barroca(a)gmail.com "May the force be with you, always" "Nerd Pride... eu tenho. Voce tem?" -- 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] vendor specific module
by Martin Schmidkunz 13 Aug '09

13 Aug '09

Hi, please find a first idea of integration of vendor specific modules at: http://en.opensuse.org/YaST/Web/Docu/Navigation#Vendor_Specific_Module The idea would be: Vendor specific modules are represented either with an icon specified by a vendor or by a generic icon (e.g. yast-vendor.png) When clicking on the module the vendor specific configuration starts in fullscreen mode and replaces the webYaST UI completely. If specified by the vendor a separate login screen is shown. Cancelling the login dialog returns the user to webYaST "Home". For changes and navigation within the module the module`s controls are used. After finishing work with the vendor specific module the module is exited by clicking either on logout or any other exit option provided within the vendor specific module. The user then returns to webYaST "Home". Retrieved from "http://en.opensuse.org/YaST/Web/Docu/Navigation" Reasons for this: * running a module inside YaST GUI leads to a confusing look and feel and a lot of unclear functionalities (e.g. how to save settings); see slide 4 on presentation at http://en.opensuse.org/YaST/Web/Docu/Navigation#Try_it_3 * most programms have an exit functionality so why not use it? Looking forward to your comments! Cu, Martin -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 4

[yast-devel] license presentation
by Martin Schmidkunz 13 Aug '09

13 Aug '09

Hi, please find a first idea for license presentation in webYaST (FATE: 306697) at: http://en.opensuse.org/YaST/Web/Docu/Navigation#Display_License_after_First… The idea is: License for running the webYaST (e.g. Novell licenses) need to be accepted during first run workflow. Licenses for specific modules are display when the user first runs the module. The license is displayed within the webYaST UI. The heading contains the module icon and "License Agreement" as title. Then the license is displayed and a set of unchecked radio buttons with the labels: * Yes, I agree to this License Agreement * No, I do not agree If the license is accepted and the user clicks "OK" the module is started. If the license is not accepted and the user clicks "OK" the user returns to the "Home" page Looking forward to your comments! Cu, Martin -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- 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] Views custom javascripts and stylesheets
by Duncan Mac-Vicar Prett 13 Aug '09

13 Aug '09

I am writing this now that the testsuite is again in blue state :-) One of the things that prevented the validation to pass was systemtime use of custom javascript. WebYaST has a main layout, which includes the standard javascript file. The plugins views are embedded inside the body of the layout. So how can a view add its custom javascripts and stylesheets? If you just add javascript or link tags, the html will be invalid, and you will breat the build. link tags are not allowed inside a div. They have to be in the head section of the document. "But the head section is in the layout". Yes. Enter the magic :-) http://asciicasts.com/episodes/8-layouts-and-content-for The trick is that the layout does a yield :head in the head section of the layut. The name is arbitrary, but for head that is the convention. Then the view can do in any part: <% content_for :head do %> <% end %> To add stuff to the head section. This trick can also be used to create an API fr the views to add content to menus, and other areas of the layout by defining new "areas", and we should document this in the documentation relative to writing modules. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] Prague YaST team meeting 2009-08-06
by Jano Kupec 13 Aug '09

13 Aug '09

Prague YaST team meeting 2009-08-06 ----------------------------------- http://en.opensuse.org/YaST/Team present: jkupec, jsrain, juhliarik, jsuchome, lslezak, mkudlvasr, mzugec absent: jreidinger, kmachalkova, locilka, mvidner minutes: jkupec YaST packages ------------- Two new packages extracted from yast2-core: yast2-dbus-client and yast2-dbus-server. This frees yast2-core of the DBus and PolicyKit dependency (lslezak). WebYaST ------- lslezak investigated the use of caching to avoid calling of long lasting operations (like getting the list of available patches via PackageKit) repeatedly. As long as the cache is valid, the UI gets the cached result instead of executing the operation. Cache gets invalidated after certain amount of time, or when a change affecting the result is detected. Zypp(er) -------- * Searching/listing/installation by issues (bugzilla #, CPE advisories) added (fate #305503) * --download-only option added to several zypper commands like 'install' to only download packages for later installation (fate #302159). * Logging of http redirections added to ZYpp's Curl backend (fate #305320). Will help resolve problems with broken mirrors used by downloads.opensuse.org redirector. -- 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] WebYaST daily status, 13-Aug-2009
by Ladislav Slezak 13 Aug '09

13 Aug '09

WebYaST 13-Aug-2009 =================== Present: kkaempf, dmacvicar, schubi, mschidkunz, bgeuken, jsrain, lslezak, mvidner, mzugec, jsuchome Status update ------------- - kkaempf: updated wiki task list TODO: continue - schubi: solved Java problems with selenium TODO: test cases for services - mschidkunz: navigation concept, shutdown/reboot UI proposal TODO: concept for vendor specific modules - bgeuken: fixes in status module TODO: continue - dmacvicar: testsuite updates, building packages in Hudson TODO: keep packages building, vendor specific configuration - jsrain: (no update) - jsuchome: YaPI in the services module for vendor specific services TODO: continue - lslezak: REST API for shutdown/reboot, fixes, tests TODO: implement UI - mzugec: CIM summary for network, REST model TODO: continue - mvidner: REST model for network TODO: continue -- 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] qt-pkg: column-size-behavior: how to get patches into the SVN-repo ?
by Frank Schaefer 13 Aug '09

13 Aug '09

Hi, I'm currently working on some improvements for the column-size-behavior in qt-pkg. I've already written a patch that has been submitted to trunk and fixed bug 441828 and the next patches will increase it's performance enormusly. What's the preferred procedure to get the patches into the SVN-repo ? Is there a review-process ? Frank -- 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] shutdown restart functionality
by Martin Schmidkunz 12 Aug '09

12 Aug '09

Hi, concerning the shutdown/restart functionality of webYaST I`d like to propose to do it in a similar way as it is done on the desktop instead of creating a single module. How this solution might look like can be viewed at: http://en.opensuse.org/Image:Concept_restart_shutdown_logout_1.odp Just click on "Exit" in the upper right corner and then a pop up appears which asks the user how he would like to end the session: * logout: just ends the session and returns to login screen * restart: restarts the system and prompts a login screen * shutdown: shuts down the system Please note that this is just a draft to show you the idea behind it. That means that icons and labels are just quick placeholders :-) I would suggest not to use any additional explanatory text (e.g. Shutdown - Shuts down your system) because the text would show only a limited amout of additional information and might annoy the target user group. The reasons to do something similar as it is done by the desktop would be: * consistency with user expectations and the users concepts of shutting down a graphical environment * to avoid confusion because the shutdown module would be on the same hierarchical level as a single module but affect the whole system and not just a single part of it * modules are used for configuration and shutdown/reboot is unrelated to configuration Looking forward to your comments, 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

3 7

[yast-devel] WebYaST daily status, 12-Aug-2009
by Ladislav Slezak 12 Aug '09

12 Aug '09

WebYaST 12-Aug-2009 =================== kkaempf, dmacvicar, schubi, mschidkunz, jsrain, lslezak, mvidner, mzugec, jsuchome Status update ------------- - kkaempf: TODO page split into subpages - dmacvicar: hudson build, testing flock and fly tools for improving the tests - schubi: status page, found dbus problems - mschidkunz: restart / shutdown functionality - jsrain: (no update) - jsuchome: planning service module - mvidner: designing REST API for network - mzugec: studying CIM network model (reuse similar names in the REST API) - lslezak: shutdown/reboot REST service, writing tests -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0