11–20 of 74 posts
The components look nice but they're not really native like I had initially thought. Are these necessarily better or different than existing styles that reproduce these components? Anyway, I would love to see these come in native form like reactive-native.
Do you mean react-native, or is there a reactive-native I'm unaware of?
Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
Earlier quoted context omitted.
Because NodeJS is popular and desktop apps were getting small and efficient so we crammed a 30MB Chrome runtime in there.
Actually it's more like this: That ugly language called Javascript that everyone derided and said was "too shit and slow to ever write a Demo in" back in the 90s when all the "real developers" were writing server side scripts in Perl and left the frontend people to their own devices caught up with them. They kept pushing the boundaries, discovering things like XMLHttpRequest, and using that crap little language. Even…
For folks just learning about Electron / web-based desktop UI — we gave a talk about UI considerations at the Bay Area ElectronJS meetup last month: https://www.youtube.com/watch?v=JIRXVGVPzn8
Earlier quoted context omitted.
Because NodeJS is popular and desktop apps were getting small and efficient so we crammed a 30MB Chrome runtime in there.
Actually it's more like this: That ugly language called Javascript that everyone derided and said was "too shit and slow to ever write a Demo in" back in the 90s when all the "real developers" were writing server side scripts in Perl and left the frontend people to their own devices caught up with them. They kept pushing the boundaries, discovering things like XMLHttpRequest, and using that crap little language. Even…
Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
This is the question I was going to ask. It seems like porting many of the poor decisions that were made in creating the web to native desktop.
Apart from Javascript, of course. But that particular "bad decision" is getting modified with every version into something more acceptable ("now with classes!").
I guess the endpoint is that React + Javascript (+ Redux) becomes the defacto language for developing UIs in, and what implements that abstraction layer is immaterial. React-native all the things!
The widgets aren't native, which would be about a thousand times cooler. They are fakes made out of CSS.
https://github.com/ptmt/react-native-desktop
Currently just "hacking weekend" level maturity. https://github.com/facebook/react-native/issues/247#issuecom...
I have never actually tried it, but this one is real native controls. It’s on my TODO list…
On OS X, how will these components interact with the accessibility features?
These components are just bunch of styles to make it look like a 'native' widget, though it's not a real native widget of OS.
Though, it leaves me with a question, how can you set up OS X accessibility features, in your web app/UI, that it could be used by OS X? I would guess you can't, and it's all left to the browser.
Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
That said, it'd be cool to have native code generation from this though.