Serendipity Forums

Hi,

The static page side plugin uses tree structure to represent the links to the static pages. It uses dtree.js to generate the tree.

Serendipity_plugin_category_dhtml_menu uses HTML_TreeMenu to do the same: generating tree, that should be shown in the sidebar.

As a result S9Y uses two packages to do the same (or similar) things. And as visible result, the two trees look differently on the frontpage (at least at my blog).

And here is what I think, and propose:

Why not to make the static page plugin an integral part of the core of serendipity? As consequence the tree generation package will become part of the core too. Then serendipity_plugin_category_dhtml_menu may be rewritten or replaced by something else that uses dtree. Also, the tree view of categories may be coded into serendipity's core too. Another cause to remove HTML_TreeMenu is that this package is not maintained since 2005.

Regards,

Hi!

Why not to make the static page plugin an integral part of the core of serendipity?

Because it makes maintainig the static page plugin harder. We can more often release new plugin versions, but a new s9y version only comes out roughly every 4 months.

Plus, the staticpage plugin is meant to be rewritten in the future, and when it is more compatible with s9y's user management, I'd love to add it to the core.

Plus, one major thing: The dtree thing is not BSD licensed, so we cannot even put that portion into the core.

Best regards,
Garvin