5 Sep 2005 23:00
Re: DCOP interface
[possible resend: I just uncovered this in my drafts folder an I can't remember if it ever got sent] On Sun, 21 Aug 2005, Robby Stephenson wondered: > Here are some thoughts: > > - The DCOP calls should go in Tellico::DCOPInterface, either as virtual > functions, or calls to existing functions somewhere else. You'll probably > end up implementing the actual functionality in Tellico::MainWindow or > Tellico::Kernel. Agreed. > - The easiest way to search is probably to create a filter on the stack and > match all the entries in the collection against it. That's true if you're willing to change the visible state of Tellico as third-party programs carry out searches. There are two separate use cases, you see: - remotely command Tellico `stick this filter on the stack' and so on, so that other apps can drive the Tellico user interface - return filtered output directly, so that other applications can use Tellico as a data source, without influencing the display. Thankfully both of these seem to be easy to implement, but I think they should probably go in separate DCOP interfaces. The influence-the-display stuff might actually belong in tellico-mainwindow, but I'm unclear as to how to add anything to that, since mainwindow.cpp(Continue reading)


RSS Feed