We’ve dropped transifex by now.
The recent weeks have been interesting in the world of online translation management as Transifex got promoted to 1.0. As we are one of the project using the hosted service at transifex.net since almost a year now it was with both joy and disappointment we read the changelog. While bringing many nice features and awesome changes it also dropped the key advantage feature and the real killer, direct integration with VCS (in our case git at sourceforge.net).
For the time being we can not guarantee that changes made in LXDE translation files at transifex.net will be integrated in the main LXDE component code. The general rule of thumb is to not use transifex.net to do updates to LXDE components until further notice because the risk of changes being in conflict it might make your changes corrupt. We still have the Pootle server running and as long as nothing changes there it is a good way of doing the translations. For a limited time period we will also accept changes via e-mail, send a message to the LXDE i18n mailinglist to get this sorted out for you.
We will try to get transifex.net going again. There is a possibility that we will fail and decide to not support it.
Either way we will state that here at the blog and in the LXDE i18n mailing list so just check back here in some days.
A way to strengthen the qualityof your software is to test it as fast as possible with the needed code. For this purpose I just launched a buildbot master and slave running Debian testing. It is not automatically run against the code yet but I will include that functionality in the future. Having a buildbot that doesn’t build is not much worth =)
For the time being one can force a build from the web interface (given the right credentials and so on. just ask…), the code is update in CEST: 01 05 08 12 16 20. I would like to have more systems running as slaves to make the testing broader. I have some ideas on how to do it but nothing firm yet. First thing is to get it to autobuild on updates to the source tree. That and making LXMusic build, there is some dependecy problem floating around.
I just merged the latest movable desktop icon support to master branch.
So now it’s available in git repository. If you’re installing from git you’ll get it.
There are still some usability issues, but it mostly works quite well.
After two years, finally we have movable desktop icons. Really thank you all for the patience.
To test the latest source code and help debug, please follow this guide:
I just did very primitive partial support for moving desktop icons.
Let’s see a screenshot.
Now the position of icons can be saved and restored, but there are sitll some bugs. As a proof of concept, however, it works already.
For the interested, the source code is in “move_icon” branch of our git repo.
So the desktop icons will become movable in version 0.9.8, finally.
Now PCManFM is much closer to a final stable release. This can become one of the best lightweight file manager ever. If you’re a programmer who is familiar with C language and GTK+ and want to help, please contact me. Help is needed! Or if you’re not coders but still want to contribute, my PayPal account is “firstname.lastname@example.org
”. (Special thanks to Mihai Militaru and Seth Smar who did donations to support the development!)
I just created a status matrix of LXDE components on our LXDE wiki. This matrix shows you the current status of every LXDE component. The content of this wiki is far from complete, but it’s just a start.
So, please take a look if you’re interested and help complete the page if possible.
In the past we used <email@example.com> to coordinate translation work for LXDE. This mailing list server, however, suffers from unexpected downtime sometimes recently and has some maintaince issues. To eliminate the maintaince load and provide more stable service, we’re moving to a new mailing list hosted on sourceforge.net after some discussions. Since all other LXDE-related mailing lists are all on sourceforge.net, it’s quite natural to do so for translations as well.
Address of the new mailing list is: <firstname.lastname@example.org.>
To subscribe or unsubscribe, please go to: https://lists.sourceforge.net/lists/listinfo/lxde-i18n
Current and potential future translators of LXDE, if you see this message, please subscibe to the new mailing list instead. We already start using the new mailing list to coordinate translation work. The traffic of the list is low and we call for translations when a new release is being planned. The lxde-i18n list is specifically used for translation and related discussions only. General development issues are discussed using the “lxde-list” mailing list.
Some new releases of LXDE components are now being planned. So let’s do it!
Since LXAppearance now supports plugins, it’s possible to add new features to it with third party plugins. Today I ported the GUI configuration tool for OpenBox obconf to LXAppearance. Now a plugin for seamless OpenBox integration is available.
A picture is worth a thousand words:
No additional dependencies are added to LXAppearance. You get this “Window Border” page and the openbox support only when the plugin is installed. In addition, the plugin won’t be loaded if openbox is not in use. Perfect!
The source code is here for the brave:
Note: Ubuntu 10.04 users cannot get this correctly compiled and linked due to a bug of Ubuntu 10.04. The bug will be fixed in Ubuntu 10.10. So don’t bug report to me if it doesn’t compile/link on Ubuntu 10.04. That’s normal.
As stated in previous posts, LXAppearance is currently being rewritten. Today, the rewrite is finished.
Now LXAppearance becomes the most feature-rich Gnome-free gtk+ theme changer.
Let’s see a screenshot:
If the gtk+ theme you use supports color schemes, such as Clearlooks, you can customize these colors in LXAppearance, just like what you can do in gnome-appearance-properties.
Later, LXAppearance2 will replace LXAppearance and move to lxappearance git repository.
Main features of LXApppearance2:
- Depends on gtk+ only. Can work completely without gnome.
- Friendly and Gnome HIG compliant user interface
- Provides real-time preview of the selected themes
- Changes icon theme
- Changes cursor theme in a almost desktop independent way.
- Supports color schemes. You can change the color used by themes if the themes support gtk color scheme.
- Able to install/remove icon and cursor themes in a user-friendly way
- Provides additional options for gtk toolbars
- Able to turn off event sound provided by libcanberra-gtk-module.
- Changes default font used by gtk+ applications
- Although this is a LXDE component, it works perfectly well outside LXDE and it has no LXDE dependencies.
To get the latest source code in development:
git clone git://lxde.git.sourceforge.net/gitroot/lxde/lxappearanceIf you’re a happy user and you want to donate, my PayPal account is email@example.com.
Please get it heavily tested and give some feedbacks. Patches is also welcomed.
While the rewrite of PCManFM/libfm is still in progress, another parts of LXDE requires more attention. So this week I did a rewrite/redesign for LXAppearance. The most notable change is the new cursor theme support. Let’s see some screenshots:
The main screen demostrating current GTK+ theme didn’t change much.
The icon theme choosing page now becomes cleaner.
Guess what? The cursor theme configuration tool with nice preview. This is the most expected feature and now it’s added.
A new option was added to change toolbar icon size. Even more, it’s now possible to turn off the annoying and disturbing GUI event sounds made by libcanberra-gtk-module with LXAppearance.
LXAppearance is the tool let you change the look and feels of gtk+ programs. However, it can work very well outside LXDE. If LXDE is detected, it uses lxde’s Xsettings daemon. Otherwise, it writes the configurations to ~/.gtkrc-2.0. So it’s fully usable outside LXDE. Among the all non-gnome dependent gtk+ theme changer, LXAppearance may become the most feature-rich one. Please stay tuned.
For those who are brave, here is the code:
I just finished direct udisks support for libfm and pcmanfm. After days of testing, it works well. So it’s now merged back t master branch and will be available in next release of libfm. Please help test it.
Nothing in pcmanfm need to be changed. You only need to update libfm and it works. Adventurous users are encouraged to try out the latest libfm in git repository.
In addition, I add a config value in libfm.conf.
Adding show_internal_volumes=1 to [config] section of
~/.config/libfm/libfm.conf can let you show system internal volumes in
side panes even when udisks asks us to hide them.
This option is available in config file, but this might not be provided in UI later since it’s a geek’s option.
Now, gvfs is not needed for volume management. Only dbus and udisks are needed and it’s quite lightweight.
However, due to known limitations of glib/gio/gvfs, the gvfs module doing volume management still gets loaded and there is no clean way to stop it being loaded. However, if later we finished our own gvfs implementation, you won’t need gnome gvfs and this will be solved.
P.S.: If you get the error message “GLib-GIO-WARNING **: Extension point gio-native-volume-monitor registered multiple times”, that means you’re using a glib with too old version. Earlier versions of glib causes this bug. It’s fixed in newer glib versions.