81–90 of 106 posts
Hi, You're using large parts of WebKit source code (LGPL) in your proprietary library. This is against the license. Please compare: https://github.com/yue/yue/blob/master/nativeui/gfx/gtk/pain... https://github.com/WebKit/webkit/blob/master/Source/WebCore/...
That's LGPL, not GPL.
It'd be really helpful if there were screenshots of a sample app from each supported platform. Is this wrapping native elements or providing custom elements?
Great job! Maybe now we'll finally see accessible and efficient GUI apps from those who insist on writing desktop applications with JS.
Too bad it ignores accessibility entirely: https://news.ycombinator.com/item?id=15219025
Hi everyone, I have written a C++ library for creating native GUI apps, it also has language bindings for Lua and JavaScript (V8). In the past I have written the Electron framework, which is a popular project for creating desktop apps with Chrome web engine and Node.js, while this library allows you to create native desktop apps. If you want to see some screenshots and example code, check out the sample apps repo: ht…
" I wouldn't like to spend time on this, but as the previous co-maintainer of node-webkit project, keeps spreading misinformation about his internship work in the node-webkit project on his blog post" ...
Why are you misrepresenting your work..
Earlier quoted context omitted.
Those two statements do contradict each other. According to my own quick analysis, this library uses truly native controls on Mac and GTK+, but its own windowless implementations on Windows. The Windows control implementations use uxtheme so they look more or less native, but that's not "native controls" as far as I'm concerned.
Interesting, what advantages this gives, maybe better skinning/theming support? But that doesn't seem to be the main goal of this framework...
Doing a cross platform UI library that uses native controls seems a lot of work.
Earlier quoted context omitted.
I don't understand what point you're trying to make. The tone of your comment comes across as if you're refuting/disputing something (that may be implied?) in what I wrote, but I'm not sure what it is.
Your comment conflates CLAs and copyright transfers.
Hi, You're using large parts of WebKit source code (LGPL) in your proprietary library. This is against the license. Please compare: https://github.com/yue/yue/blob/master/nativeui/gfx/gtk/pain... https://github.com/WebKit/webkit/blob/master/Source/WebCore/...
Wow, that's very bad. Created an issue for this to prevent anyone else using it. Let's see how the author will respond. https://github.com/yue/help/issues/4
Hi, You're using large parts of WebKit source code (LGPL) in your proprietary library. This is against the license. Please compare: https://github.com/yue/yue/blob/master/nativeui/gfx/gtk/pain... https://github.com/WebKit/webkit/blob/master/Source/WebCore/...
> By sending a pull request, you are agreeing to transfer the copyright of your code to Cheng Zhao. Nope.
I don't get why you're so attached to a PR you make to another library. So you're not contributing because you want to improve that other library, you're contributing because you want to sue them after so theycan pay you for your share of the project since you've added 10 lines of code?
As stated else where it seems like author has copied/forked existing project. Then (if I understood the license correctly) you are required to open source your software if you were to use the library, or pay $5k. On top of that if you contribute to the project you sign away your copyright.
If these things are correct it seems like a one hot mess of a project.