4 ms·
Show HN: Propeller – a front-end framework based on Material Design and Bootstrap
- yodon 10y agoThis is probably too much to ask, but is there any chance you have React bindings on the roadmap?
- supriya_a 10y agoWell, not React, but we do have a plan of including the Angular based components to the library in our future road-map. Do follow us on twitter @PropellerKit for future updates.
- bollu 10y agoSomething that Polymer and Material (IIRC) get right is that when you click multiple times on buttons, new ripples are created each time. In Propeller, the old ripple just "vanishes" and a new ripple is created. I don't know, I've been obsessed with detail of this sort for a while now. I wound up paying attention to things like this since I tried re-creating material design components in pure WebGL, It's stagnated now though: http://bollu.github.io/webgl-design/bin/paper-material.html http://bollu.github.io/webgl-design/bin/paper-material.html
- sunilsatapara 10y agoYes, you are right. Ripple effect must follow Google Material science but we have not kept it in our Propeller version purposefully. The reason is, on each click an extra ripple element is added which is difficult to handle/manage in different scenarios. Still, if you want to implement the Google Material ripple effect in our Propeller version then instead of destroying the ripple effect add a delay time to it.
- shifte 10y agoI'm not sure what the point of this is, Material Design is built on solid design principles which create well spaced and easy to understand interfaces, none of which are goals of Bootstrap. Combining Bootstrap with Material is like putting salt in coffee, and hiding with some sort of identity crisis. You've named expansion panels; accordions, which sure, they do follow a similar pattern, but which library are you basing the naming on? As a front-end developer and designer, this makes me cringe.