Difference between revisions of "Extension talk:Treeview5.php"
(Persistance) |
(Details) |
||
| Line 2: | Line 2: | ||
A more logical way of approaching a treeview in MediaWiki is for the PHP extension part to concentrate on allowing the bullet lists (and maybe numbered lists too) to work recusively with transclusion, and for the tree rendering to be handled by existing JavaScript components such as [http://www.destroydrop.com/javascripts/tree/ DTree] which are very good and packed with features such as persistence between pages. | A more logical way of approaching a treeview in MediaWiki is for the PHP extension part to concentrate on allowing the bullet lists (and maybe numbered lists too) to work recusively with transclusion, and for the tree rendering to be handled by existing JavaScript components such as [http://www.destroydrop.com/javascripts/tree/ DTree] which are very good and packed with features such as persistence between pages. | ||
| − | {{Note|If this extension is going to use an external tool, we could for the | + | {{Note|If this extension is going to use an external tool, we could for the fork and rename of the extension to [[Extension:Dtree.php]], as it is now going to be an interface to a javascript application. There is currently no extension on MediaWiki called [[MW:Extension:Dtree]].}} |
[[Extension:Treeview4.php|Treeview4]] already handles the recursion aspect well and has been written in a much more modular way than [[Extension:Treeview.php|Treeview3]] allowing it to be independent of the tree rendering. But with this version I'd like to make the list-recursion work without any parser-function syntax at all - i.e. essentially to fix the MediaWiki parser's limitation of not allowing transclusion to work properly with lists as in the following example. | [[Extension:Treeview4.php|Treeview4]] already handles the recursion aspect well and has been written in a much more modular way than [[Extension:Treeview.php|Treeview3]] allowing it to be independent of the tree rendering. But with this version I'd like to make the list-recursion work without any parser-function syntax at all - i.e. essentially to fix the MediaWiki parser's limitation of not allowing transclusion to work properly with lists as in the following example. | ||
Revision as of 22:01, 17 February 2008
|
A more logical way of approaching a treeview in MediaWiki is for the PHP extension part to concentrate on allowing the bullet lists (and maybe numbered lists too) to work recusively with transclusion, and for the tree rendering to be handled by existing JavaScript components such as DTree which are very good and packed with features such as persistence between pages.
|
Treeview4 already handles the recursion aspect well and has been written in a much more modular way than Treeview3 allowing it to be independent of the tree rendering. But with this version I'd like to make the list-recursion work without any parser-function syntax at all - i.e. essentially to fix the MediaWiki parser's limitation of not allowing transclusion to work properly with lists as in the following example.
*Foo
**Bar
**{{:Baz}}
**Fodda
The new version would allow the Baz article (if it were a bullet list) to be properly nested at the correct level in the parent tree. This would simply be based on the fact that the transclusion is directly after an asterisk.
The #tree parser-function would still be used to make bullet lists into trees, but would be optional and would simple wrap the structure in the appropriate HTML to activate the DTree JavaScript tree.
Persistance
If DTree handles persistance, we would want a temporary file location for the trees and a GUID such as [ArticleName]-[Database revision]
See also
- DTree (javascript based)
- Slipstream wp-Dtree (php based)
