4 ms·

andlabs (Pietro) is writing this library in C as a support for the Go ui library he's been building. https://github.com/andlabs/ui https://github.com/andlabs/ui

by apayan 10y ago

andlabs (Pietro) is writing this library in C as a support for the Go ui library he's been building. https://github.com/andlabs/ui https://github.com/andlabs/ui However, as others have pointed out, this will be very useful for many other languages as well. I would love to see a Renaissance of native cross platform apps.

fithisux 10y ago
Me too
Chris2048 10y ago
I've tried to stay away from the "web tech on the desktop" trend. network-connected/cloud apps are great, but the current web tech does nothing to solve it. Things like atom inherit js etc. which gains a little bit of speed up and familiarity, but also performance overheads and complexity. Not actually good, js-devs are the worst for a kind of NIH and low cross-pollination. Sometimes, a string custom and/or C-API is the nest for bringing in multiple communities.
fit2rule 10y ago
>I would love to see a Renaissance of native cross platform apps. Along similar lines, I have been using the MOAI environment, with the Hanappe GUI framework, to deliver apps across every platform you can port MOAI too, sort of .. fulfilling .. the once-jaunted "write once, run anywhere" dream, while also giving me a usable UI environment for the modern world.. ship bytecode/Lua files, run the same code everywhere (the MOAI client lives). Seriously, worth an hour or so of lab-bench time, if one is considering the prospect of having an app/run-time equilibrium, albeit with a modicum of effort: http://github.com/moai/ http://github.com/moai/ http://github.com/makotok/Hanappe http://github.com/makotok/Hanappe http://github.com/makotok/Flower http://github.com/makotok/Flower (Flower is another branch, similar concept: build your entire UI as a mini-lib, bring it with you everywhere you need it...)
- twotavol 10y ago
  A simple write up with screenshots or something would be nice.
pjmlp 10y ago
Call me old fashion, but it never went away. I only use web applications when there isn't a native alternative that I can make use of. Actually I moved back to the world of native applications and there is plenty of work.

by apayan 10y ago

fithisux 10y ago

Me too

Chris2048 10y ago

I've tried to stay away from the "web tech on the desktop" trend. network-connected/cloud apps are great, but the current web tech does nothing to solve it. Things like atom inherit js etc. which gains a little bit of speed up and familiarity, but also performance overheads and complexity. Not actually good, js-devs are the worst for a kind of NIH and low cross-pollination. Sometimes, a string custom and/or C-API is the nest for bringing in multiple communities.

fit2rule 10y ago

>I would love to see a Renaissance of native cross platform apps. Along similar lines, I have been using the MOAI environment, with the Hanappe GUI framework, to deliver apps across every platform you can port MOAI too, sort of .. fulfilling .. the once-jaunted "write once, run anywhere" dream, while also giving me a usable UI environment for the modern world.. ship bytecode/Lua files, run the same code everywhere (the MOAI client lives). Seriously, worth an hour or so of lab-bench time, if one is considering the prospect of having an app/run-time equilibrium, albeit with a modicum of effort: http://github.com/moai/ http://github.com/moai/ http://github.com/makotok/Hanappe http://github.com/makotok/Hanappe http://github.com/makotok/Flower http://github.com/makotok/Flower (Flower is another branch, similar concept: build your entire UI as a mini-lib, bring it with you everywhere you need it...)

twotavol 10y ago
A simple write up with screenshots or something would be nice.

pjmlp 10y ago

Call me old fashion, but it never went away. I only use web applications when there isn't a native alternative that I can make use of. Actually I moved back to the world of native applications and there is plenty of work.