I do see your point here and it indeed makes sense. I could invest some time and add the annotation features (and eventually other stuff) to Spectacle. The lack of those features is actually the reason why we're having this discussion, so it would make sense to resolve them. Does Spectacle have a maintainer at the moment? As said, I my opinion, Spectacle requires some redesign in order to provide annotations and be usable as other Screenshot application that are currently in use. With whom would I need to coordinate this. Don't want just to fork the repo, do all kind of changes to hear in the end that I can't or should do that. What would be my starting point?
Damir Sent: Saturday, February 03, 2018 at 8:36 PM From: "Nate Graham" <pointedst...@zoho.com> To: kde-devel@kde.org Subject: Re: Adding application to KDE and getting image of current I know, my answer sucks. I really do hate to have to bring it up. And I don't mean to throw cold water on your project or your enthusiasm! KSnip looks cool. The thing is, single-developer projects tend to have a predictable lifecycle: lots of energy and progress in the beginning, then around year two or three, the developer loses interest or gets too busy, and then the app stagnates for a few years and finally dies of bit-rot. It isn't *always* the case, but I've seen it too many times to ignore the pattern. Spectacle itself narrowly avoided this fate when community members took an interest and stepped up when its lead developer left at the beginning of 2017. It is now fairly healthy, under somewhat active development, and no longer so fragile. With your development skills and current level of enthusiasm, I think Spectacle could advance very rapidly, and your work on it would benefit *every* KDE user very quickly. The alternative is that we have two screenshot apps, splitting development effort between the two and making both more fragile and likely to fail in response to developers losing interest. I won't stand in the way of making KSnip a KDE app if others think approve, but I want to bring this up as a long-term strategic matter. I think we all benefit from having one really strong choice that's developed by many. Nate Graham On 02/03/2018 11:02 AM, Damir Porobic wrote: > Yeah, I was kind of afraid that you would say that. > > When I started to work on the project I hadn't thought about extending any > other projects, mostly due to my limited knowledge of Qt at that time. Now I > have invested a lot of time and effort into this project and it seems to be > working fine and users are happy. > Also, KSnip was written mostly with the idea to provide annotations and with > Spectacle I see the focus on screenshots and I've got the feeling that it > would require a lot of refactoring and wouldn't be doable just like that. > > Regards, > Damir > > > Sent: Saturday, February 03, 2018 at 6:30 PM > From: "Nate Graham" <pointedst...@zoho.com> > To: kde-devel@kde.org > Subject: Re: Adding application to KDE and getting image of current > I love the idea of annotations built into a screenshot tool! Our users > have been asking for this. > > However, I hate to be that guy, but have you considered extending > Spectacle instead? Spectacle is mature, well-integrated into KDE Plasma, > has all the features highlighted on > https://github.com/DamirPorobic/ksnip (except for editing and > annotation), and it's already shipped by default in all KDE distros that > I'm aware of. Your work would have a hugely greater impact if you > extended Spectacle instead! > > Nate Graham > > > > On 02/03/2018 05:30 AM, Damir Porobic wrote: >> The link that gives a hint on what needs to be done is under the "Incubated >> Projects" section, I've expected it under "Incubation Process". >> >> I've created a page based on the template and added a link to "Incubated >> Projects" under "Candidates", don't know if I was supposed to do that or >> someone else: >> https://community.kde.org/Incubator/Projects/Ksnip[https://community.kde.org/Incubator/Projects/Ksnip][https://community.kde.org/Incubator/Projects/Ksnip[https://community.kde.org/Incubator/Projects/Ksnip]] >> >> And here is the repo: >> https://github.com/DamirPorobic/ksnip[https://github.com/DamirPorobic/ksnip][https://github.com/DamirPorobic/ksnip[https://github.com/DamirPorobic/ksnip]] >> >> Was that so far correct and according to the process? If yes, what's >> supposed to happen next? >> >> About the application, Ksnip is a screenshot annotation tool, which can also >> take screenshots itself. I've started to work on it as I was missing some >> tool to annotate screenshots which I have taken via Spectacle, which is a >> great screenshot tool, but as said, the annotation features were missing in >> my opinion. >> >> Damir >> >> >> Sent: Fri, 02 Feb 2018 12:52:01 -0800 >> From: pointedstick <pointedst...@zoho.com> >> To: <kde-devel@kde.org> >> Subject: Re: Adding application to KDE and getting image of current >> cursor under wayland >> Message-ID: <161584a51bb.10ff69e3b3883.5474288975285038...@zoho.com> >> Content-Type: text/plain; charset="UTF-8" >> >> ---- On Fri, 02 Feb 2018 11:50:13 -0800 Damir Porobic<damir.poro...@gmx.com> >> wrote ---- >>> Sorry, one more question regarding the incubator process. It's not obvious >>> to me how one application/project becomes a Candidate? >>> On the link >>> https://community.kde.org/Incubator/Incubation_Process[https://community.kde.org/Incubator/Incubation_Process][https://community.kde.org/Incubator/Incubation_Process[https://community.kde.org/Incubator/Incubation_Process]] >>> it is mentioned what a Candidate needs to provide, but not where and in >>> what form. >> >> Starting here is a good bet! >> >> What's the app you're proposing? >> >> Nate >> >> >> Sent: Fri, 2 Feb 2018 21:56:04 +0100 >> From: Luigi Toscano <luigi.tosc...@tiscali.it> >> To: kde-devel@kde.org >> Subject: Re: Adding application to KDE and getting image of current >> cursor under wayland >> Message-ID: <edf05347-34cf-a4cb-e9ca-7bb9ad22c...@tiscali.it> >> Content-Type: text/plain; charset=UTF-8 >> >> Damir Porobic ha scritto: >>> Sorry, one more question regarding the incubator process. It's not obvious >>> to me how one application/project becomes a Candidate? >>> On the link >>> https://community.kde.org/Incubator/Incubation_Process[https://community.kde.org/Incubator/Incubation_Process][https://community.kde.org/Incubator/Incubation_Process[https://community.kde.org/Incubator/Incubation_Process]] >>> it is mentioned what a Candidate needs to provide, but not where and in >>> what form. >> >> With a written statement on a public place, like for example the >> kde-community >> list. Here few past examples: >> >> https://mail.kde.org/pipermail/kde-community/2013q4/000375.html[https://mail.kde.org/pipermail/kde-community/2013q4/000375.html][https://mail.kde.org/pipermail/kde-community/2013q4/000375.html[https://mail.kde.org/pipermail/kde-community/2013q4/000375.html]] >> https://mail.kde.org/pipermail/kde-community/2014q1/000552.html[https://mail.kde.org/pipermail/kde-community/2014q1/000552.html][https://mail.kde.org/pipermail/kde-community/2014q1/000552.html[https://mail.kde.org/pipermail/kde-community/2014q1/000552.html]] >> https://mail.kde.org/pipermail/kde-community/2014q2/000787.html[https://mail.kde.org/pipermail/kde-community/2014q2/000787.html][https://mail.kde.org/pipermail/kde-community/2014q2/000787.html[https://mail.kde.org/pipermail/kde-community/2014q2/000787.html]] >> https://mail.kde.org/pipermail/kde-community/2015q2/001374.html[https://mail.kde.org/pipermail/kde-community/2015q2/001374.html][https://mail.kde.org/pipermail/kde-community/2015q2/001374.html[https://mail.kde.org/pipermail/kde-community/2015q2/001374.html]] >> >> Which kind of application are we talking about? >> >> Ciao >> > >
