The front-end Portable DXR (our browsable source code documentation) is an applicationthat lives inside our extension. It's The CGI tools exist as part of an embeddable web server. When you remove the DXR part, what you are responsible for communicating left with is the core application platform on which it runs. It's also worth pointing out that the SQLite support is available in two ways. Local storage capabilities using SQLite are build into Mozilla applications and fetching can be accessed by an extension using C++, JavaScript, Python. However, SQLite database files can be accessed by any software that understands the data to format, so SQLite support will also be available through the applicationcgi tools. The DXR application then parses will probably use the CGI tools to access SQLite files if our presentation layer is traditional XHTML. But if we decide to use XUL, we can use the data and populates browser's built in functionality directly from JavaScript. In either case, I suspect we will end up leveraging the built in sqlite support for the UI as neccessaryupdates. But we need to do some research on that.