[bt-devel] BibleTime Search

[Joachim Ansorg]

Hi,

> > Copying the progress dialog code creates redundant code. We should try to
> > avoid that, as it means more work, more maintainance and more bugs :)
>
> Well, in this case the code redundancy would be there, but it would be
> minimal. I'm pretty sure that your solution would require more actual code.
> In the end the frontend calls the backend, which in turn calls frontend
> functions with signal/slot, and then returns to the frontend.

I prefer cleaner over quick, but dirty  solutions, as we save a lot of time in 
the next few years.
Maintaining hacked code is a pain :)

> > We'd probably need a layer in between for things like the progress dialog
> > connection.
>
> This depends on where it is needed, I would say. Then you have
> backend<->"middleware"<->frontend.
> Things will probably become more and more complicated the more layers there
> are.

Yes, we should be careful when we introduce new layers.
At the moment the current backend / frontend implementation is really not a 
clean solution.

> I guess it would be useful to make the interfaces of backend and frontend
> more generic/abstract, but hopefully without an additional layer in
> between.

Yes, that's probably the way to go.

> Joachim, I just looked at your proposal (task list on sf) for the
> keychooser. Why do you think it is not generic enough? Do you really want
> to create a document/view model for such a simple widget?

We could reduce the number of keychooser implementations to one single classif 
we use a tree for navigation.
At the moment we have 3 implementations which share a lot of code.

The same is probably valid for the display window stuff.

Joachim