Slide out the drawer and click any menu item, Then, transition of the navigator is very slow.

Is this issue belong to ReactNative android?

When using the List component as the row component of a ListView, scroll is overwritten by the onPress event, so I cannot scroll properly. This is a screenshot of the emulator in the docs:

If the onPress event replaces the view, the scroll automatically replaces the view, so scroll is not possible.

Hi team!
When i apply mrn in my project react-native (v0.25), then I build....

Help me, please!!
Thanks!!!

Let me explain this behaviour. This is in reference to #9 and #10. But, clearly this issue is with the button component.
When I click on the button, it doesn't bounce back to released state. It is stuck in pressed state.

Phone - Samsung Galaxy S4
OS version - 5.0.1 and 5.1.1 (Tested on both)

I will look into this as well, will pull a PR soon. Just wrote it here so as to keep track of things.

Streaming for this account has been temporarily disabled

How would you feel towards using some form of code quality tool like ESLint? After playing around with some of the components I feel that many of the files are differently formatted etc.

Happy to set it up if you'd like?

Hi, I tried to run your code in RN 0.16. I got the error which is related to .babelrc whitelist

First of all -> really nice work, I like it! But I found issue on Samsung Galaxy S4 (Android 5). If you tap on list or button you have white square (artefact after tap). As you can see:

All the doc is for Android any plan to support IOS ?

I cannot use list, face, question-answer or folder-open icons. I'm using latest version (v0.14). When I used https://github.com/oblador/react-native-vector-icons directly I had no problem, so I guess it's a thing with the font face.

Can you update it to use the original version?

Thank you!

Hi @binggg,

Lately, we have been talking about how to build a cross platform material implementation.
At first, I though that the best way to do it was to create a thrid repository to write wrapper components (abstract API differences).
However, now I'm convinced that it's better to have the different implementation in the same repository (always sync API and potentially shared code).

We have been doing a lot of changes in the material-ui repository recently.
I believe that we now have the needed infrastructures to start working on react-native:
mui/material-ui#2667

So here is my question, would merging this project back to material-ui makes sense to you?
If not, how do you think that the cross platform common API should be done?

@Ehesp I see that you have started working on https://github.com/react-native-material-design/react-native-material-design. Any insight would be valuable too.

Hi,

Firstly I would like to say that this is one of the awesome projects of React native I have come across and would like to be an active contributor and tester of it.

One very common issue I come across using the Demo APK is -

One long press of any component, it changes the state of the component to pressed or selected state. And when I try to tap on it to release the state, I see patches of square/rectangular shaped selections. Only an outside tap gets the component deselected.

Screenshots-

Screenshot 1:

Screenshot 2:

Screenshot 3:

Is there any plan on including an apk on the repository/download link in the description, for some fast testing?

For those who aren't at their development station or just want to see what react native can do with "mrn"?

Hello, and thanks for your work - your module looks very promising!
A couple of issues i've been running into (react-native 0.15)

1. I wasn't able to install the module with

npm install react-native-material-design-components

as stated in the manual. It seems that the module is registered as "mrn":

npm install mrn

2. Installing the module with the command above, and requiring it with

var mD = require('mrn');

i have the following error:

lib/Button.js: Unexpected token (50:24)

Am i missing something?

The xCode logs:

[RCTConvert.m:635] Unrecognized font family 'Roboto,Noto,sans-serif'
[RCTConvert.m:635] Unrecognized font family 'Material Design Icons'

I started installing and got to a point where I needed to change my public class MainActivity extends Activity implements DefaultHardwareBackBtnHandler but in RN 0.39.x (current version) that has been replaced by public class MainActivity extends ReactActivity {. Now I don't know how to install this.

On top of that the last commit was a year ago and there are references in Issues to problems with RN 0.16. Ouch.

Looks dead to me.

I have tried it several times. Tapping on button/checkbox/favorite is not very smooth/doesn't work.
Attaching screenshot-

PR #14 added the ability to overwrite the default Toolbar navIconName. I want to use a Toolbar without any navIcon, so I was thinking that the default behaviour could be no icon, and if the user wanted an icon then they would need to explicitly name it:

Toolbar without an icon:

        <Toolbar
          actions={this.props.actions}
          primary="paperLightBlue"
          title={this.props.title}
        />

Toolbar with an icon:

        <Toolbar
          navIconName="menu"
          actions={this.props.actions}
          primary="paperLightBlue"
          title={this.props.title}
        />

What do you think?

With a fresh install, I get the following error when following the instructions to install.

Using the latest version of the react-native cli tool.

I also get the logs:

W/ReactNativeJS( 1965): 'Warning: Native component for "RCTModalHostView" does not exist'
W/ReactNativeJS( 1965): 'ProgressBarAndroid has no propType for native prop AndroidProgressBar.indeterminate of native type boolean'

When I visit the mrn.js.org website the code examples render in my browsers' generic serif font and not "Source Code Pro". It looks like:

Having a quick look through your CSS I can't see the font being loaded in. Only the Roboto webfont. No errors popup in the browser console either.

Beyond that worth backing up "Source Code Pro" with a reference to the monospace font-family in your CSS

pre.prettyprint, pre > code {
   font-family: "Source Code Pro", monospace;
}

etc.

As much as I like this project, I feel there's quite a bit which needs improving for it to be maintainable. Also, @binggg do you have time to manage this on your own? Anyway a list:

• Support React 0.16 & Babel 6 - I have this working locally, #21 - however in my eyes the project should support 0.16.* only in my eyes, since there's some big changes in it.
• Have React Native 0.16 as a peer dependancy
• Linting files with ESLint (#15) - Loads of inconsistencies, unused code etc.
• Fixing the Ripple state bug (#9)
• Tests - currently it's hard to make changes to components because I have no idea if the change will break something else.
• Documentation - Could do with some more examples/spell-checking etc
• Contributing Guidelines
• Have react-native-vector-icons as a project dependancy
• Break this project down into an organisation? Would be better to have multiple repositories in the same place, although this is @binggg's call.

Please provide feedback on these, this project is easily the best material one out there at the moment, just needs some loving.

I upgraded from React Native v0.14 to React Native v0.16, and I got some Babel errors:

Unknown option: node_modules/mrn/.babelrc.whitelist

If I delete this file, I get to compile the project. Any idea what's the issue here?

I'm using MRN @ master.