If you are actually searching for tiny GUI library that can run on embedded devices and additionally supports Micropython bindings, check out https://littlevgl.com/ .
I’m also intrigued by Qt for MCU’s. It looks very promising and the toolset to compliment the library is likely better than anything else for the embedded space.
Qt for MCUs is definitely interesting, but I wonder if they are able to go quite as low resource-wise as these other lite-graphics libraries (like Littlevgl mentioned in another comment).
TFA boasts RAM usage of 9kb. That's something you can run on almost a literal potato, and I'd be frankly astonished if Qt devs have been able to go as low.
On the other hand, you can build a somewhat nice system with graphics already with a Cortex-M4 and 512 kb of RAM. That sounds something that Qt just might be able to reach, which would be quite awesome.
Could you share some details about the Pebble's UI framework and the general firmware (assuming Fitbit doesn't care that much)?
OT Aside, but important to me: I was super excited about the Pebble Time and with it being marketed a "geek watch" expected a super open device I could program with custom haptics, use the microphone, get replacement parts etc and was super disappointed when I discovered none of this was possible.
(Bonus aside: If you found yourself agreeing you might be interested in Rebble and the Pine Time)
You’re going to have to dumb that one down for me, if you care to explain.
My comment on the license was from an embedded perspective - if you do a bare metal product I believe adhering to *GPL becomes difficult since you have to proved the ability to update QT. Sure, there are ways to allow this but it’s not straight forward.
I’m not sure why I got downvoted for my previous comment - I mean, I just posted the license types.
Correct me if I'm wrong but all of that only applies to LGPL if you dynamically link the libraries and it doesn't apply to GPL proper at all.
When people say "embedded" they usually mean devices that run on low end bare metal hardware without an operating system (or even a memory controller!), which means nothing to provide dynamic linking, let alone the kind of end user control that the GPL philosophy is meany to promote. The vast majority of embedded software is statically linked by design so even the permissive parts of the LGPL don't apply.
No the LGPL has a clause for dealing with static linking [1]. It's more difficult to do (as the comment above us mentions).
Using static linking requires you to provide program object files which can be relinked (and re-uploaded I'd presume). This allows the user to modify the LGPL file, and then relink the original program to the updated version.
Getting people talking about your stuff because they're motivated enough to have a pineapple-on-pizza type of argument over the demo is canny and bigtechs do this deliberately.
"Did anyone notice <demo>? LOL and WTF" is why we're communicating now.
Ultra minimal, designed by greybeards. No bullshit, just UI. It's amazing. If you want to build super fast, responsive and pleasure to use embedded devices, look into RamTeX library. It is not free, but its cheap. I've talked to them a few times, they're super cool people.
I used Nuklear for a couple of project that needed a little bit of UI, it's pretty neat to add some UI to an OpenGL or similar project. It's more targeted at "game UIs" and the like tho, where the UI isn't the main component..
I am guessing that the logo was generated from a website that mimics well-known logos. This is probably the best argument against using such a logo. I kept wondering why the creator wanted this to be associated with adult content.
The logo situation is basically an aftermath of a joke in the Chinese programmer circle: Somebody made a PornHub logo generator out of probably their own boredom, and others got "inspired" by it and say, "They, I can do that too with even crapper code", "They I can try out that Vue/React/[Insert whatever front-end buzz word here] on this quick 'side-project'".
After that, you end up with many of crappy logo generators posted on the Internet.
Few month later: "HELP!!! I'm building a new project and I needed a logo. But I don't know how to design one".
Well as a sibling comment of yours pointed out, it’s basically the original YouTube logo (used for more than a decade with slight variations) which predates PornHub. I’m sure YouTube isn’t the originator either as it’s not really that creative.
That some people associate the style with adult content probably says more about themselves than the style.
> That some people associate the style with adult content probably says more about themselves than the style.
The logo is in active use and that makes it confusing. I have no interest in making moral judgments of adult content or strangers who may or may not consume it. Doing so is unproductive and off-topic.
Indeed there's not, apart from the slight tackiness of your logo looking like another logo. I don't see why it's more objectionable than looking like the YouTube logo, say.
There's quite a bit of engrish on that page. That combined with the logo doesn't really give a good first impression. That aside, it looks pretty interesting.
There’s quite a few libraries by amazing Chinese developers out there with lacking English documentation, but I can at least speak for swoole and say the code is usually fantastic and worth reading through. Hell, these days I barely trust actual docs anyway
.svg){kind=link}