[Okular-devel] Kile and Okular with ForwardDVI
pino at kde.org
Wed May 13 12:47:06 CEST 2009
> as more and more people are using our KDE4 version of kile more questions
> arise with the interaction between kile and okular.
> Due to the good support from the okular devs we could always get the
> problem nailed down and fixed quite fast.
Yes, although sometimes I found myself what was missing ;)
Also, other than ForwardDVI, there's something else that can be improved (read
up to the end).
> One remaining problem is the forwarddvi.
> In this mode kile tells the viewer to open a file and jump to a given line.
> With KDE 3.5 kile used to call kdvi like
> kdvi --unique 'file:/home/kdedev/kile-projects/test.dvi#src:16 ./test.tex'
> and kdvi jumped to the source special "#src: 16./test.tex" in the
> file /home/kdedev/kile-projects/test.dvi.
> With okular this method does not work anymore.
Actually, this was not implemented so far (that's why it does not work).
> Have you already added forward search in okular?
> If yes, how do I have to call okular in order to get it working?
It is not there yet.
Incidentally, we received a bug report about named destinations for PDF
documents, which we don't handle correctly.
Fixing this bug (for which I need to ask permission to add one string, though)
would basically add a -a/--anchor <name> parameter for the Okular shell (or,
if you have better names, they would be welcome), that would allow to jump to
the specified named destination. This way, you would just need to do:
$ okular some.dvi --anchor 'src:16 ./test.tex'
As said, this will come as a consequence of a bugfix for PDFs, so it will need
a small addition in the DVI backend (the actual resolution of the named
destination to a viewport in the current document). I really hope to have
this in KDE 4.3.
Furthermore, there's something that I would like to improve regarding the
okularpart <-> embedders interaction with source references (ie "please open
the source file foo.xxx, at line Y and column Z). This could be useful for
Frescobaldi as well.
Currently, when the user uses Kile and wants to have source links being opened
with Kile when reading a PDF within Kile, the current way is "go to the
Okular settings and set Kile as editor" (same as with KDVI).
One of the possible idea to improve this would be having the okularpart
emitting a signal like:
void sourceReferenceRequest(QString source, int row, int column, bool& open)
this way, you could just connect to such signal of the okularpart instance,
and in case you want to handle a request of source reference, you would set
the open reference to true, and then handle it yourself.
If true, Okular would then stop there, and don't go further with the editor
If false, Okular would go ahead just like now.
What do you think?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/okular-devel/attachments/20090513/ca9780e8/attachment.sig
More information about the Okular-devel