[Xastir-dev] Re: xastir server. et-al

[Owen DeLong]

I'm actually inclined to agree with Gary here.  I think that it should be
possible for the display engine to be independent from the control engine
and still preserve the desired functionality.  Perhaps, for example, there
is a way for the control program to create and own the canvas, and have
share it with the map program.  I think the control program should be
the central point where communication to/from the various other components
is passed (or at least consented, much like a directed net), but that it
should have minimal visibility to the user.  Each component should be able
to register control panels with the control program so that it can provide
the user with an opportunity to control those components, but the control
program, itself, should just be glue and little else.

Just my opinion,

Owen
KB6MER


--On Friday, August 16, 2002 4:03 PM -0400 Gerry Wheeler 
<gwheeler at vmguys.com> wrote:

> On Fri, 2002-08-16 at 14:53, Curt Mills, WE7U wrote:
>>
>> Plugins to me mean a monolithic program that can merge various
>> features in (perhaps at runtime).
>
> Agreed.
>
>> Make small programs that can be
>> linked together in various ways to perform the larger function.
>
> Absolutely.
>
>> The Map
>> program would be the main interface for the user.
>
> This is the part I would do differently. I'd like to see the map display
> program be much more autonomous, for very selfish reasons -- I can see
> uses for it completely separate from Xastir. As I mentioned in my
> original monologue, I'd like to see a map display program that can be
> driven by any program that knows how to send the correct information to
> it, and even by several programs simultaneously.
> --
> Gerry Wheeler      KG4NBB
> VM Systems, Inc.   +1 941 596 2480 x24
> Naples, FL 34109   gwheeler at vmguys.com
>
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at krypton.hscs.virginia.edu
> http://krypton.hscs.virginia.edu/mailman/listinfo/xastir-dev