Making an app command available to other apps

[Milan Bouchet-Valat]

Hi,
Thanks for your reply! Does that mean all I have to do is request the
Atom and VScode apps to implement a common extension point? Or do
changes need to happen in Flatpak before this works?
Also, I guess that if the Julia app is an extension, it won't be able
to provide its own .desktop file allowing to use it separately without
installing and launching an IDE?

Regards

Le mardi 12 juin 2018 à 08:46 +0200, Alexander Larsson a écrit :
> There are no general means to allow apps to be injected into
> otherapps, both for technical (its tricky in general to make sure
> that suchapps work in any other random apps environment, with library
> ABIs andwhatnot), and security reasons.
> However, as you say, extensions can be used to work around this.
> Therehas been discussions about adding a generic SDK tool extensions
> thatany IDE-like app can add, allowing one extension to serve many
> IDEs.
> On Mon, Jun 11, 2018 at 7:05 PM, Milan Bouchet-Valat <nalimilan at club.
> fr> wrote:
> Hi,
> Any chance to get a reply to my question? It's really blocking to
> create aJulia Flatpak app. :-/
> 
> Le samedi 28 avril 2018 à 15:34 +0200, Milan Bouchet-Valat a écrit :
> Hi,
> 
> I have recently prepared a Flatpak app for the Julia language [1]. It
> was relatively simple, and it works well (Julia provides a .desktop
> file which runs the julia executable in a terminal).
> 
> Then I realized things are more complicated when it comes to making
> Julia available to other Flatpak apps. In particular, Atom and VSCode
> plug-ins are quite popular. They need to be able to run the julia
> executable. This is possible via an extension point, which has just
> been added to the Atom app [2]. Thanks to this extension I can make
> an
> io.atom.Atom.Extension.julia app which provides Julia to Atom.
> 
> But this approach is problematic: there needs to be one app for each
> IDE where a Julia plug-in exists, plus one app for the vanilla Julia.
> Users need to install the specific app for their IDE, and it won't
> give
> them access to the vanilla Julia, which can be useful. Worse, if they
> install several Julia Flatpak apps, the settings will not be shared
> (and in particular they will have to reinstall packages manually).
> 
> So I was wondering whether this kind of scenario has been considered.
> Maybe I just missed something obvious. It looks like it would be
> possible to handle it by allowing the Julia app to provide multiple
> extensions (one for each IDE).
> 
> Thanks for your help!
> 
> 
> 1: https://julialang.org
> 2: https://github.com/flathub/io.atom.Atom/issues/8
> 
> _______________________________________________Flatpak mailing
> listFlatpak at lists.freedesktop.orghttps://lists.freedesktop.org/mailma
> n/listinfo/flatpak
> 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/flatpak/attachments/20180613/a1f0b221/attachment.html>