Thanks for responding, @Nastja.
The real objective, and the reason for using protoUI, is to wrap a third party widget into a webix widget. diff2html, to be specific. protoUI works great for this, except for the lack of functional scrolling.
The example snippet I gave was just a simple and reduced “tall html” case that is easier to hack on and discuss than a full diff2html implementation.
Your proposal to use template is interesting. Is a scrollable custom widget with protoUI difficult to make? I’ll experiment with template, but I’d much rather have a webix-friendly reusable component with settable properties that can be used just by specifying {view: "diff2html", ...}
.
As a comparison, I also use your excellent Ace editor wrapper. The implementation for this uses protoUI, and it was that example that was followed. Ace does not require webix-managed vertical scrolling, though.
It is worth noting that, while hacking around trying to figure out a way to achieve a scrollable protoUI widget (since webix.Scrollable
doesn’t seem to work), I came up with this hack with the use of some associated CSS:
https://snippet.webix.com/lslgawfn
I would much rather just use a mixin, though!! My hack is probably fragile, and certainly doesn’t enable us to use fancy webix scrolling if we decide to go that route.
Am I misunderstanding what webix.Scrollable
is supposed to do?