YAR - yet another resizer

Plugins
,
#24

Cool!

Are you in a position to publish a fixed version?

(I could override in the meantime, but if a fix is forthcoming, I’d rather stick to official versions of codemirror).

#25

It’s @oeyoews version of CodeMirror that has the “problem”
I can try making a pull request at his repo, will do so

1 Like
#26

Version 0.1.1 is out!

  • Removed the examples from the plugin, they are on the plugin page…
  • Added a collapsible-three-column-panel procedure which can be used to create nice Layouts for example
3 Likes
#27

Thanks @BurningTreeC it is working well.

I just looked at your demo site again, and something that struck me, is that resizing images makes navigating and reviewing images really easy.

However I found myself trying to grab the intersection of two resize bars to enlarge an image. Of course it did not work, and I expect this would not be easy to implement. I just thought I would mention it if you had an idea how to implement it.

This in no way diminishes what you have presented, thanks.

#28

Hi @Springer

@oeyoews has released a new version of his Codemirror 6 plugin

In that version the problem should be fixed

2 Likes
#29

Great stuff !

It would be nice, if the code $:/plugins/BTC/resizer/procedures/panels and others, where possible have code-body: yes so the code can be read without opening it in edit mode.

2 Likes
TiddlyFlex v0.7.0 and upwards
#30

Hi @pmario, I’ve now added code-body:yes to the panels procedures and other tiddlers
Version 0.2.1 should be online now

1 Like
#31

I think I may deploy the resizer widget onto setting the top of tiddler and page when using the menu bar or sticky titles.

  • I wonder what other parts of tiddlywiki would benifit. If a few I think you have a core cantidate.

Also, I think $:/core/ui/EditTemplate/body/default could be introduce through a different title and core cascade to avoid overwiting the core.

#32

Hi @TW_Tones

can you show me how that is done with the core cascades?

#33

If you look into Control Panel > Settings > Advanced > Cascades > Edit Template Body

  • the second and last/bottom filter says `[[$:/core/ui/EditTemplate/body/default]]
    • This is the tiddler you wish to modify.
  • Rather than modify the core do the following

Copy your modified $:/core/ui/EditTemplate/body/default ie; your replacement to (for example) $:/plugins/BTC/resizer/EditTemplate/body/default

Now create another tiddler and include it in your plugin (rather than the current core one) eg $:/config/resizer/EditTemplateBodyFilters/default,

  • Containing [[$:/plugins/BTC/resizer/EditTemplate/body/default]]
  • Tagged $:/tags/EditTemplateBodyFilter
  • With the list-before field containing $:/core/ui/EditTemplate/body/default

Your new edit Template Body will now be resolved and the core one ($:/core/ui/EditTemplate/body/default) will never be used. However anyone curious can look in the cascade and see this is happening.

$:/core/ui/PageTemplate/sidebar is another story.

You may still need to modify the core tiddler, but instead just remove its tag $:/tags/PageTemplate and tag your replacement tiddler $:/core/ui/PageTemplate/sidebar now with $:/tags/PageTemplate.

  • A quick experiment suggests the order of items with the $:/tags/PageTemplate tag is not importiant. Perhaps because they are positioned with CSS.
  • Now your side bar does not overwite a core tiddler someone looking at $:/core/ui/PageTemplate/sidebar will see all thats changed is you removed the tag.
  • You may wish to annotate your own tiddler with replaces $:/core/ui/PageTemplate/sidebar to permit $:/plugins/BTC/resizer to operate.
  • You may be able to design resizer differently so you just add your additional element via tagging with $:/tags/PageTemplate and not edit $:/core/ui/PageTemplate/sidebar at all (but here is where my skills are sketchy).
2 Likes
#34

Hi @TW_Tones ,

I’ve now followed your steps and the plugin doesn’t overwrite the core body/default Template anymore.
For the sidebar I’ll have to think about a solution.
I just got the idea to put the sidebar resizer into its own page template, maybe that works

#35

Will that mean new page template means you need to switch layouts?

This is one of those areas where we could look to introducing some more hackability to the core, unfortunatly for me I dont know enough hardcore HTML/CSS to do this.

I would have thought we could add an element via $:/tags/PageTemplate but this may not be true.

#36

@TW_Tones

No, not a different layout, just a new Tiddler tagged with $:/tags/PageTemplate that contains the resizer…
But that would make it far more complex to realize and wouldn’t be that smooth

#37

This tool is fabulous!

I still need time to understand how it works and how to code for it.

One comment …

The “Horizontal Collapsers” are very useful!

Any chance of a Collapser Example in Vertical panels?

Just a comment
TT

1 Like
#38

Hi @TiddlyTitch

Now there’s a collapsible-three-row-panels procedure you can use to create vertical collapsers

#39

@BurningTreeC

Wow Simon, you completely outdid yourself. What a totally fabulous presentation! :clap: :heart:

And if nobody has mentioned it yet, it’s great to see such comprehensive and professional documentation, too. Kudos!

Not sure if you’ll agree with this… one thing I would change is the variable naming: action*. For me, anything that appears…

    <<actionFoo>>

looks like a reference to an actions handler, like so:

    <$foo actions=<<actionFoo>> .. />

I wouldn’t normally suggest this, but since BTC Resizer is (rightly) headed for the core, you might consider using the TW “standard”:

    tv-resizer-delta-x   tv-resizer-handle-size etc.

Your call, of course.

1 Like
#40

@CodaCoder thanks and you’re totally right about the variables!

I’ll change them asap and hope that not too many users are already using the old variable names…

Thank you for your kind words,
Simon

1 Like
#41

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.

#42

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

#43

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.