So far LXNM(Network Manager of LXDE) was in prototype, LXDE team was just trying to implement a usable network utility. In the beginning, it was expected be enough to work instead of Network Manager of GNOME. But even today, most of people still uses LXDE desktop environment without LXNM due to it is so buggy and poor. Also LXNM has no more improvements in the past, it seems to die for a long time.
It is the truth that LXNM will bring back to life, LXDE team have tried to restart this project and plan on working to implement new architecture of LXNM. Here is a diagram of new structure for next version of LXNM:
In principle LXNM will keep original features and most of architecture, but for more requirements of networking device operations, it will be modified or re-designed some parts of that, For communication of Client/Server, LXNM protocol will be re-defined to support more features that something’s just like response of networking status, it means that in the future user can get more complete informations of networking in a moment, and also fixed a critical bug that netstat plugin of LXPanele cannot found out any wireless Access Point as non-root.
For easy to migrate to other platform which is other linux distribution or other Unix-like operating system, LXNM still keep script-based method to handle network device control. Considering that efficiency issue, LXNM will provide a new way to implement that direct call system call to operate network device for each operating system in C language without any scripts, this feature needs more time to be done due to it’s harder and more complicated than script-based method.
With the Google Summer of Code 2009, LXNM is restarting right now. We expect that LXNM will have a great usable version after three month in the future.
3 responses to “LXNM Will Bring Back to Life”
Why don’t simply get wicd as default?
sdsdwicd is not lightweight due to it is in python.
That’s awesome! I’ve been wanting to use LXNM for quite a while now, but it never worked correctly for me.
Any plan on when its usage can be depended on (meaning it can use pretty much any network device and connect to wireless networks)?