Page "Proposals/BEP-0003" was changed by olemis Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=11> Revision 11 Comment: [BEP-0003] Product logo as another special case of product-specific settings Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: Proposals/BEP-0003 ========================================================================= --- Proposals/BEP-0003 (version: 10) +++ Proposals/BEP-0003 (version: 11) @@ -77,7 +77,8 @@ {{{ #!py ->>> ps = product.api.MultiProductSystem(product_env) +>>> from multiproduct.api import MultiProductSystem +>>> ps = product_env[MultiProductSystem] >>> repr(ps) None }}} @@ -110,7 +111,7 @@ === Product components ecosystem #components -All the functionalities installed in the global environment (e.g. blogs, pastebins) should be available for products as well. Nonetheless they should be enabled/disabled on a per product basis. +All the functionalities installed in the global environment (e.g. blogs, pastebins) should be available for products as well. They may be enabled/disabled on a per product basis. {{{ #!div class="well" @@ -119,7 +120,7 @@ Implementation notes }}} -Product environments are meant to implement `trac.core.ComponentManager` API and inherit global plugins installations by design. Hence every component class will have a singleton instance for each product (besides the one for the global environment). Components are enabled/disabled via `[components]` section in configuration file. The fact that each product will have a [#config separate configuration file] also means that there will be one such section to enable/disable each one on a per product basis. +Product environments are meant to implement `trac.core.ComponentManager` API and inherit global plugins installations by design. Hence every component class will have a singleton instance for each product (besides the one for the global environment). Components are enabled/disabled via `[components]` section in configuration file. The fact that each product will have a [#config separate configuration file] also means that there will be one such section to enable/disable each class on a per product basis. This situation is quite similar to what happens nowadays in multi-environment installations. @@ -145,6 +146,21 @@ }}} The following requirements are a corollary , considering that such customizations are performed in the configuration file. + +==== Product logo #logo + +On accessing resources owned by a product its logo and description will be shown. + +{{{ +#!div class="well" + +{{{ +#!span class="label label-info" + + Implementation notes +}}} +Edit `[header-logo]` section in `product-<product prefix>.ini` file. +}}} ==== Per product ticket workflow #workflow @@ -241,7 +257,7 @@ == Rejected ideas #rejected -Many interesting ideas have been proposed but not all could make their way into final specification because of conceptual, practical or other reasons. Below you'll find the most relevant instances together with brief comments explaining the decision , and maybe links to relevant messages in [http://mail-archives.apache.org/mod_mbox/incubator-bloodhound-dev/ bloodhound-dev mailing list archive] . +Many interesting ideas have been proposed but not all could make their way into final specification because of conceptual, practical or other reasons. Below you'll find the most relevant instances together with brief comments explaining the decision as well as links to relevant messages in [http://mail-archives.apache.org/mod_mbox/incubator-bloodhound-dev/ bloodhound-dev mailing list archive] . '''TODO''' : nothing rejected so far. -------8<------8<------8<------8<------8<------8<------8<------8<--------
-- Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0003' page. If it was not you, please report to .
