[GH-ISSUE #64] Is Proton-native ready for production. Or is it still a hobby project #36

Closed
opened 2026-05-05 11:30:23 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @herlarb on GitHub (Mar 22, 2018).
Original GitHub issue: https://github.com/kusti8/proton-native/issues/64

This is not an issue per se. But can Proton-native be used for production or is it still an hobby project. I am a part-time Qt developer and I have been actively using React and React-native for about a year now.

Originally created by @herlarb on GitHub (Mar 22, 2018). Original GitHub issue: https://github.com/kusti8/proton-native/issues/64 This is not an issue per se. But can Proton-native be used for production or is it still an hobby project. I am a part-time Qt developer and I have been actively using React and React-native for about a year now.
Author
Owner

@kusti8 commented on GitHub (Mar 22, 2018):

Proton-native itself is pretty stable, most of the fixes are just small fixes in code quality and documentation. It depends on whether you see libui as stable. I see it as stable enough for many projects, but if you're going to be doing something very complex where you want years of development on your side, you're never going to beat Qt.

But if you want to make something quickly and easily, which can still pretty much stand the test of time since libui is written using native GUI libraries, then proton-native is a good choice.

Ultimately, it's up to you.

<!-- gh-comment-id:375338962 --> @kusti8 commented on GitHub (Mar 22, 2018): Proton-native itself is pretty stable, most of the fixes are just small fixes in code quality and documentation. It depends on whether you see `libui` as stable. I see it as stable enough for many projects, but if you're going to be doing something very complex where you want years of development on your side, you're never going to beat Qt. But if you want to make something quickly and easily, which can still pretty much stand the test of time since `libui` is written using native GUI libraries, then `proton-native` is a good choice. Ultimately, it's up to you.
Author
Owner

@herlarb commented on GitHub (Mar 22, 2018):

But it can't be styled as far as i see it( based on issues raised on CSS which i totally understand). Is there any way to style components without having to give then native "look and feel". Most people want polished apps not just the default app styling.Is there any way to achieve this. I have been following the project for a while now since Dan Abramov tweeted about it and I am convinced to use it in an app. Not something overly verbose .

<!-- gh-comment-id:375366310 --> @herlarb commented on GitHub (Mar 22, 2018): But it can't be styled as far as i see it( based on issues raised on CSS which i totally understand). Is there any way to style components without having to give then native "look and feel". Most people want polished apps not just the default app styling.Is there any way to achieve this. I have been following the project for a while now since Dan Abramov tweeted about it and I am convinced to use it in an app. Not something overly verbose .
Author
Owner

@kusti8 commented on GitHub (Mar 22, 2018):

No you can't style, that's a fundamental difference.

On Thu, Mar 22, 2018, 12:18 PM herlarb notifications@github.com wrote:

But it can't be styled as far as i see it. Is there any way to style
components without having to give then native "look and feel".


You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
https://github.com/kusti8/proton-native/issues/64#issuecomment-375366310,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJW73G7BkZwa3U852T8VYZMZ6IYOfOebks5tg87cgaJpZM4S3Ff5
.

<!-- gh-comment-id:375366707 --> @kusti8 commented on GitHub (Mar 22, 2018): No you can't style, that's a fundamental difference. On Thu, Mar 22, 2018, 12:18 PM herlarb <notifications@github.com> wrote: > But it can't be styled as far as i see it. Is there any way to style > components without having to give then native "look and feel". > > — > You are receiving this because you modified the open/close state. > > > Reply to this email directly, view it on GitHub > <https://github.com/kusti8/proton-native/issues/64#issuecomment-375366310>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJW73G7BkZwa3U852T8VYZMZ6IYOfOebks5tg87cgaJpZM4S3Ff5> > . >
Author
Owner

@mischnic commented on GitHub (Mar 22, 2018):

Something that's coming in the future (hope we can do a CSS-like syntax in proton-native):

bildschirmfoto 2018-03-22 um 17 24 12

<!-- gh-comment-id:375369247 --> @mischnic commented on GitHub (Mar 22, 2018): Something that's coming in the future (hope we can do a CSS-like syntax in proton-native): ![bildschirmfoto 2018-03-22 um 17 24 12](https://user-images.githubusercontent.com/4586894/37783540-09351bde-2df6-11e8-82e9-843b15d1b0f6.png)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/proton-native#36
No description provided.