Closed jihoobyeon closed 3 years ago
Hi!
Currently there is no ongoing work on react-native-desktop
, so I would suggest to not use it.
Hi! Currently there is no ongoing work on
react-native-desktop
, so I would suggest to not use it.
Oh, I'm sorry to hear that. when will this project resume?
@jihoobyeon, probably never since in Status company we don't use it anymore and there is no visible demand outside. Btw, how did you plan to use it?
@vkjr I was working with react-native-windows(https://github.com/microsoft/react-native-windows) and I wanted to run in linux too. If Status doesn't work on this anymore, may I fork it to my repo?
well, anyone can fork it to own repo :) its opensource ;)
Was keeping an eye on this one for years already, hoping to move away from balena-io/balena-electronjs
once it's ready. It's sad to know that this is officially abandoned.
@vicary, yeah, we don't use it for our project and microsoft now has react-native for windows and mac, so there is no point to maintain this since demand isn't obvious :)
You can use our maintained fork of Proton Native, called Valence Native. @jihoobyeon @vicary https://github.com/valence-native/valence-native
PR's welcome :)
@vkjr @aramodi Ok, thanks!
Hello, I just started to use this framework and made a Hello world app. this is my
App.ts
:other files are generated by
npx react-native init test --version 0.60.6
andnpx https://github.com/status-im/react-native-desktop-qt-init.git
. no files are modified elseApp.ts
.and when I ran
react-native run-desktop
at terminal, a window appears, but it's blank - does not shows the text(or anything).I've tried giving options at
View
, includeflex: 1
, but none of them worked.my result from terminal
stdout
is this:strangely, each time when I click the blank window, this appears twice in terminal:
QVariantMap utilities::makeReactTouchEvent(QQuickItem*, QMouseEvent*, QQuickItem*) target was not a reactItem
plus, my result of
react-native info
is this:I've installed Qt 5.12.2 from your site, and I'm using JetBrains WebStorm 2020.3.
Am I got something wrong, or is this a bug?