Hi, thanks for pointing out the issue, and for using Okular of course :)
> But if there is no way for a parent application (that embeds Okular) to be > called when the user clicks a textedit:// link, my nice Frescobaldi editor > will stop working in KDE 4.2 and I couldn't do anything about it. :-( Luckly we have some days before KDE 4.2, so the we can find a solution. > I certainly can live with textedit:/ handling inside Okular, but then we > should arrange a way for applications to override the default handling > (open a configured editor). That could be done via an environment variable, I personally find the idea of using a envvar quite "raw" and not that much user friendly (aren't we both developing nice comfortable GUIs for our users? ;) ). Okular in KDE 4.2 provides a way to configure the editor to be launched for "sources", ie when working with DVI files with inverse search hyperlinks. Using this configuration, the user can also setup Okular for DVI integration within Kile. The interaction way used for Kile is to run it telling it to go at a specified line of a source file (something like `kile --line 10 thefile.dvi`). IMHO, this way could also be applied for Frescobaldi. Although, from what I see from the Frescobaldi' sources, it allows multiple instances of it, unlike Kile. A second problem (that could be solved with an hidden configuration, at least for KDE 4.2) is that it should be possible to configure the editor for different file types (eg "frescobaldi --line %l %f" for application/x-lilypond, "kile ..." for "application/dvi", etc). This would have the advantage that the user could just configure the editor for lilypond files once, and forget about it :) What do you think? -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel