[yast-devel] very unimpressed by found changes
Via HTTP I just did my first Factory installation in several months. White on brown is ugly. Is there or will there be an option for an installation GUI theme more like the old, black text on light background, with visible borders, scrollers, and tabs where applicable? Red on brown (in changes to partitioning) is barely legible. Green on brown on summary screen is virtually invisible. I can tell something is there, but not what it says, and there is no popup to explain whatever is hovered. In expert partitioner, there are "checkboxes" lacking boxes. I don't like that either. Once they are all unchecked, there is nothing to indicate boxes exist, much less where they are. This particular section has always puzzled me: "visible information on storage devices" for what (installation summary/storage settings) purpose? When I open Fstab options after having selected volume label as the default mount by, why for a freshly formatted target / partition with volume label is UUID preselected instead of Volume Label? Seeing parts of the content of the fullscreen "Edit Partition /dev/sda16" spilling out from under that (apparently) borderless brown void that is the Fstab options "window" is seriously unimpressive. In detailed software selection those itty bitty things in left pane apparently representing checked boxes need to be much bigger to tell that's what they're supposed to be. Choice between no bootloader and Grub2 is very Fedora-ish, would cause all my installations to be much more complicated, since I have no need and thus no use for the overcomplicated monster (to be obsoleted in not too distant future by UEFI) that is Grub2. Since Grub remains available to select among packages, will it be possible to set it up from running the grub shell on tty2 before rebooting from the installer (I tried simply 'grub', which produces command not found from bash)? Towards the end it claimed to be installing boot manager even though Grub2 was tabooed, produced no error message. Neither did it leave a /boot/grub/menu.lst to be used as configfile from elsewhere, though it did produce a device.map. /etc/sysconfig/bootloader is too stripped to be useful. Trying to chainload it produced the invalid executable format message I'm used to seeing on installations containing no bootloader on /. I copied and edited menu.lst from 13.1 for now, and gfxboot and perl-Bootloader apparently work as always even though I had to manually configure Grub. y2logs: http://fm.no-ip.com/Tmp/SUSE/y2l-gx28b-os132-201407.tgz -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-07-12 21:30 (GMT-0400) Felix Miata composed:
y2logs: http://fm.no-ip.com/Tmp/SUSE/y2l-gx28b-os132-201407.tgz
No comments from anyone? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, 18 Jul 2014 12:41:09 -0400 Felix Miata <mrmazda@earthlink.net> wrote:
Decision of opensuse team who prepare theming for yast is to base next theme on SLE one prepared by SLE team. Yast team do not try to act as designer ( you really do not want it ;)
Opensuse theme is not done yet, I expect changes there.
I also expect that it is due to not complete theme for opensuse yast.
Question for Arvin - added to CC.
theme, see above. I think it make sense to report all such issues and assign to opensuse design team.
Few notes: - GRUB support for yast installation is planned to drop. It is just about yast, grub1 can be used as long as someone will maintain it. Code for grub1 in yast-bootloader is quite complex and we want to focus on one bootloader and do it really well, so it works for everyone and if experts need, they can use alternatives. So we give you freedom to use what you want and we expect that you give to us same freedom to decide what we develop. - GRUB2 won't be replaced by UEFI, GRUB2 support UEFI and also it supports trusted boot - grub is not available in inst-sys as it is quite size senzible place. If you need to install it, then at the end of installation go to console, chroot to /mnt and run grub from there. - it prints that it write bootloader, but if you select no bootloader it do nothing expect some initialization - perl-bootloader do not strip its GRUB1 support and currently it is not planned
y2logs: http://fm.no-ip.com/Tmp/SUSE/y2l-gx28b-os132-201407.tgz
No comments from anyone?
Summer vacations, so allow us to have some free time ;) I hope, I answer all your questions. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, Jul 25, 2014 at 10:52:26AM +0200, Josef Reidinger wrote:
As long as you have not set a label the mount method cannot be by-label. It's also unclear e.g. whether you *create* the volume before or after you have set the default mount-by method. Regards, Arvin -- Arvin Schnell, <aschnell@suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-07-25 11:13 (GMT+0200) Arvin Schnell composed:
On Fri, Jul 25, 2014 at 10:52:26AM +0200, Josef Reidinger wrote:
Question for Arvin - added to CC.
As long as you have not set a label the mount method cannot be by-label.
It's also unclear e.g. whether you *create* the volume before or after you have set the default mount-by method.
Some people have the foresight to plan in advance of installation how they want their storage configured, and have it ready to go when installation begins. I thought it perfectly clear by saying for a freshly formatted target / partition with volume label That means I did, and do, all partitioning, and filesystem creation, in advance of starting any operating system installer. I use one and only one partitioning tool for all my systems and disks. It's one never included in any Linux, Mac or Windows installer, but has binaries for DOS, Linux, Mac, OS/2 & Windows, which means there's never any partition table incompatibility among operating systems on my disks as long as no installer has done something unnecessary, unwanted and unauthorized. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, Jul 25, 2014 at 05:36:17AM -0400, Felix Miata wrote:
OK, it was unclear to me that you do not create and format the partitions with YaST. Where the mount points set by the storage proposal? In that case you can only set the default mount-by method after the proposal code has run so the volumes are not affected anymore by the default settings. I created a feature request years ago to solve this problem but so far it was not implememented. Regards, Arvin -- Arvin Schnell, <aschnell@suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-07-25 11:58 (GMT+0200) Arvin Schnell composed:
On Fri, Jul 25, 2014 at 05:36:17AM -0400, Felix Miata wrote:
I did, and do, all partitioning, and filesystem creation, in advance of starting any operating system installer...
OK, it was unclear to me that you do not create and format the partitions with YaST.
Where [sic] the mount points set by the storage proposal?
I've never ever seen YaST make a proposal from what I've prepared in advance that matches my plan. So, no, because it requires expert mode to be able to follow through with any personal plan. Make no mistake from reading my complaint. The openSUSE installer has been far and away my favorite among all I've ever used. There's only one feature it lacks found elsewhere that I really like: Mandrake/Mandriva/Mageia's cmdline option readonly=1, which provides a simple shortcut partitioning process where the only step offered is mountpoint selection from among existing partitions. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, Jul 25, 2014 at 10:52:26AM +0200, Josef Reidinger wrote:
Hi Felix, is this the color theme you see? https://openqa.opensuse.org/tests/15377/modules/installation_overview/steps/... (screenshot attached, in case the link expires) This is the theme we are using for the upcoming SLES12, designed by Ken Wimer. That means, the coders are happy not to touch it :) If you think we should adjust it to make it more legible, please file a bug and attach a screenshot, ideally enhanced with the color you find good, and assign to wimer at suse.com and cc myself.
No, the theme is complete, at least for SLE. openSUSE may decide to change it, but it should be good already. A bug report with a screenshot please? -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On 2014-07-28 18:01 (GMT+0200) Martin Vidner composed:
is this the color theme you see?
IIRC, yes. It's more than 2 weeks since I saw it, and your 1024x768 attachment makes everything too small to see any significant detail. The red on brown there is virtually invisible. The green on brown and brown on green isn't a whole lot easier to make out.
A bug report with a screenshot please?
Before I do that, please provide a pointer to the source for the current color scheme so that I may objectively quantify its brightness and contrast levels according to WCAG, and include the result when I file a bug. TIA -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Mon, Jul 28, 2014 at 12:46:16PM -0400, Felix Miata wrote:
Here: https://github.com/openSUSE/branding/blob/13.2/yast/installation.qss Actually, this theme is 3 months old now and lacking the fixes made in https://github.com/yast/yast-theme/tree/master/SLE/wizard . I will port that. But do not hold your breath, the colors are the same. It will probably help with the check box though. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On 2014-07-29 10:30 (GMT+0200) Martin Vidner composed:
Here: https://github.com/openSUSE/branding/blob/13.2/yast/installation.qss
Those can't be everything affecting colors. Neither accounts for the foreground color resembling red that appears e.g. in: http://fm.no-ip.com/SS/Suse/YaST/132/yastI-20140801-InsSet0768v.png Also I've found multiple instances of a color combination that clearly fails when checked on http://juicystudio.com/services/luminositycontrastratio.php QMenuBar::item:selected { /*# 2.84:1 Fail #*/ color: #fff; background: #28ae73;} QPushButton:default:pressed, QPushButton:pressed { /*# 1.81:1 Fail #*/ color: #2d2d2d; background-color: #175f48;} QPushButton:open { /*# 2.84:1 Fail #*/ color: #fff; background: #2d2d2d;} QPushButton QMenu::item:selected { /*# 2.84:1 Fail #*/ background-color: #28ae73; color: white;} #RepoUpgradeLabel { /*# 2.84:1 Fail #*/ color: #fff; background: #28ae73;} -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
В Mon, 28 Jul 2014 18:01:56 +0200 Martin Vidner <mvidner@suse.cz> пишет:
No, the theme is complete, at least for SLE. openSUSE may decide to change it, but it should be good already.
One thing I noticed that there is no visual feedback when button pressed or going to be pressed. I.e. default button is green, when I hover mouse over other buttons they become green but when hover over default button nothing happens. I first thought I had issues with mouse (because I once had indeed).
participants (5)
-
Andrey Borzenkov -
Arvin Schnell -
Felix Miata -
Josef Reidinger -
Martin Vidner