Loving polymer

[Filipe Araujo]

I have been following polymer for a year now, ever since I came across Eric Bidelman's "Web Components: A Tectonic Shift". And at some point last year, shortly after given my own polymer talk and getting little interest from peers about it, I stopped following the progress that was being made. However, after this years Google IO, the excitement inspired me to stop procrastinating and pick up where I had left off.

I would love some feedback on the release of the first component to my "soon to be" many ui libraries.

Github

https://github.com/filaraujo/ui-layout

Docs

http://filaraujo.github.io/ui-layout/components/ui-layout/

Demo

http://filaraujo.github.io/ui-layout/components/ui-layout/demo.html

[Dominic Cooney]

I did not look at this in detail but played with the demo and it is very slick.

It might be nice to hide the "menu" button when the responsive layout is always showing the sidebar, because it might be confusing to have a button which does not do anything.

Nice documentation and examples--kudos.

Dominic

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/f4a93ba7-0145-4a2c-a0c8-066271049a32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Filipe Araujo]

Thanx Dominic,

Good advice on the menu button. I'll update that.

[Rob Dodson]

This is really well done, nice work Filipe!

The only thing I would be mindful of is that the ui-* prefix is quite short and may start to get crowded with other elements. We usually suggest that you use a slightly longer prefix that's more unique to your project

On Mon, Jul 14, 2014 at 6:49 AM, Filipe Araujo <filipe.al...@gmail.com> wrote:

Thanx Dominic,

Good advice on the menu button. I'll update that.

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/9dd1618f-f188-43f1-a740-356f945a2cb1%40googlegroups.com.

[Pascal Precht]

Hey Rob,

that kind of conflicts with web components best practices here: http://webcomponents.org/articles/web-components-best-practices/

I think we should update that article then.

[Rob Dodson]

The best practices guide says:

Only use a prefix shorter than three characters if you already have lots of developer interest in your set of components. 

Are you referring to the x-* and my-* examples? We could change those to something longer 

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/8bd66dd1-5f3c-46df-8719-b288b9bccfd9%40googlegroups.com.

[Pascal Precht]

Ah, looks like I misunderstood what you said. It sounded to me like you would always recommend something longer and prefixes like "ui-" are too short.

But actually you made clear that its better to have longer prefixes so that his components are more unique to his app. So we're not talking about components that are used by lots of developers here.

[Rob Dodson]

So we're not talking about components that are used by lots of developers here.

I am talking about components you intend to share with lots of developers. Any component you want to share with others should have a longer prefix so it is unique. 

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/1b55b7e5-cf8e-4823-af8a-55b586771eb6%40googlegroups.com.

[Filipe Araujo]

went ahead and decided to go full steam on this.  Introducing Akyral, seems like a better prefix for than "ui".  

[Rob Dodson]

nice!

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/2a81544c-e4fd-4806-a5f5-1467db84b060%40googlegroups.com.