I thought you’d be receptive. Good stuff.
You’ll never get this opportunity again, to change it without risking too much grief on the part of (early) adopters.
Version 0.4.0 is out
Important: Variable Name changes
-
actionValue→tv-action-value -
actionValuePixels→tv-action-value-pixels -
actionFormattedValue→tv-action-formatted-value -
actionDirection→tv-action-direction -
actionProperty→tv-action-property -
actionHandleSize→tv-action-handle-size -
actionParentSize→tv-action-parent-size -
actionDeltaX→tv-action-delta-x -
actionDeltaY→tv-action-delta-y
This was a necessary change like @CodaCoder suggested above
If at one point this widget would make it into the core, the variable names would need to be renamed to follow the core standard
Best wishes
Simon
The tv- prefix is reserved for the core and core-plugins.
If I need something similar to core prefixes, I use my own pre-prefix eg: wltv- wl … WikiLabs. It is a bit more to type, but it makes it clear, that it is custom.
Hi all,
version 0.4.1 is out with an example of a resizable table which took me like forever to realize but it’s not working too bad…
I only need a way to get the content into the table cells, that’s still missing and I hope for ideas
The resizable-table procedure is in this tiddler: Resizer Widget — v0.4.3 - resize your sidebar and more
Edit: there are still some issues I’m about to fix
Edit: issues solved
I hope you like this,
best wishes,
Simon
(I’m still thinking about the core variable-names and how to react)
1 Like
Hi @pmario
Jeremy mentioned above that this plugin could be a core candidate
If it makes it into the core and users already use my plugin the transition wouldn’t be a big hassle if the variables were already like they were named as if this plugin was part of the core (haha my english…)
Because the variables are only available like that within the action-strings of the resizer widget I’m inclined to leave them tv- prefixed
1 Like
I’m not a developer. What I can say is that I’m using this tool a lot.
It is brilliant!
When I’m reading these posts I do get worried I’m gonna have to re-do things later?
Anyway, so long as it is clear, and there is only a change once?
You get my point?
p.s. Great to see a vertical collapser in the latest version examples!
1 Like
I am OK with that, if there is a chance to move it to the core.
2 Likes
Hi all,
with version 0.4.4 which is online now I’ve fixed an important issue:
The framed text-editor lost pointer-event capture after resize operations.
The fix is pure CSS, no core tiddlers needed to be modified.
I thought I’ll let you know since this is a crucial fix
3 Likes
Note to people not called Simon – pay no heed to what I am saying, this issue is very unlikely to affect YOU.
Simon, spookily enough, I just (like 15 minutes ago) tried the resizer for the very first time – it bricked my wiki. I had to open it in notepad++ and dig it out. I have a heavily customized wiki and it seems you are applying the resizer to the page/sidebar right out of the box – this is what killed my wiki.
Question I have now is, is there anything else you modified while it was first installed? I’ll need to undo that stuff too.
Thanks.
Hi @CodaCoder
The only core tiddler that is overridden is the sidebar
There may be other ways to accomplish the sidebar resizer though
I’ll try finding a way without overriding any core tiddler
1 Like
Which sidebar tiddler did you override? I can’t find a modified one…
That may explain a few things 
…
- I have had two TW RED SIGNALS and saved a JSON recovery of tiddlers.
But I recovered fine without needing it.
Anyway, I trust you. You likely know more than anyone.
Teething Problems only I think.
Best, TT
Hi @TiddlyTitch
Can you show me the screenshot of the error messages if you get them?
Thank you,
Simon
Is this difference in “grip bars” expected between browsers? …
Firefox on Chromebook …
… and Brave on Chromebook?
TT
IF it happens again I will!
The Chromebook has a Touchscreen, right?
1 Like
Yes. I’m using it now to write this.
given your awareness of this would it possible to save the cursor in the edit buttons solution?
with the save and keep open button we always loose the cursor position, this reduces the buttons value as one has to relocate where one was editing.
- I had come to believe it was impossible
- perhaps one day we could even restore the cursor from a saved offset when we return to edit a tiddler
this would be a great feature for those who spend time at the keyboard and have structured tiddlers. one real world example I faced was taking notes when in a class/training. if I did a safety save / commit I often had to reread the whole tiddler to find where I was, disrupting any flow state.