It is over two years ago since we released the last version of LXRandR, this version is merely a translation update but still brings some changes into the application that might be worth pointing out.
Get the file at sourceforge.net: lxrandr-0.1.2.tar.gz sha1: 5e2642c2e1f4c001ca27a8634ff621fd2fd7892a
d9f8449 replace symlink with real file
aed7ce0 debian: Add build-depends on xsltproc
c98f339 debian: Add docbook-xml build-depends on group needed build-depends for autogen.sh
b9cd35d debian: Add libtool and intltool to build-depends
2739ec8 debian: Add automake to build- depends
07b1f50 debian: convert to tiny debian/rules
b6ba51e Replace GTK_DIALOG_NO_SEPARATOR by GTK_DIALOG_MODAL to compile it with gtk3 (7 weeks ago)
3ab3230 Add an option to compile with gtk3
c0622ec Add an option to enable more warnings instead of maintainer mode
befa3a2 Add new items to .gitignore
1b2a535 Fix another == in if statement
3cef63e Fix again a while boucle “fix”
eb7dfd9 Fix compiler warning
7058962 Migrate to GtkComboBoxText
9aa07e8 Use display icon, like in desktop file.
4a7276d Add new item to .gitignore
41906c9 Remove new compiler warnings
ddb761c Add more compiler warnings when using maintainer mode.
a2938fd Fix compiler warnings
7e9ab79 Apply patch to save configuration (ID: 3107353)
5de5e73 Improve configure.in (slient rules, correct INIT)
e8e4df3 Add another item to .gitignore
4992cb7 Improve src/Makefile.am
4e8e2a5 Update po/LINGUAS<
b818486 Apply patch for GTK3 migration (ID: 3107356)
5e10bc8 Add .gitignore
284df0a Generated supported languages.
aeb4539 Add an icon to the window (patch by Jonathan Marsden)
0ec1b71 fixed wrong ‘\n’
3a6045a use intltool to generate desktop file
2835b9e make desktop file follow freedesktop specs and add German translations
8e91e3d Hopefully this can solve the problem on runs configure in infinite loop.
123fbaa remove distribution of mkinstalldirs
The long wait is over, LXShortcut 0.1.2 is the successor of LXShortcut 0.1.1 released in July 2009. By no surprise the vast majority of changes since then are translation related, omitting these and merge commits the git log looks like below.
Get the file at sourceforge.net: lxshortcut-0.1.2.tar.gz, sha1: 92e4510313b6c2225edc7dd49f6b4d889303ddc3
70a02e7 debian: update to build from source
f3c4b82 Use an option to enable more warnings instead of maintainer mode.
82bebca Add a debian directory
bf1bdf0 Fix compilation with gtk3
4ccf196 Add an option to compile with gtk3
cf08e16 Update to use directly .ui files
47111aa Move a g_free
f7f7c67 Add .gitignore
262e3cb Fix another compiler warning
ce3e372 Update LINGUAS
afdf644 Fix compiler warnings
5905acd Generate LINGUAS at build time
4df7c0d Add correct CFLAGS
709b41f Add INSTALL file
3bdafc7 Add silent rules
13894d6 Add option to enable more warnings
0fb97fc added a FIXME reminder
e2a360b minor changes
18ac425 fixed implicit declaration, added return 1 if no command line options are passed to lxshortcut
016eac0 removed exec bit
689c0d9 Confirmed previous patch solved the problem on runs configure in infinite loop, commit the same patch for lxappearance and lxshortcut. (Thanks Enrico Zini provided a armel machine to test this patch.)
9af910f remove distribution of mkinstalldirs
LXDM 0.4.0 was just released. Get the file at sourceforge.
But that is not the only thing happening in LXDE land. Next week we will do at least three releases if nothing special happens. PCManFM, libfm and LXDM.
PCManFM and libfm has been in development with no updates since last October and the much sought after feature of a directory tree has returned.
LXDM will “just” be a service release to get more translations into shape; Esperanto makes its first appearance in an LXDE component by this. Happy times. All three components are scheduled for release at the 27th of July.
The best guess by now is that more components will get releases in the coming weeks, some of them has seen no releases for years but has seem interesting features hidden in the git HEAD.
LXDM 0.4.0 had an error in the release, there has been a new release dubbed LXDM 0.4.1 to fix this issue and include the l10n updates as mentioned above.
We just uploaded a new version of LXTask, this version is mainly a memory leak fix but also corrects some other issues and adds newly translated strings.
lxtask-0.1.4.tar.gz (SHA1sum: caac0942cdc0b600dd9895fb4c62badb7723cded)
The code can now be built with experimental GTK3 support using the switch –enable-gtk3, please report issues with that or other things to the bug tracker.
Complete list of changes (excluding translation related changes):
- 2051468 – default to use gtk2
- b4cdfbf – add gtk3 build option
- 626fdf6 – fix process name only have 15 chars
- d26006f – same icon that the one in the desktop file
- a58111b – fix memory leak in task refresh
- 3022c6c – treat mem_buffered as mem_cached to make memory usage more accurate
- aed2946 – Fix garbled text (mw should be this) (Bug 2986070)
- e3568c6 – fixed compiler warnings: removed un-used variables, fixed implicit declaration of function ‘g_sprintf’
- d726731 – fixed implicit declaration of functions ‘textdomain’, ‘bind_textdomain_codeset’ and ‘bindtextdomain’
I’m here to call for a review for PCManFM as the source code in git isin quite good shape now.Many known bugs are fixed and I did much refactor to the tabbedbrowsing part and merge changes in tab-rework3 branch with master.Please help test and update translations in various distros. If things are ok, I propose a new release.
Some major changes:
- “Reload Folder” is available now in View menu.
- “Directory Tree” mode is available in side pane.
- Filesystem size is updated in a more correctly and efficient way.
- Many bugs causing crashes are fixed.
- Shows a warning icon in toolbar when running as “root”.
- Supports menu keys.
- Fixed some memory leaks.
- ~ and / to move focus to location bar
- Improve internal structure of PCManFM.
- Code cleanup.
A new release as 0.9.9 is required. Please help review and test the code in git.Thanks a lot!
Everybody loves screenshot!
Directory tree in side pane was a feature in PCManFM 0.5 series, but it’s not yet implemented in the latest rewrite. Yesterday, I finished the rewrite for directory tree and added it to PCManFM. This new feature is now availble in git repository. I also added a drop-down menu to side pane to swtich between different kind of side panes. Currently there are only “Places” and “Directory Tree”. Later I plan to add more modes.
I also reworked the tabbed browsing part yesterday. Due to the limitations of GTK+, I did some dirty hacks for it to reduce resource usage. This comes at the price of less readable source code, though. After the tab-browsing rework, I fixed an old bug causing incorrect and outdated info shown in status bar so now the info in status bar is up-to-date most of the times. Later, I’ll try to add a “Reload” button so remote filesystems without notifications on changes can be refreshed manually.
To test the latest features, grab the source code from git.
You have to install libfm first:
This is the supporting library required by PCManFM.
Then install pcmanfm. Notice that the new feature is in "tab-rework" branch, not in "master"
If you don’t know how to compile libfm/pcmanfm from source code, read this:
Now, it’s time to fix the remaining bugs in the bug tracker and keep heading for 1.0 release.
A picture is worth a thousand words.
The directory tree is not yet added to PCManFM itself. This screenshot is the demo program included in libfm. A very primitive directory tree is finished. Later I’ll add this to PCManFM.
Many people are curious about this feature since it used to be available in old PCManFM 0.5 series, but why it’s not implemented in the new series?
- We want a better one which supports asynchronous I/O and does not block the UI.
- It supports gio. So later we may add remote filesystem supports to it.
- It might run faster than the old one
- The source code is cleaner and more well-structured
- The “<Empty>” items look weird and less elegant, but detecting whether a folder contains sub folders and keeping all the nodes updated in real time requires much more resources since you have monitor all of them one by one. On Linux it’s not an issue since inotify supports monioring of tons of files. On other POSIX systems, this can potentially use up all file descriptors available to a process. So, finally I do it like this way.
Please, stay tuned. I’ll put this in PCManFM soon.
OK, it’s time to tell the world what we’re doing to the file manager Here is a status report for PCManFM.
- Several bugs are fixed, and others are not. I’m currently working on fixing them.
- Directory tree will be available from side pane again in next release. I have finished 50% of the feature and hope that I can make it in the following weeks
- Tabs now takes less space when showing filenames that are too long.
- The location bar is re-written. Now auto-completion for directory paths works more correctly.
- I have implemented a simple button-style path bar recently, but to add it to PCManFM, some changes to the UI are needed so this might not be available yet in the next release.
- Integration with lxshortcut is planned. So you can create new application shortcut on the desktop easier, but this is not yet implemented.
- Status messages are now more correct and human readable.
- Some code cleanup was done to make the source code more readable to future contributors.
- While fixing bugs of PCManFM, I found a severe bug in udisks regarding to CD-ROM polling. This bug leaves the filesystem on CD-ROM mounted even after the media has been removed via pressing physical eject button on the device. I made a patch for it, but upstream authors did not accept the patch. They came up with a new solution utilizing the latest in-kernel polling provided by Linux kernel and did some fixes themselves. So in the near future, this bug will be resolved anyways.
So these are basically what I’m doing on the file manager recently. Please help if you can. Thanks a lot.
Effective immediately we have stopped using Transifex.net for translating LXDE components. All translators and prospective translators inside the LXDE project have been informed about this move via the platform itself. We have removed the possibility to submit strings in the tool but unfortunately for people who have submitted stirngs there in spite of the earlier warnings we can not recover the strings. If you have done work and the file appears more complete in Tx than in git/pootle please contact the lxde-i18n mailinglist to get advice on how to proceed.
It’s sad to be forced down this path but as with every decision there is a rollback option. If the time changes we might consider to use Transifex.net again in the future. This is however way out of schedule by now.
Thanks everyone using Tx to do translations for LXDE – it’s been valuable and we hope you will switch to use Pootle instead (as upload service or as a online tool).
Thank you Transifex developers, we do know you a great guys doing a great deal of work but the connection between the projects just weren’t there for the time being. If you make changes that we might benefit from we love to here from you again!
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.