6 ms·

Sorry, dumb question, don't feel like watching the video: What platforms are targetted? Out of, say, iOS, Android, Linux/X11 desktop, Windows desktop, WinRT, O

Sorry, dumb question, don't feel like watching the video: What platforms are targetted? Out of, say, iOS, Android, Linux/X11 desktop, Windows desktop, WinRT, OSX?

kenrose 12y ago
iOS and Android.
- deleted 12y ago
  [deleted]
evv 12y ago
This is Eric, from the React Native team. We're starting with iOS and Android, which will keep us busy for the foreseeable future. That said, we will open source soon, and we'd be happy to accept help targeting other platforms!
- omard 12y ago
  Nice! What about windows phones?
- slashnull 12y ago
  This is awesome. I can't wait for the API docs and sources to be released. Tweets and videos are lousy at conveying information : )
- jbigelow76 12y ago
  Very interesting. Microsoft allows you to build fully native (not webview wrappers) apps using WinJS, and they have shown that React (along with Angular) can be used to build those apps [1]. I wonder if Microsoft will put resources into bridging the gap between React Native and Windows 10. As a long time web oriented .NET developer wanting to pick up mobile who has been wondering whether to go Cordova or dive in fully native (ObjC/Java/Xaml) this is going to make the choice very difficult. [1] https://github.com/winjs/winjs/wiki/Using-WinJS-with-React https://github.com/winjs/winjs/wiki/Using-WinJS-with-React
  - seanmcdirmid 12y ago
    Honest question: Would you even need something like react on windows given that wpf/winrt already support dependency properties and data binding?
    - jbigelow76 12y ago
      TL;DR to below: focusing on JS instead of Xaml seems like a smarter play for a .NET developer that hasn't used Xaml in WPF or SL previously. I put "web oriented .NET developer" in my response for this specific type of question. I kind of defaulted (11 years ago) into ASP classic and ASP.NET as a result of ad hoc consulting/support work for MS technologies back in 2000. But despite my affection for C# I abandoned ASP.NET's faux desktop event driven emulation for MVC as soon as it was released. Ever since then I felt sort of stuck in between thinking of myself as a Web Developer vs thinking of myself as a .NET Developer. Which brings my long winded response back to your original question about WPF and data binding. WPF and Xaml are pretty foreign to me (I still have no idea about how WPF/SL/WinRT Xaml differ it all seems like Xaml to me) despite a long history with C#. But I am interested in native app development, so I have been torn on whether to go all in with C# knowing I could take it cross platform with Xamarin but need to reorient myself into the Xaml world or go all in with HTML5 knowing Cordova could be "mostly good enough". I'm a Microsoft fan (I actually enjoy my Surface RT and Windows Phone) so WinJS on Windows 8 seemed like a good hedge for not throwing away all my JS knowledge (which is becoming a predominant part of my work with SPAs) but still letting me go fully native. But the overall Windows dev community seems to have spoken, Xaml is it and WinJS is a pariah, MS doesn't help much by staying mum on the matter but I think they are trying to shove WinJS into the Cordova camp and double down on Xaml for Win 10 with WinJS eventually fading away.
      - seanmcdirmid 12y ago
        I program in WPF in C# with absolutely no XAML. I used to use dependency properties/data binding a lot, I even made a wrapper [1] so you could write things like: w0.Right.Bind = w1.Left + w2.Width; And that would automatically generate a one way data binding in WPF (so if w1's left property, w2's width property, or w0's width property changes, w0's left property is automatically recomputed). I've since moved on to my own dependency management (rebranded hence forth as managed time) system called Glitch [2], but that's because I'm trying to invent what's next. I'm an MS employee but I have no idea what what is being done in this area. I do have lots of respect for WPF, it was weird that the other platforms couldn't put forward a decent UI platform for so long (well, JavaFX, but it didn't go anywhere). [1] http://bling.codeplex.com/ http://bling.codeplex.com/ [2] http://research.microsoft.com/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/en-us/people/smcdirm/managedti...
andybak 12y ago
Yep - is there any reading-based info on this? I can't bear absorbing tech info via a channel as slow as watching or listening to someone... Link please!
- andybak 12y ago
  All I've managed to find so far: https://www.progville.com/javascript/react-native-apps-react-js/ https://www.progville.com/javascript/react-native-apps-react...

Sorry, dumb question, don't feel like watching the video: What platforms are targetted? Out of, say, iOS, Android, Linux/X11 desktop, Windows desktop, WinRT, OSX?

kenrose 12y ago

iOS and Android.

deleted 12y ago
[deleted]

evv 12y ago

This is Eric, from the React Native team. We're starting with iOS and Android, which will keep us busy for the foreseeable future. That said, we will open source soon, and we'd be happy to accept help targeting other platforms!

omard 12y ago
Nice! What about windows phones?
slashnull 12y ago
This is awesome. I can't wait for the API docs and sources to be released. Tweets and videos are lousy at conveying information : )
jbigelow76 12y ago
Very interesting. Microsoft allows you to build fully native (not webview wrappers) apps using WinJS, and they have shown that React (along with Angular) can be used to build those apps [1]. I wonder if Microsoft will put resources into bridging the gap between React Native and Windows 10. As a long time web oriented .NET developer wanting to pick up mobile who has been wondering whether to go Cordova or dive in fully native (ObjC/Java/Xaml) this is going to make the choice very difficult. [1] https://github.com/winjs/winjs/wiki/Using-WinJS-with-React https://github.com/winjs/winjs/wiki/Using-WinJS-with-React
- seanmcdirmid 12y ago
  Honest question: Would you even need something like react on windows given that wpf/winrt already support dependency properties and data binding?
  - jbigelow76 12y ago
    TL;DR to below: focusing on JS instead of Xaml seems like a smarter play for a .NET developer that hasn't used Xaml in WPF or SL previously. I put "web oriented .NET developer" in my response for this specific type of question. I kind of defaulted (11 years ago) into ASP classic and ASP.NET as a result of ad hoc consulting/support work for MS technologies back in 2000. But despite my affection for C# I abandoned ASP.NET's faux desktop event driven emulation for MVC as soon as it was released. Ever since then I felt sort of stuck in between thinking of myself as a Web Developer vs thinking of myself as a .NET Developer. Which brings my long winded response back to your original question about WPF and data binding. WPF and Xaml are pretty foreign to me (I still have no idea about how WPF/SL/WinRT Xaml differ it all seems like Xaml to me) despite a long history with C#. But I am interested in native app development, so I have been torn on whether to go all in with C# knowing I could take it cross platform with Xamarin but need to reorient myself into the Xaml world or go all in with HTML5 knowing Cordova could be "mostly good enough". I'm a Microsoft fan (I actually enjoy my Surface RT and Windows Phone) so WinJS on Windows 8 seemed like a good hedge for not throwing away all my JS knowledge (which is becoming a predominant part of my work with SPAs) but still letting me go fully native. But the overall Windows dev community seems to have spoken, Xaml is it and WinJS is a pariah, MS doesn't help much by staying mum on the matter but I think they are trying to shove WinJS into the Cordova camp and double down on Xaml for Win 10 with WinJS eventually fading away.
    - seanmcdirmid 12y ago
      I program in WPF in C# with absolutely no XAML. I used to use dependency properties/data binding a lot, I even made a wrapper [1] so you could write things like: w0.Right.Bind = w1.Left + w2.Width; And that would automatically generate a one way data binding in WPF (so if w1's left property, w2's width property, or w0's width property changes, w0's left property is automatically recomputed). I've since moved on to my own dependency management (rebranded hence forth as managed time) system called Glitch [2], but that's because I'm trying to invent what's next. I'm an MS employee but I have no idea what what is being done in this area. I do have lots of respect for WPF, it was weird that the other platforms couldn't put forward a decent UI platform for so long (well, JavaFX, but it didn't go anywhere). [1] http://bling.codeplex.com/ http://bling.codeplex.com/ [2] http://research.microsoft.com/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/en-us/people/smcdirm/managedti...

andybak 12y ago

Yep - is there any reading-based info on this? I can't bear absorbing tech info via a channel as slow as watching or listening to someone... Link please!

andybak 12y ago
All I've managed to find so far: https://www.progville.com/javascript/react-native-apps-react-js/ https://www.progville.com/javascript/react-native-apps-react...