[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Future of libksane
From: Kåre_Särs <kare.sars () mailbox ! org>
Date: 2022-01-03 20:14:56
Message-ID: 4677255.GXAFRqVoOG () sars-xps-13-9370
[Download RAW message or body]
For almost a decade I have been thinking about splitting the UI and business-logic in
libksane, to make it possible to use without the QWidget. I started twice but never
gathered enough inspiration to get it done all the way. Luckily, about a year ago Alexander
Stippich stepped up to work on Skanpage and has now also almost finished the split I was
thinking of. He has taken over Skanpage (the multi-page paper-document scanning
application) and has done a great job with improvements to Skanpage, Skanlite and
libksane.
Our almost done plan:
The core parts of libksane are split out into a non-UI library called KSaneCore (this is
already done but all still in the libksane repository). The current QWidget API would remain
in the libksane repository, but the new dependency KSaneCore would move to a separate
repository.
With the move to Qt6 and KF6, libksane would be renamed to KSaneWidget to better
reflect what it provides.
Now to our questions/problems:
There was some problem with pushing the whole history of libksane to the KSaneCore
repository at one point, because of some author email issues in some old commit and now
that we asked for KDE Gear inclusion, force pushing no-longer works. I guess this is just a
mater of filing a sysadmin ticket to get the whole libksane history force-pushed to the
KSaneCore repository (nobody is using the repository yet).
These two libraries are KDE-internally used by at least Skanlite, Skanpage (only
KSaneCore) and DigiKam. There are also a couple of unofficial KDE projects that use
libksane. KDE-external usage I do not know about, but I suspect there might be ;)
At the time of porting to KF5, I did not pursue Frameworks integration, because I wanted
this split to be done first. Now that the split is (almost) done I'm wondering if it would be a
good time/idea to turn them into KDE Frameworks libraries?
Best regards,
Kåre
[Attachment #3 (unknown)]
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">For almost a decade I have \
been thinking about splitting the UI and business-logic in libksane, to make it possible to use without \
the QWidget. I started twice but never gathered enough inspiration to get it done all the way. Luckily, \
about a year ago Alexander Stippich stepped up to work on Skanpage and has now also almost finished the \
split I was thinking of. He has taken over Skanpage (the multi-page paper-document scanning application) \
and has done a great job with improvements to Skanpage, Skanlite and libksane.</p> <br /><p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Our almost done plan: </p> <p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">The core parts of libksane are split \
out into a non-UI library called KSaneCore (this is already done but all still in the libksane \
repository). The current QWidget API would remain in the libksane repository, but the new dependency \
KSaneCore would move to a separate repository.</p> <br /><p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">With the move to Qt6 and KF6, libksane \
would be renamed to KSaneWidget to better reflect what it provides.</p> <br /><br /><p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Now to our questions/problems:</p> <br \
/><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">There was some problem with \
pushing the whole history of libksane to the KSaneCore repository at one point, because of some author \
email issues in some old commit and now that we asked for KDE Gear inclusion, force pushing no-longer \
works. I guess this is just a mater of filing a sysadmin ticket to get the whole libksane history \
force-pushed to the KSaneCore repository (nobody is using the repository yet).</p> <br /><p \
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">These two libraries are KDE-internally \
used by at least Skanlite, Skanpage (only KSaneCore) and DigiKam. There are also a couple of unofficial \
KDE projects that use libksane. KDE-external usage I do not know about, but I suspect there might be \
;)</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"> </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">At the time of porting to KF5, I \
did not pursue Frameworks integration, because I wanted this split to be done first. Now that the split \
is (almost) done I'm wondering if it would be a good time/idea to turn them into KDE Frameworks \
libraries?</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Best \
regards,</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"> Kåre</p>
<br /></body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic