Bastien Nocera | 25 Jun 13:36 2016

gnome-desktop for GNOME 3.22 will depend on libudev


hwdb has its own database which it compiles to binary, so that:
1) initialisation is practically free
2) lookups are also quick, as they use a binary DB
3) we don't have to maintain our own copy of the database
4) allows model lookup rather than simply vendor lookup, when the
   database contains that information

jhbuild has been updated to reflect the new dependencies. Non-Linux
OSes should revert this patch in their 3.22 releases.

libudev was already a dependency of gnome-bluetooth, which uses it to
lookup vendor names from udev/hwdb's OUI database.

desktop-devel-list mailing list
desktop-devel-list <at>
philip.chimento | 23 Jun 23:34 2016

GJS documentation browser: follow up and hosting

Hi list,

About 6 months ago I announced a documentation browser for the GJS bindings [1], which has lived at ever since the 2016 developer experience hackfest.

Unfortunately I've had to take the AWS hosting down since I found out the AWS free plan lasts 6 months, instead of 12 as I thought.

My first question is, did people find it useful enough that I should look around for alternative hosting? If so, the second question is, is there any way to host it on GNOME infrastructure?

As for other free hosting solutions, OpenShift has an attractive never-ending free plan. I looked into it 6 months ago, but they did not have a Ruby 2.2 cartridge available. If you're familiar with OpenShift and have some ideas on how to get this up and running, I'd appreciate hearing from you.

For reference, here are my instructions for setting up the app on an AWS EC2 instance running RHEL 7 [2]. Setting it up on any major Linux distribution on a VM would be very similar.

Philip C

desktop-devel-list mailing list
desktop-devel-list <at>
Milan Crha | 23 Jun 10:35 2016

Keep shipping also generated gtk-doc html/ folder?

while playing with developer documentation I noticed that the source
tarballs (eventually `make dist` result) contain also developer
documentation in generated form. These documentation html/ files are
not small, in case of the glib it makes around 10MB. The thing is that
when I configure with --enable-gtk-doc, then the shipped html/ files
are regenerated, thus it looks like a waste of space and bandwidth to
distribute them.

I do not know the history behind it, maybe I just overlooked something
and it does make sense to distribute that too. That's why I raised it

It would be interesting to know whether anyone uses the html/ files
without --enable-gtk-doc these days, but I understand it's a hard

	Thanks and bye,
Michael Catanzaro | 22 Jun 03:45 2016

GNOME 3.21.3 released

Hello all,

GNOME 3.21.3, the third snapshot of the GNOME 3.21 cycle, is now
available. You want it!

To compile GNOME 3.21.3, you can use the jhbuild [1] modulesets [2]
(which use the exact tarball versions from the official release).


The release notes that describe the changes between 3.21.2 and 3.21.3
are available. Go read them to learn what's new in this release:

core -
apps -

The GNOME 3.21.3 release is available here:

core sources -
apps sources -

(Note that graphene was dropped due to a technical snafu. It will be
returning in 3.21.4.)


This release is a snapshot of early development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate development

For more information about 3.21, the full schedule, the official
module lists and the proposed module lists, please see:

For a quick overview of the GNOME schedule, please see:

Michael Catanzaro
GNOME Release Team

devel-announce-list mailing list
devel-announce-list <at>

Emmanuel Pacaud | 21 Jun 15:41 2016

SVG rendering - Librsvg and Lasem


This is a message I intended to write for some times, but the Toronto 
hackfest notes gives me incentives to actually send it.

In these notes, there is a paragraph saying Benjamin seems not too 
happy with librsvg.

And in fact, there is this library, Lasem, I have started to work on 
some years ago, that could be considered as a librsvg replacement:

Good things about lasem:

 - It is based on gobjects
 - It has a DOM like API
 - It has a quite extensive support of the SVG 1.1 specification, 
similar to librsvg
 - It is as fast, if not faster, than librsvg
 - It uses less memory than librsvg
 - It has introspection support
 - It has gtk-doc support
 - There is a test suite, with an automatic check on a selection of 
test files
 - As a bonus, it also renders MathML (well, it started as a mathml 
renderer under gmathml name)

Bad things about lasem:

 - Text support is a joke, but librsvg does not shine here neither
 - No CSS suport
 - Almost nobody uses it
 - There is only one developper, and not very active these days (that's 
 - twice the size of code compared to lirsvg (but it has mathml 

So I would appreciate any feedback regarding lasem design and 
implementation, or any comment about the possibility of using lasem as 
a replacement of librsvg.


Release Team | 17 Jun 02:00 2016

GNOME 3.21.3 unstable tarballs due (responsible: mcatanzaro)

Hello all,

Tarballs are due on 2016-06-20 before 23:59 UTC for the GNOME 3.21.3
unstable release, which will be delivered on Wednesday. Modules which
were proposed for inclusion should try to follow the unstable schedule
so everyone can test them.  Please make sure that your tarballs will
be uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.21.3. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!

For more information about 3.21, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.21

For a quick overview of the GNOME schedule, please see:

Automatically generated email. Source at:

devel-announce-list mailing list
devel-announce-list <at>

Megh Parikh | 15 Jun 23:42 2016

Design help requested: Gamepad remapping/Settings UI


I am working on GNOME Games under a GSoC project to add support to
play Games using a Gamepad. Usually connected gamepads are not always
configured properly. We need an UI to remap the plugged-in gamepad to
a standard gamepad. I request a UI for that. I have laid out certain
goals and relevant art on the design page [0]. I have also put an
experimental design idea on that page. Please give in inputs regarding
the idea.


Megh Parikh
David Woodhouse | 10 Jun 12:47 2016

Re: Design help requested: Certificate Chooser UI.

On Fri, 2016-06-10 at 06:35 -0400, Nikos Mavrogiannopoulos wrote:
> Only a nitpick. "Choose from PKCS#11" is very cryptic for users. I don't
> expect from someone not working in security to understand what is this
> about. "Choose from smart card" is something more approachable.

Except it isn't correct either. Since 'smart card' then includes such
locations as GNOME Keyring, and the user's NSS database.

Seriously, the *good* way to do this from the UX point of view is just
to make the PKCS#11 tokens show up as locations/shortcuts in the
chooser, alongside the various directories. That's what you had in the
design study:

The only problem with this is that it's hard to expose the internals of
the GtkFileChooser to allow us to 'take over' the internal
browse_files_stack and display our own list of objects within the token
— which we need because it needs to look like the Seahorse display in
the main pane of and the 'file
browser' doesn't cut it.

And obviously we don't want to use something *other* than a
GtkFileChooser for the case where the user *is* actually choosing
files; that would be horrid too.

If we can't fix this to be like the mockup, maybe the least-bad option
is to have two separate 'places sidebars' side by side. The first isn't
really a GtkPlacesSidebar; it's a lit of all the PKCS#11 tokens PLUS
'File system'. And then when it's selected, the GtkFileChooser with its
own GtkPlacesSidebar is shown next to it. So it's...

| PIV_II             | Recent
| Gnome2 Key Storage | Home
| Gemalto            | Documents
| Entersafe          | Downloads
|                    | ...
|→File system←       |
|                    |

That is still marginally confusing — users will ask why can't they all
be in the *same* list instead of having to select 'File system' first?
But at least it isn't as bad as our current hack.

If the GtkFileChooser would just allow us to use it *without* its own
GtkPlacesSidebar, that would probably suffice...

Attachment (smime.p7s): application/x-pkcs7-signature, 7783 bytes
desktop-devel-list mailing list
desktop-devel-list <at>
Jeremy Bicha | 1 Jun 05:40 2016

GNOME Games source name

It's very confusing to have a new app whose source is named
gnome-games [1] since that name was already used not that long ago.[2]

On Debian and derivatives, gnome-games is still in active use [3] as a
metapackage for those who would like to easily install all of the
games in the gnome-apps moduleset.[4]

As far as I know, the new gnome-games has not been picked up by
distros yet, so a rename now should be minimally disruptive. Note: My
objection here's isn't to the display name of "Games" or "GNOME
Games". I believe the source package needs a different name though.

A quick look at the description field of the git repo suggests one
potential new name: gnome-games-launcher.


Megh Parikh | 30 May 21:35 2016

Demo showing usage of JSX to create the Guitar Tuner demo

Hello all,

I have made a demo which shows the usage of JSX to create the Guitar
Tuner Demo. JSX basically allows you to write sort of XML code inside
Javascript and got its fame due to the adoption of the ReactJS
framework for the web. I plan on creating something similar for GTK.
While the current project is only for Javascript, I want it

The following is the link to the project

Advantages of JSX
- Easily create UI using XML (sort of similar to GtkBuilder)
- Have code embedded within this XML (similar to templating)
- Pass around elements as if they were objects and compose them (thus
you can easily make reusable components)

Features of my demo:
- Use JSX to create the UI
- Use the latest ES6/7 syntax using Babel
- Import/export modules in the commonjs fashion using webpack
- Use packages from the nodejs ecosystem

All comments, suggestions and contributions are welcome.

P.S I am not sure if this is the correct mailing list

Megh Parikh
Sébastien Wilmet | 22 May 18:06 2016

gnome-software and external plugins


It looks like gnome-software will allow external, out-of-tree plugins:

we discussed it a little on IRC on #gedit (related to libpeas).

(A discussion on a mailing list is easier than on

I wanted to comment with my experience on gedit. gedit allows external
plugins since a long time, probably more than a decade. I'm a relatively
young contributor to gedit, interested by the gedit core codebase
(making it more re-usable), but there is a big problem: maintaining the
gedit API. We cannot refactor the code freely without breaking the

I think that Firefox is also struggling with its plugin system.

So, allowing external plugins looks appealing, and in the short term it
is probably not a problem. Problems arise later, when you don't have the
choice: either you need to maintain the API and it gets in the way, or
you break all third-party plugins.

My 2 cents,

PS: on an orthogonal matter, gnome-software doesn't use libpeas, I've
filed this bug about it:
libpeas supports in-tree and out-of-tree plugins fine.