[Proposal] flat and intuitive component structure to simplify import statement.

[alitaheri]

I think this format:

import CardExpandable from 'material-ui/CardExpandable';
// or
import {CardExpandable} from 'material-ui';

is much more intuitive and convenient than this:

import CardExpandable from 'material-ui/lib/card/card-expandable';

Making this happen is hard and takes a lot of time. But it's a goo plan I think.

It can only be for deployment so gitignore and development can stick to lib.

@oliviertassinari @newoga @Zadielerick What do you think about this?

[oliviertassinari]

@subjectix That seems better, however, in the long run, I would prefer to use:

import {CardExpandable} from 'material-ui';

[alitaheri]

@oliviertassinari That would require tooling. besides not every build system can handle this from client side. I think it's best to provide both formats.

I updated my proposal

[newoga]

Yup, I can't argue with this. I like both approaches more than what we currently have.

[alitaheri]

@newoga Cool. after my marathon on the theme handling, I'll move onto improving the build script, upgrading to babel 6. updating dependencies and related housework stuff.

[Zadielerick]

@newoga @oliviertassinari Yes, both of these sound pretty easy to implement, I think I know how to make either one happen.

[oliviertassinari]

I'll move onto improving the build script, upgrading to babel 6

I'm already on it 👍 (needed for react-native)

[alitaheri]

Discussion moved to #3682