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