react-native-navigation

Aborescence: 6b406961fd

Auteur	SHA1	Message	Date
Shalom Yerushalmy	f66556accf	Gradle version back to 3.0.1	il y a 6 ans
Shalom Yerushalmy	d0aa2e2c0b	Update build.gradle	il y a 6 ans
Shalom Yerushalmy	f36f5dc0c3	Downgrade gradle version from 3.1.4 to 3.1.0	il y a 6 ans
Shalom Yerushalmy	ee34b86f26	Upgrade gradle from 3.0.1 to 3.1.4	il y a 6 ans
Daniel Zlotin	fe6f90b093	update gradle and remove weird entry point (#2330)	il y a 6 ans
Daniel Zlotin	3514bce6e8	android unit test works	il y a 7 ans
Daniel Zlotin	1d9a852533	moving stuff around to work on everything locally without hacks	il y a 7 ans
Daniel Zlotin	9cc712344a	fix android gradle out-of-date	il y a 7 ans
Daniel Zlotin	8cebd2238a	fixing android	il y a 7 ans
Daniel Zlotin	7af4cc3971	update build gradle	il y a 8 ans
Daniel Zlotin	1866fa3bf9	update gradle to 2.2	il y a 8 ans
Daniel Zlotin	31c7db12fa	update gradle to 2.2	il y a 8 ans
Daniel Zlotin	a4c91c1eed	gradle fixes	il y a 8 ans
Guy Carmeli	af2ea9207e	Initial commit for Android implementation The approach we took is fairly simple. Navigation is created natively in corresponding activity, currently only TabActivity is supported, and we pass the styling parameters and screenId to it. Each screen is rendered in its own ReactRootView and is wired to the same ReactInstanceManager, so all screens share the same java script context.	il y a 8 ans
talkol	3faaa08cad	initial	il y a 8 ans