Separate some back-end from Spectacle into a library

[David Edmundson]

There's nothing inherently wrong with just copy/pasting when it's a quite
small amount of code in 1-5 apps.

If things get beyond that, then sure, a library makes sense. Or if it ever
becomes a massive amount of code.

There is a coding guidelines about repeated code, but every coding
guidelines has an equal and opposite guideline. It's all about tradeoffs.

Right now I need selling on what the problem we're fixing is.

Also, out of curiosity, what's the app? Ideally we should be pushing the
portal API where possible, though I understand there are limitations.

David

On Mon, 15 Jun 2026, 16:49 Igor Mironchik, <igor.mironchik at gmail.com> wrote:

> Hello.
>
> I'd like to make a request to separate some back-end from Spectacle into
> a library. At least ImagePlatformKWin.h functionality may be reused by
> other developers on KDE platform for some third-party screen capturing.
> In can of move KDE to Wayland only this can be useful, at least for me :)
>
> This should not be a separate repository but in CMake should be splitted
> back-end in some library. Hm, and an option for building back-end only
> could be very great. :)
>
> What do you think?
>
> Thank you.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20260718/e703cdc4/attachment.htm>