<freemangordon>
you get XID (effectiveWinId()) from qt and pass it to gdk_window_foreign_new()
<freemangordon>
and you have GdkWindow you can add GtkWidget to
<freemangordon>
simplified
<freemangordon>
I can provide sample code later on
<dsc_>
ok :)
<freemangordon>
dsc_: I wonder if it is not a time to start implementing 'start chat' functionality, I can provide a simple qt application that does it(the selection part). what do you think?
<dsc_>
freemangordon: yes, would be nice. it needs to happen from addressbook somehow
<freemangordon>
mhm
<dsc_>
what do you have in mind?
<freemangordon>
oh, wait
<freemangordon>
I mean - there is 'new message' in the menu
<dsc_>
yes, I changed it in my current dev branch, but I figure it will be removed because we wil be doing it from abook
<freemangordon>
I think pressing that shall open abook contact searcher
<dsc_>
yes something like this
<freemangordon>
no, we already can do from abook
<freemangordon>
but my understanding is that we shall be able to start new chat from conversations, no?
<dsc_>
yes correct
<dsc_>
need a contact picker
<freemangordon>
exactly
<dsc_>
if you can spawn this gtk widget/dialog somehow
<freemangordon>
so, my plan is to provide a simple application that implements contact picker in qt
<dsc_>
yes
<freemangordon>
yes, I can
<dsc_>
and get the results from it
<freemangordon>
mhm
<dsc_>
abook is aware of the protocols right?
<freemangordon>
you will get OssoABookContact, when you select one, IIRC
<freemangordon>
sure
<freemangordon>
half of the code deals with TP
<dsc_>
yes
<freemangordon>
ok, cool
<dsc_>
let me check @ OssoABookContact,
<freemangordon>
I'll do it as soon as I have some spare time
<freemangordon>
check what? you already use it :)
<freemangordon>
you will get roster contact
<dsc_>
yes but
<freemangordon>
with remote id and such
<dsc_>
need to map it to local_uid,remote_uid
<dsc_>
there is osso_abook_contact_get_persistent_uid
<freemangordon>
map? I think there will be no need to map
<dsc_>
yes that function will work
<freemangordon>
as you can get TpAccount (the local one) from a contact\
<dsc_>
im already using it
<dsc_>
or that, yeah
<dsc_>
ok
<freemangordon>
ok, we have a deal
<dsc_>
xD
<freemangordon>
btw, for the avatar
<freemangordon>
I will also have to provide sample app
<dsc_>
well
<freemangordon>
but maybe lets do 'new message' first
<freemangordon>
hm?
<dsc_>
osso_abook_avatar_image_get_pixbuf
<dsc_>
would be easier
<dsc_>
no need to include the whole widget this way
<freemangordon>
yeah, but that's GdkPixbuf
<dsc_>
its just an image, no?
<dsc_>
yes, I can get the pixeldata from it
<freemangordon>
yes, but it will not update on-the-fly
<dsc_>
I already listen to updates
<freemangordon>
you have to connect to 'avatar-changed'
<freemangordon>
right, but all this is already implmented
<dsc_>
i think it would be easier
<freemangordon>
no
<dsc_>
no need for widget
<freemangordon>
I think it will be way easier to just embed gtk widgets
<freemangordon>
but lets see
<dsc_>
maybe, the gtk window handle bla stuff seemed a bit convoluted
<freemangordon>
ask Wizzup for help with gtk/glib while I am away
<dsc_>
(conversations:8645): GLib-GObject-WARNING **: 08:25:15.403: ../../../gobject/gsignal.c:2614: signal 'avatar-changed' is invalid for instance '0x555ee8f551d0' of type 'OssoABookContact'
<dsc_>
nom nom
<dsc_>
bye :D
<freemangordon>
well, check what provides "avatar-changed"
<sicelo>
Wizzup: seems something's not right with how we start alarmd or something ... no rush though. i should be able to look into it the coming days
<sicelo>
but alarm was correctly set and did wake device up when i ran alarmd manually. as run/started by the system, the rtc is never written to
<sicelo>
ah, simple reason - we start alarmd as user. i guess side effect of using rootless xorg, since alarmd is started from xsession?
<sicelo>
this explains why i remember it used to work, presumably when we still ran X11 as root
<sicelo>
the whole thing works nicely when you start alarmd manually as root
<sicelo>
but now i see we seem to have always started it as user (not related to rootless xorg). but yeah, as long as rtc is only managed by root (which is generally correct), then we cannot see a hw alarm
<sicelo>
s/cannot see/cannot set/
Anasko has joined #maemo-leste
hm has joined #maemo-leste
ceene has quit [Read error: Connection reset by peer]
ceene has joined #maemo-leste
MinceR has joined #maemo-leste
MinceR has quit [Changing host]
MinceR has joined #maemo-leste
ceene has quit [Ping timeout: 252 seconds]
<Wizzup>
sicelo: we can make udev rules for all rtc? devices
<Wizzup>
set perms to 0660 and add the users group or some clock group
ceene has joined #maemo-leste
pere has quit [Ping timeout: 248 seconds]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
ceene has quit [Remote host closed the connection]
fab_ has joined #maemo-leste
<freemangordon>
Wizzup: I think we shall start alarmd as root
<freemangordon>
it even complains now on chimaera
<Wizzup>
Why?
<freemangordon>
dsc_: hmm, right, lemme fix that
<Wizzup>
Why run it as root if it is a one linre to make /dev/rtc privs more sensible
<freemangordon>
Wizzup: because we start it from xsession script
<Wizzup>
so why start it as root?
<freemangordon>
isn;t is sytem-wide daemon?
<Wizzup>
that doesn't mean they should run as root
<freemangordon>
or it is per user?
<freemangordon>
so, you want every user session to has it's own alarmd?
<freemangordon>
I don;t think that will work
<freemangordon>
lemme check on which dbus session it registers
inky has quit [Ping timeout: 252 seconds]
<freemangordon>
Wizzup: seems to work on system bus
<sicelo>
i also do think rtc is best managed by root, so i would prefer running alarmd as root as well, leaving rtc permissions intact. less chance that something will try to overwrite the set wakeup time that way.
antranigv has quit [Ping timeout: 255 seconds]
antranigv has joined #maemo-leste
<freemangordon>
lemme check what it does on fremantle
<freemangordon>
1352 user 3776 S /usr/sbin/alarmd
<freemangordon>
oh
<freemangordon>
what the?
<sicelo>
and permissions of the rtc?
hm has quit [Read error: Connection reset by peer]
<Wizzup>
I think that the less that runs as root the better
<Wizzup>
/dev/rtc0 is not audio on my droid btw
<freemangordon>
in general I agree
<freemangordon>
no, that's on fremantle
<Wizzup>
and if alarmd only needs roor for /dev/rtc? then we just make a single udev rule
<freemangordon>
so, in general I agree
<freemangordon>
but, what will happen if we have start second user session
<freemangordon>
*started
<Wizzup>
if the second session has access to the system bus then it can talk with it just the same I guess?
<freemangordon>
but it will try to start alarmd again
<freemangordon>
it is the same as if we start mce as user
<freemangordon>
from xsession
<sicelo>
btw why does it need two buses? can it not be on system bus only?
<freemangordon>
no idea
<freemangordon>
that's why I think that's a mess
<freemangordon>
Wizzup: it is not only /dev/rtc
<freemangordon>
it takes care for *all* the alarms in the system
<freemangordon>
which means that 'user' can delete /var/cache/alarm without going through dbus
<freemangordon>
/var/cache/alarmd
<freemangordon>
so, we either move cache dir to $HOME or run as root
<freemangordon>
but, I guess that'd require major changes
<freemangordon>
so yeah, the easiest way to go is rtc permissions
<freemangordon>
dsc_: you don't need osso_abook_contact_get_avatar() as it requires master contact
<freemangordon>
and I think we agreed that you want roster contact avatar
xmn has joined #maemo-leste
fab_ has quit [Quit: fab_]
fab_ has joined #maemo-leste
<sicelo>
at least I can confirm that setting 660 permissions, and root:audio ownership on rtc0 does make the UI set alarm properly
antranigv_ has joined #maemo-leste
antranigv has quit [Ping timeout: 252 seconds]
<inky>
i dont know if it's only for me, but from time to time i update maemo and try conversations., and whatever i write, reaches the other party, but whatever other party writes, doesn't reach me in conversations. reaches elsewhere.
<Wizzup>
what connection manager is ths?
pere has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
Livio_ has joined #maemo-leste
Livio has quit [Ping timeout: 260 seconds]
pere has quit [Ping timeout: 260 seconds]
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
pere has joined #maemo-leste
Livio_ has quit [Ping timeout: 260 seconds]
Livio has joined #maemo-leste
arno11 has joined #maemo-leste
arno11 has quit [Ping timeout: 246 seconds]
arno11 has joined #maemo-leste
hm has joined #maemo-leste
Anasko has quit [Read error: Connection reset by peer]