Since I have a job I can’t spend as much time in ePDFView as I want, so its development slowed down a lot.

This week end I was able to add support for URI links besides the already supported internal links. In order to do this, I also had to add a new preferences dialog asking to the user which command line to use to execute the web browser when such a link is activated. The default is to use Firefox because I think is the most extended browser in GNU/Linux desktop world.

I really don’t know if this is really a good idea for handhelds users that are using ePDFView since I don’t have any and can’t test it.

I hope next time I write and update is to tell you that I have added printing support as it seems to be the most wanted missing feature.

Yay! Finally I was able to find a job after a month or so of job hunting.My new job now involves software as well as hardware. The hardware part is the most exciting, as I never had a job dealing with hardware at this level (I don’t consider tech support as a hardware job…).

The software part is like what I’ve done in my spare time. I also like it a lot, even though I have to use Qt. Nothing wrong about it, but I’m more confortable and used to making projects in gtk.

I do hope to have fun with this new job!

Long time no update!

During the past days since my last post I’ve been able to solve the threading problems that I was having. Or at least that is what I think.

I was creating a thread for each background job that the application needed, like opening a file or rendering a page. This made the application too complicated, since in nearly every class I was dealing with thread code. Now I have a simpler approach: I have only one threaded function that waits jobs to be enqueued and, once a job has entered the queue, pops them out and runs them. Of course that means that only one job is in execution at once, but I have found that most jobs don’t take that long, except rendering pages.

I also have made the document classes follow the observer pattern, that way all GUI presenters can attach themselves to the document classes and wait for the document to send notify messages when the document’s states changes. This helped a lot while separating the main window’s presenter and the document page’s presenter, although the SVN version was broken a long period while doing all those changes.

Now I’m trying to implement search functionality that will use a find bar similar to firefox’s find bar. Currently I have implemented the search code in a background job that passes all the tests, but I think tomorrow I’ll have the actual find bar.

I guess that when the find bar is implemented I’ll release version 0.1.4 of ePDFView, leaving the selection options, print features and continuous mode for the next version.