[docs] Add a Q&A section around the next branch #5718
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mbrookes
previously requested changes
Dec 6, 2016
| @@ -8,7 +8,7 @@ The roadmap is a living document, and it is likely that priorities will change, | |||
|
|
|||
| The `next` release is going to be huge :sparkles: | |||
|
|
|||
| Material-UI was started [2 years ago](https://github.com/callemall/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46). | |||
| Material-UI has started [2 years ago](https://github.com/callemall/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46). | |||
There was a problem hiding this comment.
"was started" is grammatically correct.
| - [[#2251](https://github.com/callemall/material-ui/issues/2251)] Full featured Table. | ||
| ## Q&A with the `next` branch | ||
|
|
||
| The `next` branch has gained some maturity. |
| ## Q&A with the `next` branch | ||
|
|
||
| The `next` branch has gained some maturity. | ||
| We think that it's a good time to communicate more in this effort. |
| The CSS (cascading style sheets) specification emerged in 1994. | ||
| At that time, a bunch of others specifications were competing. | ||
| That's the cascading part that made is succeed over his competitors. | ||
| Allowing users to provide their own sheet, that will be later combined. |
There was a problem hiding this comment.
'It was the cascading concept that made CSS succeed over its competitors, by allowing users to provide their own style-sheet, that will be later combined.'
Combined with what?
| At that time, a bunch of others specifications were competing. | ||
| That's the cascading part that made is succeed over his competitors. | ||
| Allowing users to provide their own sheet, that will be later combined. | ||
| That feature was removed 2 years ago from the most popular browser in the world. |
There was a problem hiding this comment.
'from the most popular browsers.'
|
|
||
| 1. We focus on migrating the components to the `next` branch. They may not be fully migrated. | ||
| 2. We merge the `next` branch into master. | ||
| At that point, we gonna stop supporting the `v0.16.x` releases. |
| 5. We release our first pre-release. | ||
| 6. We ship :100:. | ||
|
|
||
| ### Have we ever considered using the best libraries for each functionality and provide only a wrapper for the UI? |
| We have, it really depends on the problem we are trying to solve. | ||
| For UI related things, providing a wrapper for the functionality is often the wrong approach. | ||
| We think that it should be done the other way around. | ||
| I.e. providing a low-level API that can be combined with third-party libraries. |
There was a problem hiding this comment.
'the other way around, i.e. providing..."
| For UI related things, providing a wrapper for the functionality is often the wrong approach. | ||
| We think that it should be done the other way around. | ||
| I.e. providing a low-level API that can be combined with third-party libraries. | ||
| E.g: |
| - [react-swipeable-views](https://github.com/oliviertassinari/react-swipeable-views) | ||
| - [react-dnd](https://github.com/gaearon/react-dnd) | ||
|
|
||
| On the other, using a smart data library for the DatePicker / TimePicker would probably be much better as data management is tricky and not a core business. |
oliviertassinari
dismissed
mbrookes’s stale review
I don't know how we could be handling it without you. Thanks for correcting my english!
Thanks @lucasbento for asking those questions. That's a first iteration on the answers. There is room for improvement.
|
Thanks for the the clear explanation @oliviertassinari . |
gustavohenke
reviewed
Dec 8, 2016
| The CSS (cascading style sheets) specification emerged in 1994. | ||
| At that time, a bunch of others specifications were competing. | ||
| It was the cascading concept that made CSS succeed over its competitors, by allowing users to provide their own style-sheet, that will be later combined with browsers and authors style-sheets. | ||
| That feature was removed 2 years ago from the most popular browser. |
There was a problem hiding this comment.
|
Please excuse the ignorance. If I wanted to use "next" today, how would I go about that? If I npm install from the github next branch, I get a "material-ui-build" folder in "node_modules", but the entry file in "package.json" doesn't export the components. Thanks. |
|
Excellent. Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks @lucasbento for asking those questions.
That's a first iteration on the answers.
There is room for improvement.