forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject Re: Plugins can now provide xconf file
Date Wed, 03 Aug 2005 11:18:06 GMT
Thorsten Scherler wrote:
> On Wed, 2005-08-03 at 11:05 +0100, Ross Gardler wrote:
> 
>>In order for us to use the Cocoon Portal Engine as a layout engine (or 
>>just to experiment with it at this stage) we will have to integrate 
>>portal block into Forrest. This will be a breeze when real blocks arrive 
>>in Cocoon, but in the meantime we will have to use an internal plugin.
>>
>>Problem is the Cocoon Portal Block provides an xconf file.
>>
>>I've just committed some new plugin code that allows a plugin to provide 
>>additional configuration information to cocoon.xconf. Simply place your 
>>*.xconf file in PLUGIN_HOME/conf/*.xconf.
>>
>>Note that changes to this configuration file will not take effect until 
>>Forrest has been restarted.
>>
>>My next task is to create a Portal internal plugin as a forrest:views 
>>implementation, but I figured this part might be useful for other devs 
>>so committed early.
>>
> 
> 
> Can you setup a basic portal plugin? I will then play around with it.
> Right now I am just tweaking some portal stylesheet on my local
> harddrive, but as soon we have the plugin I can do it here.

That is my intention, but I don't have the time for at least a few days 
(other than an hour here and there).

Ross

Mime
View raw message