Hey, this is not my GSoC final report. 🙂
I didn’t expect to be still talking about my work on Tracker at this time, but Martyn Russel has made some nice suggestions of modifications to my code on his review of my patch. The ‘IndexMount’ DBus method has been exchanged for an ‘IndexFileForProcess’ DBus method. It’s a more generic mechanism which allows Tracker to index files on a client-application basis.
It works almost equally to the old ‘IndexMount’. Receives a request-to-index a file/directory/mount-point and watches the bus name of the calling application. It stops the indexing process when no bus names are associated to the file.
I am not that late, I am also working in Documents. Currently Documents loads plugged-in removable devices, uses the Tracker mechanism I’ve described in the previous paragraph to index them, and creates a Device Collection into the overview containing documents inside the device.
I am preparing a preview for my GSoC Final Report (that I will post tomorrow).
See you! 😉
Hey! I’ve finished the work that was necessary on Tracker to make it better able to serve Documents and other applications. I just need to get my patch reviewed and perform the necessary alterations.
By the way, It actually took me more time to get DBus working on JHbuild than tying the DBus method to the tracker-miner-fs‘ method which I wrote before. I bypassed it by following this old Murray’s blog post.
So, how useful is it?
To begin with, a typical scenario would be an application sitting on Tracker (such as Documents), which wants to tell the file-system-miner to index a given mount (by indexing, I mean crawling the mount point for files AND adding the device as datasource on the Store).
Besides, the most obvious scenario we want to avoid is when an application, which calls off directly a miner method, crashes. It would cause the indexing operation to fail.
In doing so, we have chosen a different approach using DBus. Now you can send a message to the /org/freedesktop/Tracker1/Miner/Files/Index object, with a mount-point-uri as parameter, and it will tell the tracker-miner-fs daemon to index the Mount accordingly. It also avoids unnecessary crawling of Mounts when more than one application wants their content.
Front-end side: using this mechanism in Documents…
From now on, Documents lists on plugged-in removable devices as collections on the overview. By clicking on a Device Collection, you get it indexed.
A couple of things that I consider essential are:
- Let users Import documents from a device (maybe exporting?)
- Do not index already imported documents
That’s all folks!
I’ve had such a wonderful time at this year’s GUADEC. It was a great opportunity of making new friends, meeting awesome rockstars/ninjas, and visiting a beautiful [and delightful] city. I’ve fallen in love with A Coruña. It’s definitely a place I’d love to live on.
One of the things that I cannot forget is to thank the GNOME Foundation for sponsoring my trip. The accommodation was wonderful. We’ve had great discussions about all kind of things on the Rialta’s cafeteria.
Besides, we’ve had a Documents meeting to discuss bugs and enhancements. It was very productive. So expect brand new features on your favorite documents management app. 🙂
Thank you all!
They say time goes faster when you are having fun. This first-half of GSoC has passed in a blink of eye, really! Despite having a hard time conciliating GSoC with my university duties, this period is definitely something I would love to experience again.
During this first-half of the program my mentor (Cosimo Cecchi) has been so patient in helping me toward achieving my goals and has been always available to answer my doubts. Grazzie Dude!! 🙂
So, let’s face the second-half of the Summer! o/
I almost forgot to announce that I’m attending GUADEC in A Coruña, Spain. I’m sure it will be a great opportunity to go deeper into GNOME development, meet new people, make new friends and put faces on names I see on mail-lists/IRC.
Thanks to the GNOME foundation for sponsoring me!
See you there! o/
Hey, it’s been almost two weeks since my last report, but I’m still here working. I am [finally] free of my university exams, i. e., GSoC is my new full-time occupation. 🙂
In my last report, I described a method that I was working on which adds a mount point easily to the tracker store. It’s now finished!
So I’m now working on tying this method up to the DBus name of the calling application. I’m getting familiar with DBus and this code will be available ASAP on my tracker repository on GitHub.
I’m a little late on my report, but [finally] it’s here now. It’s been hard to conciliate college and GSoC but I’m making good progress on my task.
As I told you before, my first task is to make Tracker capable of indexing files on removable devices on an application basis (on demand). It means making the Tracker API easily capable of receiving calls from applications to index a given device.
Currently, Tracker uses a GSettings key to flag whether or not removable devices and optical discs should be indexed. In these first 3 weeks I’ve worked on a mechanism to escape the strict duality dictated by these GSettings keys.
I’m working on building a method for tracker-miner-fs which receives a GMount object as a parameter, adds this GMount to the Tracker Store, and call the indexer to perform its job.
The next step is to tie these mechanisms up to the DBus name of the calling application in order to finally make it work on an application basis (on demand).
You can hit me anytime on IRC. Let me know if you have doubts/questions/suggestions.
This period between the accepted students announcement and the hands-on part of GSoC is called the ‘Community Bonding period’. It’s when students meet their mentors/community, and read documentation. I have met the awesome Cosimo Cecchi, who’s guiding me in the project. I also have contacted the Tracker community.
My first impressions were great. Everything about Tracker (and GNOME libraries in general) is pretty well documented.
In addition to that, I had my blog added to Planet GNOME. I’m glad to be in this planet after so many years reading it daily.
From now on, the Coding period has started. So it’s time to jump straight into coding. Unfortunately it’s not summer in Brazil, so I have classes to attend and exams to take, all this occurring simultaneously with the Google Summer of Code. Fortunately, I have scheduled my classes accordingly so that I have some extra free time to work on GSoC.
In this first half of the coding period you’ll see my work on Tracker. And in the second half, you’ll see my work directly on Documents. I’d love hear your feedback, comments, suggestions, ideas… anything, really.
Yay! I am on Planet GNOME!!
Hi everyone! I’m a 20 years old Brazilian student at UFPel studying Computer Science. For the first time I’ve been accepted into the Google Summer of Code program.
This summer, I will be working with my mentor Cosimo Cecchi on Documents in order to make it able to manage and view files on plugged in removable devices. To accomplish that, I’m also going to work on Tracker.
I will keep you updated about my progress. Stay tuned. Same bat-hour, same bat-blog. 🙂
It is winter in the Southern Hemisphere, but it is going to be warm because my GSoC proposal was accepted.
I am going to work on Documents in order to make it able to manage and view files on plugged in removable devices. This is a feature proposed by Cosimo Cecchi, who is my mentor in the program.
In this blog I am going to log my progress weekly. Keep tuned for updates here!