As some (most? none? who knows =P) of you already know, last cycle I worked as a Google Summer of Code intern with Gtk+ and Nautilus. We saw the very positive results of it. And the picky eyes out there noticed that I wrote with these exact words: “While the project is over, I won’t stop contributing to Nautilus. Even with the interesting code, even with all the strange things surrounding it. Nautilus is like an ugly puppy: it may hurt your eyes, yet you still warmly love it.”
So, did I keep with my promises? Oh yeah, I freakin’ did! And here’s what happened:
What’s that, my dear lord?!
Exactly what you just saw: a cleaner, saner and more intuitive search filter editor. Nautilus has very complex but powerful internals, which allows us to do many things. And indeed, there is code for the many options in there. So, why did it used to look so poorly implemented/broken/<insert your bad word here>?
In simple terms: there was no UI to handle that up to now. See it in action:
Obviously, it’s still a work in progress. While I did my best to implement it as clean as I could possibly do – I even refactored a whole class for it! – there still is a long road of reviews and cleanups ahead. And I still didn’t implement the full text search for Tracker backend (believe me, it won’t be easy).
Hope you all enjoy it 🙂