Fw: Re: New F15 Wallpaper and Idea for Easier defaults switching
by Martin Sourada
Oops, forgot to CC the desktop list.
Begin forwarded message:
Date: Thu, 3 Feb 2011 23:39:13 +0100
From: Martin Sourada <martin DOT sourada AT gmail DOT com>
To: Christoph Wickert <christoph DOT wickert AT googlemail DOT com>
Subject: Re: New F15 Wallpaper and Idea for Easier defaults switching
Hi Christoph,
On Thu, 03 Feb 2011 18:19:08 +0100
Christoph Wickert wrote:
>
> lxde-common and lxdm als use usr/share/backgrounds/default.png. Just
> like slim and some others. This means we still need
> usr/share/backgrounds/default.png and the desktop-backgrounds-compat
> package.
>
> I am not sure if we need
> [release-name]-backgrounds-[desktop-environment] packages. I suggest
> to
Their primary purpose is to add the wallpaper to the lists in
background choosers (plus both GNOME and KDE have their own
specifications so we need more files than just the images)
> * do all of that in desktop-backgrounds-compat, it's just a few
> symlinks
> * build the desktop specific subpackages as part of
> desktop-backgrounds rather than [release-name]-backgrounds. If
> somebody has the packages of 2 different releases installed,
> the subpackages will collide.
Actually, I have thought about that but didn't consider it too common
to install wallpapers from rawhide into stable releases. It's done in a
way that within a single release it wouldn't collide. But your idea
seems slightly better, I'd just prefer if they were subpackages of the
[release-name]-backgrounds (we could actually make the current virtual
provides into their own package so the system-backgrounds-* would
actually be packages of their own) to keep the packages needed to
update to minimum. We could probably also move
the /usr/share/backgrounds/default.png out of
desktop-backgrounds-compat to system-backgrounds-compat (I wonder who
initially came with the system-backgrounds name for the virtual
provides...).
All this would make the update consist of two packages.
It also seems a little cleaner to me to have one %if in each
[release-name]-backgrounds package than zillions of %ifs (or different
SPECs between branches) in desktop-backgrounds.
In short, e.g. for GNOME the packages generated by
[release-name]-backgrounds would be
[release-name]-backgrounds-{single,gnome} and system-backgrounds-gnome
(if on [release-name]). Of course all properly versioned to allow
smooth upgrade path between releases. But if you'd still prefer the
defaults to be handled via desktop-backgrounds-* I can go that way as
well.
What do you think?
Regards,
Martin
13 years, 2 months
New F15 Wallpaper and Idea for Easier defaults switching
by Martin Sourada
Hi all,
The default wallpaper for F15 lovelock release is being packaged right
now (I'm awaiting adding it to git right now). It is a sort of
compromise [1] between what desktop folks wanted (use default gnome
wallpaper for desktop spin for f15) and many design folks wanted
(default wallpaper on default spin should be created by ourselves).
I'll let you know again when all the packages are in rawhide so you can
change the defaults.
Now I would like to present an idea how to handle the defaults in a
more efficient way. Since I'm not an expert in handling these in all
the desktops we ship your input would be very much welcome.
Let's start with GNOME since that is what I've been using till now:
Along with the virtual system-backgrounds-gnome provides also provide
a symlink (I propose /usr/share/backgrounds/default.xml) to the
intended default and set it to by system wide defaults. This way just
updating the wallpaper packages would also update the symlink and thus
the default background. Correct me if I'm wrong or need something more.
Of course you could override the system defaults for spins if needed.
Now for XFCE which I'm using now. I noticed that if I put an image
into /usr/share/xfce4/backdrops it will appear in the backgrounds
applet, so I created new -xfce subpackage (with system-backgrounds-xfce
virtual provides) to provide the wallpapers for xfce users. For easier
defaults I propose to create default.png symlink in the same directory
which you could then set as default. That way updating the wallpaper
packages would also update the default wallpaper. I have no idea how
defaults are handled in XFCE so this might not be the correct way to do
it, so please correct me if I'm wrong.
For KDE I'm thinking about symlinking the whole (currently) Lovelock
directory with images and wallpaper description to Default directory at
the same place (of course, provided by package with
system-backgrounds-kde virtual provides). Not sure if that would be all
that's needed or whether different procedure would be desirable. So
again, correct me if I'm wrong.
For LXDE I have not the slightest idea so any suggestions how to keep
handling the defaults limited to [release-name]-backgrounds* packages
is welcomed.
Thanks,
Martin
PS: I hope I CCed the right people, if not I apologize and if you know
of a better person/interest group suited for this discussion not CCed
yet, please forward the mail to them.
PPS: And sorry for cross posting it to both desktop design-team mailing
list, but I think both groups might have something to add to the
discussion.
References:
[1] https://fedoraproject.org/wiki/File:Mockingbird-stripes-3-mo-jef.png
13 years, 2 months
GNOME 3 Test Day #1: announcement up
by Adam Williamson
Hey folks, just a quick note that I've put up the 'official'
announcement
of the first GNOME 3 Test Day:
http://www.happyassassin.net/2011/01/31/gnome-3-test-day-1-come-try-the-n...
If you can blog it (or dent it or tweet it or whatever the cool kids
are doing with the intarwebs nowadays) that would be really great -
especially if you can get it on aggregators, particularly Fedora and
GNOME Planets, and any news sites you know of.
Also huge thanks to John Palmieri, Christopher Aillon and David
Malcolm who fed me a huge set of test case ideas today at FUDCon -
I definitely have enough to make a really comprehensive set of tests
for the event. Right now the page still has the crappy initial set of
test cases, but I'll be writing up the ideas I got today and the ones
from Cosimo as test cases tonight and tomorrow, probably, and updating
the page to be way more awesome.
Of course, if you have any time on Thursday (whenever that is, in your
time zone) please come and drop by the IRC channel, and do some testing
or help out other testers or whatever you can, that would be really
helpful too. And please let me know if you have any suggestions or
corrections or ideas or anything for the event(s). thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 2 months
Status of bluetooth in Gnome3
by Jóhann B. Guðmundsson
What's the current status of Bluetooth in Gnome3
I performed Gnome 3 show and tell last Saturday and after finally
managing to pair the device Logitech diNovo Edge Wireless bluetooth
Keyboard the keyboard did not work.
It took 3 tries since the time I had to enter all those numbers and the
time the pairing timed out seem to be a bit short.
Now I'm not sure what policy you guys have for Bluetooth devices but I
hope that you dont expect that users can enter "code" on all of them for
example I have a Bluetooth GPS module that when pairing uses the default
0000 or 01234 ( I cant recall at the moment but it's one of those common
defaults ) so I would have no way on the device to entered some kind of
number to pair it together with the laptop.
We might want to add few bluetooth testcases to our test days to cover a
bit bluetooth devices ( pairing and using phones keyboard mice etc ).
JBG
13 years, 2 months
