November 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] Work report
by Stephan Kulow 12 Dec '07

12 Dec '07

Hi! For those seeing my commits on the commit list, I thought I give you a little report on what I did in your SVN: http://www.kdedevelopers.org/node/3119 What's not written in there: the way it's implemented relies on a fixed size of 1024x768 and I bet on my laptop screen to even look just as bad as on the screenshot. But that's details - and basically out of scope of ITO :) Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 5

[yast-devel] Language::language (and maybe other variables / functions)
by Lukas Ocilka 10 Dec '07

10 Dec '07

Hi, As I've already written, I'm just trying to break some YaST*.rpm dependencies (See thread "[yast-devel] openSUSE 11.0 - Splitting YaST packages - Call for help"). I've found that there might be a candidate for moving some functionality (or only variable) to yast2.rpm or somewhere similarly. It is: +-------------------------------------------------+ | modules/Language.ycp, namely Language::language | +-------------------------------------------------+ These modules use Language YCP module: add-on autoinstallation firstboot installation metapackage network packager Language.ycp is part of yast2-country which directly uses (requires) these rpms: yast2 yast2-bootloader yast2-storage yast2-x11 I'm writing to the yast-devel mailing-list first before asking yast2-country maintainer to move Language::language (or more) somewhere else because I want to know where you think it is a good idea, whether it would help your modules at all ;) So, let me know, please :) Bye and Thanks! Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic clients/release_notes_popup.ycp: string tmp = sformat (path_templ, Language::language); clients/release_notes_popup.ycp: tmp = sformat (path_templ, substring (Language::language, 0, 2)); clients/release_notes_popup.ycp: string tmp = sformat (path_templ, Language::language); clients/release_notes_popup.ycp: tmp = sformat (path_templ, substring (Language::language, 0, 2)); clients/inst_rpmcopy.ycp: Packages::SlideShowSetUp (Language::language); clients/inst_rpmcopy.ycp: Pkg::SetTextLocale (Language::language); clients/inst_rpmcopy.ycp: SlideShow::SetLanguage (Language::language); clients/yast_inf_finish.ycp: linuxrc["Language"] = Language::language; clients/inst_proposal.ycp: Pkg::SetLocale (Language::language); clients/inst_proposal.ycp: Pkg::SetAdditionalLocales ([Language::language]); clients/software_proposal.ycp: if (Pkg::GetPackageLocale () != Language::language) clients/software_proposal.ycp: Pkg::SetPackageLocale (Language::language); clients/software_proposal.ycp: if (! contains (Pkg::GetAdditionalLocales (), Language::language)) clients/software_proposal.ycp: add (Pkg::GetAdditionalLocales (), Language::language)); clients/inst_welcome.ycp:map welcome = CustomDialogs::load_file_locale(patterns,directory, Language::language); clients/language_auto.ycp: "language" : Language::language_on_entry, clients/language_auto.ycp: "languages" : Language::languages_on_entry, clients/language_auto.ycp: Console::SelectFont (Language::language); clients/language_proposal.ycp: string language_on_entry = Language::language; clients/language_proposal.ycp: (Language::languages == "" || Language::languages == language_on_entry) && clients/language_proposal.ycp: Language::languages = Misc::CustomSysconfigRead ("INSTALLED_LANGUAGES", "", clients/language_proposal.ycp: y2milestone ("languages got from target system: %1", Language::languages); clients/language_proposal.ycp: language_on_entry, Language::language, Language::languages); clients/language_proposal.ycp: if (force_reset && language_on_entry != Language::language) clients/language_proposal.ycp: "language_changed": (language_on_entry != Language::language ) clients/language_proposal.ycp: "language_changed": (language_on_entry != Language::language) clients/firstboot_language.ycp: string language_on_entry = Language::language; clients/firstboot_language.ycp: if( Language::language != language_on_entry || Language::ExpertSettingsChanged ) clients/language.ycp: splitstring (Language::languages, ",")); clients/language.ycp: y2milestone ("canceled -> restoring: %1", Language::language_on_entry); clients/language.ycp: Language::Set (Language::language_on_entry); clients/language.ycp: Console::SelectFont (Language::language); clients/language.ycp: Language::language, selection[Language::language,1]:"")); clients/language.ycp: string languages = Language::languages; clients/language.ycp: splitstring (languages, ","), ``(lang_code != Language::language)); clients/language.ycp: string language = options["lang"]:Language::language; clients/language.ycp: Language::languages = mergestring (llanguages, ","); clients/language.ycp: if (language != Language::language) clients/select_language.ycp: string language = Language::language; clients/select_language.ycp: list<string>languages = splitstring (Language::languages, ","); clients/select_language.ycp: // with the default selection according to Language::language clients/select_language.ycp: if (language != Language::language) clients/select_language.ycp: y2milestone ("Language changed from %1 to %2", Language::language, language); clients/select_language.ycp: Language::languages = clients/select_language.ycp: Language::languages = mergestring (selected_languages, ","); clients/inst_autoinit.ycp: Installation::encoding = Console::SelectFont( Language::language ); clients/inst_autoinit.ycp: UI::SetLanguage (Language::language, Installation::encoding); clients/inst_autoinit.ycp: WFM::SetLanguage (Language::language, "UTF-8"); clients/save_config_finish.ycp: string lang = Language::language; clients/inst_release_notes.ycp: Language::language, clients/inst_release_notes.ycp: substring (Language::language, 0, 2), clients/inst_productsources.ycp: language_long = Language::language; include/packager/load_release_notes.ycp: string tmp = sformat (path_templ, Language::language); include/packager/load_release_notes.ycp: tmp = sformat (path_templ, substring (Language::language, 0, 2)); include/installation/inst_inc_second.ycp: Pkg::SetLocale (Language::language); include/installation/inst_inc_second.ycp: string language = Language::language; include/installation/inst_inc_first.ycp: Installation::encoding = Console::SelectFont (Language::language); include/installation/inst_inc_first.ycp: UI::SetLanguage (Language::language, Installation::encoding); include/installation/inst_inc_first.ycp: WFM::SetLanguage (Language::language, "UTF-8"); modules/AutoinstClone.ycp: general["language"] = Language::language; modules/Timezone.ycp: string new_timezone = lang2tz[Language::language]:""; modules/Timezone.ycp: GetTimezoneForLanguage( Language::language, "US/Eastern"); modules/Timezone.ycp: * Uses Language::language for translation. modules/Packages.ycp: string language = Language::language; modules/Packages.ycp: list<string> locales = LocaleVersions (Language::language); modules/Packages.ycp: Pkg::SetTextLocale (Language::language); modules/Packages.ycp: force_reset, reinit, Language::language); modules/Packages.ycp: Pkg::SetAdditionalLocales ([Language::language]); modules/Keyboard.ycp: * Uses Language::language for translation. modules/Keyboard.ycp: default_keyboard = GetKeyboardForLanguage( Language::language, "english-us" ); modules/Keyboard.ycp: GetKeyboardForLanguage ( Language::language, "english-us" ); modules/ProductLicense.ycp: Language::language, modules/ProductLicense.ycp: substring (Language::language, 0, 2), // "it_IT" -> "it" modules/ProductLicense.ycp: y2milestone ("Preffered lang: %1", Language::language); modules/SlideShow.ycp: global string language = Language::language; modules/OneClickInstall.ycp: summary = YPX::SelectValue(xml,"/metapackage/group[@distversion='" + Product::name + "']/summary[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: summary = YPX::SelectValue(xml,"/metapackage/group[not(@distversion)]/summary[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: description = YPX::SelectValue(xml,"/metapackage/group[@distversion='" + Product::name + "']/description[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: description = YPX::SelectValue(xml,"/metapackage/group[not(@distversion)]/description[@lang='" + Language::language + "']"); modules/OneClickInstall.ycp: string summary = YPX::SelectValue(xml,THIS_REPO_XPATH + "summary[@lang='"+ Language::language +"']"); modules/OneClickInstall.ycp: string description = YPX::SelectValue(xml,THIS_REPO_XPATH + "description[@lang='"+ Language::language +"']"); modules/OneClickInstall.ycp: string summary = YPX::SelectValue(xml,THIS_SOFTWARE_XPATH + "summary[@lang='"+ Language::language +"']"); modules/OneClickInstall.ycp: string description = YPX::SelectValue(xml,THIS_SOFTWARE_XPATH + "description[@lang='"+ Language::language +"']");

4 5

[yast-devel] Re: [opensuse-factory] Accessible installer
by Stanislav Visnovsky 07 Dec '07

07 Dec '07

Let's move to yast-devel. Dňa Wednesday 28 November 2007 04:23:55 Hans Petter Jansson ste napísal: > The GNOME team set up a wiki page for 11.0 ideas. One of the requests is > for accessibility options to be available in the YaST installer, in > particular: > > * Screen magnifier - shows a magnified version of the portion of the > screen you're pointing at. > > * Screen reader - reads the labels and input text out loud. > > * Braille output - provides tactile display of labels and input text via > a special device. > > In GNOME, we use Orca to accomplish this, together with the at-spi > infrastructure. It is a Python app. I don't know what Qt/KDE uses, but I > imagine something similar. > > So I have some questions for the YaST/installer guys: > > * What accessibility technologies are available in the installer today, > and how are they configured? AFAIK, we have support for visually impaired people: - linuxrc can be run in linemode to allow screen readers - yast2 ncurses interface has high contrast color scheme available - there is support for braille peripherials > > * If we're missing accessibility functionality, how feasible would it be > to implement it for 11.0? Depends on the technology. One constraint I see right away is the size of of inst-sys, we would need to do some magic there to keep it reasonably sized. First, we would need to know exactly what we want to support. The 3 points above? Stano > > * Given that the installer is a Qt app, what technologies could we use? > > Also see > > http://en.opensuse.org/GNOME/Ideas/11.0#Accessibility -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 8

[yast-devel] Re: [opensuse-factory] Help Wanted: Move YaST tutorials from forgeftp.novell.com to openSUSE WIKI
by Lukas Ocilka 30 Nov '07

30 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdd wrote: > jdd wrote: >> Lukas Ocilka wrote: >> >>> I don't think there need to be a tutorial about "How to use YaST" :))) >> >> you think badly. > > please don't worry. I just jumped a little too fast on the keyboard and, > reading my mail, I find it too (much too) harsh. > > I appreciate greatly your work. I only think you underestimate the need > of documentation Easy :) It's true that several YaST modules would need help from our users. Yes, we are well aware of that and we are constantly pushing hard to make our modules more and more useful. Some examples: * Fully-open our development SVN (the newest YaST source code) (we accept patches) * Fully-open YaST documentation (we accept patches) * Generated documentation at http://forgeftp.novell.com * Fully-open IRC (irc.freenode.net) * Fully-open yast-devel(a)opensuse.org maililing-list However, it's also true that our view is a bit shaded by the knowledge we have. We'd appreciate if the community helped us to see what they don't understand well, why is that hard to understand, and how to improve the current state. What we need is the users' feedback, ideas, opinions, or even patches ;), ... As you certainly know, I've asked the openSUSE community what they wanted from YaST SSH Configuration module, I wanted to hear their opinion on the current implementation, labels, helps, etc. There hasn't been much feedback, but frankly, YaST SSHD is almost 'unused' YaST module ;) For the YaST documentation, there is a openSUSE manual available and also WIKI page for every single YaST module: http://en.opensuse.org/YaST/Modules Your example (YaST Printer): http://en.opensuse.org/YaST_Printer Well, tell us what you want :) Please. Thanks and Bye Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHUHlTVSqMdRCqTiwRApTUAKCLNAUGC1lZf4nUsAybKl2/0uMtWwCbBOX2 ZR5XZD1QGVkLPzEJr0bdHk8= =tswe -----END PGP SIGNATURE----- -- 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] Help Wanted: Move YaST tutorials from forgeftp.novell.com to openSUSE WIKI
by Lukas Ocilka 30 Nov '07

30 Nov '07

Hi, I've added a new idea to idea.opensuse.org | Move YaST tutorials from forgeftp.novell.com to openSUSE WIKI | http://idea.opensuse.org/content/ideas/move-yast-tutorials-from-forgeftp.no… We are currently working on implementing features and that's why the documentation is a bit loosing at the end of the queue. On the other hand, moving those YaST tutorials can: * Help you to gain a respect from openSUSE community as well as from YaST developers :) ;) * Help you to understand YaST a lot more Additionally, this is not only about moving some texts somewhere else, you are expected to bring new ideas, new tutorials, you can realize your dreams :))) * * * * * More about idea.opensuse.org: It's a web/page for sharing ideas how to improve (openSUSE) Linux and also implementing those ideas. Maybe you are good designer but can't write in any programming language. Maybe you can just write in Perl or C++ and you are really good at it :) ... idea.opensuse.org is the best way to go! File an idea there or pick already filed one. * * * * * Thanks in advance Bye Lukas PS: YaST developers and their (development-related) help can be found also on IRC at irc.freenode.net, channel #yast -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

1 0

[yast-devel] symbols in builtins
by Duncan Mac-Vicar Prett 30 Nov '07

30 Nov '07

Hi y2hackers For a normal namespace I can do: for (unsigned int i=0; i < ns->symbolCount(); ++i) { SymbolEntryPtr s = ns->symbolEntry(i); Yes, I can also access the symbol table, which is the most useless structure as you can't iterate it and everything useful is private and everything useless is public ;-) But that iteration is enough to know the name of the symbols the namespace offers and their type (variable, function, etc). However, for a builtin., extern StaticDeclaration static_declarations; declaration_t *bi_dt = static_declarations.findDeclaration (qualified_name); and then create the call using the declaration YEBuiltin *bi_call = new YEBuiltin (bi_dt); IIRC from the declaration, I can get the symbol table, but as I said it is like getting nothing. Is there a way to get the symbol count and access every symbol somehow? Cheers! Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 1

[yast-devel] Re: [opensuse-factory] YaST Extension: Progress with Icons
by Lukas Ocilka 29 Nov '07

29 Nov '07

Will Stephenson napsal(a): > On Thursday 29 November 2007, Lukas Ocilka said: >> PS: It's currently implemented by replacing images with another ones but >> it would be better if there was a native Qt/GTK support for making >> images gray-scaled (initial state) and then make them colored again >> (active). Would it be possible? Thanks. > > Yes, in Qt4 see > QPixmap QIcon::pixmap ( const QSize & size, Mode mode = Normal, State state = > Off ) const > > in Qt3 it's in QIconSet. > > Will Great! :) Would be somebody so kind and implement such option to yast2-qt for me :)? The YaST Qt SVN is here: http://svn.opensuse.org/svn/yast/trunk/qt/ Thanks in advance Lukas

2 1

[yast-devel] YaST Extension: Progress with Icons
by Lukas Ocilka 29 Nov '07

29 Nov '07

Hi, I've just implemented a new feature of the YaST 'Progress' module: | Icons shown during the progress run | I hope you find it useful and that we get more icons to the UI to make it brighter, cooler, and ... ;) See this article with screen-shots: http://en.opensuse.org/YaST/Development/Progress_With_Icons (This feature is available in yast2-2.16.16 and later) Bye Lukas PS: It's currently implemented by replacing images with another ones but it would be better if there was a native Qt/GTK support for making images gray-scaled (initial state) and then make them colored again (active). Would it be possible? Thanks. -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

1 0