RE: Blackboard

Hello!

In the plugin api, each plugin could have two indicators: plugin type and
plugin name.

So, a plugin for import/export in povray format can have the type "IO
Plugin" and name "Povray v3.x"
A plugin for a new object could have plgin type "New Object" and name "Lens
Flare" for instance.

When the plugin for the new object initializes, if it implements IO for a
given format it could do that that through the following:

bool PluginLensFlare::serialize( format, document )
{
  if( format == "Povray 3.x" )
  {
     printPovrayCode( document );
     return true;
  }
  else if( format == "RenderMan" )
  {
     printRendermanCode( document );
     return true;
  }
  else
     return false;
}

When the IO plugin needs to serialize an object it calls the serialize
method of the objects plugin for it's specific format.

It only makes sense to create a new object if you provide a way to serialize
it in at least one format. If it can't be serialized in one plugin the io
plugin should ignore the object.

This has one problem however, when the user downloads a new object, it won't
be clear if the object can be serialized on the format you're using.

Will adding a plugin manager that shows what services each plugin implements
help?

Plugins can be a real mess. :(
	
Luis Passos Carvalho


> -----Original Message-----
> From: Andreas Zehender [mailto:[email protected]]
> Sent: domingo, 14 de Julho de 2002 22:34
> To: [email protected]
> Subject: Blackboard
> 
> 
> Hi!
> 
> I have just written down the ideas from the last discussions
> You can see it at http://www.kpovmodeler.org/blackboard.html
> 
> Please send me the missing or additional ideas and I will add them.
> 
> Andreas
> 
> -- 
> --------------------------------------------------
>  Andreas Zehender, Dipl. Ing. (BA)
>  Student, 10th semester computer science
>  http://www.azweb.de
>  [email protected] | [email protected]      
> --------------------------------------------------
> 
> 
> List archive and information: 
> http://mail.kde.org/mailman/listinfo/kpovmodeler-devel
> 

List archive and information: http://mail.kde.org/mailman/listinfo/kpovmodeler-devel