What are you working on? December 2011

jsalvatier

This is the sixth bimonthly 'What are you working On?' thread. Previous threads are here. So here's the question:

What are you working on?

Here are some guidelines:

Focus on projects that you have recently made progress on, not projects that you're thinking about doing but haven't started.
Why this project and not others? Mention reasons why you're doing the project and/or why others should contribute to your project (if applicable).
Talk about your goals for the project.
Any kind of project is fair game: personal improvement, research project, art project, whatever.
Link to your work if it's linkable.

This is the sixth bimonthly 'What are you working On?' thread. Previous threads are here. So here's the question:

What are you working on?

Here are some guidelines:

Focus on projects that you have recently made progress on, not projects that you're thinking about doing but haven't started.
Why this project and not others? Mention reasons why you're doing the project and/or why others should contribute to your project (if applicable).
Talk about your goals for the project.
Any kind of project is fair game: personal improvement, research project, art project, whatever.
Link to your work if it's linkable.

I've tried Eclipse's search before, and it's way too slow for my needs. Also, the Eclipse UI has a lot of annoyances since it's not a native OS X application. It doesn't obey my keyboard map, for example.

I haven't seen grepcode before, but it looks like it builds an index. That's a non-starter for me, since code often changes and I don't want to wait for an index to get rebuilt before searching. If the tool silently rebuilds the index in the background, it's even worse. Then I don't know if the search results are correct or not.

If the tool silently rebuilds the index in the background, it's even worse. Then I don't know if the search results are correct or not.

It doesn't have to mean that. It could respond to your search by walking the directory structure checking last-modification times, comparing them against its index, and updating anything that's been modified.

0Bugmaster14y

I see, that makes sense, but I think that you might be better off with a hybrid approach: build an index first, and do real-time search on all files that have been changed, and thus haven't been [re-]indexed yet. I'm not sure if any of the existing systems do that, but it's worth checking out. Of course, if your codebase is relatively small, performance won't be much of a problem...

12

What are you working on? December 2011

12

12

12

What are you working on? December 2011

12

12