I was browsing the xfce4-dev mailing list when I stumbled on a request for comment by Steve Dodier-Lazaro (who I
knew in the past through the #exaile IRC room) on his
article regarding the design of authorisation UIs.
The article covers a lot of ground, from current issues plaguing these UIs (in Windows UAC dialog, gksu, etc.), to
the types of operations in Wayland that are planned to require authorisation, to brainstorming ideas for moving
forward. A lot of issues are still unsolved and I suspect will be years away from being solved, but I’m glad that
people are talking about them. The article also calls for further academic research on fixing these issues.
The next version of Exaile, which was to be version 0.3.3, will be version 3.3.0. We feel that the 0.x versioning
was more confusing than actually useful or representative of the development process; in addition, the new
versioning avoids long version numbers like 0.3.2.1.
In related news, Exaile 3.3.0 is going to be released soon. The RC is already out; please help us test it and iron
out last-minute bugs.
If you’re compiling a piece of code and getting an error message saying something about PUSHL or “invalid suffix
for PUSH”, it means you’re feeding x86 assembly code to an x86_64 assembler.
Possible causes:
-
The code you’re trying to compile really does contain x86 assembly, perhaps inlined from C, but you’re targeting
x86_64.
-
Your toolchain somehow contains a mix of x86 compiler and x86_64 assembler. Try cleaning up your PATH.
If you’ve been using Exaile’s Shoutcast plugin, you would have realised that it
hasn’t been working for a while now. This is due to a
change in the SHOUTcast directory API.
However, SHOUTcast directory support is not coming back. The VLC developers
explain in detail the problems that also prevent us from
complying with SHOUTcast’s terms of service. The specific wording in the terms makes me believe that we will never
see an acceptable solution, and that makes the issue of fixing the plugin a moot point. Following what VLC and
Amarok have
done, we have removed SHOUTcast directory support from Exaile.
Note, however, that Shoutcast/Icecast streams still work as long as you know the stream URI. It’s
just the directory that is not working; for the time being, you can use the
Icecast Web-based directory for this purpose.
In the future, we would love to switch to the Icecast directory, but their documentation seems
a bit sketchy. If you would like to help with this, feel free to contact us through IRC or at the
wishlist report. There is an
Amarok script that you may be able to use as reference.
Meanwhile, I have removed the Shoutcast plugin from Exaile’s list of installed plugins. The outdated code is still
in the source tree, but it will not be installed by our makefile.
[Update: I am was working on an Icecast directory plugin. It’s literally half-working (I can
get genres but not individual stations, still figuring out why). For this plugin I’m screen-scraping the website
because the actual YP directory seems to be incomplete.]
[Update 2: I’ve stopped working on the plugin for now as I’m occupied with something. Apparently there’s a working
Icecast plugin in the bugtracker somewhere; I haven’t tested it.]
If you have a GtkFontButton, finding out whether the chosen font is monospaced is quite a complicated process. Here
is a complete walk-through.
(By the way, I will be using PyGTK’s Pango documentation because the C version is a mess.)
FontButton.get_font_name
returns the font family (a.k.a. “font name”), style, and size; for example,
“Liberation Serif Italic 14”. The first thing we need to do is pick just the family name. We do this by going
through a PangoFontDescription.
desc_str = font_button.get_font_name()
desc = pango.FontDescription(desc_str)
family_name = desc.get_family()
Next, check whether the font family describes a monospaced font. Here is where
it gets dodgy. We need an arbitrary PangoContext, which
can be obtained from a GtkWidget using Widget.get_pango_context
. We then list all available font
families and find the one with the appropriate name. Call
FontFamily.is_monospace
to finish the job.
(By the way, this is also a good place to show off Python’s
for-else construct.)
context = widget.get_pango_context()
for family in context.list_families():
if family.get_name() == family_name:
break
else:
assert False
family.is_monospace()