[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: RAW processing plug-in - any interest?
From: EI <geneing () gmail ! com>
Date: 2017-03-11 3:27:15
Message-ID: CAD-3yKu+COQCr4bhMPT03AaeEQkTumAkM5rMz924vw442Vfdqg () mail ! gmail ! com
[Download RAW message or body]
Screencast looks impressive!
- I don't think there a way to prioritize which plugin will handle loading.
One option may be to add a menu item under "File" for PhotoFlow. The
actions are configured through krita/kritamenu.action
- Krita can keep almost arbitrary metadata for the loaded image. An example
can be found here: krita/libs/image/tests/kis_meta_data_test.cpp. The code
itself is in krita/libs/image/metadata/. However, your plugin would have to
write this metadata to the raw file and then read it. Storing metadata in
an xml "sidecar" file may be easier.
- Have you looked at QProcess? http://doc.qt.io/qt-5/qprocess.html
- You can probably request a developer account. boud@valdyas.org may be
able to help. Is your plugin code available through
https://github.com/aferrero2707/PhotoFlow?
Eugene
>
> Today's Topics:
>
> 1. Re: RAW processing plug-in - any interest? (PhotoFlow Editor)
> (PhotoFlow Editor)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 9 Mar 2017 14:41:59 +0100
> From: PhotoFlow Editor <photofloweditor@gmail.com>
> To: Krita's developers and users mailing list <kimageshop@kde.org>
> Subject: Re: RAW processing plug-in - any interest? (PhotoFlow Editor)
> Message-ID: <DFC8CB20-2075-4244-94DA-10377E0FC8FF@gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi!
>
> the initial implementation of the RAW loading plug-in turned out to be
> relatively easy… just a couple of spare-time coding hours to achieve the
> result shown in this screencast: https://youtu.be/9K6RJv-O6Yw <
> https://youtu.be/9K6RJv-O6Yw>
>
>
> However, this is just the very beginning. Unfortunately I do not have much
> time to chat on IRC, only to read/write emails from time to time.
> Therefore, if any krater developer is reading those lines, here are a few
> questions (some might be trivial):
>
> - is there a way to prioritise the file loading plug-ins in Krita? In my
> first experiments I had to remove the official impex/raw plug-in from the
> CMakeLists.txt file, otherwise my own plug-in would not be invoked…
>
> - does Krita provide a mechanism to store arbitrary meta-data in the image
> structure? The idea would be to store the RAW processing parameters
> directly inside the krita image, so that next time the photoflow plug-in is
> invoked it can re-open the RAW file and restore the last saved processing
> parameters
> GIMP provides such mechanism through functions like gimp_parasite_new() (
> https://developer.gimp.org/api/2.0/libgimpbase/
> libgimpbase-gimpparasite.html <https://developer.gimp.org/
> api/2.0/libgimpbase/libgimpbase-gimpparasite.html>) and
> gimp_item_attach_parasite() (https://developer.gimp.org/
> api/2.0/libgimp/libgimp-gimpitem.html <https://developer.gimp.org/
> api/2.0/libgimp/libgimp-gimpitem.html>)
>
> - is there a way in Qt to spawn a process and pass parameters to it in the
> form of QStrings instead of char*? I would need this to properly invoke the
> photoflow executable with UTF8 file names…
>
> - what is the best way to distribute the preliminary code so that experts
> can have a look?
>
>
> By the way, the photoflow executable used for the test in the screencast
> is actually this AppImage package: https://github.com/
> aferrero2707/PhotoFlow/releases/download/continuous/
> PhotoFlow-20170307-git-stable-d1501a91826e6b768af51bf6c734bd
> 989507915d.glibc2.14-dbg-x86_64.AppImage <https://github.com/
> aferrero2707/PhotoFlow/releases/download/continuous/
> PhotoFlow-20170307-git-stable-d1501a91826e6b768af51bf6c734bd
> 989507915d.glibc2.14-dbg-x86_64.AppImage>
> I simply downloaded the package, made is executable with
>
> chmod u+x PhotoFlow-20170307-git-stable-d1501a91826e6b768af51bf6c734bd
> 989507915d.glibc2.14-dbg-x86_64.AppImage
>
> and moved is to a folder in the PATH so that is gets automatically found:
>
> mv PhotoFlow-20170307-git-stable-d1501a91826e6b768af51bf6c734bd
> 989507915d.glibc2.14-dbg-x86_64.AppImage $HOME/.local/bin/photoflow
>
>
> This AppImage should be compatible with most of the current Linux
> distributions, and requires no installation of additional packages… just
> download the AppImage and run it!
>
>
[Attachment #3 (text/html)]
<div dir="ltr">Screencast looks impressive! <div><br></div><div>- I don't think \
there a way to prioritize which plugin will handle loading. One option may be to add \
a menu item under "File" for PhotoFlow. The actions are configured through \
krita/kritamenu.action</div><div><br></div><div>- Krita can keep almost arbitrary \
metadata for the loaded image. An example can be found here: \
krita/libs/image/tests/kis_meta_data_test.cpp. The code itself is in \
krita/libs/image/metadata/. However, your plugin would have to write this metadata to \
the raw file and then read it. Storing metadata in an xml "sidecar" file \
may be easier. </div><div><br></div><div>- Have you looked at QProcess? <a \
href="http://doc.qt.io/qt-5/qprocess.html">http://doc.qt.io/qt-5/qprocess.html</a></div><div><br></div><div>- \
You can probably request a developer account. <a \
href="mailto:boud@valdyas.org">boud@valdyas.org</a> may be able to help. Is your \
plugin code available through <a \
href="https://github.com/aferrero2707/PhotoFlow">https://github.com/aferrero2707/PhotoFlow</a>? \
</div><div><br></div><div>Eugene</div><div><br></div><div><br><div \
class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><br> <br>
Today's Topics:<br>
<br>
1. Re: RAW processing plug-in - any interest? (PhotoFlow Editor)<br>
(PhotoFlow Editor)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Thu, 9 Mar 2017 14:41:59 +0100<br>
From: PhotoFlow Editor <<a \
href="mailto:photofloweditor@gmail.com">photofloweditor@gmail.com</a>><br>
To: Krita's developers and users mailing list <<a \
href="mailto:kimageshop@kde.org">kimageshop@kde.org</a>><br>
Subject: Re: RAW processing plug-in - any interest? (PhotoFlow Editor)<br>
Message-ID: <<a href="mailto:DFC8CB20-2075-4244-94DA-10377E0FC8FF@gmail.com">DFC8CB20-2075-4244-94DA-<wbr>10377E0FC8FF@gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi!<br>
<br>
the initial implementation of the RAW loading plug-in turned out to be relatively \
easy… just a couple of spare-time coding hours to achieve the result shown in this \
screencast: <a href="https://youtu.be/9K6RJv-O6Yw" rel="noreferrer" \
target="_blank">https://youtu.be/9K6RJv-O6Yw</a> <<a \
href="https://youtu.be/9K6RJv-O6Yw" rel="noreferrer" \
target="_blank">https://youtu.be/9K6RJv-O6Yw</a>><br> <br>
<br>
However, this is just the very beginning. Unfortunately I do not have much time to \
chat on IRC, only to read/write emails from time to time. Therefore, if any krater \
developer is reading those lines, here are a few questions (some might be \
trivial):<br> <br>
- is there a way to prioritise the file loading plug-ins in Krita? In my first \
experiments I had to remove the official impex/raw plug-in from the CMakeLists.txt \
file, otherwise my own plug-in would not be invoked…<br> <br>
- does Krita provide a mechanism to store arbitrary meta-data in the image structure? \
The idea would be to store the RAW processing parameters directly inside the krita \
image, so that next time the photoflow plug-in is invoked it can re-open the RAW file \
and restore the last saved processing parameters<br> GIMP provides such mechanism \
through functions like gimp_parasite_new() (<a \
href="https://developer.gimp.org/api/2.0/libgimpbase/libgimpbase-gimpparasite.html" \
rel="noreferrer" target="_blank">https://developer.gimp.org/<wbr>api/2.0/libgimpbase/<wbr>libgimpbase-gimpparasite.html</a> \
<<a href="https://developer.gimp.org/api/2.0/libgimpbase/libgimpbase-gimpparasite.html" \
rel="noreferrer" target="_blank">https://developer.gimp.org/<wbr>api/2.0/libgimpbase/<wbr>libgimpbase-gimpparasite.html</a>><wbr>) \
and gimp_item_attach_parasite() (<a \
href="https://developer.gimp.org/api/2.0/libgimp/libgimp-gimpitem.html" \
rel="noreferrer" target="_blank">https://developer.gimp.org/<wbr>api/2.0/libgimp/libgimp-<wbr>gimpitem.html</a> \
<<a href="https://developer.gimp.org/api/2.0/libgimp/libgimp-gimpitem.html" \
rel="noreferrer" target="_blank">https://developer.gimp.org/<wbr>api/2.0/libgimp/libgimp-<wbr>gimpitem.html</a>>)<br>
<br>
- is there a way in Qt to spawn a process and pass parameters to it in the form of \
QStrings instead of char*? I would need this to properly invoke the photoflow \
executable with UTF8 file names…<br> <br>
- what is the best way to distribute the preliminary code so that experts can have a \
look?<br> <br>
<br>
By the way, the photoflow executable used for the test in the screencast is actually \
this AppImage package: <a \
href="https://github.com/aferrero2707/PhotoFlow/releases/download/continuous/PhotoFlow \
-20170307-git-stable-d1501a91826e6b768af51bf6c734bd989507915d.glibc2.14-dbg-x86_64.AppImage" \
rel="noreferrer" target="_blank">https://github.com/<wbr>aferrero2707/PhotoFlow/<wbr>r \
eleases/download/continuous/<wbr>PhotoFlow-20170307-git-stable-<wbr>d1501a91826e6b768af51bf6c734bd<wbr>989507915d.glibc2.14-dbg-x86_<wbr>64.AppImage</a> \
<<a href="https://github.com/aferrero2707/PhotoFlow/releases/download/continuous/Ph \
otoFlow-20170307-git-stable-d1501a91826e6b768af51bf6c734bd989507915d.glibc2.14-dbg-x86_64.AppImage" \
rel="noreferrer" target="_blank">https://github.com/<wbr>aferrero2707/PhotoFlow/<wbr>r \
eleases/download/continuous/<wbr>PhotoFlow-20170307-git-stable-<wbr>d1501a91826e6b768af51bf6c734bd<wbr>989507915d.glibc2.14-dbg-x86_<wbr>64.AppImage</a>><br>
I simply downloaded the package, made is executable with<br>
<br>
chmod u+x PhotoFlow-20170307-git-stable-<wbr>d1501a91826e6b768af51bf6c734bd<wbr>989507915d.glibc2.14-dbg-x86_<wbr>64.AppImage<br>
<br>
and moved is to a folder in the PATH so that is gets automatically found:<br>
<br>
mv PhotoFlow-20170307-git-stable-<wbr>d1501a91826e6b768af51bf6c734bd<wbr>989507915d.glibc2.14-dbg-x86_<wbr>64.AppImage \
$HOME/.local/bin/photoflow<br> <br>
<br>
This AppImage should be compatible with most of the current Linux distributions, and \
requires no installation of additional packages… just download the AppImage and run \
it!<br> <br></blockquote></div></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic