I would like to see more documentation about how to accomplish some of the benefits of web components with Riot.js, such as the ability to style your custom components without having those styles influenced by the host page's CSS and the ability to selectively theme nested elements with things like /deep/ and ::shadow.
Riot – A React-like, 2.5K user interface library
91–100 of 222 posts
Re: Riot – A React-like, 2.5K user interface library
#92I would like to see more documentation about how to accomplish some of the benefits of web components with Riot.js, such as the ability to style your custom components without having those styles influenced by the host page's CSS and the ability to selectively theme nested elements with things like /deep/ and ::shadow.
Also the ability to easily broadcast events up and down the component hierarchy.
Re: Riot – A React-like, 2.5K user interface library
#93Earlier quoted context omitted.
Size is multiple things: 1. simplicity 2. maintanability 3. API surface and learning curve Riot also about minimalism , especially in syntax. Less proprietary stuff (and keystrokes).
In my experience with Backbone, another relatively small js library, the fact that the library is smaller and "does less for you" also means that you end up in one of these scenarios: you need to figure out how to solve a lot of things that other, larger libraries handle out of the box; or, you need to glue libraries together that provide those solutions; or, you have a bunch of prior experience with the library in q…
This is all very true.
But in case of Riot I suppose it's best for you to read the documentation and see whether it does the job for you. I personally think the custom tag approach is a great way to go.
Re: Riot – A React-like, 2.5K user interface library
#94Question: do I read your compiler right, that any line starting with 'var', 'function' or 'this' is assumed to be javascript? So for instance:
How will riot.js compile
this line?
[Don't mean to sound negative: I've been playing around with my own minimalist framework, so this is right up my alley. I'm reading the code to get a feel for how we've solved problems the same or differently, including the compile phase. Neat stuff and I'll write more when I have time to go over it in more depth.]
Re: Riot – A React-like, 2.5K user interface library
#95Earlier quoted context omitted.
Definitely some similarities exist like you listed. Riot offers following to the (massive) client-side table: 1. Custom tags (with unscary HTML + JS syntax) 2. Minimalism (both size and API surface) 3. Performance (minimizing DOM operations with virtual DOM) The 3rd item is not battle-tested / benchmarked yet and there is probably room for improvements.
Thank you for your comment. Me thinks Mithril is fairly minimal, too, but this point can't be completely objective. If API allows to do things I find complicated to do myself, then I happily accept a little bloat here and there. I will be looking at Riot custom tags and how they might help (or hinder) creating components out of functionality. There is currently an interesting discussion on the Mithril mailing list ab…
Nothing in the Universe is completely objective
Re: Riot – A React-like, 2.5K user interface library
#96This seems way different than the library I remember 6 months ago... https://github.com/muut/riotjs/tree/8c7e841e2c7724df9bab9397... Rebrand?
We certainly thought about rebranding. But since Riot 2.0 continues the minimalistic approach and "only" changes the way how views are assebled we thought the name can stay.
Re: Riot – A React-like, 2.5K user interface library
#97Question: do I read your compiler right, that any line starting with 'var', 'function' or 'this' is assumed to be javascript? So for instance: How will riot.js compile this line? would fail? [Don't mean to sound negative: I've been playing around with my own minimalist framework, so this is right up my alley. I'm reading the code to get a feel for how we've solved problems the same or differently, including the compi…
Not sure but this might indeed fail. Can you place an issue to github? Thanks!
Maybe it's good to split HTML and JS with the last HTML tag.
Re: Riot – A React-like, 2.5K user interface library
#98This seems way different than the library I remember 6 months ago... https://github.com/muut/riotjs/tree/8c7e841e2c7724df9bab9397... Rebrand?
It seems like their manifesto here hasn't really stood the test of time: https://muut.com/blog/technology/riotjs-the-1kb-mvp-framewor...
(The bits about jQuery at least, anyway.)
Re: Riot – A React-like, 2.5K user interface library
#99I would like to see more documentation about how to accomplish some of the benefits of web components with Riot.js, such as the ability to style your custom components without having those styles influenced by the host page's CSS and the ability to selectively theme nested elements with things like /deep/ and ::shadow.
Currently styling is outside Riot's responsibility. Shadow elements are not supported enough on browsers and require too much polyfilling.
Also not sure about component- based styling in general. I think that CSS should be controlled separately <-- highly personal opinnion.
Re: Riot – A React-like, 2.5K user interface library
#100Seems more like Angular than React with the template expression, why compare it with React then ? Angular is now a dirty word ?
Angular has nothing to do with MVP, why would be compared to it?