I certainly noticed all the emails :) As it happens I'm in the process of getting started on making some changes myself after promising you a few months ago that I'd do so.
I'm going to fix a few bugs (which don't seem to be listed on SourceForge) and then look at adding the following new functionality:
* Allow reserved words to be specified using a regular expression. Mainly to to fix bug 1832713: Implement case-insensitive language processing.
* Update the processing of includes so any files not found using incprefix are looked up in the database. If a single match is found then the include becomes a link to that file whilst if multiple matches are found then the include becomes a link to the search page for that file.
* Update the detection of symbols so that only symbols for the language of the file being processed are marked up. E.g. C++ symbols won't be shown in a make file etc.
More on the above anon ...
> -----Original Message-----
> From: ext Malcolm Box [mailto:malcolm.box@...]
> Sent: 26 March 2009 18:02
> To: lxr-developer@...
> Subject: [Lxr-dev] LXR project coming back to life
> You might have noticed the recent flurry of activity on lxr-developer
> (assuming anyone is still reading these mails). Thanks to the state
> of the economy, I now have more time on my hands and am planning to
> spend more time working on the LXR. Sorry for the 3 year hiatus - and
> if anyone else wants to take over/become a maintainer I'm more than
> happy to hand over the reins.
> The codebase at SF is now a bit old and tired, and Arne's LXRng has
> some nice new features. My hope/plan is to:
> - Resolve all the remaining bugs reported, and apply any outstanding
> patches etc. to the 0.9.x tree
> - Release v1.0.0 at last
> - Start on a major refresh/overhaul of LXR, merging/incorporating the
> work Arne's done on LXRng.
> Main goals for the overhaul from my point of view are:
> - Much improved browsing experience, using AJAX etc to provide a much
> smoother searching and browsing experience.
> - Move to a proper web framework for the frontend (currently seriously
> considering Django) so that setup, caching, templates and providing a
> RESTful API are all easier.
> - Improve the speed and accuracy of the genxref process
> Any comments or criticism would be welcome!
> Lxr-developer mailing list