Tag Archives: LXDE

LXNM current status and the plan in the future

Next generation of LXNM (Lightweight Network Manager) is still under development right now, You guys can see the prototype which was implemented in SVN already. In the future, LXNM will provide some programs includes lxnm daemon, utility which is a command line program to make control of all kind of networking devices be unified into only one utility, a LXPanel plugin and a standalone applet for running without LXPanel.

So the project will has three parts to be maintained:
1. lxnm (LXNM Daemon and command line utility – lxnetctl)
2. lxpanel-netstat (LXPanel plugin)
3. lxnm-applet (standalone applet)

For the current version in SVN, lxnm can be working now, we can using lxnetctl utility to connect to lxnm daemon to control our networking devices and get informations include ethernet and wireless interface.

BTW, I am now working on lxnm-applet to implement a graphical LXNM client to display and control network devices.

Besides, in the future, LXNM will provide a library to make easy to write a new LXNM client(eg, lxnm-applet) for developer.

LXDE core member Chris Wickert for Fedora Engeneering Steering Committee

Please support LXDE and vote for our core member Chris Wickert in the elections of the Fedora Engeneering Steering Committee.

  • Christoph is the maintainer of Xfce and LXDE in Fedora. A vote for Chris is a vote for lightweight desktops in Fedora.
  • His goals are to make Fedora more lightweight and less ressource hungry as well as keeping depencies low.

chriswickert-fedora-lxde

To vote for Chris you need to have a  (1) Fedora Account and (2) be accepted in a group, for example join Fedora Ambassadors. Voting is possible until June 22, 2009.

Chris is the most active distro package maintainer of LXDE in Fedora. His engagements is a great success for both Fedora and LXDE as the large interest at Chemnitzer Linuxtage and other events have shown recently.

A quote from Chris Wickert:

(I want to) … improve packaging quality and enforce higher standards for better cross desktop interoperability. Try to reduce the dependency bloat to make sure Fedora does not become too fat, so it still can be used on older or smaller hardware like netbooks or the OLPC without too much pain.

Nominations followed a predefined structure, where people could ask questions and get answers. The answers of Chris here. There was also an official IRC meet up for candidates with the logs also available.

Please vote for Chris on this page: https://admin.fedoraproject.org/voting/about/fescof12

Links

* Blog of Chris Wickert http://www.christoph-wickert.de/blog/
* Join Fedora https://admin.fedoraproject.org/accounts
* https://fedoraproject.org/wiki/Elections/Questionnaire
* http://www.leemhuis.info/files/fedora/answers.txt
* http://www.leemhuis.info/files/fedora/answers-table.ods
* https://fedoraproject.org/wiki/Meetings:Town_Hall_FESCo_2009-06-03_1400

Next generation PCManFM is now under development!

Everybody loves screenshots!
This is the little demo program included in libfm demonstrating the functionality of libfm – the core of next generation PCManFM.

libfm-demo

Due to some limitations and various hard-to-fix problems in the original PCManFM, a new project is started to work on a fresh rewrite of PCManFM. Now I’ve created a project named libfm. It’s a gio-based library used to develop file manager-like programs.

http://sourceforge.net/projects/libfm

This will be the core of next generation PCManFM. Currently the work that has been done is in branches.  It contains a simple demo program named libfm-demo. Most of the menu items in this demo program are not working.

Currently it can only listed the files on your disk. No other operations are avaiable since they haven’t been written yet. I’ll work hard to finish it and hope the first really usable release can be made before 2010.  The project is in its very early stage, but you can see the progress here.

http://cia.vc/stats/project/libfm

After finished, the lib will be separated into two parts, libfm and libfm-gtk.  The former is a generic non-gui library, and the later provides useful file manager-related widgets.

The roadmap of PCManFM is updated, too. Those are the tasks to finish.

http://wiki.lxde.org/en/PCManFM_Roadmap

If someone is willing to help, that’ll be appreciated. Help is wanted!!

LXDE start pages in Portuguese

The LXDE.org start pages are now available in Portuguese thanks to Henrique P. Machado (zehrique) from Brazil who has translated the content. The set up of the language was done together with Mwei from Taiwan. We welcome contributors who are interested in having the LXDE start pages in their language. Please contact us through the mailing list of the translation project.

lxde.org-lightweight-x11-desktop-environment-portugues

The Portuguese Introduction of LXDE

O “Lightweight X11 Desktop Environment”, é um ambiente de área de trabalho extremamente rápido, ágil e poupador de energia. Ele é mantido por uma comunidade internacional de desenvolvedores e vem com uma bonita interface com o usuário, suporte a múltiplos idiomas, atalhos de teclado padrões e características adicionais, como um gerenciador de arquivos com navegação em abas. O LXDE exige menos da CPU e consome menos memória RAM. Ele é desenhado especialmente para computadores em nuvem com especificações de hardware limitadas, como netbooks, dispositivos móveis (ex.: MIDs) ou computadores antigos. O LXDE pode ser instalado em distribuições como Ubuntu ou Debian. Ele provê uma rápida interação com o desktop, conectando-se facilmente com aplicativos na nuvem. O LXDE suporta uma gama enorme de programas, que podem ser instalados localmente com os sistemas Linux. O código-fonte do LXDE está licenciado parcialmente sob os termos da Licença Pública Geral (GPL) e parcialmente sob a LGPL.

Join the Translation Project

Please join the translation project, subscribe to the mailing list and add your name into our wiki page for the Translation project.

Links

* Translation Project http://wiki.lxde.org/en/Category:Translations

* Translation Mailing List http://mailinglist.lxde.org/cgi-bin/mailman/listinfo/translation

* LXDE Online Translation of components http://pootle.lxde.bsnet.se

xkb: New Applet for LXPanel

PCMan has added a new branch named lxpanel-xkb in the LXDE Repository.

svn co https://lxde.svn.sourceforge.net/svnroot/lxde/branches/lxpanel-xkb

It’s a new applet for lxpanel which will be a keyboard layout switcher. The original one in lxpanel is broken, and will be removed. The new one will be based on libxlavier, a good library handling xkb. However, we’re from Taiwan, and we don’t know how keyboard layouts work. So help is needed. If you’re a developer living in Europe or some other places requiring switching between different keyboard layouts, please help. (PCMan)

If you are interested in the development of LXDE, please also join our developers mailing list.

Links

* http://wiki.lxde.org/en/LXPanel

* https://lists.sourceforge.net/lists/listinfo/lxde-list

If you don’t like to be forced to use gnome standards, please join xdg mailing list.

The current standard/specifications followed by most of the major UNIX desktop enviromnents, such as Gnome, KDE, XFCE, LXDE, and ROX, is called freedesktop.org.  See http://www.freedesktop.org/ for detail.

Freedesktop.org is formed by a group of developers. Developers duscusses on the so called ‘xdg’ mailing list to come up with some specs which will be followed by major desktop environments. The specs developed by Freedesktop.org are not formal standards, but they are widely used in Gnome, KDE, and XFCE.

lxde-fdoFreedesktop.org standards defines the way window managers work, they way how file types are recognized, how icons are named, the way to define the main application menu, to exchange data between applications and different desktop environments, and more.

The process to form those specs, however, is quite inefficient and problematic. All discussions are held on their xdg mailing list. If someone has a proposal, he/she then writes a draft of the spec for it, and then post it to  the mailing list. Then, if you’re lucky enough, or you’re a big guy (famous Gnome or KDE developers), you’ll get attentions and some feedbacks. After lenghthy discussions, if there are no obvious objections, the draft will be added to freedesktop.org repository, and was posted on their wiki. This is roughly how the specs are formed. Nevertheless, if there is no one implement your spec, your spec soon became useless. That means, either Gnome or KDE should support your proposal, otherwise no one will use it. How can something be called ‘standard’ when nobody is following it?

Later, if someone has some good ideas regarding to improving the spec, he/she can post his/her proposal in the mailing list with a patch, and if there is no objection, the patch *might* be applied to the spec. However, once the original author/maintainer of that spec doesn’t like your idea, your proposal will never be accepted. Or even worse, your messages got omitted by the original author/maintainer of existing specs, then there is no way to improve anything in existing specs. This is a real problem in freedesktop.org.

Besides, another big issue here is, most of the specs/standards are advocated by Gnome or KDE developers, and they don’t even consider the needs of other desktop environments. The so-called cross-desktop standards are actually well-implemented in Gnome and KDE only. XFCE tried hard to follow all those standards, but never get everything work flawlessly. LXDE tried to follow those specs, too, but found that many of the specs are very complicated and inefficient, which can slow down our desktops and add bloatness. Nowadays they are trying to add more things, and get modern desktops more and more complicated. It’s nearly impossible to keep lightweight if you want to follow ‘all’ the standards developed by Gnome and KDE. So that’s why we only supports the parts we need.

Recent changes in freedesktop.org, like PolicyKit and ConsoleKit, are mainly developed and implemented by Gnome-related developers. Then the KDE guys are forced to follow them. They even drop their well-designed and high performance IPC mechanism, DCOP, and adopt dbus, which is mainly advocated by Gnome developers. Some people even suggested that KDE should replace their own VFS with GIO/GVFS developed by Gnome. Some new technologies are developed by Gnome first, and then they wrote freedesktop.org specs for them. Later, those things are copied to KDE and they soon have their KDE equivalence. Unfortunately, all other desktop environments are forced to follow those standards whether they really need it or not, to keep the compatability with those two major desktop environments.

Why should we always be forced to follow all those things we don’t like or don’t even need? If we don’t follow them, we lost compatibility with many existing Gnome/GTK+ and KDE programs. In addition, they modify the specs frequently, and always break backward compatibility. So our precious time are wasted on re-implement everything in their new specs and try to fix all broken compatibility left by them.  It’s enough!

Sometimes things developed by the two major DEs are quite awesome and useful. However sometimes those specs just don’t suitable for other DEs and they didn’t consider the needs of users of DEs other than Gnome and KDE.

So, every enthusiastic developers/users of lightweight desktop environments, please join their xdg mailinst list and join their discussions and let them listen to your voice. If you don’t want to be forced to use things developed by Gnome and KDE, please let them hear your voice in the mailing list. Since they are now moving gnome libs into GTK+, like it or not, all gtk+ applications will be affected. Desktop environments other than Gnome and KDE might have some special needs and goals and those Gnome standards might not suitable for us sometimes. So we need to let them hear our voice and we should be part of the decision making.

So, please, join the xdg mailing list and get involved if you can.

Subscribe to xdg mailing list at http://lists.freedesktop.org/mailman/listinfo/xdg .

PCManFM: OpenSolaris distribution Milax with LXDE component

The first LXDE component has been included in an OpenSolaris distribution. Milax includes PCMan File Manager in its new release. The LXDE/OpenSolaris project was started last year. Alfred Peng from China is responsible for porting LXDE components to OpenSolaris.

Milax OpenSolaris with LXDE components

Links:

* http://www.milax.org/?p=218

* PCManFM http://wiki.lxde.org/en/PCManFM

* http://opensolaris.org/os/community/desktop/communities/lxde/

* http://wiki.lxde.org/en/OpenSolaris

Nominate LXDE for the Community Choice Awards 2009

cca_nominatePlease nominate LXDE for the Community Choice Awards 2009 till May 29, 2009.

LXDE was started already in 2005 in Taiwan and has spread all over the world. During the last year the project made big advances. New components have been added and older ones were updated. We have formed a viable translation project with people translating components from Peru to Egypt to Japan to Germany and all around the globe. LXDE is now included in many Linux distros, was ported to Google Android, has been shown to work on BSD, and was established as a Desktop Project for OpenSolaris.

During my recent travel to China I discovered that many of the small Chinese hardware producers customize LXDE and use it on their devices. LXDE offers new business opportunities for these producers. I have received many emails of people using LXDE like in whole universities in Brazil.

Please tell us your story how you use LXDE or participate in the project and please show your support for LXDE and the growing community by nominating the project for the community choice awards 2009. The LXDE project is still a project of a small community, but looking to who is participating, we already achieved to form a truly international project, which inspires me to continue supporting the project and freely licensed Open Source projects in general.

The message of LXDE: International Free and Open Source development across cultures and regions works! Faster, more lightweight and energy efficient systems are possible!

There are many projects that deserve to get this awards. I certainly believe LXDE should be one of them. I nominated LXDE for:

  • Best Project
  • Best Commercial Open Source Project
  • Most Likely to Change The Way You do Everything

Please join us. Thank you for your support!

Important Dates

  • May 6 – Nominations open
  • May 29 – Nominations close
  • June 22 – Finalists announced, voting opens
  • July 20 – Voting closes
  • July 23 – Winners are announced at OSCON
Links

Improving the translations workflow with Transifex

Roughly about a month ago Martin Bagge mentioned that we were researching the possibility of using Transifex as a translation platform for all of the LXDE components. That is not to say that our Pootle server won’t be around, but we felt that our translators could benefit from a few handy features that Transifex has to offer.

So what exactly is Transifex you may ask? I guess the best way to describe it is as a bridge between source code that needs to be localized and people who know how to translate it. But that was a rather simple description of what this amazing tools does! I could go on and on about the cool features, but for this post I’ll try to keep it simple and go directly to the point.

For the administrators: Nothing needs to be done! That’s right, nothing! No more local user accounts, ssh keys and all of that nonsense! Put your feet up and relax!

For the translators: At first glance it may seem like there is yet another entry point for you to do your work, but bear with me for a bit. If you love how Pootle works and that does the trick for you, then nothing has changed. The same goes for those who like me have direct commit access and like to use the command line! Keep up the good work! However, if you crave for some some type of management and up to the second information about your translations, then you’re going to enjoy what Transifex has to offer!

As I mentioned before, Transifex acts like a bridge between your source code and translators. It doesn’t really matter what type of versioning control system is used to store the source code (by the way, we use subversion). All this tool needs to know is: where does the code live, who is entitled to work on translations, and if translations that are uploaded can be automatically committed upstream.

Transifex workflow
Transifex workflow

So your job as a translator will be:

  1. to create a (free) account in the Transifex server;
  2. associate yourself with the LXDE project and the specific language you want to work on;
  3. and use the web interface to reserve a file for translation. This file can then be downloaded and translated offline and then submitted back via the same interface. The translation is then validated and committed upstream into the official repository.

If you are responsible for managing one of the language teams or just want to make sure you know what is happening with the project as a whole, you can choose to be notified every time someone reserves a file for translation, writes down a comment, reviews someone’s work, or a commit takes place. Since people will have to reserve a file for translation, you can make sure that no two people work on the same file at the same time, in the end saving time, headaches and redundancy. Best of all, since your work can be committed automatically when you upload your translation, you can see in real time your progress and that of your teammates.

Reserving and submitting translations
Reserving and submitting translations

In the next few weeks we will have a LXDE project officially set up and hosted by our friends from the Transifex project and we will then make a call to arms so that those who want to use this new platform can get the proper permissions configured, but I kindly ask everyone to wait until we make another announcement here.

In the meantime, keep up the excelente work you’ve  been doing and let us know how we can make your lives easier! Comments, concerns and suggestions are more than welcome!

GPicView 0.2 beta is coming with GIF animation support!

Finally, we have yet another new release of GPicView.

http://www.gnomefiles.org/app.php/GPicView

Really glad to announce the upcoming release of gpicview 0.2.
With the help from Marty Jack and Louis Casillas, some new features are added.
* GIF animation support!!
* Save jpeg and png files with different compression ratio.
* Background color can be freely changed.
* Some bug fixes.
* UI polishing.
* New translations

So, we’re going to release gpicview 0.2 soon.
Currently a beta version 0.1.99 will be released first for testing.
If there are typos or inappropriate text on UI, feel free to bug report.

Once everything goes fine, the strings in the UI will be frozen.
Then it’s the time for translators to get all of them translated, and
we can make a 0.2 stable release.

Cheers!