[Docs] Components roadmap? #245
Comments
|
I just published react-native-button if you want to give it a try. It's very simple and primarily makes it more convenient to create iOS-style buttons with the correct opacity constant. |
|
Cool! I think for the secure text field, there needs to be a way to enable the secureTextEntry |
|
You're totally right. I added a bunch of TextInput properties in #109. It wouldn't be too hard to expose |
|
My use case is having a user type in their password to the secure textinput (regular textinput isn't desirable for this) as part of logging into the app. I see |
|
+1 on a roadmap |
|
@vjeux - any plans to publicize a project roadmap? in other words, is it on your roadmap to publish a roadmap? 😄 |
|
For the components, we open sourced all the ones that we have that do not depend on fb infra and are in a good shape. As for publishing a roadmap, we first need to figure one out :)) More seriously, one idea that was thrown around was to add a "What are we working on" section in the rc changelogs every two weeks. This way we can give people some visibility into what's coming next. |
|
@vjeux - "What are we working on" would be nice to see! |
|
👍 for "What are we working on" |
1 similar comment
|
👍 for "What are we working on" |
|
+1 for "What are we working on" |
react/lib/cx has been deprecated
|
+1 for "What are we working on" -- I bet it's amazing. |
|
+1 for "What are we working on". That's avoid to work hard on breaking changes. |
|
This issue should be closed as the FB dev team agrees that this is a great idea, but needs to get around to doing it eventually :) /cc @brentvatne |
|
Usually you'd wait to actually fix the issue before closing? |
|
@bootstraponline - agreed, but this issue isn't doing much good just lingering open in its current state among several hundred others. This would require a time commitment from the team at Facebook to 1) do the initial write up 2) maintain and 3) it would potentially frustrate people if they do not stick with what they proposed as the roadmap. It's not something that I or other external contributors could really take on. So I don't know what a good solution here is. cc @vjeux |
|
@bootstraponline - here you go, components roadmap for Android! https://facebook.github.io/react-native/docs/known-issues.html#content |
|
Thanks! |
|
:) |
|
Informal without any promises "What are we working on" section would be amazing. Community support could help reduce the maintenance of it. We can use github issue with locked conversation or official docs or with every RC release notes we can add this section. cc @vjeux |
Summary:
We really need a better list view - so here it is!
Main changes from existing `ListView`:
* Items are "virtualized" to limit memory - that is, items outside of the render window are unmounted and their memory is reclaimed. This means that instance state is not preserved when items scroll out of the render window.
* No `DataSource` - just a simple `data` prop of shape `Array<any>`. By default, they are expected to be of the shape `{key: string}` but a custom `rowExtractor` function can be provided for different shapes, e.g. graphql data where you want to map `id` to `key`. Note the underlying `VirtualizedList` is much more flexible.
* Fancy `scrollTo` functionality: `scrollToEnd`, `scrollToIndex`, and `scrollToItem` in addition to the normal `scrollToOffset`.
* Built-in pull to refresh support - set set the `onRefresh` and `refreshing` props.
* Rendering additional rows is usually done with low priority, after any interactions/animations complete, unless we're about to run out of rendered content. This should help apps feel more responsive.
* Component props replace render functions, e.g. `ItemComponent: ReactClass<{item: Item, index: number}>` replaces `renderRow: (...) => React.Element<*>`
* Supports dynamic items automatically by using `onLayout`, or `getItemLayout` can be provided for a perf boost and smoother `scrollToIndex` and scroll bar behavior.
* Visibility callback replaced with more powerful viewability callback and works in vertical and horizontal mode on at least Android and iOS, but probably other platforms as well. Extra power comes from the `viewablePercentThreshold` that lets the client decide when an item should be considered viewable.
Demo:
https://www.facebook.com/groups/576288835853049/permalink/753923058089625/
Reviewed By: yungsters
Differential Revision: D4412469
fbshipit-source-id: e2d891490bf76fe14df49294ecddf78a58adcf23
Is there a list of components that are planned for react-native on iOS?
It'd be nice to have:
The text was updated successfully, but these errors were encountered: