joshpeterson / biblestudy Goto Github PK

I think the following operations need notification in the status bar:

• Search
• Translation loading

The current build process is not automated. It should be.

Maybe QTest would work, or maybe C++Unit.

Some possible search options are:

• Case in-sensitive search
• Search for each word with an and query by default
• Search for quoted strings exactly
• Omit common words from the query

A few quick tests show that the behavior of some of the buttons is inconsistent near the beginning and the end of translations.

It would be nice to get long running operations, like searching and translation loading off of the GUI thread so that the application remains responsive.

For an example, see the Qt Mandelbrot example at:

http://doc.trolltech.com/4.4/threads-mandelbrot.html

Once, the search results are sorted, there is now way to return to the original sort order right now. I suspect this should be a RMB option on the search results.

In the current state, the GUI can take a little while to start up. It is waiting for the translations to load. We should push the translation load to after the GUI starts.

It would be nice to be able to save and resume and entire project. I wonder if it is possible to actually auto-save the project after each change.

Search for the word "sword", then use the filter search results field to type the word "word". It looks like the filtering is not applied. If I type "word of God", the filtering works.

I think that we need an RMB option on the search results to clear the filter. Currently, the user has to delete all of the text in the filter entry dialog, which is a bit clunky.

We should at least have one DLL which encapsulates the bible database functionality, which does not use Qt. Maybe we can have another DLL to hold all of the Qt stuff (the models and views).

Currently, translations load relative to the working directory. They really should be loaded relative to the executable, so the working directory will not matter.

Create an installer (hopefully cross-platform) to handle in the user installation of the application.

This should contain at least:

• A description of the application
• A list of dependent libraries and there versions
• A guide to building the application

This should mean that we simply need to clear the proxy model for the search results when a search is complete.

Determine which prerequisites need to be deployed with the application and write some scripts to handle the deployment. This will also include compressing the translations.