Hi, I've commited a first implementation in my sandbox. Besides from adding new interfaces (which I think need some more work especially the attachment handling), this bundle registers a web console plugin for the configuration status. All new status providers are registered as console plugins under the category "Status" as well and old web console configuration printers are registered as new ones internally.
Carsten 2012/12/4 Felix Meschberger <[email protected]>: > Hi > > Sounds like a good idea. > > Here are some more random thoughts (after a talk to Carsten): > > * Create a new Configuration Status bundle > * Move the ConfigurationRender plugin to this new bundle > (ConfigurationPrinter API remains with the Web Console for now) > * Create improvided ConfigurationPrinter API in the new bundle > * Support WebConsole ConfigurationPrinter service natively or by proxy > * Create Plugin Proxies for ConfigurationPrinter services to > expose them as categorized plugins in the Web Console > (instead of as tabs on the ConfigurationRander page > * Add a "creation time" marker file to ZIP file as a more > accurate representation of the time at which the ZIP file > was created (as opposed to the file name) > * Question: How to request TXT and ZIP files ? > > Regards > Felix > > Am 04.12.2012 um 09:47 schrieb Carsten Ziegeler: > >> Hi, >> >> if we're doing some major work on the web console, I think we could >> also move the configuration printer support into its own bundle which >> is not tied to the web console or the http service. >> This would allow to get status information by a defined api and even >> when there is no web console started etc. This allows for new use >> cases to deal with configration status. >> >> We could also add support for a machine readable format like json to >> the printers. >> >> WDYT? >> >> Carsten >> -- >> Carsten Ziegeler >> [email protected] > -- Carsten Ziegeler [email protected]
