Thank you all. I do apologize for repeating bug-reports that seem to have already <br>been there... I didn't see any of them in a search, so I just went ahead. <br><br>I'll definitely take a look at the source and see if I can start tinkering with it. Thanks for all the encouragement! <br>
<br>Navneet<br><br><br><div class="gmail_quote">On Wed, Jul 8, 2009 at 4:14 PM, Pino Toscano <span dir="ltr"><<a href="mailto:pino@kde.org">pino@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Hi,<br>
<br>
> I wasn't sure if this mail belonged in the Okular Development mailing list.<br>
> So I had sent a personal mail to Pino first, which I didn't get any reply<br>
> to.<br>
<br>
</div>Sorry for not having replied earlier, but given that your email was quite long<br>
and not the only one to reply in (limited) time, I started writing bits for<br>
its reply offline.<br>
<div class="im"><br>
> 1. Additional functionality for annotations in PDF files : Default values<br>
> of opacity, width, font size, etc should be adjustable.<br>
<br>
</div>Ok.<br>
<div class="im"><br>
> Another thing I<br>
> find very annoying is that Highlighting is not possible neatly in a<br>
> 2-column file. Is it not possible to figure out that a file is in 2-column<br>
> format (some hack like looking for a vertical line of blank space, maybe?)<br>
> and adapt the Highlighting feature accordingly?<br>
<br>
</div>If it would have been easy it was there already ;) This is reported already as<br>
bug #161324.<br>
Basically, the work is figuring out how to layout the text entities we have<br>
(each text character+its position in the page), recognizing also things like<br>
"²" (which have a bounding box slightly up wrt the other ones in the same<br>
"text line"), etc.<br>
<div class="im"><br>
> 2. This should be simple: just a "Back" button in the navigation toolbar<br>
> (at the bottom of the window) so that it's easy to go back after you've<br>
> clicked on a link (a hyper-reference in a pdf file).<br>
<br>
</div>This was bug #192143 already.<br>
<div class="im"><br>
> 3. Library management : Would it be possible to have a management of files<br>
> on the personal computer from within Okular?<br>
<br>
</div>As written in the bug report, we decided time ago to not going this route.<br>
The reasons are various: adding those functionalities inside Okular is simply<br>
overloading a viewer with stuff which don't belong to it. Also, given that<br>
Okular provides a KDE KPart (okularpart), it is fairly easy (~5 LOC) to load<br>
and embed it in any KDE application.<br>
That said, we encourage any external application doing that, and using the<br>
okularpart for allowing the user to view documents.<br>
<div class="im"><br>
> Another useful feature would be a snapshot of links in files, in particular,<br>
> links within the file. For example, if you could see a snapshot of an<br>
> equation, a publication reference (just the citation at the end of the<br>
> paper, say) or a figure when a reference to the item occurs in the file.<br>
<br>
</div>Loading external links is not cheap, so this might not feel "smooth". There's<br>
also the privacy concern, ie somebody could know you are reading a document<br>
because you are hovering a link and downloading another document/file from the<br>
Internet.<br>
For links to local pages, there's bug #128434 (originally for KPDF, which I<br>
just moved, as KPDF will not have it anyway).<br>
<div class="im"><br>
> I am an undergrad EE student with some programming experience, but no<br>
> software development (nothing >1500 lines of code!). I would be interested<br>
> in joining the development team to help with these aspects, if possible. Is<br>
> there a large barrier to entry, in terms of size of code or lack of<br>
> experience?<br>
<br>
</div>Theorically there's no "large barrier"; although being "big" (even if not that<br>
much, actually), Okular' source code is more or less "divided" into various<br>
parts, for example the core library, the ui parts for<br>
viewing/annotating/forms/etc. Of course some components show their complexity<br>
(like the Document, the PageView - which is more than 4k LOC -), but I'd say<br>
that generally the trick should be understanding first the system behind page<br>
generation and visualization. Once understood that, allthe other pieces can be<br>
(more or less) easily related to it.<br>
<br>
--<br>
<font color="#888888">Pino Toscano<br>
</font></blockquote></div><br>