December 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] buttons buttons buttons
by Martin Schmidkunz 24 Oct '08

24 Oct '08

Hi, when testing openSUSE 11.1/SLES 11 I came across a rather curious situation: many modules have already switched their label from Abort/OK(Accept, Finish...) to the style guide compliant Cancel/OK label. However in every case there is a third, inactive "Back" button included. This doesn't make sense as there is nothing to go back and the dialog is just an overview. I suppose this is due to many of you using wizard.ycp as base template for creating your module. What do you think about using the button box (http://lizards.opensuse.org/2008/08/28/button-order-in-yast-trying-to-make-…) instead of the buttons of wizard.ycp? In my opinion this would have the following advantages: * consistent button order in pop ups and in the module * user would not need to deal with an inactive button * button order in YaST would be consistent with the desktop used by the user What do you think about that issue? Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 6

[yast-devel] 3 questions about yast....
by Roberto Angelino 28 Feb '08

28 Feb '08

OK. First some background: My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script. Here are the 3 questions they have (for sles10 version): 1) After yast completes installation (i.e., post-install), the fstab is created. What yast module makes this call? It has to be in yast2-installation, but I can't find the connection between the installation and yast2-storage where WriteFstab() lives. 2) How does yast determine what the source partition to mount is? 3) bootloader_finish.ycp breaks the install at the end. They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do? Thanks -robert -- 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] yast2-ncurses has a status line :)
by Katarina Machalkova 14 Jan '08

14 Jan '08

Hola brave yast hackers! As I kept receiving user complaints that the navigation in yast text-mode UI is a bit clumsy, I took my ITO and decided to do something with it. Here's the first bigger improvement (I hope so): We have many 'cheat-codes' for quick access to push buttons in text-mode in the form of Fxx keys, but: 1) hardly anyone knows about those 2) it is because they are well hidden in a pop-up that appears if F1 key is pressed (real hackers use F1 help key as the very last resort ;-) ) 3) this popup is so confusing that it leaves user even more clueless than (s)he was before (see ttps://bugzilla.novell.com/show_bug.cgi?id=335291) Now ncurses UI has a nice contrast status line where all Fxx cheat codes for current dialog are listed, as you can see in attached screenshot (I used yast2-users module as an example, because it makes quite intensive use of Fxx keys). User has these quick shortcuts in front of his/her eyes at all times and can use them right away without having to open a help popup or to remember that e.g. F10 usually stands for 'Finish'. The only disadvantage is that the status line takes yet another line off the small (and sometimes really crowded) text-mode screen :( Anyway, so far it's just a prototype, I'm thinkin about disabling status line completely should the screen be smaller than e.g. 25 lines ... So, enjoy this improvement and feel free to use Fxx shortcuts in your modules more intensively (hint: add `opt(`key_Fxx) to your widget to make it quickly accesible by selected Fxx key) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

14 34

[yast-devel] My first ycp dialog :)
by Stephan Kulow 09 Jan '08

09 Jan '08

Hi! I thought prototyping in ycp is easier than creating mockups in gimp, so I coded http://ktown.kde.org/~coolo/yast7.png - but it looks weired - suggestions are welcome ;) Greetings, Stephan

11 29

[yast-devel] christmas
by Martin Schmidkunz 21 Dec '07

21 Dec '07

Hi, I wish all merry and recreative Christmas holidays and a successful, healthy and lucky new year! To those I was able to work with: Thanks for your time and patience. Due to that I learned some fascinating things this year :-) Best regards, 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

1 0

[yast-devel] home:coolo
by Stephan Kulow 20 Dec '07

20 Dec '07

Hi! For those interested, I built latest yast-qt and dependencies in home:coolo - I did not test them myself, but I have http://download.opensuse.org/repositories/home:/coolo/openSUSE_10.3/ and http://download.opensuse.org/repositories/home:/coolo/openSUSE_Factory/ Greetings, Stephan -- 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] TimezoneSelector widget
by Stephan Kulow 18 Dec '07

18 Dec '07

Hi! I spent some time implementing a very rough first version of a graphical timezone selector widget and commited it into branches/tmp/coolo/zone. The widget is rather useless as it does not have any kind of valus or properties and that is what I'm wondering: what would be a good connection to ycp? I assume I need to send events if the current selection changes and I could accept a given selection from outside - e.g. from a combo box below. I guess through a property? Please help out a clueless ycp programmer :) Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 19

[yast-devel] yast2-ncurses help wanted : tab support
by Katarina Machalkova 14 Dec '07

14 Dec '07

Hola opensuse users! (and yast hackers) If you're using YaST ncurses interface, you might have already noticed that currently there is no support for tab widgets there (i.e. ncurses equivalent of Qt TabBar, see some screenshots here: http://doc.trolltech.com/4.2/qtabwidget.html#details ). Instead, quite a clumsy workaround with push buttons or radio buttons is used in some modules I'm looking for someone who would write tab support for yast2-ncurses library, in other words, add a C++ class for tab widget into YaST ncurses UI. Ideally, I'd like it to be someone from openSUSE community :) With current mod-ui (which is a new UI engine in openSUSE 11) it could be pretty simple and straightforward. You don't need to know anything about ncurses programming (actually, you'll see none, or the very minimum of libncurses code when coding the class). What you really need is: * knowledge object-oriented programming in C++ * at least some awareness about UI events and event handlers So if you are e.g. an university student looking for simple C/C++ assignment (that you could 'recycle' at school ;-) ), or if you're looking for a way how to spend your ITO, or if you just want to help to improve your favourite UI ;-) just drop me an e-mail ev. ping me on freenode IRC #yast channel. I'm going to assist you with coding and provide all the information you'd need. Thanks B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

1 0

[yast-devel] Installation is green now
by Stephan Kulow 13 Dec '07

13 Dec '07

Hi! As every problem I wanted to have fixed is fixed in qt4 port, Stefan and me agreed to move out qt3. So I submitted yast2-qt and installation-images to Factory. There are many problems still with it, e.g. it's still not possible to install packages correctly - but I decided Factory users are zypper users anyway and it will only take another couple of days to fix these issues. The theme used is still my wild hack, but I've shown Jakub how to develop something new, so I'm expecting just the best ;) Greetings, Stephan -- 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] make_wrapper for CMake vs. Autotools Projects
by Stefan Hundhammer 12 Dec '07

12 Dec '07

New: http://svn.opensuse.org/svn/yast/trunk/devtools/yast2/make_wrapper (or: svn up devtools) This is a script you can use to make life more convenient when working with both CMake and autotools based projects: CMake is intended for building out of the source tree. Autotools (and pure "make") build in the same tree where the source files are. If you have both kinds of projects, you always have to keep in mind where to "cd" to (or to what shell window to go) to invoke "make". And for CMake out-of-source-tree building it's really hard to invoke "make" directly from the editor of your choice so it can immediately load the source file where the compiler reported an error and fix it. Coolo suggested to use the "makeobj" script from the KDE 4 SDK, but not only does this require the user to set environment variables where the build tree is, it also does not seem to work well in mixed CMake / Autotools environments. So I wrote this "make_wrapper" script that checks the current directory for a file "Makefile" and call "make" there directly if there is one. If there is none, it checks ../build/Makefile, then ../../build/Makefile etc. All you have to do is stick to that convention to name the CMake out-of-source-tree build directory "build" (configurable in the script of course) and simply call "make_wrapper" rather than "make". The toplevel Makefile.cvs in libzypp and yast2-qt4 support that anyway: They create a "build" directory and invoke "cmake" there. Emacs users might want to set their "compile-command" variable in ~/.emacs : (setq compile-command "make_wrapper -k && sudo make_wrapper install") or, when using "icecream" distributed compilation: (setq compile-command "make_wrapper -k -j20 && sudo make_wrapper install") CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2