Re: folder icons where should they be set
On Freitag, 11. September 2015 00:16:35 CEST, Harald Sitter wrote: being my confused self I am rather clueless as to where the correct place to implement this is, so any help on this would be very welcome. http://www.linfo.org/etc_skel.html Guessing the "correct" folder icon by the directory name/path is rather wonky. I don't have ~/music or ~/images but somewhen (ages ago) created ~/MyFiles and put subdirs for specific types there. So i rather have ~/MyFiles/Images than eg. "~/Images" or "~/My Images" or "~/MyImages" or "~/Meine Bilder" - which is localized and that's the next problem of "guessing" icons from directory names. A distro could possibly add downstream patches to dolphin and/or KFileItem to match their autocreated paths (because they also patched useradd instead of using /etc/skel?) but I doubt there's any way to do that upstream without adding a *very* long and hackish list of path/icon mapping (ending up incompatible with the hackish(?) list in gnome and totally not covering other desktop environments. => simply follow the present standards to a) create a $HOME structure b) define directory icons etc. Cheers, Thomas
Re: Adding further modules to api.kde.org
Am 2015-09-10 21:50, schrieb Allen Winter: On Thursday, September 10, 2015 10:57:10 AM Martin Graesslin wrote: Hi all, back in KDE4 days the workspace libraries were listed on api.kde.org [1]. But for the current version we don't have any API docs available. The section "Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground but apparently nothing from what used to be KDE SC. Does anybody know how I can get our KDE Workspaces listed there again? I'm in particular interested in getting KWayland API documentation published. If nobody knows: does anyone know who needs to be poked. http://api.kde.org/4.x-api/workspace-apidocs/ exists The KDE SC stuff is shown under "KDE4 Versions" http://api.kde.org/history4.php I do notice that under the various KDE 4.foo tables we don't have a workspace entry we have kde-workspace, but not workspace. seems like kde-workspace and workspace are similar. I'm not sure there's anything to fix. Well it's KDE4, it's old and outdated. It doesn't list new modules like the new KDecoration library or KWayland. Looking at the documentation it seems like at least KWin's documentation is from latest master - this is rather unexpected to be found under "KDE4". So yes I think there is lots to fix and I'm willing to look into it. Just I need to be told how. If I as the maintainer are not able to find the documentation of my own software, nobody else is. Just that should show that there is quite something to fix ;-) Cheers Martin
Re: Review Request 125097: Icons for hiding/unhiding files
> On Sept. 10, 2015, 9:29 p.m., andreas kainz wrote: > > hi, we have > > hint https://dl.dropboxusercontent.com/u/1642456/VDG/KF5/hint.svg and > > visibility > > https://dl.dropboxusercontent.com/u/1642456/VDG/KF5/visibility.svg > > in the kde:breeze Plasma/5.4 brunch and on 13.09. in master. > > Roman Gilg wrote: > Hi! Were these icons already planned for this switch? To be honest, I > normally wouldn't care which icong goes there, I just want an icon there. But > one thing makes me a little doubtful about these icons: Don't you think an > eye, striked or not, always starring at you from the top of the file explorer > will be a little disturbing? Especially when you increase the size of the > icons. > But if the dolphin devs want this icon or you more (I don't know who > decides this), I would change my other review request and link to thes icons > instead. :) I discussed it with Uri the main icon designer. he would prefere the hint icon. the icon from Roman is good but it could also be an cut icon. - andreas --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125097/#review85144 --- On Sept. 10, 2015, 8:19 p.m., Roman Gilg wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/125097/ > --- > > (Updated Sept. 10, 2015, 8:19 p.m.) > > > Review request for kde-workspace, andreas kainz and Emmanuel Pescosta. > > > Repository: breeze > > > Description > --- > > Icon is based on 'edit-copy.svg'. This icon is a follow up to my first review > request https://git.reviewboard.kde.org/r/125094/ > which I opened because Dolphin missed an icon for its switch to see hidden > files. > > > Diffs > - > > icons-dark/actions/22/hidden-files.svg PRE-CREATION > icons/actions/16/hidden-files.svg PRE-CREATION > icons/actions/22/hidden-files.svg PRE-CREATION > icons-dark/actions/16/hidden-files.svg PRE-CREATION > > Diff: https://git.reviewboard.kde.org/r/125097/diff/ > > > Testing > --- > > Tested on Arch, Plasma 5.4. > > > File Attachments > > > Demonstration in Breeze > > https://git.reviewboard.kde.org/media/uploaded/files/2015/09/07/9e208176-204f-4ab1-8fd5-6eef57bc10f4__change.png > > > Thanks, > > Roman Gilg > >
Re: Review Request 125097: Icons for hiding/unhiding files
> On Sept. 10, 2015, 11:29 p.m., andreas kainz wrote: > > hi, we have > > hint https://dl.dropboxusercontent.com/u/1642456/VDG/KF5/hint.svg and > > visibility > > https://dl.dropboxusercontent.com/u/1642456/VDG/KF5/visibility.svg > > in the kde:breeze Plasma/5.4 brunch and on 13.09. in master. Hi! Were these icons already planned for this switch? To be honest, I normally wouldn't care which icong goes there, I just want an icon there. But one thing makes me a little doubtful about these icons: Don't you think an eye, striked or not, always starring at you from the top of the file explorer will be a little disturbing? Especially when you increase the size of the icons. But if the dolphin devs want this icon or you more (I don't know who decides this), I would change my other review request and link to thes icons instead. :) - Roman --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125097/#review85144 --- On Sept. 10, 2015, 10:19 p.m., Roman Gilg wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/125097/ > --- > > (Updated Sept. 10, 2015, 10:19 p.m.) > > > Review request for kde-workspace, andreas kainz and Emmanuel Pescosta. > > > Repository: breeze > > > Description > --- > > Icon is based on 'edit-copy.svg'. This icon is a follow up to my first review > request https://git.reviewboard.kde.org/r/125094/ > which I opened because Dolphin missed an icon for its switch to see hidden > files. > > > Diffs > - > > icons-dark/actions/22/hidden-files.svg PRE-CREATION > icons/actions/16/hidden-files.svg PRE-CREATION > icons/actions/22/hidden-files.svg PRE-CREATION > icons-dark/actions/16/hidden-files.svg PRE-CREATION > > Diff: https://git.reviewboard.kde.org/r/125097/diff/ > > > Testing > --- > > Tested on Arch, Plasma 5.4. > > > File Attachments > > > Demonstration in Breeze > > https://git.reviewboard.kde.org/media/uploaded/files/2015/09/07/9e208176-204f-4ab1-8fd5-6eef57bc10f4__change.png > > > Thanks, > > Roman Gilg > >
folder icons where should they be set
salut mes amis so this popped up https://bugs.kde.org/show_bug.cgi?id=352498 and GTK/Gnome rather seems to set the folder icon as part of their folder-display-component sort of thing (e.g. file open as well as file browsers and what not). it does so however *without* creating a .directory file hardcoding a relevant icon now the question is where this sort of thing needs to be implemented in our tech to get all folder displaying things to display the correct icon. being my confused self I am rather clueless as to where the correct place to implement this is, so any help on this would be very welcome. thanks HS
Re: RFC: Enabling -DECM_ENABLE_SANITIZERS='address' in jenkins
El Dijous, 10 de setembre de 2015, a les 18:20:19, Lamarque Souza va escriure: > I agree but there is a problem: it can catch a lot of errors in our > dependency libraries (upstream bugs). No, it can not, asan works only on code you have compiled with asan enabled (which for most of our dependencies we do not compile or they don't use ECM). Cheers, Albert > I had this problem when I used it > with a program I develop at my work. Enabling it for all programs at once > and fixing all those upstream bugs can be overwhelming. Maybe we should do > it for a limited number of programs first and add more programs as we fix > the errors. > > Lamarque V. Souza > > http://planetkde.org/pt-br > > On Thu, Sep 10, 2015 at 5:36 PM, Albert Astals Cid wrote: > > We have this nice ECM module that gives us the option to compile with > > ASAN. > > > > I'd like to propose that we enable it by default in jenkins. > > > > This way we get all the autotests run with ASAN and potentially catch more > > bugs/regressions. > > > > Comments? > > > > Cheers, > > > > Albert
Re: Review Request 125097: Icons for hiding/unhiding files
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125097/#review85144 --- hi, we have hint https://dl.dropboxusercontent.com/u/1642456/VDG/KF5/hint.svg and visibility https://dl.dropboxusercontent.com/u/1642456/VDG/KF5/visibility.svg in the kde:breeze Plasma/5.4 brunch and on 13.09. in master. - andreas kainz On Sept. 10, 2015, 8:19 p.m., Roman Gilg wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/125097/ > --- > > (Updated Sept. 10, 2015, 8:19 p.m.) > > > Review request for kde-workspace, andreas kainz and Emmanuel Pescosta. > > > Repository: breeze > > > Description > --- > > Icon is based on 'edit-copy.svg'. This icon is a follow up to my first review > request https://git.reviewboard.kde.org/r/125094/ > which I opened because Dolphin missed an icon for its switch to see hidden > files. > > > Diffs > - > > icons-dark/actions/22/hidden-files.svg PRE-CREATION > icons/actions/16/hidden-files.svg PRE-CREATION > icons/actions/22/hidden-files.svg PRE-CREATION > icons-dark/actions/16/hidden-files.svg PRE-CREATION > > Diff: https://git.reviewboard.kde.org/r/125097/diff/ > > > Testing > --- > > Tested on Arch, Plasma 5.4. > > > File Attachments > > > Demonstration in Breeze > > https://git.reviewboard.kde.org/media/uploaded/files/2015/09/07/9e208176-204f-4ab1-8fd5-6eef57bc10f4__change.png > > > Thanks, > > Roman Gilg > >
Re: RFC: Enabling -DECM_ENABLE_SANITIZERS='address' in jenkins
I agree but there is a problem: it can catch a lot of errors in our dependency libraries (upstream bugs). I had this problem when I used it with a program I develop at my work. Enabling it for all programs at once and fixing all those upstream bugs can be overwhelming. Maybe we should do it for a limited number of programs first and add more programs as we fix the errors. Lamarque V. Souza http://planetkde.org/pt-br On Thu, Sep 10, 2015 at 5:36 PM, Albert Astals Cid wrote: > We have this nice ECM module that gives us the option to compile with ASAN. > > I'd like to propose that we enable it by default in jenkins. > > This way we get all the autotests run with ASAN and potentially catch more > bugs/regressions. > > Comments? > > Cheers, > Albert >
Re: Moving KDE Connect out of playground
On Thu, Sep 10, 2015 at 2:20 PM, Luigi Toscano wrote: > On Thursday 10 of September 2015 02:33:55 Albert Vaca wrote: >> +kde-core-devel >> >> Hi, >> >> With the latest changes we are making to KDE Connect as part of the sprint >> in Randa, I think that the project is becoming mature enough to be moved >> out of playground. Not only that, but Kubuntu and other distros are already >> installing KDE Connect by default, regardless of it being in playground. >> >> I think that extragear/network is the best place for KDE Connect to be in, >> as we don't want to be tied to external release schedules for now. >> >> Any thoughts? > > Nothing against moving it outside playground, it should have been done long > time ago. > > From a technical point of view, shouldn't we follow the usual procedure with a > moving to kdereview? > > Ciao > -- > Luigi > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << The move to kdereview has been requested this afternoon by Albert. I'd say the review itself can start already, I'm unsure it makes a big difference. Aleix
Re: Porting to frameworks 3: Krfb
If anyone using kde-telepathy is interested I just reenabled the ktp support in krfb frameworks branch (but I haven't set up ktp locally yet to test). BR, Jeremy On Sun, Sep 6, 2015 at 3:39 PM, Jeremy Whiting wrote: > Ah, another note. Sysadmin kindly created a phabricator board for this > effort. [1] I've added some tasks to it already, but if you know of > other tasks that need doing, please add them or take them and fix the > issues from the tasks. > > thanks, > Jeremy > > 1. https://phabricator.kde.org/tag/qt_5_porting/ > > On Sun, Sep 6, 2015 at 3:37 PM, Jeremy Whiting wrote: >> Hey all, >> >> Third project I took what I thought would be a a quick stab at but >> turned out to take a few hours over a couple of days. Krfb has a >> frameworks branch that is using Qt5/KF5 libraries. It builds and runs >> and I was able to vnc view my linux machine from another machine, but >> probably could use some more love. Its desktop files probably need to >> be changed to org.kde.krfb.desktop, it probably could use some help >> porting away from KIcon and the rest of KDELibs4Support etc. Play with >> it, build it, use it, report bugs, fix bugs, etc. etc. :) >> >> BR, >> Jeremy
RFC: Enabling -DECM_ENABLE_SANITIZERS='address' in jenkins
We have this nice ECM module that gives us the option to compile with ASAN. I'd like to propose that we enable it by default in jenkins. This way we get all the autotests run with ASAN and potentially catch more bugs/regressions. Comments? Cheers, Albert
Re: Adding further modules to api.kde.org
On Thursday, September 10, 2015 01:55:21 PM Jeremy Whiting wrote: > Allen, > > Those are both KDE4 versions of workspace stuff. I don't see any place > where kf5 versions are. > oh. sorry I misunderstood the problem. > > On Thu, Sep 10, 2015 at 1:50 PM, Allen Winter wrote: > > On Thursday, September 10, 2015 10:57:10 AM Martin Graesslin wrote: > >> Hi all, > >> > >> back in KDE4 days the workspace libraries were listed on api.kde.org [1]. > >> But > >> for the current version we don't have any API docs available. The section > >> "Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground > >> but > >> apparently nothing from what used to be KDE SC. > >> > >> Does anybody know how I can get our KDE Workspaces listed there again? I'm > >> in > >> particular interested in getting KWayland API documentation published. > >> > >> If nobody knows: does anyone know who needs to be poked. > >> > > > > http://api.kde.org/4.x-api/workspace-apidocs/ exists > > The KDE SC stuff is shown under "KDE4 Versions" > > http://api.kde.org/history4.php > > > > I do notice that under the various KDE 4.foo tables we don't have a > > workspace entry > > we have kde-workspace, but not workspace. seems like kde-workspace and > > workspace are similar. > > > > I'm not sure there's anything to fix. > > > > -Allen > > > >
Re: Adding further modules to api.kde.org
Allen, Those are both KDE4 versions of workspace stuff. I don't see any place where kf5 versions are. BR, Jeremy On Thu, Sep 10, 2015 at 1:50 PM, Allen Winter wrote: > On Thursday, September 10, 2015 10:57:10 AM Martin Graesslin wrote: >> Hi all, >> >> back in KDE4 days the workspace libraries were listed on api.kde.org [1]. But >> for the current version we don't have any API docs available. The section >> "Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground but >> apparently nothing from what used to be KDE SC. >> >> Does anybody know how I can get our KDE Workspaces listed there again? I'm in >> particular interested in getting KWayland API documentation published. >> >> If nobody knows: does anyone know who needs to be poked. >> > > http://api.kde.org/4.x-api/workspace-apidocs/ exists > The KDE SC stuff is shown under "KDE4 Versions" > http://api.kde.org/history4.php > > I do notice that under the various KDE 4.foo tables we don't have a workspace > entry > we have kde-workspace, but not workspace. seems like kde-workspace and > workspace are similar. > > I'm not sure there's anything to fix. > > -Allen > >
Re: Adding further modules to api.kde.org
On Thursday, September 10, 2015 10:57:10 AM Martin Graesslin wrote: > Hi all, > > back in KDE4 days the workspace libraries were listed on api.kde.org [1]. But > for the current version we don't have any API docs available. The section > "Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground but > apparently nothing from what used to be KDE SC. > > Does anybody know how I can get our KDE Workspaces listed there again? I'm in > particular interested in getting KWayland API documentation published. > > If nobody knows: does anyone know who needs to be poked. > http://api.kde.org/4.x-api/workspace-apidocs/ exists The KDE SC stuff is shown under "KDE4 Versions" http://api.kde.org/history4.php I do notice that under the various KDE 4.foo tables we don't have a workspace entry we have kde-workspace, but not workspace. seems like kde-workspace and workspace are similar. I'm not sure there's anything to fix. -Allen
Re: Review Request 125097: Icons for hiding/unhiding files
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125097/#review85127 --- Please add andreask as reviewer, so that we get these icons in before the next freeze ;) - Emmanuel Pescosta On Sept. 7, 2015, 11:12 p.m., Roman Gilg wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/125097/ > --- > > (Updated Sept. 7, 2015, 11:12 p.m.) > > > Review request for kde-workspace and Emmanuel Pescosta. > > > Repository: breeze > > > Description > --- > > Icon is based on 'edit-copy.svg'. This icon is a follow up to my first review > request https://git.reviewboard.kde.org/r/125094/ > which I opened because Dolphin missed an icon for its switch to see hidden > files. > > > Diffs > - > > icons-dark/actions/22/hidden-files.svg PRE-CREATION > icons/actions/16/hidden-files.svg PRE-CREATION > icons/actions/22/hidden-files.svg PRE-CREATION > icons-dark/actions/16/hidden-files.svg PRE-CREATION > > Diff: https://git.reviewboard.kde.org/r/125097/diff/ > > > Testing > --- > > Tested on Arch, Plasma 5.4. > > > File Attachments > > > Demonstration in Breeze > > https://git.reviewboard.kde.org/media/uploaded/files/2015/09/07/9e208176-204f-4ab1-8fd5-6eef57bc10f4__change.png > > > Thanks, > > Roman Gilg > >
Re: Moving KDE Connect out of playground
+kde-core-devel Hi, With the latest changes we are making to KDE Connect as part of the sprint in Randa, I think that the project is becoming mature enough to be moved out of playground. Not only that, but Kubuntu and other distros are already installing KDE Connect by default, regardless of it being in playground. I think that extragear/network is the best place for KDE Connect to be in, as we don't want to be tied to external release schedules for now. Any thoughts? Albert
Re: Adding further modules to api.kde.org
Well, it's not even just about workspace, we had in kde4 times kdeedu, kdegames, etc. etc. all on api.kde.org. Not all of it was api per se (I don't know anyone that would want to read the apidocs for kanagram for example, except to know how it's internals work or used to work when hacking on it). Currently we only show frameworks and other. This misses a lot of useful documentation, nothing is there about libkomparediff2, libkeduvocdocument, libkdegames, etc. since those aren't generated anymore for some reason. A good idea that Ben suggested when the gardening project started was having the apidocs generate on commit, rather than regenerating everything every night at a specified time. A lot of the sources don't actually change very often, so rebuilding part of the apidocs when the code or it's doxygen comments change would make a lot of sense. BR, Jeremy On Thu, Sep 10, 2015 at 11:05 AM, Adriaan de Groot wrote: > On Thursday 10 September 2015 06:07:40 Jeremy Whiting wrote: >> It would be awesome to have what used to be in KDE SC on api.kde.org >> again. We have many libraries that aren't frameworks that are Qt5/KF5 >> based which would be good to show on there imo. > > Perhaps half of this is figuring out what actually constitutes the "Workspace > API" that would be interesting here and how to subsequently pull information > out of the metadata-services that we have (src-build? projects.kde.org? I > don't know, I haven't followed very closely what lives where now). > > > > [ade] (who is now reminded that the original ebn domain is expiring and needs > renewal, yeah)
Re: Adding further modules to api.kde.org
On Thursday 10 September 2015 06:07:40 Jeremy Whiting wrote: > It would be awesome to have what used to be in KDE SC on api.kde.org > again. We have many libraries that aren't frameworks that are Qt5/KF5 > based which would be good to show on there imo. Perhaps half of this is figuring out what actually constitutes the "Workspace API" that would be interesting here and how to subsequently pull information out of the metadata-services that we have (src-build? projects.kde.org? I don't know, I haven't followed very closely what lives where now). [ade] (who is now reminded that the original ebn domain is expiring and needs renewal, yeah)
Re: Moving KDE Connect out of playground
On Thursday 10 of September 2015 02:33:55 Albert Vaca wrote: > +kde-core-devel > > Hi, > > With the latest changes we are making to KDE Connect as part of the sprint > in Randa, I think that the project is becoming mature enough to be moved > out of playground. Not only that, but Kubuntu and other distros are already > installing KDE Connect by default, regardless of it being in playground. > > I think that extragear/network is the best place for KDE Connect to be in, > as we don't want to be tied to external release schedules for now. > > Any thoughts? Nothing against moving it outside playground, it should have been done long time ago. >From a technical point of view, shouldn't we follow the usual procedure with a moving to kdereview? Ciao -- Luigi
Re: Moving KDE Connect out of playground
+1 here too. On Thu, Sep 10, 2015 at 3:39 AM, Albert Vaca wrote: > +kde-core-devel > > Hi, > > With the latest changes we are making to KDE Connect as part of the sprint > in Randa, I think that the project is becoming mature enough to be moved out > of playground. Not only that, but Kubuntu and other distros are already > installing KDE Connect by default, regardless of it being in playground. > > I think that extragear/network is the best place for KDE Connect to be in, > as we don't want to be tied to external release schedules for now. > > Any thoughts? > > Albert > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe >>> << >
Re: Adding further modules to api.kde.org
Martin, I took a look at this as part of the gardening documentation websites, but I didn't get very far. The code that runs this and ebn is in kde:websites/quality-kde-org and is pretty outdated unfortunately. Actually now that Allen Winter is back maybe he could add it (Added him to cc)? What I tried here during gardening which I couldn't get to work locally was: 1. Install it (I had some trouble with the perl based installer putting files in different places than expected, maybe perl itself changed over the years?) 2. Once I manually copied some files to places where they were expected I couldn't figure out how to manually run the doc generator, the --help documentation mentioned what arguments to use, but it wasn't obvious what I should put for my Qt documentation paths and such somehow, so I didn't try anything further. It would be awesome to have what used to be in KDE SC on api.kde.org again. We have many libraries that aren't frameworks that are Qt5/KF5 based which would be good to show on there imo. BR, Jeremy On Thu, Sep 10, 2015 at 2:57 AM, Martin Graesslin wrote: > Hi all, > > back in KDE4 days the workspace libraries were listed on api.kde.org [1]. But > for the current version we don't have any API docs available. The section > "Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground but > apparently nothing from what used to be KDE SC. > > Does anybody know how I can get our KDE Workspaces listed there again? I'm in > particular interested in getting KWayland API documentation published. > > If nobody knows: does anyone know who needs to be poked. > > Cheers > Martin > > [1] http://api.kde.org/4.x-api/kde-workspace-apidocs/ > [2] http://api.kde.org/other.php
Adding further modules to api.kde.org
Hi all, back in KDE4 days the workspace libraries were listed on api.kde.org [1]. But for the current version we don't have any API docs available. The section "Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground but apparently nothing from what used to be KDE SC. Does anybody know how I can get our KDE Workspaces listed there again? I'm in particular interested in getting KWayland API documentation published. If nobody knows: does anyone know who needs to be poked. Cheers Martin [1] http://api.kde.org/4.x-api/kde-workspace-apidocs/ [2] http://api.kde.org/other.php signature.asc Description: This is a digitally signed message part.
