This looks great, in particular because it provides a generic solution.
The sidebar is a common need and this seems more reliable than previouse solutions, installing resizer delivers the sidebar resizer out of the box but can be used to build other resizable “objects”.
- It has the issue of overwriting core tiddlers,
- perhaps we should leverage an alternate layout/page template to avoid this?
- Or perhaps alternative “view template Body” and “View Template subtitles” used if a sidebar resizer config tiddler is set to yes.
I can build this for you @BurningTreeC if you want?
As I try to come to terms with this I can see that the $resizer widget primarily manipulates a size value in a nominated configuration tiddler and is CSS size format aware. If tiddlywiki is aleady using such a configuration tiddler and the appropriate CSS is known we can modify existing tiddlers as the sidebar resizer does $:/core/ui/EditTemplate/body/default
and $:/core/ui/PageTemplate/sidebar
.
- Note: It is not easy to determin what changes were made to allow this, the Difference view is not working because of the shadow overwrite, by a plugin shadow tiddler.
However if we want to build other resizable objects as in the examples given quite a lot needs to be done to build the containers and define the CSS to achive it. This is quite a large scope if we wanted to document it, so I understand why it is not.
Supporting elements
This makes me wonder if a set of html/css classes and tags could be provided in the plugin for common use requirements, as in the examples, including one that helps verticaly resize tiddlers. The user can then use shared config tiddlers or qualified tiddlers against a named html element or class.
- This would allow this effective resizer to be used without the need to write all the CSS.
- Although it would call for a library of resizable objects/elements to be developed.
- In a manner similar to @Mohammad Shiraz cards etc…