[kde] Can Picture Frame plasmoid set to remote URL?
Hi all, I just tried to set my Picture Frame plasmoid to Slideshow, and set an sftp:// remote url to the path. However, it told me that the folder was empty. I'm sure that there are pictures inside the url. I can also see it using dolphin or even gwenview. Just Picture Frame failed to get pictures with remote URL. Since it can play Picture of the Day, which should get picture remotely, I think that using sftp:// should work. Could anyone please tell me how to set remote folder in Picture Frame? Thanks, Franklin ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Dolphin search anomalies KDE 4.6.0
On Friday, 2012-04-06, John Woodhouse wrote: I'm trying to use Dolphin - the file manager as konq used to be Comments related to Dolphin Hmm, ok. But why not use Konqueror if you are looking for its features? Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] KDE release cycles?
On 04/05/12 13:57, Kevin Krammer wrote: On Thursday, 2012-04-05, Duncan wrote: dE . posted on Thu, 05 Apr 2012 07:23:16 +0530 as excerpted: So 'feature release' may mean (apart form including absolutely new features) - 1) Restructuring the code (better management). 2) New backend or changed backend which may increase or decrease bugs. And bug fixes mean fixing small time bugs in library or directly in the app. I'll let Kevin respond to that (tho it seems a reasonable summary to this non-dev, here), I agree. My guess is that the term feature release is used to indicate that this is not just the same thing again. From a developer's perspective it just means that restrictions on what you can do are less tight. There are still things that are not allowed, e.g. changing libraries in a way that makes them incompatible with applications, but on the application level you can do almost anything you want. but there is certainly one practical limitation of the bugfix releases as opposed to feature releases: * Strings are generally frozen during a six-month bugfix series. This is to help the various l10n (localization, basically, translation) efforts, but it DOES mean a tradeoff in terms of fixing things properly sometimes, if that would mean a UI and string change, even if the actual code fix is reasonably small and safe and would otherwise be allowed. Yes, very good observation. Sometimes an essential bug fix needs a string change, in which case the translators usually grant an exception [1]. This is actually one reason the distros tend to ship later bugfix releases instead of newer feature releases One additional thing might be that distributions themselves use a very similar development and release model so they have a better understanding what each step along the way carries with it. Early bug fix releases of a feature release are basically more like the public beta of proprietary software, i.e. the beta releases of Free Software products (and of distributions which do such things) are more like the interal or private beta. 'Early bug fix' release? I thought that bug fix releases were the minor versions like 4.8.1, or 4.8.2 etc... ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] KDE release cycles?
On Saturday, 2012-04-07, dE . wrote: On 04/05/12 13:57, Kevin Krammer wrote: On Thursday, 2012-04-05, Duncan wrote: dE . posted on Thu, 05 Apr 2012 07:23:16 +0530 as excerpted: So 'feature release' may mean (apart form including absolutely new features) - 1) Restructuring the code (better management). 2) New backend or changed backend which may increase or decrease bugs. And bug fixes mean fixing small time bugs in library or directly in the app. I'll let Kevin respond to that (tho it seems a reasonable summary to this non-dev, here), I agree. My guess is that the term feature release is used to indicate that this is not just the same thing again. From a developer's perspective it just means that restrictions on what you can do are less tight. There are still things that are not allowed, e.g. changing libraries in a way that makes them incompatible with applications, but on the application level you can do almost anything you want. but there is certainly one practical limitation of the bugfix releases as opposed to feature releases: * Strings are generally frozen during a six-month bugfix series. This is to help the various l10n (localization, basically, translation) efforts, but it DOES mean a tradeoff in terms of fixing things properly sometimes, if that would mean a UI and string change, even if the actual code fix is reasonably small and safe and would otherwise be allowed. Yes, very good observation. Sometimes an essential bug fix needs a string change, in which case the translators usually grant an exception [1]. This is actually one reason the distros tend to ship later bugfix releases instead of newer feature releases One additional thing might be that distributions themselves use a very similar development and release model so they have a better understanding what each step along the way carries with it. Early bug fix releases of a feature release are basically more like the public beta of proprietary software, i.e. the beta releases of Free Software products (and of distributions which do such things) are more like the interal or private beta. 'Early bug fix' release? I thought that bug fix releases were the minor versions like 4.8.1, or 4.8.2 etc... Yes. What I wanted to say was early as in x.y.1 and x.y.2 as opposed to late as in x.y.5 Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Dolphin search anomalies KDE 4.6.0
if it has happened but that would be a useful step up from Konq. I also thought that the general idea was to replace konq with dolphin. It is more an addition, i.e. having a file managment only application available additional to the graphical shell Konqueror. Konqueror with all its modes and settings specific for certain modes is mainly addressing the needs of a type of user who like to have a wide range of options at hand at all times. Other users prefer simple tools even it that means not being able to do things a certain way. One of the options to solve this was to create another Konqueror mode that, when activated, would lock down some of the application's capabilities. In the end the option to create a new and dedicated application was chosen instead for various reasons (additional and very committed developers, not needing to add complexity to an already quite complex application, etc). The replacing part of the whole change only applies to the default setting, i.e. which of the two application's is registered as the default file manager. This registration can of course be changed or Konqueror can be used by choice if it fits a user's workflow or mental patterns better. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Dolphin search anomalies KDE 4.6.0
Have to forgive me here Keven but having checked the 2 konq looks to be the same as dolphin and just presented in a different way but dolphin has a file search and konq has bookmarks and I can open text files into another tab with it. File bookmarks don't work in my case. Do they in any version? I have my doubts. Konq is so similar to dolphin I can understand why certain people describe it as a window not an application. I haven't much time for people who blindly resist change just because it doesn't work in exactly the same way as it did - selections etc but as things stand there isn't much point in having the 2 apps except for people like that and as it is they will still be unhappy. :-) Must admit I did like Konq with full feature viewing and complained, a natural reaction. One app doing all is handy once some one has got used to the idea but dolphin previews and ok has to launch an app to actually view - big deal really for anyone who views such changes sensibly. Konq also launches and ap if I open a video in another tab. Text, pictures and pdf are ok but the latter takes time to load. A bit too long really. Trying to do that with all viewable files could understandably be a rather difficult option given the variations. Kitting out dolphin with a file search is a sensible place to put it and it's not exactly intrusive. What makes no sense what so ever is not making the results function in the same way as a normal file view mode does. As to the 2 being really different I think you must have your tongue in your cheek really. I have because I'm not convinced konq could ever bookmark files else why did I use kate. In 2 modes actually normal and su mode. What would be super cool (60's jargon) would to be to add file bookmarks that simply went to them and highlighted them where ever they are ( or were but web pages have that problem too= error message) Click launch , right click open with . su mode etc. People who have m8's etc who crop up on k - dumb - unbuto from time to time could even bookmark there current favourite video's etc or what ever else that they have probably illegally down loaded and use what ever app they liked to view it. Fortunately just about every one on the planet over the age of about 2 1/2 knows what bookmarks are. It could also be used to bookmark folders - duplication I know but why not. Less frequently used ones maybe but some would remove the panel. That aspect makes me think that the code is already mostly there really. :-) Apologies to any of the ubunto school - just that I tried it and found out it crippled root fine for people who want to cripple a lot of people in an office. I also nosed around a fair few forums. I had a feeling that the typical users had changed some what. All to the good really. The more the better. In the meantime or for ever I suppose I will have to use the old file search facility. :-) I found the dolphin one by accident really, just clicking on edit to see what was there many months after having upgraded from 3 to 4. Looks to me like konq could get a search and bookmarks too for those that like the tabs and split views etc. Wow I just found that dolphin has them too - fibbing a bit there I already knew. It's a nice piece of software really but the search results fiasco is clearly a silly omission. John - Original Message - From: Kevin Krammer kram...@kde.org To: kde@mail.kde.org Cc: Sent: Saturday, 7 April 2012, 16:34 Subject: Re: [kde] Dolphin search anomalies KDE 4.6.0 if it has happened but that would be a useful step up from Konq. I also thought that the general idea was to replace konq with dolphin. It is more an addition, i.e. having a file managment only application available additional to the graphical shell Konqueror. Konqueror with all its modes and settings specific for certain modes is mainly addressing the needs of a type of user who like to have a wide range of options at hand at all times. Other users prefer simple tools even it that means not being able to do things a certain way. One of the options to solve this was to create another Konqueror mode that, when activated, would lock down some of the application's capabilities. In the end the option to create a new and dedicated application was chosen instead for various reasons (additional and very committed developers, not needing to add complexity to an already quite complex application, etc). The replacing part of the whole change only applies to the default setting, i.e. which of the two application's is registered as the default file manager. This registration can of course be changed or Konqueror can be used by choice if it fits a user's workflow or mental patterns better. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring ___ This message is from
Re: [kde] Dolphin search anomalies KDE 4.6.0
On Saturday, 2012-04-07, John Woodhouse wrote: Have to forgive me here Keven but having checked the 2 konq looks to be the same as dolphin and just presented in a different way but dolphin has a file search and konq has bookmarks and I can open text files into another tab with it. The two programs use the same view engine for displaying and interacting with directories and files, however everything around that is diffferent. E.g. Konqueror uses a standard browser address input while Dolphin uses breadcrum hints by default. Konqueror can do vertical and horizontal view splits, separate views can be linked (changing path in one changes path in all linked ones), etc., while Dolphin has all kinds of useful sidebars or docks. File bookmarks don't work in my case. Do they in any version? I have my doubts. Work fine here: konqueror --version Qt: 4.7.4 KDE: 4.6.5 (4.6.5) Konqueror: 4.6.5 (4.6.5) I tried a directory bookmark, one for a text file and one for an image file. All worked as expected. As to the 2 being really different I think you must have your tongue in your cheek really. They share code for some things, but they have a different philosophy on the general UI. I have because I'm not convinced konq could ever bookmark files else why did I use kate. Where you add your bookmarks might depend on the workflow associated with the bookmarked things. E.g. if your workflow it to start Kate and then browse for the files to edit, then having the file bookmarked in Kate fits better than bookmarking in in Konqueror. If your workflow is to browse to the file using a file manager and then start Kate by clicking on the file, bookmarking the directory the file is in would probably be more efficient. In 2 modes actually normal and su mode. What would be super cool (60's jargon) would to be to add file bookmarks that simply went to them and highlighted them where ever they are Yes, that sounds useful. Currently a bookmarked file is opened, i.e. the bookmark works like clicking the file, not just selecting it. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
