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