/srv/irclogs.ubuntu.com/2012/11/19/#ubuntu-touch.txt

=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== scottb` is now known as scottb
=== dandrader is now known as dandrader|lunch
=== dandrader|lunch is now known as dandrader
dandraderbregma, ping18:53
=== dandrader is now known as dandrader|afk
bregmadandrader|afk, pong19:04
=== dandrader|afk is now known as dandrader
dandraderbregma, what do you think: https://bugs.launchpad.net/bugs/108081919:26
ubot5Ubuntu bug 1080819 in frame "It should be possible to build frame without x11" [High,In progress]19:26
dandradergrail would need something similar, to #ifdef its frame_x11_* calls19:27
bregmadandrader, the whole point of the frame library was indeed to hide the dirty details of X11, so it's legit19:28
bregmagrail wasn;t supposed to know about X11, so something leaked19:28
bregmabut the same bug could be used for grail, so the changes go in together19:28
dandraderyeah, it's bad to have fraem_x11_* calls in grail indeed19:28
dandraderwhat it uses is frame_x11_accept_touch and frame_x11_reject_touch19:29
bregmathere's also som e X11 calls in geis in the grail back end19:30
dandraderI think the idea of having it in the x11 namespace instead of in the regular frame_ api was that not all platforms would have the accept/reject concept for touches19:30
dandraderso in that sense grail would have to know if the frame objects it receives are using the x11 backend or not. which is weird because then it's not really a backend anymore as it's also being exposed on the front side19:31
bregmathere's also a bit of X11 dependency leaking through geis, in that the windowid gets used as a filter, but then again toolkits use that information19:32
bregmageis uses X11 directly for (1) detecting input devices (2) pumping the frame event loop, and (3) dark xsync magic19:37
bregmaperhaps there is a way to tease those functions out into a separate chunk of code so that geis is also no dependent on X11?19:38
dandraderso I think the best way would be for the platform-specific calls to be available only on their corresponding platforms. like Qt does. I has a couple of mac  windows and linux specific functions that only existing when Qt is built in those platforms. and then code that make use of those platform-specific functions would have to surround them with #ifdefs19:39
bregmaproblem with that is you can;t have the library built both ways on the same platform (which may not be a problem in the long run but may be difficult suring the transition)19:41
bregmas/suring/during/19:41
dandraderbregma,  what do you mean by "both ways"?19:43
bregmawell, if we wanted to have, for example, X11 support and some other non-X11 support in the same OS19:44
bregmayou could build the libraries twice and use different SONAMEs and -D options for each build19:44
dandraderin frame, for instance, we currently have 2 backends:  x11 and platform-independent19:46
dandraderthe platform-independent backend is always built19:46
dandraderand the platform specific ones would be mutually exclusive19:47
dandraderwell, actually they don't need to be mutually exclusive, just optional/configurable19:47
dandradere.g. if you don't have foo libs or passed --disable-foo, don't build foo backend19:48
dandraderbut for the sake of simplicity it might be better to make them mutually exclusive19:49
TheMusoHey folks. I've made some progress on the python3 port, but when attempting to run pygeis, I am getting a traceback with relation to the callback wrappers in python and ctypes, and I am not sure what the problem is, as my experience with ctypes limited. https://code.launchpad.net/~themuso/geis/python320:46
TheMusoThat branch is what I have done so far.20:46
bregmaTheMuso, I'll try to take a look in a few hours, but my ctypes is a little rusty21:14
TheMusobregma: Thanks.21:15
MuNk`general ubuntu UI it just to small, thought Ubuntu had its own Touch U by now?22:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!