uvos | freemangordon: theres a wierd bug in osso-addressbook | 14:09 |
---|---|---|
uvos | freemangordon: sometimes when you click on a contact and then open the drop down menu the menu ends up in a loop where its continuesly resized | 14:09 |
freemangordon | coould you attach gdb in such case and provide backtrace of the loop? | 14:10 |
freemangordon | install debug symbols first ofc | 14:10 |
freemangordon | as I never seen that here | 14:10 |
freemangordon | *have never | 14:11 |
freemangordon | maybe it is something contact-specific (I doubt, but still) | 14:11 |
uvos | i did | 14:12 |
freemangordon | and? | 14:12 |
uvos | its not osso-addressbook, stoping the program dosent stop the resize loop | 14:12 |
uvos | its h-d somehow | 14:12 |
freemangordon | uvos: there are 2 osso-addressbook processes | 14:13 |
freemangordon | which one did you attach? | 14:13 |
freemangordon | lower or higher pid? | 14:13 |
uvos | lower it seams | 14:13 |
freemangordon | you must attach to higher | 14:13 |
uvos | ok | 14:13 |
freemangordon | lower is your beloved maemo-launcher :p | 14:14 |
uvos | mhh this again | 14:14 |
uvos | ok | 14:14 |
freemangordon | yes, this. and *this* is the reason such a complicated piece of SW opens in a split-second | 14:14 |
freemangordon | compare to the launch time of evolution | 14:14 |
uvos | benefits or no, benefits, its not a sustanable solution | 14:15 |
uvos | as soon as you are trying to accelerate a lib thats not dead | 14:15 |
freemangordon | will see | 14:15 |
freemangordon | anyway, this is aside | 14:15 |
freemangordon | uvos: besides that, I guess everything works fine, no? | 14:16 |
uvos | well | 14:16 |
uvos | mimes dont work | 14:16 |
uvos | but i gues it just dossent support those | 14:16 |
freemangordon | they do, in modest | 14:16 |
uvos | but would be very nice if it used xdg mimes | 14:16 |
uvos | right i mean xdg mimes | 14:16 |
freemangordon | tmm, they should | 14:16 |
uvos | dosent work | 14:16 |
freemangordon | osso-addressbook registers itself as text/x-vcard handler | 14:17 |
uvos | right this direction might work | 14:17 |
uvos | but like sms:// tel:// would open sphone or http:// should open default browser etc | 14:17 |
freemangordon | but it seems .vcf files are text/vcard | 14:17 |
uvos | also emails should open the default email client | 14:17 |
uvos | but it just uses modest anyways | 14:17 |
uvos | etc | 14:17 |
freemangordon | you mean xdg-open? | 14:18 |
freemangordon | uvos: actually sms:// and tel:// should not open sphone | 14:18 |
uvos | well not nesscarly xdg-open (the script) | 14:18 |
uvos | but it should use the mime database | 14:18 |
uvos | freemangordon: sure it should why not? | 14:18 |
freemangordon | but rather telepathy chat/call UI | 14:19 |
uvos | ??? | 14:19 |
uvos | it should open what is set as default | 14:19 |
uvos | that is sphone right now | 14:19 |
uvos | as its the only app that regisers for those mimes | 14:19 |
freemangordon | well, I mean in addressbook | 14:19 |
uvos | well thats the point | 14:19 |
freemangordon | it uses telepathy to handle different types of contact communication properties | 14:19 |
uvos | it should check what is the default application to handle whatever is clicked | 14:20 |
freemangordon | it cannot use mime | 14:20 |
freemangordon | it simply won;t work | 14:20 |
freemangordon | as sms:// is just another chat in telepathy world | 14:20 |
uvos | even if you dont want that for tp suff (massive mistake imo) | 14:20 |
uvos | what your going to use telepathy for http:// ? | 14:21 |
freemangordon | see, we are again using standard, just not xdg :) | 14:21 |
freemangordon | no, it call hildon_uri_open(), ior something | 14:21 |
freemangordon | sec | 14:21 |
uvos | and hildon_uri_open should open firefox or whatever browser is registerd as default | 14:21 |
uvos | i dont think you can argue any different sanely | 14:22 |
freemangordon | sure | 14:22 |
uvos | and that means co-operating with xdg | 14:22 |
freemangordon | the point is that addressbook that decides on that | 14:22 |
freemangordon | see https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-contact-field.c#L4681 | 14:22 |
freemangordon | *it is not addressbook that decides | 14:22 |
uvos | i also dont see why tel:// can also use xdg, opening a tp window need not be the only possibility | 14:23 |
uvos | *cant | 14:23 |
freemangordon | because tel:// is not any diferent than skype:// for example | 14:23 |
freemangordon | or viber:// or whatever | 14:23 |
freemangordon | we shall ask telepathy to handle that | 14:24 |
uvos | i dont follow | 14:24 |
freemangordon | tel:// is just another protocol in telepathy world | 14:24 |
uvos | same with xdg really | 14:24 |
freemangordon | it is more complicated | 14:24 |
freemangordon | lemme give you an example | 14:24 |
uvos | user clicks on phone numner -> check if tp ui is active -> its not -> xdg-open tel:// | 14:24 |
freemangordon | there is no "tp ui" | 14:25 |
freemangordon | wait, lemme try to explain | 14:25 |
uvos | sure there is conversations for instance (for sms://) | 14:25 |
freemangordon | no, it is just "dbus client" in tp workd | 14:25 |
freemangordon | that happens to support Text channels with handle type of 0 | 14:26 |
uvos | i dont see how this is material | 14:26 |
freemangordon | example: back then skype was used to call landlines, so, you can call +123999888 by using either pstn or skype | 14:26 |
freemangordon | what will xdg do in that case? | 14:26 |
freemangordon | the same for viber now, btw | 14:27 |
freemangordon | so, how is xdg going to implement "call with skype" functionality? | 14:27 |
uvos | well you can choose to send skype://+123999888 or tel://+123999888 and it will end up in the right place | 14:27 |
freemangordon | no, you have tel://+123999888 and that's all | 14:27 |
freemangordon | in the addressbook I mean | 14:28 |
freemangordon | all you have is a phone number | 14:28 |
freemangordon | and you know this is mobile/landline/whatever | 14:28 |
uvos | so? the user has to make the choise about the protocoll somehwere | 14:28 |
freemangordon | but, just a phone number | 14:28 |
freemangordon | addressbook/tp does that for you automagically | 14:28 |
uvos | it must get the information from somewhere | 14:28 |
freemangordon | sure | 14:28 |
freemangordon | but it is already there, in a standarts | 14:29 |
freemangordon | lemme explain: | 14:29 |
freemangordon | skype protocol (example) has the so called "supported uri schemes" or "secondary vcard field", which tells telepathy what other types of uris it can handle | 14:30 |
freemangordon | so, primary vcard field of skype is x-skype, put it also have tel as supported uri scheme | 14:30 |
freemangordon | *but it also | 14:30 |
uvos | right | 14:31 |
uvos | skype.desktop is exactly the same | 14:31 |
uvos | it has tel:// and skype:// | 14:31 |
freemangordon | but, you don;t know which one is the primary handler of tel:// | 14:31 |
freemangordon | also, what about icons? | 14:31 |
uvos | yes you do | 14:31 |
uvos | this is how the default mime handlers work | 14:32 |
freemangordon | yes, I understand what you mean | 14:32 |
uvos | ie one .desktop file is coniserd default as per user preferances | 14:32 |
freemangordon | yeah, I know | 14:32 |
freemangordon | also, how do you connect EDS contacts with xdg mimetype? | 14:33 |
freemangordon | and with telepathy account | 14:33 |
uvos | well with telepathy account you dont | 14:33 |
uvos | if the user has something not telepathy as the default that part ill just not work obv | 14:33 |
uvos | since the backedn application (closed source skype applcation in this case) is not tp | 14:34 |
freemangordon | wait, sphone is not telepathy | 14:34 |
uvos | as per EDS contact the applcation (liek skype) looks up the phone number itself | 14:34 |
freemangordon | no, it is addressbook that does it for yopu | 14:34 |
uvos | if that ends up in EDS or its won database (as is the case for skype) depends on the program | 14:34 |
freemangordon | and provides both calling (from) and caller (to) account | 14:34 |
uvos | sure but it dosent have to, everything works without this | 14:35 |
freemangordon | and it becomes the mess android communication is | 14:35 |
uvos | ofc if its using tp, wich is a option you could have by having a magic tp.desktop file | 14:35 |
uvos | it would work as is | 14:35 |
freemangordon | no, tp is not an application | 14:35 |
uvos | so? | 14:35 |
freemangordon | it works in totally different way | 14:36 |
uvos | i saying it could work like this: | 14:36 |
uvos | you have a default .desktop file | 14:36 |
uvos | for a url | 14:36 |
uvos | if its any usual application the address book (like skype application or sphone) it xdg-opens the url. | 14:36 |
freemangordon | uvos: sorry to interrupt, but you forget about vcf and its fields | 14:36 |
uvos | if the handler is set to the magic tp.dekstop file | 14:37 |
freemangordon | because you don;t have urls in vcf | 14:37 |
uvos | it just informs tp | 14:37 |
uvos | sp | 14:37 |
uvos | so? | 14:37 |
freemangordon | so, I don;t see how you start with vcf and end in url | 14:37 |
uvos | translating vcf fields to urls is not that hard | 14:37 |
freemangordon | who will do it? | 14:37 |
uvos | the addressbook? | 14:37 |
freemangordon | it does not have any knowledge on that | 14:38 |
uvos | hmm so osso-addressbook deals in eds contacts no? | 14:38 |
freemangordon | sure | 14:38 |
uvos | and when you click on a filed it coul take that field | 14:38 |
freemangordon | yes | 14:39 |
uvos | prepend a url depending on the field type and then decide what to do | 14:39 |
uvos | either passing to tp as it dose right now | 14:39 |
freemangordon | this is where it is broken aiui | 14:39 |
freemangordon | tp uses another shape of contact uid | 14:39 |
freemangordon | it does not use url | 14:39 |
uvos | so? | 14:39 |
freemangordon | so, addressbook should support a DB to translate eds vcard_field<->url | 14:40 |
uvos | if the magic desktop file is set as default for that url it just dose whatever it dose rn to get the field to be handeld by tp | 14:40 |
uvos | pretty sure this exists | 14:40 |
freemangordon | no | 14:40 |
freemangordon | afaik | 14:40 |
uvos | maybe check what gnome-contatcs dose | 14:41 |
freemangordon | because vcf and telepathy have no idea about mime | 14:41 |
uvos | it dose exactly this | 14:41 |
freemangordon | well, feel free to check :) | 14:41 |
uvos | ie you click on a feld | 14:41 |
uvos | it opens via xdg or its own dialer ui depending on settings | 14:41 |
freemangordon | also, are you sure they support skype call of phone number? | 14:41 |
freemangordon | as I am almost sure they don;t | 14:41 |
uvos | it just xdg-opens tel:// | 14:42 |
freemangordon | the only place I have ever seen that (besides skype ofc) is n900 addressbook | 14:42 |
uvos | if thats skype for you | 14:42 |
uvos | yeah | 14:42 |
uvos | ofc | 14:42 |
uvos | it opens skype | 14:42 |
freemangordon | uvos: I think I explained the usecase | 14:42 |
freemangordon | you can open tel:// by using either phoneui or skype | 14:42 |
uvos | right as choosen by the user | 14:43 |
uvos | i really dont se the problem | 14:43 |
freemangordon | the problem is that we don;t have anything like that in place | 14:43 |
freemangordon | but we have everything like that in place in telepathy | 14:43 |
uvos | but it exists allready | 14:43 |
uvos | thats the point | 14:43 |
uvos | all it has to do is use gnome infra to open a url | 14:44 |
freemangordon | ok, maybe trust me on that one, I am dealing with addressbook/tp/eds/etc for that last ~3 years | 14:44 |
uvos | anyhow none of this touches at all | 14:44 |
uvos | that actions that deff cant be handled by tp at all | 14:45 |
uvos | (home page fields email etc) | 14:45 |
freemangordon | like? | 14:45 |
freemangordon | they are not | 14:45 |
uvos | must be opend via xdg | 14:45 |
freemangordon | they are more or less xdg-open | 14:45 |
freemangordon | sure | 14:45 |
uvos | except it dosent work | 14:45 |
freemangordon | I know | 14:45 |
freemangordon | "open address" is still to be REed | 14:45 |
freemangordon | this https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-contact-field.c#L4312 | 14:46 |
freemangordon | email works | 14:46 |
freemangordon | but not in a way you expect :) | 14:46 |
uvos | yeah it breaks user defaults and forces a single email program i dont use | 14:46 |
uvos | pretty broken imo | 14:46 |
uvos | functionally wise | 14:46 |
freemangordon | uvos: oh, for tp - addressbook is not just that, it is addressbook + presence | 14:48 |
freemangordon | with your xdg scheme, how is presence updated? | 14:48 |
uvos | i dont see how these things are related at all | 14:49 |
uvos | the addressbook gets presence information form somewhere | 14:49 |
freemangordon | if you have standalone application that lives its own life? | 14:49 |
freemangordon | yes, telepathy | 14:49 |
uvos | that somewhere need not be the same place it ends up opening fields with | 14:49 |
uvos | also i strongly dislike presence features | 14:49 |
uvos | but thats beside the point | 14:50 |
freemangordon | sure it does, because the field button has account status | 14:50 |
uvos | so? | 14:50 |
uvos | how is that related to what heppens when you click on it | 14:50 |
freemangordon | where do you gat account status from if you get rid of telepathy? | 14:50 |
freemangordon | *get | 14:50 |
uvos | if you dont have tp installed presence dosent work | 14:50 |
uvos | i dont see how this is a problem | 14:50 |
uvos | if you dont have the accout configured fro tp | 14:50 |
uvos | presence dosent work for the fields that acount services | 14:51 |
uvos | i again dont se the porblem | 14:51 |
freemangordon | you also don;t have your account buddies inported in addressbook too | 14:51 |
freemangordon | so, basically you have evolution | 14:51 |
freemangordon | so, if you want evolution, just install and use it | 14:52 |
uvos | this is a straw man argument | 14:52 |
uvos | if its not configured to use tp | 14:52 |
uvos | it dosent use tp | 14:52 |
freemangordon | no, really, osso-addressbook is contacts+presence | 14:52 |
uvos | that means no tp features | 14:52 |
freemangordon | 80% of the code deals with tp | 14:52 |
uvos | irellivant | 14:53 |
uvos | adding the abillity to open xdg mimes takes away nothing | 14:53 |
freemangordon | without that, it is no different than evolution and makes no sense to me to have it | 14:53 |
uvos | and adds lots of options | 14:53 |
freemangordon | that's another story | 14:53 |
freemangordon | opening mimes != remove telepathy :) | 14:53 |
uvos | i never said to remvoe tp | 14:53 |
uvos | i said please add the option to open xdg mimes | 14:54 |
uvos | thats all | 14:54 |
uvos | evolution has bad ui for small screens | 14:54 |
uvos | so there is use beyond tp integration | 14:54 |
freemangordon | I don;t think this should be an option (mime open) | 14:54 |
freemangordon | but, I want to have have it working as it do in fremantle before changing it | 14:55 |
freemangordon | xdg open should be easy | 14:55 |
freemangordon | but, we shall consider osso as well | 14:55 |
freemangordon | becuase hildon-mime-open looks for osso services | 14:55 |
freemangordon | maybe this is where the change shall happen | 14:55 |
freemangordon | if it does not find osso service for mime type, do xdg open on it | 14:56 |
uvos | it should def allow rearaging defaults | 14:56 |
uvos | otherwise its mostly useless | 14:56 |
freemangordon | maybe have a look @ https://github.com/maemo-leste/libhildonmime/blob/master/libhildonmime/hildon-mime-open.c#L535 | 14:57 |
freemangordon | i guess we can fallback to xdg open here https://github.com/maemo-leste/libhildonmime/blob/master/libhildonmime/hildon-mime-open.c#L565 | 14:57 |
freemangordon | should be a trivial fix | 14:57 |
uvos | totaly useless if it dosent allow giveing prio over a osso service | 14:58 |
uvos | so no thats not a fix | 14:58 |
freemangordon | well, I guess it can be changed | 14:58 |
freemangordon | well, if you don;t want mdest, just uninstall it | 14:59 |
freemangordon | *modest | 14:59 |
freemangordon | then you won;t have osso service as email and xdg open will work as you want it to | 14:59 |
uvos | osso has insane interdepdancy problems | 14:59 |
uvos | that might work for modest | 14:59 |
freemangordon | that's another story | 14:59 |
uvos | but its not a good solution | 15:00 |
freemangordon | I would say on maemo osso services shall prevail over gnome ones | 15:00 |
uvos | i would say its not our place to say what service the user wants to use | 15:00 |
freemangordon | not to say I *never* said I want evolution to be my default vcf handler | 15:00 |
freemangordon | but it registers itself as such | 15:01 |
uvos | no think your os dident allow you to choose anything but evoltion as vcf handler | 15:01 |
uvos | and you have arrived at maemo :P | 15:01 |
freemangordon | welcome to meamo :p | 15:01 |
freemangordon | yeah, I got your point | 15:02 |
freemangordon | and you are right | 15:02 |
freemangordon | but I don;t think now is the right time to fix that | 15:02 |
freemangordon | as it won;t be an easy fix | 15:02 |
sicelo | Nicely said | 15:09 |
sicelo | We likely won't have skype for any of the supported phones however. Still, the presence is UX some of us would love to see supported :-) | 15:13 |
freemangordon | sicelo: think about viber | 15:13 |
freemangordon | it uses phone numbers as wee | 15:14 |
sicelo | I see. Never used it. Do they support arm(hf|64)? | 15:14 |
freemangordon | they support something linux, but that's not the point | 15:16 |
freemangordon | in long term *we* shall support it | 15:16 |
dsc_ | ha, tel:// and callto:// already taken by conversations https://github.com/maemo-leste/conversations/blob/master/src/lib/globals.h#L9 | 15:16 |
dsc_ | first come first served!! | 15:17 |
freemangordon | :D | 15:17 |
dsc_ | suckersss! | 15:17 |
dsc_ | just joking, they are placeholders | 15:17 |
freemangordon | sicelo: and in the light of today's news re DMS... | 15:17 |
dsc_ | until we figure out how to handle these mimes | 15:17 |
freemangordon | hmm, what do you mean? it should be in shape of tel://+1234888999000 or something | 15:18 |
freemangordon | and you dial out by using /ring/tel/account0 | 15:18 |
freemangordon | well, dial: https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-contact-field.c#L4515 | 15:20 |
freemangordon | dsc_: ^^^ | 15:20 |
dsc_ | oh, ehh.. no comment on the current shape/format of my link just now - should be considered 'dev' | 15:20 |
dsc_ | so that regex is probably wrong | 15:21 |
freemangordon | not sure how you create a temp account for the number to dial | 15:21 |
freemangordon | maybe you can call osso-abook to create one for you :) | 15:21 |
dsc_ | right | 15:22 |
dsc_ | i dont know either :) | 15:22 |
freemangordon | shouldn;t be that hard though | 15:22 |
freemangordon | dsc_: btw, if you install addressbook, and you have some telepathy account set-up , it will pull contacts from there and will allow you to start chat | 15:23 |
dsc_ | freemangordon: how does addressbook allow you to start chatting? | 15:24 |
dsc_ | (since conversations is used to start chatting :P) | 15:25 |
freemangordon | it call telepathy | 15:25 |
freemangordon | *calls | 15:25 |
dsc_ | ah | 15:25 |
freemangordon | and if conversations is tp client, it will be called | 15:25 |
freemangordon | in my VM here it is empathy that's registered | 15:26 |
freemangordon | and as soon as I click on gtalk contact, empathy chat window pops out | 15:26 |
dsc_ | I see | 15:26 |
freemangordon | this https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-contact-field.c#L4527 | 15:26 |
freemangordon | try it, it is fun :) | 15:27 |
dsc_ | I wonder how tp-mission-control launches such client | 15:27 |
freemangordon | it does not | 15:27 |
dsc_ | (if mission-control does this, idk *which* tp thing does this, if at all) | 15:27 |
dsc_ | maybe its a dbus thing? | 15:27 |
freemangordon | mission-control does not deal with channels | 15:27 |
freemangordon | yes | 15:27 |
dsc_ | right | 15:27 |
dsc_ | ok | 15:27 |
freemangordon | it is dbus thing | 15:27 |
dsc_ | cool | 15:27 |
freemangordon | check in /usr/share/telepathy/clients | 15:28 |
freemangordon | in theory this means that you can have as many clients per channel type as you want | 15:28 |
freemangordon | and all of them will be able to chat | 15:28 |
freemangordon | I think conversations shall implement org.freedesktop.Telepathy.Client.Handler | 15:29 |
dsc_ | Wizzup: ^ :D | 15:29 |
freemangordon | see Empathy.Chat.client | 15:30 |
dsc_ | Yeah I see it | 15:30 |
freemangordon | the same goes for audio/video/etc | 15:30 |
freemangordon | do we have that in conversations-ui? | 15:30 |
dsc_ | org.freedesktop.Telepathy.Channel.Type.Text | 15:30 |
dsc_ | right | 15:30 |
dsc_ | ok | 15:30 |
freemangordon | mhm | 15:30 |
dsc_ | no | 15:31 |
dsc_ | text for now | 15:31 |
freemangordon | yes, that's what I mean | 15:31 |
dsc_ | so Wizzup and I were doing telepathy stuff, I got very frustrated with telepathy-qt, mostly because I rather focus on implement UI / QML stuff | 15:32 |
dsc_ | dbus is a bit above my paygrade | 15:32 |
freemangordon | btw, if it does not work fro rooms etc, it is because of TargetHandleType | 15:32 |
freemangordon | hmm, dbus is very easy with qt | 15:32 |
freemangordon | you bsically get everything for free | 15:32 |
dsc_ | we are still trying to figure out some stuff (nothing complicated, just something I rather not focus on) | 15:32 |
freemangordon | I gained some experience with telepathy while working on addressbook, can help if you have particular (or general) questions | 15:33 |
dsc_ | hmm yeah actually in this case its not so much about dbus, more about 'how to massage tp' in a way where we can listen and send messages | 15:33 |
dsc_ | + multi account support | 15:33 |
dsc_ | I forgot specifically what, but it was annoying for me | 15:33 |
freemangordon | my understanding is that you have to register your client in /usr/share/telepathy/clients | 15:34 |
freemangordon | and tp/dbus will just call it | 15:34 |
dsc_ | right | 15:34 |
freemangordon | I 'guess' the file name consists of service that implements the client + .client | 15:35 |
dsc_ | there is a `telep` branch where I was trying things and mostly failing ,ended up hardcoding the account: https://github.com/maemo-leste/conversations/blob/telep/src/lib/tp.cpp#L12 | 15:35 |
freemangordon | so, conversations ui shall expose com.maemo.conversations.ui.chat | 15:35 |
dsc_ | right | 15:36 |
freemangordon | does it do it now? | 15:36 |
freemangordon | also, have a look at https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-contact-field.c#L4527 | 15:36 |
freemangordon | this call is passing both 'from' and 'to' accounts it seems | 15:37 |
freemangordon | and I suspect your handler gets them, so you don;t have to hardcode ;) | 15:37 |
freemangordon | you cannot simple start chat from a chat client | 15:37 |
freemangordon | someone else shall start it, you just obey | 15:37 |
dsc_ | eh its a bit out of my comfort zone, I think Wizzup is going to look at this first ^^ | 15:37 |
freemangordon | this is my understanding | 15:37 |
dsc_ | thing is, I'm just a UI monkey | 15:38 |
freemangordon | come on | 15:38 |
dsc_ | what even is a computer?? | 15:38 |
dsc_ | etc | 15:38 |
freemangordon | it is fun+lots of coffee :) | 15:38 |
dsc_ | :D | 15:38 |
freemangordon | no, really, once you get it (or someone explains it to you) it all fits tight | 15:38 |
freemangordon | and qt is sweet to code with | 15:39 |
dsc_ | qt is indeed sweet | 15:39 |
freemangordon | https://telepathy.freedesktop.org/doc/book/sect.channel-dispatcher.clients.html | 15:39 |
dsc_ | its good to know you are a TP god, when we continue we'll keep it in the back of our minds (albeit I think Wizzup only needs to look at it for 15sec and he knows the solution) | 15:40 |
freemangordon | no, O am not TP god, that's for sure | 15:40 |
freemangordon | *I am not | 15:40 |
dsc_ | im traveling currently with only laptop which is not super powerful so its a bit annoying | 15:40 |
dsc_ | sun is shining onto the screen etc. | 15:40 |
dsc_ | need a real setup first | 15:40 |
dsc_ | im moving to .bg as you know | 15:41 |
dsc_ | im in the middle of it | 15:41 |
freemangordon | ah, you will move! | 15:41 |
dsc_ | I got my 5 year residency card yesterday ^^ | 15:41 |
freemangordon | good :) | 15:41 |
freemangordon | will have a beer together when you settle | 15:41 |
dsc_ | yes!! | 15:42 |
freemangordon | in the meanwhile, see https://telepathy.freedesktop.org/doc/book/sect.channel-dispatcher.clients.html#sect.channel-dispatcher.clients.impl.tp-glib | 15:42 |
freemangordon | telepathy-qt should have the same | 15:42 |
dsc_ | right | 15:43 |
freemangordon | so it looks like a couple of lines of code to register your client | 15:43 |
dsc_ | I think clients are activated upon an existing account | 15:44 |
dsc_ | i.e: if a tp account does not exist yet, you have to create one | 15:44 |
freemangordon | "to" account? | 15:45 |
dsc_ | https://github.com/maemo-leste/conversations/blob/telep/src/lib/tp.cpp#L12 | 15:45 |
dsc_ | uhmm | 15:45 |
freemangordon | hmm, no, this is 'from' account | 15:45 |
freemangordon | and you can get that by asking TpAccountManager | 15:46 |
freemangordon | but really, it is not conversation-ui's job to do it | 15:46 |
freemangordon | you get it for free from addressbook | 15:46 |
freemangordon | or from rtcom-el | 15:46 |
freemangordon | (as local-uid or whatever it was) | 15:47 |
dsc_ | < freemangordon> and you can get that by asking TpAccountManager | 15:47 |
dsc_ | yeah, was trying this one, to enumerate the accounts | 15:47 |
dsc_ | had some problems with it | 15:47 |
freemangordon | yes, but you should not do it, addressbook already does all this for you | 15:48 |
dsc_ | no point in discussing it really, because I dont have examples or logs for you | 15:48 |
freemangordon | lemme show you something | 15:48 |
dsc_ | its all at home on my desktop | 15:48 |
freemangordon | see https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-account-manager.c#L1446 | 15:49 |
freemangordon | basically https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-account-manager.c#L1413 | 15:49 |
freemangordon | tp_account_manager_new_with_factory() is where the magic happens :) | 15:50 |
dsc_ | ok yes, conversations shouldnt be creating accounts | 15:50 |
dsc_ | but it needs to connect to an account | 15:50 |
dsc_ | and in order for this it needs to know about which account(s) exist | 15:50 |
freemangordon | yes, I know, you were forced to | 15:50 |
freemangordon | but not anymore now we have addressbook to choose the account you want to use | 15:50 |
dsc_ | so conversatios asks the addressbook? | 15:51 |
freemangordon | mhm | 15:51 |
freemangordon | lemme see on my fremantle device | 15:51 |
freemangordon | yes, when you click on "New IM" you are presented with "Select account" dialog | 15:52 |
freemangordon | but, what is important, is that I think this happens over dbus | 15:52 |
freemangordon | mhm | 15:53 |
freemangordon | ugh, and I am still to RE that :( | 15:54 |
dsc_ | ok so ill spare you some time right now becuase I think it is pointless to discuss this, I ought to look into some TP basics/terminology first, which I did 2 months ago - but I already forgot everything | 15:54 |
dsc_ | i got rather frustrated with that whole telepathy-qt/dbus part | 15:54 |
dsc_ | so I asked Wizzup to look at it ^^ | 15:55 |
freemangordon | yeah, ok | 15:55 |
dsc_ | but we *were* able to eventually send and receive messages over tp with conversations in our test, albeit hardcoded - it was pretty cool | 15:56 |
freemangordon | yeah | 15:57 |
freemangordon | it will become even more cool when it gets integrated with AB | 15:57 |
dsc_ | oh for sure :) | 15:57 |
freemangordon | yeah, it seems you basically call com.nokia.osso_addressbook open_group and it will open a disalog to select | 16:01 |
freemangordon | *dialog | 16:01 |
dsc_ | so | 16:07 |
dsc_ | New IM (from conversations) -> call 'com.nokia.osso_addressbook open_group' | 16:07 |
dsc_ | which is a dbus thingy | 16:07 |
dsc_ | yes? :P | 16:07 |
dsc_ | or from AB? (or both, I guess) | 16:08 |
freemangordon | both | 16:08 |
dsc_ | yep | 16:08 |
freemangordon | run-standalone.sh dbus-send --session --dest=com.nokia.osso_addressbook --type=method_call --print-reply /com/nokia/osso_addressbook com.nokia.osso_addressbook.open_group string:"" string:"google-talk" boolean:false | 16:09 |
freemangordon | asks me to select gtalk buddy on n900/fremantle | 16:09 |
freemangordon | or, if you pass "dscbot0" as group, the same will happen | 16:10 |
freemangordon | not sure what happens if you have multiple online accountys | 16:10 |
freemangordon | *account | 16:10 |
freemangordon | argh | 16:10 |
freemangordon | *accounts | 16:10 |
freemangordon | hmm, it seems conversations-ui calls osso-abook directly, not through dbus | 16:11 |
freemangordon | maybe it uses osso_abook_tp_account_selector_get_account | 16:13 |
freemangordon | will check that when it comes to it | 16:13 |
dsc_ | right | 16:14 |
freemangordon | we can wrap that api in qt, the same way it is done for the other specific maemo components | 16:14 |
freemangordon | or I can simply implement "select_account" functionality in addressbook | 16:15 |
freemangordon | (I guess this is more portable) | 16:15 |
freemangordon | uvos: https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Generic_Platform_Components/Using_Address_Book_API | 16:47 |
freemangordon | fyi | 16:47 |
freemangordon | oh, we need http://repository.maemo.org/extras/pool/fremantle/free/source/o/osso-abook-plugin-merge-contacts/ imported | 21:28 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!