mantisbt:plugins_feedback
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:plugins_feedback [2007/11/07 10:13] – jreese | mantisbt:plugins_feedback [2014/02/27 03:05] (current) – Bascy | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
====== Plugin Feedback and Questions ====== | ====== Plugin Feedback and Questions ====== | ||
+ | ===== General Suggestions ===== | ||
+ | |||
+ | After reading the documentation, | ||
===== IRC Chats ===== | ===== IRC Chats ===== | ||
Line 10: | Line 14: | ||
< | < | ||
with their own branding, are we going to support this via plugins? | with their own branding, are we going to support this via plugins? | ||
+ | < | ||
+ | unless the user has set $g_top_include_page in their configuration. | ||
+ | As plugins are meant to *add* features and content, rather than modify | ||
+ | the existing functionality, | ||
+ | current form. | ||
< | < | ||
- | page, event before the logo etc. This is important to allow integrating | + | page, event [even? -jr] before the logo etc. This is important to allow |
- | Mantis into websites and CMS. | + | integrating |
+ | < | ||
+ | up $g_top_include_page and $g_bottom_include_page, | ||
+ | rather than trying to make this happen in plugins. | ||
< | < | ||
- | avoid generating our own HEAD/BODY etc, right? | + | avoid generating our own HEAD/BODY etc, right? |
+ | < | ||
+ | resource links in the < | ||
+ | Mantis integrated into other applications (not vice versa a la Dokuwiki) | ||
+ | we could have the < | ||
+ | set. | ||
< | < | ||
Line 22: | Line 39: | ||
* To be answered shortly. | * To be answered shortly. | ||
+ | |||
mantisbt/plugins_feedback.txt · Last modified: 2014/02/27 03:05 by Bascy