August 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] TraditionalYaST: searching YaST modules by keywords
by Katarina Machalkova 03 Sep '09

03 Sep '09

YaST hackers, I've just finished implementing ground for feature #305845 [1], that is support for defining additional keywords for YaST module and querying those (in addition to module names) in (Qt4) control centre search. However, to put the feature really into practice, I need your help. It is very simple: all you have to do is to modify .desktop file(s) your YaST module ships by adding a new key-value pair to it. The key name is 'X-SuSE-YaST- Keywords' (to conform to xdg standards [2]) and its value is comma-separated list of words describing the function of the module. Example: [Desktop Entry] Type=Application //those you already have Name=Flinstones GenericName=Modern Stone Age Family //this you will need to add X-SuSE-YaST-Keywords=fred,wilma,barney,betty I'm sure you know best which keywords to put in in order to make it easier for the users to find the module :) Thanks for the cooperation. hB. [1] https://features.opensuse.org/305845 [2] http://standards.freedesktop.org/desktop-entry-spec/desktop-entry- spec-1.0.html -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

2 2

[yast-devel] WebYaST: Vendor service - Summary + TODO
by Ladislav Slezak 03 Sep '09

03 Sep '09

(Resending to yast-devel for a broader discussion....) Dne 21.8.2009 10:08, Jiří Suchomel napsal(a): > On Thursday 20 of August 2009 13:30:12 Ladislav Slezak wrote: >> The REST service >> ================ >> >> - provides a REST API for both LSB and custom services >> - uses YaPI for LSB services >> - custom services are handled directly, config files are read/parsed >> directly, SCR service is used for execution >> - uses new YaST::ConfigFile library >> >> >> Web UI (webclient) >> ================== >> >> - provides a separate view on LSB services and custom services >> - allows custom branding (via modifications in /public directory) > > TODO > > The REST service > ================ > - enhance testsuite > - add function to query service status (Q: use new policy for query, or use > the one for "execute"?) I'd reuse the existing right, no need for extra one IMHO. > Web UI (webclient) > ================== > - testsuite > - design the UI (talk to mschmidkunz), may be different for System vs. Custom > services The question is if vendors would like to change "Custom Services" to a better name (with real service name). With current implementation they need to change the name directly in .yml config file. Is that OK? > - show the service status: > - for system services, probably first show list of services, that update the > status of each one service with AJAX calls Maybe one AJAX call for all services could be better (I'm not sure about the overhead, running 30 requests in parallel instead of big one might be too slow.) Any idea? I'm not an AJAX expert... > - custom service is expected to be only one currently, so the status could > be load on loading index page I'd keep the same functionality, this creates unnecessary complexity. More over reading the current status might take long time so the complete page would be displayed after a (possibly long) delay. > - think how the service execution result should be shown better -- 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 4

[yast-devel] Don't use sudo git...
by Björn Geuken 01 Sep '09

01 Sep '09

Hi, I accidently send a patch with Author: root <root(a)linux-qwou.(none)> by using sudo. I appologize for any confusion and would be happy if anyone could help fixing this. thanks Björn -- 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] WebYaST: package versioning?
by Jiří Suchomel 01 Sep '09

01 Sep '09

Hi, I've just realized that most of traditional yast2 packages present in WebYaST repository have the versions of 2.18.*. But this is versioning based on trunk, should we have there the versions of patches SLE11 packages (2.17.<sles-11-released>++), instead of the trunk ones? That's not only about versioning, but also about the non-webyast related changes in these packages; I assume there should be no new stuff between SLE11 release and now, except the WebYaST related one... 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

2 2

[yast-devel] Re: [yast-commit] <rest-service> network : fixed test
by Klaus Kaempf 01 Sep '09

01 Sep '09

* Michal Zugec <mzugec(a)suse.cz> [Aug 31. 2009 13:13]: > @@ -13,8 +13,10 @@ class RoutesControllerTest < Test::Unit::TestCase > # to extract routes data from all YaPI map > # > def test_show > - Routes.expects(:find).returns({:routes=>{:default=>'10.20.30.40'}}) > - Routes.find > + # if this code raises, test-unit 2.0.3 and mocha 0.9.5 fail > + # with PASSTHROUGH_EXCEPTIONS. version mismatch?! > + Route.expects(:find).returns({:routes=>{:default=>{'via'=>'10.20.30.40'}}}) > + Route.find Can you explain what you're actually trying to test here ? 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

2 1

[yast-devel] shutdown module
by Martin Schmidkunz 31 Aug '09

31 Aug '09

Hi, + The functionality for reboot/shutdown is already in the GIT repository, + the remaining part is UI look (how it shoulod look like and where it + should be available). Thanks, Lado, for implementing that functionality! When writing my first comment, I didn`t realize that it makes sense to distinguish between logout and shutdown as the two actions may happen on two different machines. So therefore it would be fine for me, to leave the shutdown UI functionality implemented as it is. When the user clicks on shutdown/reboot I would ask to display a "are you really sure?" pop up in order to prevent an unintended reboot/ shutdown. Thanks, Martin --- Martin Schmidkunz User Experience Specialist mschmidkunz(a)novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™

2 2

[yast-devel] WebYaST: AJAX callbacks, chaining AJAX calls
by Ladislav Slezak 31 Aug '09

31 Aug '09

Hi, in the services plugin I needed to call an AJAX function (current status) when another AJAX call is finished (start/stop a service). I found that remote_function and link_to_remove provide before and after hooks. Example: Show a progress indicator while remote call is in progress: link_to_remote ..., :loading => "$('#progress').show()", :complete => "$('#progress').hide()" :complete can be also used to chain another AJAX call: link_to_remote ..., :complete => remote_function(:update => ...) See link_to_remote documentation for more details. I hope this helps someone else... -- 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

1 0

[yast-devel] Suggestions for improving the YaST partitioner
by Marco Poletti 31 Aug '09

31 Aug '09

Hi, I propose to modify the expert partitioner, say what you think of these changes: 1) I think the "Overview" and "Used devices" tabs associated with each drive are out of place, I think they should become the property window of the drive, that can be accessed by right-clicking the drive and selecting the new item "Properties", or in the "Hard disk" view by selecting it and clicking the new button "Properties" , or by right-clicking an empty space in the drive's own view and selecting Properties, or by clicking the new button "Drive properties" in the drive's own view. 2) About partitions, I'd completely remove them from the tree on the left and move those informations to the partition's Properties window, accessible from right-clicking the partition and selecting the new item "Properties" or selecting the partition and clicking the new "Properties" button, both in the drive view and in the "Hard disks" view. 3) In computers with not too many HDs, say max 6, I'd show all the graphical bars in the "Hard disk" view. I have also filed these as a wish: https://bugzilla.novell.com/show_bug.cgi?id=534720 Thanks for reading, Marco Poletti -- 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 status 31-Aug-2009
by J. Daniel Schmidt 31 Aug '09

31 Aug '09

WebYaST 31-Aug-2009 =================== present: kkaempf, dmacvicar, schubi, mschmidkunz, bgeuken, jdsn, mzugec, lslezak, mvidner, jsuchomel, fnadge absent: jsrain, visnov Status: ----------- kkaempf: code review of checkins plan new milestones as the progress of the project is too slow we want to have a new appliance for the openSUSE conference all current features should work by then: * shutdown, reboot, basic net setup, basic setup workflow dmacvicar: work on error handling, render exceptions schubi: was on vacation, will coordinate with Duncan mschmidkunz: work on styleguide plan to work on how to display error messages bgeuken: checked in code for XML format of staus module plan to fix limits an interval of status jdsn: plan to start work on registration module mzugec: work on network plugin plan to read system data via YaPI lslezak: work on test suite in services plugin, still not fully covered mvidner: work with mzugec, writing client side tests jsuchomel: was on vacation, will coordinate next task with Ladislav fnadge: plan to collect information about features from everybody this week to integrate it in the documentation Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 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] Awareness of BNC 528789
by Dominique Leuenberger 31 Aug '09

31 Aug '09

Dear hackers and users, I have bnc 528789 [1] opened for some time now and apart from trying to push it to a 'theming' error, apparently nothing happened. As there seem not to be to many reports, I was wondering if I'm just the only one having the problem (or the only one using yast2 gtk package manager). What's the bug about: Once you start PM (gtk version), you have a 'filter' field in the upper right part. This widget does not behave in a way I would expect it. Mainly entering any text does not show it (maybe white on white? but then: SHIFT-HOME would normally mark / invert it). Also, once you click on the lower field to select a package, it seems no longer possible to use the filter at all. Anybody out there that can confirm this mis-behavior and maybe comment on the bug mentioned above? It would be a shame to not have an issue like this addressed. Thanks for listening / testing! Dominique [1] https://bugzilla.novell.com/show_bug.cgi?id=528789 -- 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] Re: [yast-commit] <rest-service> network : added config file for routes
by Klaus Kaempf 31 Aug '09

31 Aug '09

* Michal Zugec <mzugec(a)suse.cz> [Aug 31. 2009 08:59]: > ref: refs/heads/network > commit 0dfc80d23eaec24c737fd30f9e2b09b14d77a487 > Author: Michal Zugec <mzugec(a)suse.cz> > Date: Mon Aug 31 08:58:53 2009 +0200 > > added config file for routes This comment doesn't match the change. > --- > plugins/network/config/resources/routes.yml | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/plugins/network/config/resources/routes.yml b/plugins/network/config/resources/routes.yml > index 09c08d5..3f765a5 100644 > --- a/plugins/network/config/resources/routes.yml > +++ b/plugins/network/config/resources/routes.yml > @@ -1,3 +1,4 @@ > interface: org.opensuse.yast.modules.yapi.network.routes > policy: org.opensuse.yast.modules.yapi.network > controller: network/routes > +singular: true Why would 'routes' be singular ? This means that only one route ever exists. 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

2 1

[yast-devel] Re: [yast-commit] <rest-service> master : packages module: compare installed packages with vendor list (on rest-service)
by josef reidinger 28 Aug '09

28 Aug '09

Bjoern Geuken napsal(a): > ref: refs/heads/master > commit cddddcc11c0d9e7f04d9f2fca0ded04e50a71a45 > Author: Bjoern Geuken <bgeuken(a)suse.de> > Date: Fri Aug 28 16:45:34 2009 +0200 > > packages module: compare installed packages with vendor list (on rest-service) > --- > .../patches/app/controllers/packages_controller.rb | 25 ++++++++++++++++++++ > 1 files changed, 25 insertions(+), 0 deletions(-) > > diff --git a/plugins/patches/app/controllers/packages_controller.rb b/plugins/patches/app/controllers/packages_controller.rb > index e3e9718..e2b46ca 100644 > --- a/plugins/patches/app/controllers/packages_controller.rb > +++ b/plugins/patches/app/controllers/packages_controller.rb > @@ -40,11 +40,36 @@ class PackagesController < ApplicationController > > public > > + def compare_lists(packages) > + vendor_packages = Hash.new > + # yml datei auslesen: ["packages"] => ["yast-core", "ruby-dbus", ...] Hi, Please write comments in english > + package_list = Array.new > + package_list << ["yast2-users", "3ddiag", "foo"] > + > + package_list.each {|pk_name| > + packages.each {|p| > + # package installed? > + if p.name == pk_name > + # store version and name > + vendor_packages["package"] = {:name => "#{p.name}", :version => "#{p.version}"} > + end > + } > + unless vendor_packages.has_key? pk_name > + vendor_packages["package"] = {"#{pk_name}" => "not installed"} > + end I don't understand what it should do, especially condition at unless as you notime insert key that is pk_name. You always insert key "package" which you overwrite. I think you want do this: package_list.each {|pk_name| package = packages.find { |pkg| pkg.name == pk_name } vendor_packages[pk_name] = package ? {:name => "#{package.name}", :version => "#{package.version}"} : {"#{pk_name}" => "not installed"} } But I am not sure what is your goal, so maybe it can be done better (especially marking uninstalled packages look little strange) > + } > + # puts vendor_packages.inspect > + vendor_packages > + end > + > # GET /patch_updates > # GET /patch_updates.xml > def index > # note: permission check was performed in :before_filter > @packages = Package.find(:installed) > + if params[:filter] == "custom" > + @packages = compare_lists(@packages) This is really confusing as you change type of field. It was array of packages and result is another hash. > + end > respond_to do |format| > format.html { render :xml => @packages.to_xml( :root => "packages", :dasherize => false ) } > format.xml { render :xml => @packages.to_xml( :root => "packages", :dasherize => false ) } -- 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] text style guide
by Martin Schmidkunz 28 Aug '09

28 Aug '09

Hi, I am currently thinking about the webYaST text style guide and particularly about capitalization issues. There are two ways how to capitalize text: title style and sentence style. Whereas sentence style is quite easy to use (only capitalize first letter in a sentence) title style is quite difficult to handle: the first letter of each word is capitalized, the rest are lower case. In some cases short articles, prepositions, and conjunctions are not capitalized. (see http://msdn.microsoft.com/en-us/library/ aa511441.aspx#T and http://en.wikipedia.org/wiki/Sentence_case ) Currently (http://en.opensuse.org/YaST/Style_Guide) YaST uses sentence style in: * messages (warning, error, question,...) * progress stages * status bars * help text title style is used in: * headings, titles, and group labels * input and command widgets * module names * progress bar labels * status information, summaries and proposals * trees * tables For webYaST we could simply adopt the YaST text style guide or change it to this: "Use title style for titles and sentence style for all other UI elements." Titles would be: * headings, titles * module names This rule is used in many web applications (e.g. google) and in the UI of our target group (MS Windows style guide). Would the second suggestion (Use title style for titles and sentence style for all other UI elements.) be easier for you as developers or would you prefer to stick to the old YaST rules? As the only important thing with text style guide is consistency I would be fine with both solutions (although I have a slight personal preference towards the second solution :-)), I would like to pick the solution which is easier for you, the developers! If you think, that the old YaST text style is easier for you, please let me know until next Tuesday (1st September) otherwise we will go for the second suggestion. Have a nice weekend, Martin --- Martin Schmidkunz User Experience Specialist mschmidkunz(a)novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™ -- 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 status 28-Aug-2009
by Klaus Kaempf 28 Aug '09

28 Aug '09

WebYaST 28-Aug-2009 =================== Status: ----------- present: kkaempf, mschmidkunz, bgeuken, mzugec, lslezak absent: mvidner, jsrain, jsrain, visnov, dmacvicar, jsdn mschmidkunz: - worked on UI documentation in Wiki sent around on yast-devel - Next: more docs bgeuken: - more Ruby training - learned ruby-dbus - Next: Vendor setting for vendor packages (version display) mzugec: - hostname/domainname works in network stack (yapi->server->client) - Next: more YaPI work and tests lslezak: - service modules display current status now - still too slow - Next: benchmarking, improve test suite kkaempf: - code reviews - Next: more code reviews --- 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] UI documentation
by Martin Schmidkunz 28 Aug '09

28 Aug '09

Hi, please find some UI documentation on: http://en.opensuse.org/YaST/Web/Docu/Style_Guide The documentation includes: * generic webYaST layout * generic module layout * overview dialog * add wizard * edit * delete Looking forward to your comments, Martin --- Martin Schmidkunz User Experience Specialist mschmidkunz(a)novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] Webyast: REST error response
by Josef Reidinger 27 Aug '09

27 Aug '09

Hi, I look what is possible to use to report errors on our rest-service. I find summary there http://www.oreillynet.com/onlamp/blog/2003/12/restful_error_handling.html and improvement here http://www.dalouche.com/wordpress/2009/04/25/error-handling-in-rest-applica…. For our purpose I think that the best sollution is to use our own error code which is not used, ( i that one which begin 4** is good) and in body specify type of error, needed data for generate report (like which permission mission and for which user) and english error description. This error description should not use frontend, as it must match type and print localized error description. So what I plan to do: - Defined exceptions in backend which modules should throw in case of errors - Add exceptions to webservice method where it is appropriate (like check_permission should not return anything, just throw exception because user already should check its permission) - Add rescue_from to application controller to automatic generate proper response code and body - Add error handler to webclient - ideal is throw exception which is catch by rescue_from and this exception contain response from which generate localized error page) For this I suggest little refactoring of resource loader, at least I try make it less dynamic to easier enhance it. Welcome any comments and suggestion. Now I create branch for it and try start which some ideas, so it doesn't break any code until it is ready. -- 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

2 4

[yast-devel] JavaScript.code_quality <> Ruby.code_quality
by J. Daniel Schmidt 27 Aug '09

27 Aug '09

Hi WebYaST hackers, Yesterday I fixed this JavaScript browser detection bug: https://bugzilla.novell.com/show_bug.cgi?id=529931 and just wanted to tell you my observations. We spend a lot of time writing good, clean, DRY, easily readable ruby code and even have tools like Flog, Flay and Heckle(1) to check its quality. All this is great, sure. But on the other hand we just dump JavaScript code into the users browser to do some magic but don't care for quality there. The bug above was just 4 tests if a variable had a value. Here's a diff snippet: - window.G_vmlCanvasManager.init_(document); + if (window.G_vmlCanvasManager) { + window.G_vmlCanvasManager.init_(document); + } My JavaScript debugger(2) still gets flooded with warnings about the code that we run in the users browser. So there might arise other stuff in the future. Somehow this feels strange. Focussing on good code on the one side but forgettig about it on the other. (1) http://ruby.sadi.st/Ruby_Sadist.html (2) Web Developer plugin for Firefox: https://addons.mozilla.org/en-US/firefox/addon/60 I also recommend Firebug: https://addons.mozilla.org/en-US/firefox/addon/1843 Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- 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 27-Aug-2009
by Duncan Mac-Vicar Prett 27 Aug '09

27 Aug '09

WebYaST 27-Aug-2009 =================== Status: ----------- present: kkaempf, dmacvicar, jdsn, jreidinger, mzugec, jsrain, lslezak, visnov, bgeuken, mvidner, mschmidkunz dmacvicar: - vendor settings discussion with Björn - hudson: client builds, service: network call depends - rack middleware for engine's static assets, submitted discussion to upstream: http://groups.google.com/group/rubyonrails-core/t/fbc79b21b0ddc3ed - hudson git plugin bug: https://hudson.dev.java.net/issues/show_bug.cgi?id=2827 kkaempf: - no status jdsn: - javascript browser detection - will continue to work in bugzilla jreidinger: - basesystem, controller action - send mail to designers. Will work in a branch some error handling - AI: write mail with proposal, look at ErrorResult facility mzugec: - network tests - discussion about YaPI testing models. Language plugin an example. jsrain: - no update lslezak: - monday: services testsuite, no more updates - plan today: status custom services visnov: - no updates bgeuken: - packages controller - dbus problems: discussing with mvidner - integrate the vendor settings mvidner: - released dbus library, loop.quit support - will work with Björn to fix packages controller - submitted to YaST:Web devel:languages:ruby:extensions - http://github.com/mvidner/ruby-dbus/tree/master mschmidkunz: - document basic UI behavior, continue to work on that. - will notify others when these updates happen -- 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] RFC: plugin static assets
by Duncan Mac-Vicar Prett 26 Aug '09

26 Aug '09

Hi By default, rails engines do not support static assets in their own public/ directory. It is a so obvious feature that I had the prejudge in mind that it would not be trivial. I implemented a Rack middleware that looks in all the loaded plugins for a resource, if it can be served from there, it does it, if not, it forwards to the application (a simple overlay, just like the other parts of the engines work). Attached is the patch for review. This allows engines to have their own public/ directory with files, images, css files, etc. Just like with engines controllers and views, you need to have name conventions, as the names may clash. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)

1 0

[yast-devel] Webyast session with consultant
by Josef Reidinger 26 Aug '09

26 Aug '09

Hi, I bring notes from today's session with consultant. We look at test-driven development. Usual presentation which can be also find on net, so nothing especially interesting. We try shoulda gem, which is quite good for reporting problems (test reports looks better). I ask also how to move our 2.2 generated rails to 2.3. Karel says that rails from 2.2 have templates which can generate code better (really good for business convence, so we should create some template for webyast plugins) and maybe exist some template to convert generated application. I google it and write result. Second think which we learn is how to work routes. especially interesting methods for rest is method resources and resource (and parameters only and except). Also we look how REST work. What Karel find strange is that we have default route, which often lead to unintended routes and behavior. Second what he think is that we should use route for each plugin as each plugin should define its routes which it provides. For REST we should look how is designed cloudkit ( http://getcloudkit.com/ and http://www.bestechvideos.com/2009/06/04/pivotal-labs-talks-cloudkit-hacking… ). Rest tutorial is at http://www.infoq.com/articles/rest-anti-patterns and http://www.infoq.com/articles/rest-introduction We also talk about our webclient and what we should improve. We should have webclient also rest. Especially we should operate easy on hosts. Karel propose have sub-resources. So url should look like /hosts/1/systemtime for setting systemtime on first host. Also we give another hints how to change our dynamic creating ActiveResource to normal classes and have in each plugin usual model, which should contain a lot of functionality and can be easily tested. (So we should have something like YaSTController as ancestor and YaSTResource as model ancestor). Welcome any another ideas which I forget mention. -- 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

6 10

[yast-devel] Re: [yast-commit] <rest-service> master : Use format instead of content type, as it seems to set the
by Klaus Kaempf 26 Aug '09

26 Aug '09

* Duncan Mac-Vicar P <dmacvicar(a)suse.de> [Aug 25. 2009 00:04]: > ref: refs/heads/master > commit 72faf37c3f8dda4ab91a97f677f8833a775bded8 > Author: Duncan Mac-Vicar P <dmacvicar(a)suse.de> > Date: Tue Aug 25 00:01:33 2009 +0200 > > Use format instead of content type, as it seems to set the > content type too. Hmm, this looks 'fishy' to me. Actually, both ways (@request.accept and setting :format) should work. The (http-wise and restful) correct way is setting the http 'accept' header to the list of mime types (yes, there can be multiple) acceptable by the client. The server is then free to choose one of them. The :format is a Rails extension to support setting the mime type via the URL. Just look at the default routes.rb entry: map.connect ':controller/:action/:id.:format' This is basically a regexp saying that if the url contains two slashes and a dot its to be parsed as controller-slash-action-slash-id-dot-format Summary: Honoring the accept header is a 'must', honoring the :format extension a 'can'. Hth, 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

2 2

[yast-devel] WebYaST 26-Aug-2009
by Duncan Mac-Vicar Prett 26 Aug '09

26 Aug '09

WebYaST 26-Aug-2009 =================== Status: ----------- present: visnov, jsrain, mvidner, mzugec, kkaempf, dmacvicar, begeuken, jdsn dmacvicar: hudson still in bad state, but now in the rpm packages area (like postin scripts failing) good example: polkit-auth an already granted policy returns non-zero. How to handle that in the packages? bgeuken: improving patch tests, having trouble mocking dbus callbacks. mvidner will help. discuss vendor adaptations with dmacvicar today kkaempf: no status jsrain: no status mvidner: doing release of ruby-dbus with Dbus::Main stop featre. mzugec: committed and reverted, test failed. Continue work on YaPI jsdn: bug browser detection making troubles to status page. -- 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 : Revert "introduction to use dbus service"
by Klaus Kaempf 26 Aug '09

26 Aug '09

* Michal Zugec <mzugec(a)linux.intech-solutions.com> [Aug 25. 2009 17:09]: A couple of comments: > + ret = Scr.instance.execute(["/sbin/yast2", "lan", "list"]) > + lines = ret[:stderr].split "\n" > + devices = [] > + lines.each do |s| > + dev = Network.new Why is the class called 'Network' and the variable 'dev' ? The class should be either called NetworkDevice or embedded inside a module (aka namespace), resulting in Network::Device > + dev.id = s.split("\t")[0] > + dev.name = s.split("\t")[1] Its more readable (and more Ruby like) to have id and name as 'constructor' arguments: Network::Device.new id, name And these assignments are wasting cycles as you're splitting the string two times. 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

2 1

[yast-devel] Re: [yast-commit] <rest-service> master : Do not fail if authorization is already granted
by josef reidinger 26 Aug '09

26 Aug '09

Duncan Mac-Vicar P napsal(a): > ref: refs/heads/master > commit 3e0888a99fc4e8eafdd54633acb92c17266eb853 > Author: Duncan Mac-Vicar P <dmacvicar(a)suse.de> > Date: Wed Aug 26 00:13:26 2009 +0200 > > Do not fail if authorization is already granted > --- > .../system/package/yast2-webservice-system.spec | 8 ++++---- > 1 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/plugins/system/package/yast2-webservice-system.spec b/plugins/system/package/yast2-webservice-system.spec > index 25bb247..c6872dd 100644 > --- a/plugins/system/package/yast2-webservice-system.spec > +++ b/plugins/system/package/yast2-webservice-system.spec > @@ -56,10 +56,10 @@ rm -rf $RPM_BUILD_ROOT > > %post > # granting all permissions for the web user > -polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.shutdown > -polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.shutdown-multiple-sessions > -polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.reboot > -polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.reboot-multiple-sessions > +polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.shutdown ||: > +polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.shutdown-multiple-sessions ||: > +polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.reboot ||: > +polkit-auth --user %{pkg_user} --grant org.freedesktop.hal.power-management.reboot-multiple-sessions ||: > > %postun > # discard all configured permissions for the web user Hi, I think that this is not good idea as silently fail could hide real problem. I think that we should prefer checking if permissions is set and if not then grant it. Now if somethink fail in setting permission noone know it. Josef -- 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] Disabling and enabling modules
by Leonardo L. P. da Mata 25 Aug '09

25 Aug '09

Hello, i'm trying to add a new module into the installation so i can create a partition for recovering the system if the user causes a damage into the installed system. The module must create one autoyast.xml file that will be used to reinstall the system with the same configuration. To call this module i must add it into the control.xml file. If i add it into the "automatic configuration" step, it is called, but when i try to add it just before the congratulations step, it is not called. During my investigation i've found that this module is disabled by the function AdjustDisabledItems() called by the inst_worker_continue.ycp. This function call disable some modules and i don't know how to enable then only adding into the control.xml file. The only way i found how to enable this module was adding a call into the inst_worker_continue.ycp to the function ProductControl::EnableModule("name"); but to do this i need to change the content of the yast2-installation package. Is there any way to enable a module only adding it into the control.xml file? Thanks -- 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