New panel framework

[Jasper Huijsmans]

Benedikt Meurer schreef:
> Benedikt Meurer wrote:
> 
>>>>I think I'm missing something here.  How does the panel know about these
>>>>external plugins?  Unless I'm misunderstanding, the external plugins
>>>>don't talk to the panel at all until their binary is run.  But how does
>>>>the panel find out about external plugins so it can list them in the
>>>>"Add Item" dialog?  Assuming there's a separate mechanism for this,
>>>>letting language bindings write plugins shouldn't be a problem at all.
>>>
>>>Hehe, I guess I forgot to mention something here...
>>>
>>>Yeah, you're right. It uses .desktop files (in 
>>>${prefix}/share/xfce4/panel-plugins/) to describe the plugins.
>>>
>>>[Xfce Panel]
>>>Name=Test Plugin
>>>Comment=This plugin has no purpose
>>>Icon=xfce-unknown
>>>External=true
>>>FullPath=/home/jasper/experimental/libexec/xfce4/panel-plugins/testplugin
>>
>>
>>Since this is a .desktop file, we should follow the spec here and use
>>vendor ids for the two non-standard keys:
>>
>>X-XFCE-External=true
>>X-XFCE-FullPath=/home/jasper/experimental/libexec/xfce4/panel-plugins/testplugin
> 
> 
> BTW: Is there a reason to not just use Exec for the command?
> 

Hmm, if external is 'false' FullPath points to the loadable module instead.

Alternatively, I could get rid of the 'External' key and use 'Exec' for 
external plugins and 'X-XFCE-Module' for internal plugins.

	Jasper