June 2011 - YaST Development - openSUSE Mailing Lists

[yast-devel] Translation rounds for SP2?
by Ladislav Slezak 08 Jul '11

08 Jul '11

Hi, will be there any translation round for SP2? If yes, when? Can we change the translatable strings to SP2? I have noticed many typo fixes in trunk, can we backport them to SP2? -- 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

3 2

[yast-devel] GsoC Weekly Report - "Separating libYUI"
by N.B.Prashanth 05 Jul '11

05 Jul '11

Hi, I would like to summarize my progress so far. I am working on the libYUI project as mentioned above. 1. libYUI and all three UI plugins (Qt, ncurses and GTK) have been ported to target systems (Fedora and Ubuntu). 2. The git repository at gitorious.org/libyui/libyui has been removed. This will be replaced with the official YUI svn repo once the conversion is complete. The old repo can be found at gitorious.org/libyui/gsoc2011 and will contain files related to my project. 3. Builds now make use of OBS. The download repository can be found at : http://download.opensuse.org/repositories/home:/nbprashanth/ . Currently build targets are Ubuntu (10.10 & 11.04), Fedora (14 & 15) and Debian 6. 4. GTK plugin no longer has libzypp as a dependency and can hence be ported. 5. Due to CMake issues on Ubuntu 11.04 with the GTK CMake module (Bug report : https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/751940 ), builds using CMake have failed. Moreover, the default install location for gdk-pixbuf on F14 and F15 are different which caused the GTK plugin build to fail on F14 as well. 6. I have converted the GTK plugin to use autotools as opposed to CMake. This has made it compile successfully in Ubuntu 11.04 using pkg-config and I hope, it will compile of F14 as well. I will be updating the GTK package on OBS this week. 7. Documentation for libyui is now online and can be found at :http://doc.opensuse.org/projects/libyui/HEAD/ . This is an initial version and improvements may be expected in near future. The absolute path issue is now fixed. 8. Examples, update for YUI and full GsoC reports are also updated on my blog which can be found at : http://nbprashanth.wordpress.com/ . My last weeks GsoC report (GsoC Report - 3) can be found at : http://nbprashanth.wordpress.com/2011/06/27/gsoc-report-%E2%80%93-3/ 9. Patches for minor bugs such as "long long warnings" have been made. Not integrated upstream yet. 10. If anyone happens to test any of the YUI packages at OBS and finds a bug, please send me an email or leave a comment on the blog. -- Regards, N.B.Prashanth -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 3

[yast-devel] Re: [yast-commit] r64648 - /trunk/fcoe-client/src/FcoeClient.ycp
by Ladislav Slezak 30 Jun '11

30 Jun '11

Dne 30.6.2011 13:27, gs(a)svn2.opensuse.org napsal(a): [...] > + fcoe_config = FcoeClient::GetFcoeConfig(); > + summary = Summary::AddLine( summary, sformat( "DEBUG: %1", fcoe_config["DEBUG"]:"" ) ); > + summary = Summary::AddLine( summary, sformat( "USE SYSLOG: %1", fcoe_config["USE_SYSLOG"]:"" ) ); Just some notes: The translation marks are missing. I guess these values mean the direct config options, I think there should be rather some human readable texts instead. > + summary = Summary::AddLine( summary, _("<b>Starting of services</b>") ); > + summary = Summary::AddLine( summary, sformat( "fcoe: %1", (service_start["fcoe"]:false)?"true":"false" ) ); > + summary = Summary::AddLine( summary, sformat( "lldpad: %1", (service_start["lldpad"]:false)?"true":"false" ) ); The same here: no translation. Although "fcoe" might seem to be untranslatable translation allows to change the order which is essential in RTL (right-to-left) languages (like arabic). But again, here I'd rather see a service description text instead of the abbreviations (lldpad? WTF? Do I need it?). Do not use "true" "false" but rather _("Enabled") _("Disabled") to be consistent with other proposals. And the summary is printed in proportion font (in GUI) so the spaces do not guarantee any alignment in the output, just one space is enough IMO. -- 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] GsoC Weekly Report - "Separating libYUI"
by N B Prashanth 30 Jun '11

30 Jun '11

Hi, I would like to summarize my progress so far. I am working on the libYUI project as mentioned above. 1. libYUI and all three UI plugins (Qt, ncurses and GTK) have been ported to target systems (Fedora and Ubuntu). 2. The git repository at gitorious.org/libyui/libyui has been removed. This will be replaced with the official YUI svn repo once the conversion is complete. The old repo can be found at gitorious.org/libyui/gsoc2011 and will contain files related to my project. 3. Builds now make use of OBS. The download repository can be found at : http://download.opensuse.org/repositories/home:/nbprashanth/ . Currently build targets are Ubuntu (10.10 & 11.04), Fedora (14 & 15) and Debian 6. 4. GTK plugin no longer has libzypp as a dependency and can hence be ported. 5. Due to CMake issues on Ubuntu 11.04 with the GTK CMake module (Bug report : https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/751940 ), builds using CMake have failed. Moreover, the default install location for gdk-pixbuf on F14 and F15 are different which caused the GTK plugin build to fail on F14 as well. 6. I have converted the GTK plugin to use autotools as opposed to CMake. This has made it compile successfully in Ubuntu 11.04 using pkg-config and I hope, it will compile of F14 as well. I will be updating the GTK package on OBS this week. 7. Documentation for libyui is now online and can be found at :http://doc.opensuse.org/projects/libyui/HEAD/ . This is an initial version and improvements may be expected in near future. The absolute path issue is now fixed. 8. Examples, update for YUI and full GsoC reports are also updated on my blog which can be found at : http://nbprashanth.wordpress.com/ . My last weeks GsoC report (GsoC Report - 3) can be found at : http://nbprashanth.wordpress.com/2011/06/27/gsoc-report-%E2%80%93-3/ 9. Patches for minor bugs such as "long long warnings" have been made. Not integrated upstream yet. 10. If anyone happens to test any of the YUI packages at OBS and finds a bug, please send me an email or leave a comment on the blog. -- Regards, N.B.Prashanth -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 3

[yast-devel] Review code, please
by Martin Vidner 28 Jun '11

28 Jun '11

Hi, so far only a few people have been commenting on others' commits, and I'd like to ask the others to join the party. We need you! - One obvious reason is sharing the workload (but so far the volume is manageable). - Reading other people's code makes you a better programmer. - Commenting on other people's code improves the code, it prevents ugly code or outright bugs from getting in. - You think it is not your problem? So did I think before inheriting a certain ****ing piece of juicy ****. - Reading *good* code makes me feel better about our work, the project, the product. Or is everyone already reading everything and finding nothing to comment on? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

4 5

[yast-devel] Deleting items from a selectionWidget
by Manu Gupta 28 Jun '11

28 Jun '11

Hi All I am trying to delete a single item from a selection widget, but I am unable to find a solution to it directly atleast. -- Regards Manu Gupta -- 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] Changing the Attitude to Coding YaST
by Lukas Ocilka 27 Jun '11

27 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yasties, Developers and Friends, According to the feedback I've got recently and what I've been feeling for a longer time, there is a chance to make YaST development cleaner, simpler and more enjoyable just with little tricks learned from the other projects we've been working on recently. Here you can see a list of unsorted ideas that came into my mind thinking about the other project and reusing experience with them in the YaST development: Code Reusability - - Usually the code is written for one purpose, but maybe we should start thinking before the development: Isn't the code reusable from anywhere else? Can the code be more generic? Think about CWM. - - Additionally, a lot of the code is in "include"d files or even in "client"s which makes the code almost impossible to be tested. That's also why we get syntax and/or runtime errors. - - Fix|Easy: Develop code in reusable libraries and write simple and understandable tests. Testing - - Connected to the previous point. Most of the current code is not tested because it actually cannot be tested. - - On the other hand, sometimes we think that writing testsuites is for dummies. But untested code causes bugs that need to be fixed later and thus is doesn't save the time at all. - - Fix|Medium: Write tests, make sure they are called during build. Coding Standards - - The code should be not only understandable to ourselves but also to the others. Using the same coding standards make it easier to understand the code structure, parameters, expected return value and so long. - - Examples: * Package::IsValid(package) -> returns boolean (maybe only Valid()) * Package::Install(package) -> do you need to read any documentation? * Using hashes with parameters instead of twelve parameters, eight of them optional * Indentation * No more "include"s if not necessary * Useful comments * Useful documentation of all the public functions * ... other ideas? ... - - Fix|Medium: Define the standards and use them (let's learn from other projects) Cooperation - - When the code has tests and it's mostly in compiled libraries, it's quite easy for more developers to work on the same project in the same time. The only thing they need to define is the API and using the same standards they can understand the API almost instantly. - - Better cooperation is usually useful when someone needs help from the others: too many features and bugs and to few time. - - Fix|Depends: ... Code Reviews - - In the SLMS team, we've found out that all the commits should be reviewed by someone else. This helps to identify potential issues in time. All the commits are public anyway. - - Fix|Easy to Medium: Either someone is always assigned to review everyone's code (takes too much time) or developers usually check code of someone else only. Shared Task List - - There are often even smaller tasks that need to be done by anyone in the team but they don't have their priority high enough (so called easy-hacks) - and that's why we forget them quite easily. - - Fix|Easy to Medium: Use some of the task managers, e.g., http://www.producteev.com/ anyone can pick a task and try to implement / fix it. I believe that you have other ideas how to improve the development - how to make the development and maintenance easier for you and/or the others. Or you maybe have an opinion on the ideas I just presented. Share them with us, please! :) Thanks in advance and Bye Lukas - -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFN73YzVSqMdRCqTiwRAuC2AJsFP391iBGZwiJtbFNeN3FdwfZqRACfQqZZ xvmYF1Ar/q64o1iFMhVImlI= =R8U6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

13 31

[yast-devel] Testing Classical YaST in Hudson
by Lukas Ocilka 27 Jun '11

27 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Many of us have already found out how running tests in Hudson can find potential (or real) issue just a few moments after a commit that breaks the code is submitted. We use Hudson for most of our projects now but we still don't run any tests for the Classical YaST: * What do you think of running the YaST tests in Hudson? * How could we do that? * Are there any additional tests we could run, for instance YCP syntax check for clients (?). * What about checking whether all functions are actually in use? Thanks in advance for your opinions and ideas. Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk4EjEkACgkQVSqMdRCqTizhGACgkUuu7QAsJFQaqF5spFr9YmLI 02gAmwX+bP9dhmly3CuXZf89o9egmkb/ =B0Mk -----END PGP SIGNATURE----- -- 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] Classical YaST in Appliances: Choosing the UI
by Lukas Ocilka 24 Jun '11

24 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just created a new JeOS appliance in SUSE Studio for testing purpose (YaST Backup bug). JeOS is known to have as few packages as possible. After selecting YaST Backup for installation, I've rather also checked whether I'll be actually able to run it, so searched for all YaST packages, especially the UI ones. And which one was selected? *yast2-gtk* OK, yast2.rpm requires yast2_ui and yast2-gtk, yast2-ncurses and yast2-qt all provide that symbol. Isn't there anything we could do about /better/ [1] selection [2]? Ideas? Opinions? Thx && Bye Lukas #1 'better' might be pretty subjective, I know. But this seems to be just alphabetically sorted list of solutions (for the first sight) #2 for example, KDE is installed -> Qt, GNOME/LXDE is installed -> GTK, neither of them (?) -> ncurses - -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFOAvTtVSqMdRCqTiwRApcVAJ0aI3C01fxcJJSBIVUXduIqbLaFuQCfeIvy EIcQnPEenv7n64RHekoQiho= =GoF7 -----END PGP SIGNATURE----- -- 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] A few questions about libYUI
by Manu Gupta 23 Jun '11

23 Jun '11

Hi I am trying a few things in libYUI to ask of 1. How to set a value in a ComboBox? I have tried with both editable and non-editable comboBoxes I have a YComboBox * cc = YUI::widgetFactory(dialog,"SELECT",true); cc->addItem("XYZ"); cc->addItem("Blah"); cc->setValue("Manu"); In this case, the value Manu is not set and highlighted Now lets take this case YComboBox * cc = YUI::widgetFactory(dialog,"SELECT",true); cc->addItem("XYZ"); cc->addItem("Blah"); cc->setValue("Blah"); Same thing blah is not highlighted case 3 YComboBox * cc = YUI::widgetFactory(dialog,"SELECT",false); cc->addItem("XYZ"); cc->addItem("Blah"); cc->setValue("Blah"); I get a YUI::Exception So if anyone can cross check this case and let me know if it is a bug or not? Second Question is related to event handling If a selection in a comboBox changes, how would I able to recognise it Currently I follow this approach YDialog * dialog = YUI::widgetFactory->createDialog(); YComboBox * cc = YUI::widgetFactory(dialog,"SELECT",false); YWidgetEvent * event = (YWidgetEvent*)dialog->waitForEvent(); while(1){ if(event->reason()==SelectionChanged){ cout<<"XYZ"; } }; this does not seem to work ie the dialog is not recognising changes in my combobox, how do I solve them? -- Regards Manu Gupta -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3