When are you going to release riot.js 1.0? February is almost over.
I used close to an hour before understanding every line of the (pretty dense) code, but once I did I was a bit underwhelmed (great as those few lines are). It seems like the "riot" here is more about keeping things minimal and sticking to MVP, than Riot.JS in itself, since the API is basically just adding $.route and $.render to jQuery (yeah, I know it is not a hard dependency). In that sense the most valuable contribution so far is actually the demo code for the admin interface, which I applaud for being very succinct and clear in execution. There are lots of bits and pieces missing from the documentation/docs on the site (when seen from the perspective of a MVP clueless noob) that clear up once you read the code for the demo. Especially the bits on how to actually implement multiple presenters that don't get it in the way. I think smaller bits and pieces of code that are thoroughly documented are what people need to get started. Thanks for your efforts; I have learned a lot after reading and testing your code for the last four hours :-)
Sorry, but I can't understand work of route in riot.js, can you describe it little bit more ? thank you.
Hi Please can you explain in more detail what testing framework you use. Ideally in the context of the demo app. Thanks
@rudinandrey28: The idea on the router is to simply listen to the back button and make URL changes manually. Riot.js leaves a lot of things open in purpose. Curious: what would you expect a router to do? We have plans on [improving](https://github.com/muut/riotjs/pull/111) the router though. @purvezdesai: We use our own minimal [BDD](https://github.com/muut/riotjs/blob/master/bdd.js) "framework" for testing.
Tero, can you create/have a video tutorial building a simple app. Topic: Explaining the concepts of riot and mvp pattern.
I'm working on Riot 2.0 and it will change how views are rendered making current stuff somewhat outdated. Stay tuned!
Tero, some things come along and the AWESOME Riot.js and the MVP mindset have turned my world upside down, thank you for your clear, concise and minimial approach have totally inspired me!!! NO more bloated frameworks and lengthy APIs to learn, spent today writing some simple Model, Presenter constructors and up and running with the beautiful jQuery taking care of the DOM, keep up the fantastic work Tero and really looking forward to Riot 2.0
@SebastianSastre +1 The philosophy behind Riot is so simple, it is brilliant, my new best friend too! I spent this last week following Riot's idiom and wow my model logic is so clear now and not entwined into Angular directives, scopes and 2-way binders! - I can just focus on my app! @Tero when can we expect Riot 2.0?, you say views will be rendered differently? - hopefully still pure and passive and no logic in there? @Tero Thank you!
Here's a TypeScript variety of Observable, and a simple example demonstrating type-safe registration of event-listeners and type-safe event dispatch. https://gist.github.com/mindplay-dk/3df3f6f996ce6837edd9
Cool! How widely typescript is used? Any notable open source projects?
Hi, I was reading https://muut.com/riotjs/docs/ again and I think there's a small problem with the sentence 'Note that other frameworks may call this layer a “view", but in MVP this is called the “presenter”.' Should "view" be "controller" instead?
[Riot 2.0 is out!](/riotjs/) This is large rewrite brings custom tags for all browsers starting from IE8. Think React + Polymer, but squeezed into 2.5K. It's a full stack with virtual DOM, "reactive views", router and observable.
which library do you use for the virtual dom diffing?
"It’s frustrating when your application fails because of a bug on the framework." OH YOU CAN SAY THAT AGAIN BROTHA!
Re : "notable open source projects", Angular 2 is entirely written in Typescript.
it seems like a lot of these statements are out of date now - " Model-View-Presenter (MVP) ... strict MVP pattern to keep things organized. " but is the MVP pattern strictly enforced? I see people describing riot as 'the M in MVP'. I agree that a model and controller can be programming with riot trivially with the observer module, but still. theoretical design != strict . Also 'separation of HTML & logic' seems totally out of place, as both are combined in the template files. I love the riot libraries. Did I miss something here?
I think in my previous comment i mistook the some elements - indeed the HTML is logic-less, and using the observer module to create MVP is a great intuitive way of interfacing with the view and model - however it does seem that we could also build MVC or anything else with the flexible riot components.
> @Tero Piirainen > This is large rewrite ... Tero, I love linking to this article, but the pictures in the comparison are missing. Maybe you should consider uploading them to an external site to avoid breaking this post every time you move the documentation around?