Drawbacks from appimage version

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Drawbacks from appimage version

Erick Moreno
Recently I migrated from Philips PPA to AppImage to keep update with latest Digikam versions.

Since them I'm facing two drawbacks to my workflow and would like to share them to figure out some workaround.

The first one is that I can't open files with showphoto outside digikam.
      My usual way used be select a file on my disk, right click, open with showfoto, but this is not possible anymore. Now, I must import the file into digikam and only them open with the editor.

Another thing is: I can't import new Lut3D .png files and make digikam recognize them.
      This new problem really bothers me, since I feel like I lost a great functionality just because I change the way I installed the software.


So guys, any tips or workarounds?

--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Drawbacks from appimage version

jdd@dodin.org
Le 09/08/2017 à 16:29, Erick Moreno a écrit :

> Recently I migrated from Philips PPA to AppImage to keep update with
> latest Digikam versions.
>
> Since them I'm facing two drawbacks to my workflow and would like to
> share them to figure out some workaround.
>
> *The first one is that I can't open files with showphoto outside digikam. *
>        My usual way used be select a file on my disk, right click, open
> with showfoto, but this is not possible anymore. Now, I must import the
> file into digikam and only them open with the editor.

you have to link your photos with the appimage and option showphoto,
mine is:

/home/jdd/Telechargements/digikam/digikam-5.5.0-02-x86-64.appimage showfoto

jdd

--
http://dodin.org
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Drawbacks from appimage version

Erick Moreno
Hi jdd, thank you!

With your information I could create a showfoto.desktop file and now I can use the "open with" entry on menu.

This is .desktop file I created and worked:
[Desktop Entry]
Version=1.0
Type=Application
Name=Showfoto
GenericName=Showfoto Image Editor
Comment=Edit photographs
Exec=sh -c '/home/erick/Downloads/digikam-5.6.0-01-x86-64.appimage showfoto %U'
Terminal=false
StartupNotify=true
MimeType=image/bmp;image/gif;image/x-portable-bitmap;image/tiff;image/jpeg;image/png;image/x-icon;



Now, I just need a way to make digikam read new Lut3D files.




On Wed, Aug 9, 2017 at 11:39 AM, [hidden email] <[hidden email]> wrote:
Le 09/08/2017 à 16:29, Erick Moreno a écrit :
Recently I migrated from Philips PPA to AppImage to keep update with latest Digikam versions.

Since them I'm facing two drawbacks to my workflow and would like to share them to figure out some workaround.

*The first one is that I can't open files with showphoto outside digikam. *
       My usual way used be select a file on my disk, right click, open with showfoto, but this is not possible anymore. Now, I must import the file into digikam and only them open with the editor.

you have to link your photos with the appimage and option showphoto, mine is:

/home/jdd/Telechargements/digikam/digikam-5.5.0-02-x86-64.appimage showfoto

jdd

--
http://dodin.org



--
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Drawbacks from appimage version

Gilles Caulier-4
> Now, I just need a way to make digikam read new Lut3D files.

I just take a look in source code. The path to lut3d files is hard
coded. No way for the moment to test with customized files. To do it,
this require to touch 4 cpp files and to add a patch handler in GUI.
It's not simple.

The current PNG lut3d file are into the AppImage as data. It read only.

My tips : create a new entry in bugzilla, and attach a tarball with
your new LUT 3d files with a description for each one (effect one
image, transformation done, simulate performed, etc...)

Gilles Caulier
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Drawbacks from appimage version

Maik Qualmann
New Lut3D files are also searched in the home directory. This also works with
the AppImage.

$HOME/.local/share/digikam/data/lut3d/

Maik

Am Freitag, 11. August 2017, 18:43:25 CEST schrieb Gilles Caulier:

> > Now, I just need a way to make digikam read new Lut3D files.
>
> I just take a look in source code. The path to lut3d files is hard
> coded. No way for the moment to test with customized files. To do it,
> this require to touch 4 cpp files and to add a patch handler in GUI.
> It's not simple.
>
> The current PNG lut3d file are into the AppImage as data. It read only.
>
> My tips : create a new entry in bugzilla, and attach a tarball with
> your new LUT 3d files with a description for each one (effect one
> image, transformation done, simulate performed, etc...)
>
> Gilles Caulier
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Drawbacks from appimage version

Erick Moreno
Thanks, Maik!

Worked perfectly!

On Fri, Aug 11, 2017 at 5:43 PM, Maik Qualmann <[hidden email]> wrote:
New Lut3D files are also searched in the home directory. This also works with
the AppImage.

$HOME/.local/share/digikam/data/lut3d/

Maik

Am Freitag, 11. August 2017, 18:43:25 CEST schrieb Gilles Caulier:
> > Now, I just need a way to make digikam read new Lut3D files.
>
> I just take a look in source code. The path to lut3d files is hard
> coded. No way for the moment to test with customized files. To do it,
> this require to touch 4 cpp files and to add a patch handler in GUI.
> It's not simple.
>
> The current PNG lut3d file are into the AppImage as data. It read only.
>
> My tips : create a new entry in bugzilla, and attach a tarball with
> your new LUT 3d files with a description for each one (effect one
> image, transformation done, simulate performed, etc...)
>
> Gilles Caulier



--
Loading...