gtg-gsoc team mailing list archive

[Paul Natsuo Kishimoto <mail@xxxxxxxxxxxxxxxxxxx>]

On Fri, 2010-05-21 at 21:20 +0200, Luca Invernizzi wrote:
> On Fri, May 21, 2010 at 01:48:14PM -0400, Paul Natsuo Kishimoto wrote:
> >  * For backends offered by plugins, does the PluginManager notify the
> > BackendTypeManager that a new backend is available, or does the latter
> > query the former?
> > 
> >         (This also makes me wonder if it is worth distinguishing
> >         backends and plugins, i.e. no longer "plugin X provides backend
> >         Y". If we later have client (UI) / server separation, plugins
> >         will go with the client, backends must stay with the server,
> >         roughly.)
> I always thought plugins and backends  to be completely separated things. I find
> that saying to a user "enable plugin X  and you will have backend Y available to
> configure" is extremely confusing.
> In my idea, Backends do their job alone.  if a plugin wants to mimick a backend,
> it will have to do it by itself (I mean, it will need to contain all the code to
> do  that or  to trick  somehow the  normal flow  of GTG  - like  the RTM  plugin
> currently does).
> I really  don't see  how providing  a normal  Backend though  a plugin  would be
> useful.  Maybe you  could  help me  here.  The plugins  which  currently act  as
> backends will continue to work normally.
> 
> In short, I see Backends working at the very bottom of GTG layers, while plugins
> work at the very top, alongside with the UI.

  We are in agreement, then...when I said "if it is worth" I was hinting
that we *should* separate the two.

-- 
Paul Kishimoto
MASc candidate (2010), Flight Systems & Control Group
University of Toronto Institute for Aerospace Studies (UTIAS)

http://paul.kishimoto.name — +19053029315

Attachment: signature.asc
Description: This is a digitally signed message part