Strict Standards: Non-static method Flyspray::absoluteURI() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/constants.inc.php on line 29 Strict Standards: Non-static method Flyspray::get_tmp_dir() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/constants.inc.php on line 78 Strict Standards: Non-static method Flyspray::base_version() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 29 Strict Standards: Non-static method Flyspray::base_version() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 29 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 39 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Req::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 40 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/header.php on line 42 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::enum() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 15 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 37 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::enum() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 37 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 21 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 21 Strict Standards: Non-static method Cookie::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 28 Strict Standards: Non-static method Get::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 36 Strict Standards: Non-static method Get::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 100 Strict Standards: Non-static method Get::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 95 Strict Standards: Non-static method Get::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 100 Strict Standards: Non-static method Flyspray::requestDuplicated() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 104 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/index.php on line 143 Strict Standards: Non-static method Req::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 15 Strict Standards: Non-static method Req::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Req::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 26 Strict Standards: Non-static method Filters::num() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 32 Strict Standards: Non-static method Flyspray::GetTaskDetails() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 17 Strict Standards: Non-static method Flyspray::GetAssignees() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.flyspray.php on line 358 Strict Standards: Non-static method Get::val() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 34 Strict Standards: Non-static method Get::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.gpc.php on line 100 Strict Standards: Non-static method Post::has() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 34 Strict Standards: Non-static method TextFormatter::render() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/scripts/details.php on line 128 FS#276 : 1.2.0 - Make build-system more modular, plugin-example, plugin's docu
homepage | forum | wiki | feature requests & bugs

MMS

Before posting a bug report please read: http://wiki.mymediasystem.org/wiki/index.php/Bug_reports
Tasklist

FS#276 - 1.2.0 - Make build-system more modular, plugin-example, plugin's docu

Attached to Project: MMS
Opened by Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 281 Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Wednesday, 15 August 2007, 18:47 GMT+2
Last edited by Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Tuesday, 12 August 2008, 10:14 GMT+2
Task Type Feature Request
Category Backend / Core
Status New
Assigned To No-one
Operating System Linux
Severity High
Priority Normal
Reported Version 1.1.0
Due in Version 1.2.0
Due Date Undecided
Percent Complete 0%
Votes 2
  • Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 281 Pablo Castorino (castorinop) ( Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 2008-06-17)
  • Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 281 Lutz Thielemann (magicamun) ( Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 2008-04-02)
Private No

Details

Right now we have every plugin integrated within MMS ... meaning that it is possible to en-/disable them with configure.

If we want more new plugins, we need to provide a framework (plugin-example) and a new build-system, which is able to compile plugins, even if they are not integrated. For instance something like:
make PLUGINS
&
make PLUGINS clean

which builds all plugins sitting within plugins/
Therefor a plugin should have it's configure-parameters included in it's Makefile like:
WITH_???=1/0
WITHOUT=1/0

Another one:
Each plugin should have it's own README, COPYRIGHT, etc. ...

This task depends upon
Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 189 FS#163 - 1.2.0 - Separate core-configs and plugin-configs
Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 189 Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 301  FS#164 - Separate core translations from plugin translations 

View Dependency Graph

Comment by Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Monday, 31 March 2008, 18:16 GMT+2
This one is goal for 1.2.0, isn't it?
Comment by Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 281 Anders Rune Jensen (arj) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Thursday, 03 April 2008, 18:39 GMT+2
yes
Comment by Roman (Uatschitchun) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /var/kunden/webs/mms/flyspray-0.9.9.6/includes/class.tpl.php on line 613 Sunday, 26 April 2009, 09:45 GMT+2
I just want to bring this one up to attention again ;)

In my eyes, this one is the essential step to do within 1.2.0! Build core and plugins apart from each other. So MMS' core should provide a set of devel files, which plugins are able to use for to compile.

I guess this needs a huger change to upstream, so it should be done better sooner than later ...

'mms -v' should only note the configure settings for core then and list installed plugins by looking them up within install-path.

For startup we have two possible ways:
Start core and load all plugins found in plugin's path (like it is now)
or
start core with:
mms -P plugin_name -P plugin2_name ...
so the user is able to tell what plugins should be used
Maybe both ways are possible with a parser script, checking what plugins are in plugin's path and load each of them with -P ;)
Advantage:
No deinstallation of plugins is needed for to not have it loaded ...

A major change would also be needed regarding developing.
Imho each plugin should get it's own place in bzr

With these steps we open up MMS for external developers a lot! With these steps we would ease package building a lot! With these steps we start a new age of MMS buidling making it future safe ;)

So, what's your opinion?

Loading...