Hi, After discussing with Taras during FOSDEM, I've put some thoughts on how to make DXR rock and have some appeal in the community.
Currently, I see some weaknesses that may hurt DXR massive adoption. IMHO, this should be fixed before speaking more about DXR. 1) Indexing consume too much memory, making it impossible to use on less than high-end server. 2) DXR is too tight to mozilla-central 3) Indexing is currently too slow (is it really a problem?) 4) DXR is hard to install and to use. 5) I still don't have a clear picture on how to use one DXR instance with multiple repositories Regarding 2), we have identified the HG link and are currently trying to put that in a config file. 1) and 3) looks rather critical because, for now, you need an high-end machine and lote of time just to test it. For 4), Carlos think that DXR should use autotools (or, I would say, python-distutils). That would allow easy installation and, even more, distribution packages. We should also make some clear shell commands : index, deploy. Even a small PyGTK gui might be done quickly. Anyway, lot of opportunity there. So, what are, in your opinion, the priorities of DXR as an OpenSource project? Should we try to make a roadmap? Lionel _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
