Profile cover photo
Profile photo
Jouni Koivuviita
150 followers -
Product Manager and Design Director
Product Manager and Design Director

150 followers
About
Jouni's posts

Post has attachment
vaadin-combo-box is getting a great new feature: custom item templates!

Here’s a JSFiddle you can try out: https://jsfiddle.net/18qLdegq/3/

Will be released very soon in vaadin-combo-box 1.3 (and then be included in vaadin-core-elements 1.5). Currently available in the master branch – do try it out and give us feedback!
Photo

Post has attachment
Has anyone succeeded in using a Polymer element with Angular 2? We managed to get it to work, but it’s very hacky how it’s initialized: https://github.com/jojule/angular-grid-example

Is there any way to add extra functionality on top of custom-style / cross scope styling? It would be really nice to get a chance to try out some other upcoming CSS features, namely color functions: http://dev.w3.org/csswg/css-color/#modifying-colors

Something like this:

my-button {
  background-color: var(--my-button-bg-color);

  /* Set the text color according to the background color */
  color: color(var(--my-button-bg-color) contrast(95%));
}

I’m not expecting the Polymer team to do these, but it would be awesome if the custom-style stuff would be open for extension! Any pointers welcome!

Post has attachment
A quick update on the "v-grid" element I promoted a week ago: we now have version 0.2.1 available with a new Material Design inspired theme. Check out the examples at http://tomivirkki.github.io/components-examples/v-grid/

http://g.recordit.co/5FkksJWSQy.gif

Post has shared content
We have been working on a data grid component for a while now – think of iron-list but with columns, headers and footers (plus many other features), and we’re ready to get feedback from the community.

We will eventually work on other components as well, but for now we just have the v-grid element. It’s a port of an existing GWT implementation to a Web Component API using Polymer.

So if you’re at all interested in trying it out, go to https://github.com/vaadin/components and look for the "Getting Started" instructions. It’s a 0.2 version, so expect some bugs :)

If you just want to see it in action, go to http://tomivirkki.github.io/components-examples/v-grid/

And be sure to report any and all issues to the GitHub repository.

Thanks!

Post has attachment
We have been working on a data grid component for a while now – think of iron-list but with columns, headers and footers (plus many other features), and we’re ready to get feedback from the community.

We will eventually work on other components as well, but for now we just have the v-grid element. It’s a port of an existing GWT implementation to a Web Component API using Polymer.

So if you’re at all interested in trying it out, go to https://github.com/vaadin/components and look for the "Getting Started" instructions. It’s a 0.2 version, so expect some bugs :)

If you just want to see it in action, go to http://tomivirkki.github.io/components-examples/v-grid/

And be sure to report any and all issues to the GitHub repository.

Thanks!

I’ve been wondering whether we can still document Polymer elements the same way as before, using JsDoc comments, and whether the documentation viewer elements work with 0.8 yet? Or does the 0.5 core-component-page display the documentation for 0.8 elements nicely?

If not, are there any pointers what to expect in the future regarding documenting our own Polymer elements?

Has anyone tried to use virtual DOM (e.g. https://github.com/Matt-Esch/virtual-dom) inside a Polymer element to manage the component state? Would that even make sense?

What are the real benefits of publishing core/paper elements (or any other element bundles) as separate Bower packages, instead of just providing the bundles (i.e. core-elements and paper-elements)?

Is it inconvenient to make everyone download all the dependencies, even if they’re not using them? Is it just for the extra flexibility, that you feel more like you’re picking and choosing what you import (since you can still pick-and-choose what you import even when downloading the full bundle)?

Maybe this is a silly question, but I’ve been thinking about this regarding our product, Vaadin Components, how we should publish those on Bower, and I would appreciate any opinions.

Post has attachment
Hi everyone!

Just wanted to share a large project that we just published I’ve been working on for almost a year now: The new customizable Valo theme for the Vaadin web framework: https://vaadin.com/valo

Valo uses Sass heavily, maybe even too much, many would say. But it was kind of the only way we could reach our goal of making the theme easily customizable for Java developers (i.e. not CSS experts).

The source code for Valo is probably not the best source for inspiration, but I’m pretty happy how the custom color keywords are functioning. You can read about those in the SasDoc for Valo: https://vaadin.com/api/valo/#variable-v-color-keywords

Btw, SassDoc is pretty great for documenting this kind of Sass framework/library): https://github.com/SassDoc/sassdoc

Another interesting thing is that Vaadin built it’s own, Java based, Sass compiler, in order to avoid using JRuby (a long story). It’s currently almost Sass 3.2. compatible, and we’re committed to updating it with the newer features: https://github.com/vaadin/sass-compiler

Anyway, thanks for the interest, hope you found something interesting.
Wait while more posts are being loaded