mantisbt:addson_requirements
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:addson_requirements [2007/09/06 10:40] – DGtlRift | mantisbt:addson_requirements [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 205: | Line 205: | ||
* Detail the parameters sent to each of the events. | * Detail the parameters sent to each of the events. | ||
* How are the plug-ins going to be distributed. | * How are the plug-ins going to be distributed. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
Line 217: | Line 223: | ||
* I'm also thinking that it may be easier to use a hash table to store the constants in # | * I'm also thinking that it may be easier to use a hash table to store the constants in # | ||
* Perhaps XML would be better for having this info | * Perhaps XML would be better for having this info | ||
+ | * (deboutv) In my plugin manager, I have chosen to provide Mantis plugin in pkg format. This file is the result of a zip and a serialize of an array => gzcompress( serialize( array ), 9 ); The array contains the following fields: | ||
+ | < | ||
+ | $t_pkg[' | ||
+ | $t_pkg[' | ||
+ | // | ||
+ | $t_pkg[' | ||
+ | $t_pkg[' | ||
+ | $t_pkg[' | ||
+ | $t_pkg[' | ||
+ | </ | ||
+ | * (deboutv) Hacking Mantis with a plugin. We need to think about the security of the Mantis application and its data. Allowing plugins is dangerous because of the content of the plugin (it could pretend to be a BBCode interpreter but in reality it could be a BBCode interpreter and a spy). With a plugin (ie: code of third parties), you can read/write the SQL database, grant priviledges to the users... | ||
+ | * (DGtlRift) There should also be a description of how plugins themselves should generate events. | ||
+ | * (DGtlRift) Re: Distribution. | ||
+ | * The most simple way is to just have a list of tar.gz compressed archives of each plugin. | ||
+ | * The next option would be to offer the ability to install via the admin interface, where Mantis would check against a web list of available plugins and download (to the server) and install the plugin (requiring Mantis to have write privileges) to the plugins directory. | ||
+ | * Another option is to have all the plgins in RPM form - which would automate installation for the sysadmin. | ||
+ | * (DGtlRift) Should the plugins be globally " | ||
==== First implementation ==== | ==== First implementation ==== |
mantisbt/addson_requirements.1189089623.txt.gz · Last modified: 2008/10/29 04:31 (external edit)