MediaMath / strand

A collection of modular, reusable Web Components built upon Polymer
http://mediamath.github.io/strand/
BSD 3-Clause "New" or "Revised" License
119 stars 46 forks source link

where is the demo? #79

Open mdagit opened 8 years ago

mdagit commented 8 years ago

I can't find a demo on mediamath.com or http://strand.mediamath.com or even in the source tree. I can kind of imagine from the example fragments how an editable grid might be put together with mm-grid and mm-collection and mm-grid-item template but it sure would be nice to see a complete working demo, as a whole html page showing all links and styling and so on.

Also, with the size of mm plus polymer, it is extra important to not have full page refreshes, so i'm wondering how you deal with routing and tabs and so on.

dlasky commented 8 years ago

Thanks for your interest in strand.

It sounds like you might be looking for something similar to the polymer starter kit which should get you started with how to set up polymer apps in general.

You might also want to look at google's new carbon-router component to address single page app concerns.

As far as a full demo app, Its something we'd like to build eventually, but the reality is that our current workload prioritizes component development. We'll certainly keep it in mind, but short of accepting a pull request there isn't much we can do in the short term to help you out there.

mdagit commented 8 years ago

I have the PSK.  But it is kind of weak in things like showing async loading, routing, etc.

I was hoping you had something better than carbon-router , which I'm disappointed with.

I was also hoping you had runnable online demos of each of your components, you know, like everybody else does :) ... As it is, it is pretty hard to decipher what you have in mind for how to address styling and data sources and so on. Particularly because Polymer's iron-ajax doesn't really cut it for a general data-driven web app, and Polymer has multiple contradictory stories on styling none of which seem very well thought out.

Anyway, that is just me ranting. I'm grateful you've put anything out at all open source in the brave new world of web components.

-mda

On Mon, Apr 25, 2016, at 09:05 AM, Dan wrote:

Thanks for your interest in strand. It sounds like you might be looking for something similar to the polymer starter kit which should get you started with how to set up polymer apps in general. You might also want to look at google's new carbon-router component to address single page app concerns. As far as a full demo app, Its something we'd like to build eventually, but the reality is that our current workload prioritizes component development. We'll certainly keep it in mind, but short of accepting a pull request there isn't much we can do in the short term to help you out there. — You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub[1]

Links:

  1. https://github.com/MediaMath/strand/issues/79#issuecomment-214420074
dlasky commented 8 years ago

I wrote a router prior to carbon existing, but its super specific to our closed source app's usecase so i'm not sure how useful it would be to open source it. If you wanted to type up a bit of your use cases we could see how well it matches and make a case for open sourcing it.

We don't use the polymer demo pages because this library actually predated all that, so we wrote a ton of tooling to do our own stuff before then, and supporting our internal app unfortunately supersedes efforts like that for the time being.

That said the individual component docs pages are using the components themselves in the output render, and the editor itself is a live-edit so you can play around with the config in realtime:

http://strand.mediamath.com/mm-grid-item.html

At some point I would like to move to a more 'polymery' way of handling the library export + docs pages just to be more standards compliant, but again its largely based on time constraints more than anything else.

I totally hear you on the iron-ajax stuff. I really didn't like where they were going with it either which is why we developed the request/ajax/sync paradigm, and we have a bunch of closed api specific behaviors that leverage the plugin model of sync to extend it.