[bt-devel] ideas

[Martin Gruner]

> Hi!
>
> > Proposal: we could offer the configuration option "optimize bt for speed
> > or for memory usage". The module key caches could be deleted, if bt was
> > otimized for memory usage. (just an example)
> > But better would be to find a clever way to optimize bt for speed and
> > memory usage. It has improved a lot up to this point, good work!
> > But what i see is that bt will always use more memory if you open modules
> > etc., but not less when you close them.
>
> Should this option be for runtime or compilation time?

Runtime, but I think it was no good idea. It is no solution -- speed would 
slow down dramatically. We must optimize in other ways...

> > The search result page layout nedds to be changed: i normally only see
> > the result verse list when i resize the whole dialog, because the module
> > names are so long. maybe each of them shold get 50%? Or we could use the
> > short module names instead?

Before we release 1.0, one thing I would want: we should implement parallel 
viewing of 
a) bible passages (best solution: html tables -- similar to bibleworksop)
b) commentary entries (also?? -- view several commentaries in parallel)
c) lexicon entries (same??)

It should be possible to synchronize (former autoscroll button)
a) a commentary presenter to a bible presenter (current key)
b) a lexicon presenter to 
 1) words that were highlighted(and right-clicked), 
      clicked or maybe just mouse moved over?
 2) strong numbers

These are just proposals for discussing. Maybe it is impossible.
I am sorry but at the moment I cannot help coding. :(

Please comment everybody, especially those who are not coding! What features 
would you like to see?

Maybe we need a place (website) to collect feature requests from users?


Martin