AW: Commander Activation changes.

["Baulig, ITS P A800, TR" <MartinB2 deutschepost de>]

IMHO we should reallly use _one_ factory for the commander. This factory
will then register itself with the GNOME
naming service and will be used for all factory activation.

Otherwise, I don't see why we need to have factories at all - if we need to
find & contact the commander's servant anyways
to get the factory, it can also provide a GNOME::Debugger::Commander::new ()
method.

On the other hand, one factory for everything has the advantage that this
factory is the only thing that needs to deal with the
.commander files - ideally all clients / GUIs can talk to that factory to
find & activate a commander.

Martin

> ----------
> Von: 	Dave Camp[SMTP:campd@oit.edu]
> Gesendet: 	Freitag, 24. September 1999 07:36
> An: 	gnome-debugger-list@gnome.org
> Betreff: 	Commander Activation changes.
> 
> 
> I have made some changes to how DebuggerCommanders are located and loaded.
> 
> First of all, I have partially implemented the readdir() solution we 
> discussed earlier.  Backends now install a .commander file that contains 
> the following information:
> 	* name          : The name that clients will use to identify the 
>                           commander.
> 	* display-name  : A human-readable name for the commander.
> 	* description   : A short description of the commander.
> 	* goad-id       : The goad-id of the server to be activated when 
>                           the commander is invoked.
> 	* mime-types    : Mime types of executables that the debugger
> supports.
> 	* languages     : Languages that the debugger supports.
> 
> The file is in a simple XML format.  I haven't implemented the parser for
> the
> last two items yet.
> 
> In order to better support pluggable backends, I have made some changes to
> how
> commanders are activated.  
> 
> Instead of one large commander-factory, each commander will implement its
> own factory.  I have moved the commander-factory directory BACK into ggdb.
> It is now used only for ggdb.
> 
> debugger_commander_client_new_from_factory() now searches the installed
> commanders, and activates the correct server.  This method performs the
> task we had originally set aside for commander-factory.  This is done in
> 8 lines of code, so I don't think a separate server is necessary.
> 
> We should now be ready to implement multiple commanders.
> 
> Cheers,
> -dave
> 
> 
> -- 
> To unsubscribe: mail gnome-debugger-list-request@gnome.org with
> "unsubscribe" as the Subject.
>