FlexWebListPlugin installer installs
GluePlugin for no good reason other than the fact it is used in an example topic.
It is bad to impose another plugin just for a couple of example. Examples should be changed and dependency removed. Isn't this plugin written so the multiline can be done without the odd glue thing?
The dependency is not even documented so it is a total surprise that you end up with a plugin as
GluePlugin (which I really do not want to have installed)
--
TWiki:Main/KennethLavrsen
- 20 May 2008
Ah, the plugin's topic is missing a
%$DEPENDENCIES%
tag so that
BuildContrib would insert them into the text when building the release. But that's all with regards to documenting dependencies. The DEPDENDENCIES file reads:
TWiki::Plugins::GluePlugin,>=1.5,perl,Recommended; Download from TWiki:Plugins/GluePlugin
As you can see,
GluePlugin is not
required but
recommended. If the installer still insists to install
GluePlugin, then this really is not my fault. You can safely disable
GluePlugin. You won't lose much besides the sidebar widgets
FlexWebListNavi
and
FlexWebListTree
not working anymore. Oh, looking at
FlexWebListTree
I will have to add
JQueryPlugin as an
recommended plugin as well.
--
TWiki:Main.MichaelDaum
- 21 May 2008
widgets
FlexWebListNavi
and
FlexWebListTree
???
OK now you mention I notice the
FlexWebListNavi.txt
and
FlexWebListTree
files. Maybe you should document these also by simply listing also these under examples.
This is a plugin and it is your decision which dependencies you wish to have. Please interpret my report as
suggestions more than a bug report.
I tried to remove the Glue from the widgets but that will not work unless you also transforms the expressions to very long lines. So I understand your motive for using Glue. I believe there is also an additional dependency on another plugin related to extended IF.
--
TWiki:Main.KennethLavrsen
- 21 May 2008