Reply to thread

Message

AW: MP2 - Development Suggestion - Web Configuration Interface

Very short answer:
MP2 is designed to provide several ways of configuration. The config engine provides all configuration settings to the system and it provides an API to read/set/upate the settings. A config program only needs to access that config API. Currently, we have a plugin for the MP2 application (shown in the settings menu point) and we have a standalone config application (which doesn't compile atm, IIRC). To provide a Web UI, you just need to write a plugin which renders the config settings into a HTML page and install that plugin in the client and server - that's all. Even a HTTP server is already included in MP2 and can be used by such a plugin.
Most of the config settings are simple settings which can be rendered by just providing standard renderers - string, number, multi-entry-list, single-entry-list, filepath etc. Some settings are more complicated, for example the shares config. For those more complicated settings, the plugin which provides that setting must provide a kind of plugin for the configuration renderers to make the setting visible in the renderers. For example, the shares configuration is currently only available in the MP2 UI, not in the standalone config app because we currently only provide a renderer plugin for the MP2 config UI.
That's the architecture in short, maybe that already helps a bit.

<blockquote data-quote="Albert" data-source="post: 780507" data-attributes="member: 67886">AW: MP2 - Development Suggestion - Web Configuration InterfaceVery short answer:MP2 is designed to provide several ways of configuration. The config engine provides all configuration settings to the system and it provides an API to read/set/upate the settings. A config program only needs to access that config API. Currently, we have a plugin for the MP2 application (shown in the settings menu point) and we have a standalone config application (which doesn't compile atm, IIRC). To provide a Web UI, you just need to write a plugin which renders the config settings into a HTML page and install that plugin in the client and server - that's all. Even a HTTP server is already included in MP2 and can be used by such a plugin.Most of the config settings are simple settings which can be rendered by just providing standard renderers - string, number, multi-entry-list, single-entry-list, filepath etc. Some settings are more complicated, for example the shares config. For those more complicated settings, the plugin which provides that setting must provide a kind of plugin for the configuration renderers to make the setting visible in the renderers. For example, the shares configuration is currently only available in the MP2 UI, not in the standalone config app because we currently only provide a renderer plugin for the MP2 config UI.That's the architecture in short, maybe that already helps a bit.</blockquote>

[QUOTE="Albert, post: 780507, member: 67886"] [b]AW: MP2 - Development Suggestion - Web Configuration Interface[/b] Very short answer: MP2 is designed to provide several ways of configuration. The config engine provides all configuration settings to the system and it provides an API to read/set/upate the settings. A config program only needs to access that config API. Currently, we have a plugin for the MP2 application (shown in the settings menu point) and we have a standalone config application (which doesn't compile atm, IIRC). To provide a Web UI, you just need to write a plugin which renders the config settings into a HTML page and install that plugin in the client and server - that's all. Even a HTTP server is already included in MP2 and can be used by such a plugin. Most of the config settings are simple settings which can be rendered by just providing standard renderers - string, number, multi-entry-list, single-entry-list, filepath etc. Some settings are more complicated, for example the shares config. For those more complicated settings, the plugin which provides that setting must provide a kind of plugin for the configuration renderers to make the setting visible in the renderers. For example, the shares configuration is currently only available in the MP2 UI, not in the standalone config app because we currently only provide a renderer plugin for the MP2 config UI. That's the architecture in short, maybe that already helps a bit. [/QUOTE]