core-splitter

[Phillip Young]

Firstly, I'm really excited about Polymer and I'm having great fun playing around with it. My post is really a comment more than anything else but any salient tips, tricks, do's and don'ts is appreciated.

On my journey I have spent a bit of time looking at core-splitter. I've been trying to replicate a data rich interactive interface that we had written in WPF previously. One thing I have noticed is that as a consumer you need to do a lot of plumbing in order to make use of the core-splitter element to stop bad visual effects and deal with resizing. You can see what I mean if you put a core-toolbar as a left element of a core-splitter and move the divider all the way to the left. Lots of bleed through to the component on the right.

Now, my CSS Kung-Fu isn't the best and I'm sure I'm missing several tricks but from an implementation point of view the lack of an easy to use resize framework might result in a lot of boilerplate and workarounds to get suitable use out of core-splitter and avoid bad visual effects. Does anyone know of any plans to work toward this?

[Steve Orvell]

The idea is that `core-splitter` should make this better/simpler. The element is simply immature. We went ahead and addressed the overflow issue and added a minSize property here: https://github.com/Polymer/core-splitter/commit/122b928fa8f597af142587935f4875252445e56a

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/fcd90c56-1aca-4bfb-b248-404781fb4454%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.