From: Martin B. / b. <br...@bs...> - 2012-08-13 22:08:34
|
Hi team An outstanding effort from the developers has finally resulted in a pcmanfm release. The changelog for this beast is massive! See http://blog.lxde.org/?p=939 After some fixing I count to 70 commits for pcmanfm, for libfm the number totals at 256! And the best part? 1.0.1 is already in the tree, there will be a announcement about string freeze next week - if you have changes you want to slip in do it now! The release will happen first half of September (can not remember date now) and it wouldn't surprise me if another release pops up before the end of the year. * c65ba57 - Implemented multi-monitor support. (22 hours ago) anyone interested in that? =) LStranger++ Files linked in blog as usual. <http://sourceforge.net/projects/pcmanfm/files/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.0.tar.gz/download> <http://sourceforge.net/projects/pcmanfm/files/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/libfm%20%28required%20by%20PCManFM%29/libfm-1.0.tar.gz/download> -- /brother http://martin.bagge.nu Bruce Schneier factors integers in constant time. |
From: Julien L. <gi...@ub...> - 2012-08-14 20:57:30
|
Le 08/14/2012 12:08 AM, Martin Bagge / brother a écrit : > An outstanding effort from the developers has finally resulted in a > pcmanfm release. Happy to see a stable release out. Thanks ! :-) 1.0 was already uploaded to the Lubuntu Quantal (next 12.10 version). > And the best part? 1.0.1 is already in the tree, there will be a > announcement about string freeze next week - if you have changes you want > to slip in do it now! The release will happen first half of September (can > not remember date now) and it wouldn't surprise me if another release pops > up before the end of the year. Ubuntu is planning a feature freeze on 23rd August. Is more features are expected after this date for 1.0.1 ? Just to know which version we can ship in Lubuntu 12.10 :-) Regards, Julien Lavergne |
From: Martin B. / b. <br...@bs...> - 2012-08-14 21:42:07
|
On Tue, 14 Aug 2012, Julien Lavergne wrote: > Ubuntu is planning a feature freeze on 23rd August. Is more features are > expected after this date for 1.0.1 ? Just to know which version we can > ship in Lubuntu 12.10 :-) We will not push 1.0.1 beofre 23rd, I am pretty sure about that. I think there were some bugs reported for 1.0 already but I am not sure if those are serious, LStranger? If they are I think we can consider to push a earlier 1.0.1, the multi monitor support is in 1.0.1 and I guess that is a feature sought after at least =) just looking at the pcmanfm repo we have these changes already: * c4e5298 - Fix: cur_desktop was set to 0 always on startup. * d5cbf01 - Added 'Fullscreen' toggle into main menu. * 4cb6570 - Fixed shortcut creation when path contains spaces. * 18aab7b - Added missing config.h inclusions. * 6f316e3 - Fixed invalid detection of fm_default_dnd_dest_targets. * f04f910 - Revert "Added configurable timeout for non-immediate config saving." * 3b53a34 - Added configurable timeout for non-immediate config saving. * 1bba6c9 - Set version to 1.0.1~beta. * 012b296 - Fixed invalid cast in init_entry(). * 98666c0 - Fixed pref.glade that has been made invalid by glade. * cdcefd9 - Fixed invalid callback on_notebook_switch_page(). * 6e23f80 - Updated DnD to latest changes in libfm API. * 244f9d2 - Fixed compatibility with GLib < 2.26. * 3310f26 - Updated NEWS file. * b53b7b3 - Implemented toggling fullscreen by 'F11'. * 8b85c2d - Fixed usage of SI units (closes #2964811). * a0ac0f2 - Added config option for usage of SI units (closes #2964811). * 3b5a3d9 - Fix for #3138596: Does not remeber window dimension after reboot * a56a9de - Fix for #3411306: Open a folder on the wrong desktop. * c65ba57 - Implemented multi-monitor support. the list for libfm is like double or tripple that in number of commits... yes, LStranger is that amazing! =) him and the powers of git branches... -- /brother http://martin.bagge.nu There are no such thing as Carmichael numbers, only primes that Bruce Schneier has beaten factors into. |
From: Andrej N. G. <an...@re...> - 2012-08-14 22:34:30
|
Hello! Julien Lavergne has written on Tuesday, 14 August, at 22:57: >Le 08/14/2012 12:08 AM, Martin Bagge / brother a écrit : >> An outstanding effort from the developers has finally resulted in a >> pcmanfm release. >Happy to see a stable release out. Thanks ! :-) 1.0 was already uploaded >to the Lubuntu Quantal (next 12.10 version). Hey, you still don't counted any of those changes I've published and told you. That will give the users problems when they upgrade from older ubuntu versions. Do you know users don't always do fresh installs? ;-) And I believe there is no sense to include libfm-demo into any of packages as main purpose of that binary is for developers to test all features in working tree before install. And name 'libfm-gtk-bin' of the package will give users completely wrong impression about purpose of that package because both libfm-pref-apps and libfm-demo are general purpose applications that use gtk and bit of libfm. Probably there is a reason to rename libfm-pref-apps into pref-apps-chooser or something alike to give you idea what I mean. ;-) Don't know how to tell you all this the way you can hear me. ;-) >> And the best part? 1.0.1 is already in the tree, there will be a >> announcement about string freeze next week - if you have changes you want >> to slip in do it now! The release will happen first half of September (can >> not remember date now) and it wouldn't surprise me if another release pops >> up before the end of the year. >Ubuntu is planning a feature freeze on 23rd August. Is more features are >expected after this date for 1.0.1 ? Just to know which version we can >ship in Lubuntu 12.10 :-) I believe 1.0.1 will get feature freeze before that date so you can probably plan to include 1.0.1 into quantal. With best wishes. Andriy. |
From: Julien L. <gi...@ub...> - 2012-08-15 10:11:16
|
Le 08/15/2012 12:34 AM, Andrej N. Gritsenko a écrit : > I believe 1.0.1 will get feature freeze before that date so you can > probably plan to include 1.0.1 into quantal. Ok, so I'll start to test current git version. But, well, I'm currently happy with the features of 1.0 :-) The only feature I really miss is a way to have a different sorting for specific folders. Currently, you can only sort files in 1 way for all the folders. It's annoying to switch the sorting each time I go to my download folder to sort it by "last modified", when all my others folders should be sorted "by name" :-) Otherwise, it's already very good for day-to-day usage. Regards, Julien Lavergne |
From: PCMan <pcm...@gm...> - 2012-08-15 10:37:15
|
On Wed, Aug 15, 2012 at 6:11 PM, Julien Lavergne <gi...@ub...> wrote: > Le 08/15/2012 12:34 AM, Andrej N. Gritsenko a écrit : >> I believe 1.0.1 will get feature freeze before that date so you can >> probably plan to include 1.0.1 into quantal. > Ok, so I'll start to test current git version. > > But, well, I'm currently happy with the features of 1.0 :-) The only > feature I really miss is a way to have a different sorting for specific > folders. Currently, you can only sort files in 1 way for all the > folders. It's annoying to switch the sorting each time I go to my > download folder to sort it by "last modified", when all my others > folders should be sorted "by name" :-) Otherwise, it's already very good > for day-to-day usage. > > Regards, > Julien Lavergne > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Pcmanfm-develop mailing list > Pcm...@li... > https://lists.sourceforge.net/lists/listinfo/pcmanfm-develop Any suggestions on per-folder settings? I planned to do this long time ago and even study the source code of thunar and decided to use libtdb to store the per-folder config. While it's not difficult to implement per-folder settings, it's difficult to get it properly done in the GUI. How can a user specified that he or she want to use per-folder settings for a folder, and use default settings for others? Where should we put the options and how to avoid confusion? I think about this for months and did not find a solution yet. Besides, if a folder is deleted outside the file manager, the settings will remain there and waste the disk space. The old KDE way is to put the per-folder config file in a hidden file and put that file in the folder. This works for some folders, but not for those read-only ones. Besides, it's annoying to have hidden files in my folder other than home dir. The ubiquitus "thumbs.db" file in Windows is a pretty good example of this annoyance. I want to avoid this for pcmanfm. So, brain storming is needed. |
From: Julien L. <gi...@ub...> - 2012-08-15 12:24:44
|
Le 08/15/2012 12:37 PM, PCMan a écrit : > Any suggestions on per-folder settings? > I planned to do this long time ago and even study the source code of > thunar and decided to use libtdb to store the per-folder config. > While it's not difficult to implement per-folder settings, it's > difficult to get it properly done in the GUI. How can a user specified > that he or she want to use per-folder settings for a folder, and use > default settings for others? Where should we put the options and how > to avoid confusion? I think about this for months and did not find a > solution yet. If I take my use-case for example, you can have the global settings available in the menu bar ("View"), and use the context menu when you do a right click inside a folder to apply custom settings. It may also have a button to clear custom settings also on the context menu. Changing the string to specify that it will change the settings only for this folder should avoid confusion. > Besides, if a folder is deleted outside the file manager, the settings > will remain there and waste the disk space. > The old KDE way is to put the per-folder config file in a hidden file > and put that file in the folder. This works for some folders, but not > for those read-only ones. > Besides, it's annoying to have hidden files in my folder other than home dir. > The ubiquitus "thumbs.db" file in Windows is a pretty good example of > this annoyance. > I want to avoid this for pcmanfm. Yes please, don't do that :-) Regards, Julien Lavergne |
From: Geoffrey De B. <com...@zo...> - 2012-08-15 14:45:23
|
> Le 08/15/2012 12:37 PM, PCMan a écrit : > > Any suggestions on per-folder settings? > > I planned to do this long time ago and even study the source code of > > thunar and decided to use libtdb to store the per-folder config. > > While it's not difficult to implement per-folder settings, it's > > difficult to get it properly done in the GUI. How can a user specified > > that he or she want to use per-folder settings for a folder, and use > > default settings for others? Where should we put the options and how > > to avoid confusion? I think about this for months and did not find a > > solution yet. > If I take my use-case for example, you can have the global settings > available in the menu bar ("View"), and use the context menu when you do > a right click inside a folder to apply custom settings. It may also have > a button to clear custom settings also on the context menu. Changing the > string to specify that it will change the settings only for this folder > should avoid confusion. > > > Besides, if a folder is deleted outside the file manager, the settings > > will remain there and waste the disk space. > > The old KDE way is to put the per-folder config file in a hidden file > > and put that file in the folder. This works for some folders, but not > > for those read-only ones. > > Besides, it's annoying to have hidden files in my folder other than home dir. > > The ubiquitus "thumbs.db" file in Windows is a pretty good example of > > this annoyance. > > I want to avoid this for pcmanfm. > Yes please, don't do that :-) > > Regards, > Julien Lavergne > Maybe it's possible to make a database which is stored in a subdirectory of ~ where the settings are stored in? And a kind of "updater" to remove non-existant folders from the database? Just an idea. Kind regards, Geoffrey |
From: PCMan <pcm...@gm...> - 2012-08-15 16:28:01
|
On Thu, Aug 16, 2012 at 12:05 AM, Ikem Krueger <ike...@gm...> wrote: >> 2012/8/15 PCMan <pcm...@gm...>: > >> The old KDE way is to put the per-folder config file in a hidden file > >> I want to avoid this for pcmanfm. > > I think I found a better place to store them: > > Extended file attributes: > > http://en.wikipedia.org/wiki/Extended_file_attributes#Linux > http://www.freedesktop.org/wiki/CommonExtendedAttributes No, it's not. I considered the possibility to use this long time ago. 1. It's only supported by a limited number of filesystems. 2. It does not work for non-local filesystems, such as smb, sftp, ... 3. It does not work for read-only folders. Though sounds atracting, it cannot be implemented with xattr. A possible way, however, is to store the info in xattr when it's supported, and put it in a db if the filesystem does not support it, but this makes things very complicated. |
From: Andrej N. G. <an...@re...> - 2012-08-18 21:03:07
|
Hello! Julien Lavergne has written on Wednesday, 15 August, at 14:24: >Le 08/15/2012 12:37 PM, PCMan a écrit : >> Any suggestions on per-folder settings? >> I planned to do this long time ago and even study the source code of >> thunar and decided to use libtdb to store the per-folder config. >> While it's not difficult to implement per-folder settings, it's >> difficult to get it properly done in the GUI. How can a user specified >> that he or she want to use per-folder settings for a folder, and use >> default settings for others? Where should we put the options and how >> to avoid confusion? I think about this for months and did not find a >> solution yet. >If I take my use-case for example, you can have the global settings >available in the menu bar ("View"), and use the context menu when you do >a right click inside a folder to apply custom settings. It may also have >a button to clear custom settings also on the context menu. Changing the >string to specify that it will change the settings only for this folder >should avoid confusion. I've already prepared an option in folder context menu but it's hidden for now and no handler implemented yet so setting exclusive sorting for folder will be easy for user - just check the option and it will be remembered. So current behavior is still preserved but may be extended. With best wishes. Andriy. |
From: Julien L. <gi...@ub...> - 2012-08-20 19:27:19
|
Le 08/18/2012 11:02 PM, Andrej N. Gritsenko a écrit : > I've already prepared an option in folder context menu but it's > hidden for now and no handler implemented yet so setting exclusive > sorting for folder will be easy for user - just check the option and it > will be remembered. So current behavior is still preserved but may be > extended. Sounds interesting :-) Let us know when it can be tested :-) Regards, Julien Lavergne |
From: Andrej N. G. <an...@re...> - 2012-08-20 22:23:16
|
Hello! Julien Lavergne has written on Monday, 20 August, at 21:27: >Le 08/18/2012 11:02 PM, Andrej N. Gritsenko a écrit : >> I've already prepared an option in folder context menu but it's >> hidden for now and no handler implemented yet so setting exclusive >> sorting for folder will be easy for user - just check the option and it >> will be remembered. So current behavior is still preserved but may be >> extended. >Sounds interesting :-) Let us know when it can be tested :-) It still should be decided where and how to save it before even start to implement that. Unused hidden option still is nothing. :) And BTW I've experienced a SIGSEGV in pcmanfm on fresh test install of Lubuntu 12.10, I've fixed it in 1.0.1. May be it should be backported to 1.0 package too? See commit e0854cdbeb11e4fc2ad4cdd537913c818179688d. The most unpleasing thing is the bug wasn't ended in SIGSEGV with older glibc+glib so left unnoticed until now. I also got into some crash with 1.0.1 on new gtk but fortunately 1.0.1 isn't released yet so there is a time to fix it. Andriy. |