Sure drop it into /src/trunk. I'm not at all for complicating things, I hate diving into complicated code bases <g> -- but I guess it really depends on what features we want to offer. What about maybe a "plugin" system. Qt I believe has all the hooks for making a working plugin system. That would allow a basic simple Bible program for release, with little comlication. But then allow us/others to make enhancements for those who want it. So if person A want commentaries; he downloads the "commentaries" plugin which allows them to be viewed and handled. etc. If person B wants ability to take notes, it would be a plugin. If person C wanted maps; it would be a plugin. We could technically make the "sword" engine a plugin. Then if we do decide to make a engine compatible with a third party format it is just another "plugin" that is added to the system. Thoughts? That does "complicate" it a bit more initially, but it would make keeping things a bit more simple for those who actually want a simple reader w/o all the bells and whistles. ;-) Nathan.