Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
Openfree` has quit [Remote host closed the connection]
jivs_ has quit [Ping timeout: 252 seconds]
jivs_ has joined #qi-hardware
kyak has joined #qi-hardware
kyak has quit [Changing host]
kyak has joined #qi-hardware
dvdk has joined #qi-hardware
<kristianpaul>
hi dvdk :)
<dvdk>
hi
<kristianpaul>
100usd good to me,
<kristianpaul>
But i also wanted to comment about development
<kristianpaul>
Most mobile devices have an SDK
<kristianpaul>
and owrt provide a SDK, but is no the most friendly for UI desing for example
<kristianpaul>
What do you think about the lack(?) of a nanonote SDK for developing apps
<dvdk>
kristianpaul: owrt is not really a SDK, it's more a build system.
<kristianpaul>
I'm not against porting, but something you need develop for making thing more unified
<kristianpaul>
dvdk: exactly (owrt)
<dvdk>
you'd have to decide on a tooolchain/menu-system to base your sdk on.
<dvdk>
maybe qt, maybe sdk, maybe sth else
<kristianpaul>
yeah nanomap for example was developed in qt for the nanonote
<Ayla>
funny, we were speaking about UI design on #dingoonity like 30min ago
<dvdk>
I've always been in favor of a script-language based approach that'd move the SDK part to the nanonote, i.e. user won't ahve to install stuff on his pc
<dvdk>
maybe putting a simple SDK onto the nanonote, one that can be used remotely via e.g. tightvncclient might be the sipmlest way?
<kristianpaul>
ah good point
<kristianpaul>
Ayla: any conclusions? :-)
<kristianpaul>
Ayla: dingoo have lots of games, and porting more very day, i heard also you have a online "library" of games as well no?
<dvdk>
all of this lives and dies with a well-made documentation/tutorial
<dvdk>
the RHIDE IDE feels a little bit like a modern desktop OS despite running on a terminal http://www.rhide.com/. used it extensively some 10 years ago.
<Ayla>
kristianpaul: we didn't really conclude anything. I was suggesting to use the EFL instead of Qt/embedded to design UIs
<dvdk>
(wrt rhide) also implements proper project management, online help via GNU info-files etc.
<dvdk>
ugly but low footprint, designed for fast startup
<Ayla>
mmhhh allegro
<dvdk>
anything to complain about allegro? we have a very stable, efficient port running on nanonote
<Ayla>
yeah. Never got it to work on the dingoo
<dvdk>
we even have (partial) python bindings
<dvdk>
and alex4, and aseprite painting program, and and and... :)
<Ayla>
a SDL backend for allegro would be nice :)
<dvdk>
Ayla: just strip it down to only use fbdev driver, why bother with SDL? also look at our patches. I think i tweaked video mode selection a little.
<dvdk>
Ayla: allegro has a lot of backends, maybe SDL is among it?
<dvdk>
we even have sw-synthesized midi driver working in allegro.
<dvdk>
call me an allegro fan :)
<kristianpaul>
:)
<Ayla>
SDL 1.* is flawed
<Ayla>
but SDL 2.0 has a much better design
lwhalen has joined #qi-hardware
xwalk_ has joined #qi-hardware
xwalk has joined #qi-hardware
emeb has joined #qi-hardware
compcube has quit [Ping timeout: 244 seconds]
<dvdk>
Ayla: for me sdl always felt like having too many layers, too much "API" to be fun to program. This is were allegre excells.
<dvdk>
s/allegre/allegro/
<qi-bot>
dvdk meant: "Ayla: for me sdl always felt like having too many layers, too much "API" to be fun to program. This is were allegro excells."
<kristianpaul>
dvdk: had you coded games for allegro before?
<wpwrak>
huh ? SDL ? that's about as bare metal as it gets ...
<kristianpaul>
wpwrak: did you find the fonts API?
<dvdk>
wpwrak: wrt api: allegro has stuff like key[KEY_SPACE] to check for (possibly concurrent) keypresses. or you write stuff like screen->w to get screen size. use of global vars in APIs has somewhat declined recently :)
<wpwrak>
dvdk: hmm, you can get keys and screen size in SDL, too. it's not particularly difficult.
<wpwrak>
kristianpaul: yeah, picking the right thing to use on top of SDL is kinda tricky
dvdk has quit [Remote host closed the connection]
Ayla has quit [Quit: leaving]
rejon has joined #qi-hardware
rejon_ has joined #qi-hardware
jekhor has quit [Ping timeout: 244 seconds]
rejon has quit [Ping timeout: 244 seconds]
Ayla has joined #qi-hardware
rz2k has quit [Ping timeout: 245 seconds]
jivs_ has quit [Quit: Leaving]
kuribas has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
antgreen has quit [Ping timeout: 248 seconds]
GNUtoo-desktop has quit [Quit: [INFO] fsogsmd : received signal -11, exiting.]
rzk has joined #qi-hardware
Ayla has quit [Quit: leaving]
phirsch has quit [Ping timeout: 246 seconds]
urandom__ has joined #qi-hardware
phirsch has joined #qi-hardware
rejon_ has quit [Remote host closed the connection]
jekhor has joined #qi-hardware
Ayla has joined #qi-hardware
lwhalen has left #qi-hardware ["Leaving"]
Ayla has quit [Quit: leaving]
DocScrutinizer05 has quit [Quit: Konversation terminated!]
DocScrutinizer05 has joined #qi-hardware
DocScrutinizer05 has quit [Client Quit]
DocScrutinizer05 has joined #qi-hardware
DocScrutinizer05 has quit [Remote host closed the connection]
Aylax has joined #qi-hardware
DocScrutinizer05 has joined #qi-hardware
antgreen has joined #qi-hardware
Aylax has quit [Quit: Bye]
wej has quit [Ping timeout: 248 seconds]
urandom__ has quit [Remote host closed the connection]
DocScrutinizer05 has quit [Remote host closed the connection]