Best posts made by argelius

@theprotocol We wrote a Navigator component for React that is using <ons-navigator> under the hood:

https://github.com/OnsenUI/react-onsenui/blob/master/src/components/Navigator.jsx

This code might help in making it work for Riot.js :)

Vue.js is a lightweight library used to create user interfaces. Its powerful but still intuitive API makes it very easy to learn. Vue has long been a favorite for us in the Onsen UI team and we know that some of our users are already creating apps using Vue and Onsen UI. We are happy to announce that we are currently working on adding better support.

Click here to see the original article

@mentizm Thanks for trying out Onsen UI 2.0! :)

Actually, in Onsen 2.0 you don’t need to use ons.compile since all elements use the Custom Elements API, which means that they are compiled automagically.

I wrote a sample where I use ons.ready to wait for the DOM to load and it works fine:

<script src="https://cdn.rawgit.com/OnsenUI/OnsenUI-dist/2.0.0-beta.5/js/onsenui.js"></script>
<script>
  ons.ready(function() {
    var content = document.getElementById('content');
    content.innerHTML = "<ons-button>Another button</ons-button>";
  });
</script>
<ons-page>
  <ons-toolbar>
    <div class="center">Append element</div>
  </ons-toolbar>
  
  <div id="content" style="text-align: center"></div>
</ons-page>

Codepen example: http://codepen.io/argelius/pen/jWYvZx

It’s been a little over four months since we released the first RC version of Onsen UI 2.0. Since then we have gone through several iterations, ironing out the creases in order to deliver a great UI solution for all hybrid and mobile web app developers out there.

Click here to see the original article

@евгений-гедройц: That repo has nothing to do with Onsen UI. It’s something I threw together while trying out Web Components.

In the renderToolbar() method you use a variable navigator but it doesn’t exist. Since it looks like you pass the Navigator component as a prop maybe you should do this.props.navigator instead.

Which line is causing the error?

@aboteler I don’t think there is anything wrong with your code. There was an issue with the <ons-splitter> component where the <ons-splitter-side> element was registered before it’s parent. This only happened if you load the JS at the end of the body.

This has been fixed now so it will work fine in the next version.

Onsen UI 2 just went out of beta. The RC was released today with React Components!

These components make it easy to create beautiful hybrid apps using React.

To see them in action please take a look at this repo. It’s a kitchensink example that uses most of the components available.

• Try demo!

This version also includes automatic styling so the app will look native on both iOS and Android.

We’ve also released a new website with docs for Onsen UI 2. Here are links directly to the React docs:

• Component reference
• Guide for React

We hope you like it!

If you have any questions don’t hesitate to ask. Spread the word to your React developer friends! :)