| *** T7g has quit IRC | 00:14 | |
| *** woglinde has quit IRC | 00:19 | |
| *** woglinde_ has joined #maemo-devel | 00:24 | |
| *** t7g__ has joined #maemo-devel | 01:31 | |
| *** t7g_ has quit IRC | 01:33 | |
| *** woglinde has joined #maemo-devel | 01:43 | |
| *** Miniscalope has joined #maemo-devel | 01:46 | |
| *** woglinde_ has quit IRC | 01:58 | |
| *** jpetersen has quit IRC | 01:59 | |
| *** Miniscalope has left #maemo-devel | 02:07 | |
| *** kamui__ has joined #maemo-devel | 02:11 | |
| *** shinkamui has quit IRC | 02:17 | |
| *** woglinde_ has joined #maemo-devel | 02:36 | |
| *** woglinde1 has joined #maemo-devel | 02:41 | |
| *** woglinde has quit IRC | 02:42 | |
| *** woglinde_ has quit IRC | 02:45 | |
| *** JPohlmann has quit IRC | 02:59 | |
| gdfire | anyone know how to create desktop widget with pyqt? | 03:15 |
|---|---|---|
| woglinde1 | same as with qt | 03:16 |
| *** woglinde has joined #maemo-devel | 03:29 | |
| *** woglinde_ has joined #maemo-devel | 03:34 | |
| *** woglinde has quit IRC | 03:40 | |
| *** woglinde1 has quit IRC | 03:43 | |
| gdfire | i don't know how to transalate c++ to python | 03:45 |
| gdfire | i ave little time to learn | 03:47 |
| *** gdfire has quit IRC | 03:50 | |
| *** BabelO has quit IRC | 03:54 | |
| *** pH5_ has joined #maemo-devel | 04:02 | |
| *** pH5 has quit IRC | 04:18 | |
| *** pH5_ has quit IRC | 04:19 | |
| *** VDVsx has quit IRC | 04:27 | |
| *** woglinde_ has quit IRC | 04:44 | |
| *** kamui__ is now known as shinkamui | 07:10 | |
| *** flux has quit IRC | 07:16 | |
| *** DocScrutinizer51 has quit IRC | 07:30 | |
| *** Docscrutemp has joined #maemo-devel | 07:30 | |
| *** Docscrutemp is now known as DocScrutinizer51 | 07:31 | |
| *** Acedip has joined #maemo-devel | 08:16 | |
| *** flux has joined #maemo-devel | 09:39 | |
| *** blanc has joined #maemo-devel | 10:57 | |
| *** Acedip has quit IRC | 11:16 | |
| *** BabelO has joined #maemo-devel | 13:01 | |
| *** kamui__ has joined #maemo-devel | 14:11 | |
| villager | ruskie: I just uploaded syncevolution 0.9.2 beta, and built it against curl instead of soup since there were complaints about soup... | 14:21 |
| villager | I suppose that was perhaps you complaining | 14:22 |
| ruskie | yeah that was me | 14:22 |
| ruskie | I'll try it | 14:22 |
| ruskie | I actually managed to build after that patch but seems to have failed to do so with curl | 14:23 |
| ruskie | then I tried a more recent version of libsoup 2.26 and 2.27 | 14:23 |
| ruskie | basically with 2.27 I got passed SSL issues | 14:24 |
| ruskie | but still basic auth didn't work | 14:24 |
| villager | I'm working on writing a gui frontend in python | 14:25 |
| ruskie | well I can live without one :) | 14:25 |
| ruskie | I plan on having this in a cron job anyway :) | 14:25 |
| villager | I thought maemo didn't have cron | 14:26 |
| ruskie | built my own :) | 14:26 |
| ruskie | and zsh and a few other bits and pieces :) | 14:26 |
| villager | well, I guess a frontend would still be good for other people then | 14:27 |
| ruskie | true | 14:27 |
| ruskie | or for on-demand syncs | 14:27 |
| villager | was planning to hook it into libalarm, but not sure where to store the alarm cookie | 14:27 |
| ruskie | there any way to increas the verbosity? | 14:28 |
| villager | of syncevolution? | 14:28 |
| ruskie | yup | 14:28 |
| *** shinkamui has quit IRC | 14:29 | |
| ruskie | would like to see quite detailed info on what's happening with this | 14:30 |
| villager | checking the source a bit... | 14:31 |
| ruskie | there is some setting but I tried changing with not much luck | 14:32 |
| villager | there's a loglevel in the config.ini for each source... doesn't seem to be much more | 14:34 |
| villager | perhaps it just doesn't output that many messages | 14:36 |
| ruskie | ok... now atleast I get some info on what's going on(with curl) | 14:42 |
| ruskie | [INFO] CurlTransport Failure: error:140920DF:SSL routines:SSL3_GET_SERVER_HELLO:parse tlsext | 14:42 |
| ruskie | :) | 14:42 |
| ruskie | I think I'll try getting a more recent openssl | 14:43 |
| *** JPohlmann has joined #maemo-devel | 14:52 | |
| *** V13 has joined #maemo-devel | 15:02 | |
| V13 | hello | 15:02 |
| V13 | Is there a way to find out when a chat message is received *and* when it is acknowledged by the user ? | 15:03 |
| V13 | I looked at dbus signals using "dbus-monitor" but I couldn't find any signal for acknowledgment of the chat message | 15:03 |
| V13 | I'm testing with with MSN / telepathy-butterfly | 15:04 |
| V13 | ping | 15:05 |
| ruskie | only if the protocol supports it | 15:07 |
| ruskie | and don't be impatient ;) | 15:07 |
| V13 | oh.. | 15:07 |
| V13 | so there is not a standard signal from telepathy for that? | 15:08 |
| ruskie | look at the telepathy docs | 15:08 |
| ruskie | but I'm not aware of any IM clients that would send back a: I have read your message | 15:08 |
| V13 | I really can't understand the specification of dbus on telepathy. I'm not very good with dbus and it confuses me. So I uses dbus-monitor and some guessing. | 15:09 |
| V13 | "I uses" == "I'm using" | 15:09 |
| V13 | oh... no no no | 15:09 |
| V13 | that's not what I want. | 15:09 |
| ruskie | what then? | 15:09 |
| ruskie | that's what I understood | 15:10 |
| V13 | Example: when you receive a chat message there is a notification and the top-left icon becomes white. | 15:10 |
| ruskie | yes | 15:10 |
| V13 | that lats until you acknowledge the message (i.e. read it) | 15:10 |
| V13 | lasts | 15:10 |
| ruskie | ahh | 15:10 |
| V13 | that's what i'm looking for | 15:10 |
| ruskie | to active that notification? | 15:10 |
| ruskie | erm activate | 15:10 |
| V13 | hm. no | 15:10 |
| ruskie | deactivate it? | 15:10 |
| V13 | just find out when the notification is no longer active | 15:10 |
| V13 | i don't want to mess with it... just get it's status changes | 15:11 |
| ruskie | hmm | 15:11 |
| ruskie | that wouldn't be part of telepathy I think | 15:11 |
| V13 | or rtcomeventlogger | 15:11 |
| ruskie | rtcom-notification-ui python-notify libnotify1 libhildonnotify0 hildon-plugins-notify-sv <-- probably one of these is more likely | 15:12 |
| V13 | I see signals only from notification. (/org/freedesktop/Notifications) | 15:12 |
| ruskie | that would be libnotify1 sending it to a notification daemon | 15:12 |
| V13 | but I can't match this against any other signal that actually says that this is a chat message notification | 15:12 |
| ruskie | it's not a chat message notification... I think it's a generic notification that has a do this when I click on it content | 15:13 |
| V13 | so, I can find out that a chat message arrived and that a notification is no longer shown. But I can't match those two | 15:13 |
| V13 | exactly. | 15:13 |
| V13 | I'm writting a custom notification program | 15:13 |
| ruskie | did you dump the entire stuff from dbus-monitor ? | 15:13 |
| V13 | well.. I do "dbus-monitor type=signal" | 15:14 |
| V13 | the system bus has no info at all | 15:14 |
| V13 | only the session | 15:14 |
| V13 | Should I try to trace the method calls instead of looking for signals ? | 15:14 |
| V13 | (I can copy-paste you the messages. I'm testing it right now) | 15:15 |
| ruskie | try to trace everything | 15:15 |
| ruskie | for half a minute or so | 15:15 |
| V13 | I did | 15:15 |
| ruskie | hmm I'm not sure if notifications have any feedback | 15:16 |
| ruskie | or as you state status changes | 15:16 |
| V13 | perhaps I'm asking the wrong questions... | 15:16 |
| ruskie | you would like to know when a user acknolweldges a notification | 15:17 |
| V13 | Is there any other way to find out the duration that a user needs to be notified ? (e.g. the duration to blink the led when there is a missed incoming call) | 15:17 |
| V13 | somehow mce (right?) is notified for start and stop of an event. No? | 15:17 |
| ruskie | maybe by this: hildon-plugins-notify-sv | 15:17 |
| ruskie | Sound and vibra notification plugin | 15:17 |
| V13 | is there documentation for it ? | 15:18 |
| *** jebba has quit IRC | 15:19 | |
| V13 | I can't find something... | 15:21 |
| V13 | I believe that I can do this by polling eventlogger database and looking for unacknowledged events, but that would be very bad for battery. right ? | 15:22 |
| *** DocScrutinizer51 has quit IRC | 15:27 | |
| *** Docscrutemp has joined #maemo-devel | 15:27 | |
| *** Docscrutemp is now known as DocScrutinizer51 | 15:27 | |
| *** bjangle has joined #maemo-devel | 15:29 | |
| bjangle | Whats the easiest way to port to something to my n800? create a project with madde, shove the stuff into src, change the prog.pro file, mad make? | 15:35 |
| bjangle | gives make targets not found etc. | 15:37 |
| *** DocScrutinizer51 has quit IRC | 15:37 | |
| *** Docscrutemp has joined #maemo-devel | 15:37 | |
| *** Docscrutemp is now known as DocScrutinizer51 | 15:37 | |
| *** blanc has quit IRC | 15:43 | |
| *** blanc has joined #maemo-devel | 15:44 | |
| ruskie | hmm villager does this look proper to you: src/syncevo/Cmdline.cpp:988:boost::replace_first(assignment, "= syncml:auth-basix", "= basic"); ? | 15:49 |
| ruskie | considering everywhere else it's: syncml:auth-basic ? | 15:50 |
| villager | don't know | 15:51 |
| villager | that seems to only be part of the unit tests though | 15:52 |
| ruskie | hmm | 15:53 |
| villager | so probably not critical | 15:54 |
| ruskie | still trying to figure out why basic doesn't work | 15:54 |
| villager | not even compiled in | 15:54 |
| *** VDVsx has joined #maemo-devel | 15:56 | |
| * ruskie considers if syncevolution is the problem here | 15:56 | |
| *** sleipnir has joined #maemo-devel | 15:59 | |
| *** bjangle has quit IRC | 16:08 | |
| *** blanc has quit IRC | 16:09 | |
| ruskie | http://bugzilla.moblin.org/show_bug.cgi?id=2429 <-- hmm maybe this is the problem | 16:09 |
| ruskie | well I guess no sync for me | 16:17 |
| ruskie | thanks for the help villager I guess upstream needs to fixup things first | 16:28 |
| villager | maybe so | 16:28 |
| villager | been wondering if it would be a good idea to port opensync to maemo, not just syncevo | 16:30 |
| villager | unlike syncevo, it can do much more than just syncml... but perhaps it's more complex and less mature | 16:33 |
| ruskie | iirc it did evolve out of multisync | 16:33 |
| ruskie | so I doubt it's less mature | 16:34 |
| ruskie | but the api might be more in the air | 16:34 |
| villager | the webpage is more messy at least | 16:34 |
| ruskie | I rarely judge projects on their websites :) | 16:35 |
| villager | if I ported it, perhaps I could sync directly to google calendar, though | 16:35 |
| ruskie | well they have an #opensync chan around here | 16:35 |
| villager | I'll just make the python gui I'm writing able to work with both syncevo and opensync, perhaps | 16:36 |
| wnd | has opensync api finally been freezed? do the plugins actually compile against the core again? | 16:37 |
| villager | dunno | 16:37 |
| villager | you think it's not worth it trying to port it yet? | 16:37 |
| villager | hmm, the webpage says that opensync's syncml doesn't support one-way sync... but syncevo does, of course... hmm, doesn't give me much confidence in maturity | 16:40 |
| wnd | stable branch isn't very useful as is, and http://www.opensync.org/wiki/status suggests that migration to the new api is far from complete | 16:40 |
| V13 | that's for the last 1-2 years | 16:41 |
| villager | yeah, the faq says that the 0.3x and 0.4 can't even sync calendars | 16:41 |
| villager | guess it's better to fix stuff in syncevo then | 16:42 |
| wnd | V13, I know, but least now that 0.39 is out, "The complete API was examined and should be stable." | 16:45 |
| V13 | oh! | 16:48 |
| V13 | perhaps I'm lagging behind | 16:48 |
| V13 | ryskie: FWIW, I managed to do it. Here is how: I'm monitoring all notifications for com.nokia.HildonSVNotificationDaemon. At the beginning there is a call to PlayEvent with "urgency:1" as parameter. This call returns an ID. When the event is ACKed by the user, there is another call for StopEvent with this ID as the only argument | 16:59 |
| V13 | ruskie: So, I had to monitor 3 messages: The callfor Play Event, its reply and the call for StopEvent. The first two are matched by serial and reply_serial. The first and the last are matched by the ID that is returned by the second. | 17:00 |
| V13 | A relevant message is: method call sender=:1.249 -> dest=com.nokia.HildonSVNotificationDaemon serial=715 path=/com/nokia/HildonSVNotificationDaemon; interface=com.nokia.HildonSVNotificationDaemon; member=PlayEvent | 17:01 |
| V13 | btw, thanks for your help. | 17:01 |
| ruskie | :) | 17:06 |
| *** BirdFlew has joined #maemo-devel | 17:25 | |
| *** BirdFlew has left #maemo-devel | 17:29 | |
| *** JPohlmann has quit IRC | 17:44 | |
| *** JPohlmann has joined #maemo-devel | 17:45 | |
| *** DocScrutinizer51 has quit IRC | 17:53 | |
| *** simoneb_ has joined #maemo-devel | 17:54 | |
| *** DocScrutinizerXX has joined #maemo-devel | 17:56 | |
| *** DocScrutinizerXX is now known as DocScrutinizer51 | 17:56 | |
| *** lardman has joined #maemo-devel | 18:39 | |
| *** SpeedEvil has joined #maemo-devel | 18:41 | |
| simoneb_ | do i have to make a gtkbutton a composite widget to make it half transparent? | 19:09 |
| villager | ruskie: so if curl didn't help, think I should go back to libsoup? | 19:47 |
| villager | wonder if the N900's proxy settings are honored by default by soup | 19:47 |
| *** kodomo_ has joined #maemo-devel | 19:54 | |
| *** kodomo has quit IRC | 19:54 | |
| *** simoneb_ has quit IRC | 20:08 | |
| ruskie | villager, from what I know libsoup doesn't respect http_proxy | 20:18 |
| ruskie | or HTTP_PROXY | 20:18 |
| ruskie | curl does | 20:18 |
| ruskie | finally | 20:19 |
| ruskie | modified the digital nature theme to be nice and green | 20:19 |
| ruskie | though wrong colour... need to modify it a bit more | 20:19 |
| ruskie | villager, of course with syncevo not really sure how proprely something is implemented | 20:20 |
| ruskie | from looking at it it even implements it's own auth stuff | 20:20 |
| ruskie | instead of using the ones from the used lib | 20:20 |
| *** tealbird has joined #maemo-devel | 20:27 | |
| ruskie | villager, as far as curl is concerned it was a step closer... atleast I got out that something was whacked with the SSL SNI stuff | 20:32 |
| ruskie | then figured out that syncevo doesn't implement HTTP AUTH | 20:33 |
| V13 | is anyone familiar with the led of n900 ? | 20:35 |
| ruskie | there's a thread on it on how you can play with it | 20:35 |
| V13 | hm.. | 20:35 |
| V13 | m.o ? | 20:35 |
| ruskie | also some instructions on how to modify it in mce | 20:36 |
| V13 | yes.. i'm aware of that | 20:36 |
| V13 | i'm using /sys | 20:36 |
| V13 | but i'm afraid to change led_current | 20:36 |
| ruskie | erm | 20:36 |
| V13 | well i changed it some times.. but i restore it | 20:36 |
| V13 | somehow, the leds are disabled from time to time... | 20:37 |
| *** mj_ has joined #maemo-devel | 20:37 | |
| V13 | I've seen at least the blue having the led_current==0 and ==2 without me changing anything. | 20:37 |
| V13 | so it is manages by mce probably | 20:37 |
| V13 | managed | 20:37 |
| SpeedEvil | Generally the drivers manage all of the current so that it's safe | 20:38 |
| V13 | I'm wondering about safe values | 20:38 |
| SpeedEvil | which LEDs | 20:38 |
| V13 | well.. somehow they turn off the led | 20:38 |
| V13 | at least the blue and the green | 20:38 |
| SpeedEvil | the colour LED is driven by a horribly complex chip | 20:38 |
| SpeedEvil | which can do flash sequences and stuff | 20:38 |
| SpeedEvil | that is driven I think by mce | 20:38 |
| V13 | the chip does the sequences? not mce ? | 20:39 |
| * V13 newbee | 20:39 | |
| SpeedEvil | IIRC, yes. | 20:39 |
| V13 | arg... bad bad bad... | 20:39 |
| SpeedEvil | So it doesn't need to wake the CPU at all to flash | 20:39 |
| *** simoneb_ has joined #maemo-devel | 20:39 | |
| V13 | are there any docs on how to program that on n900 ? | 20:40 |
| mj_ | hi all, just want to know what is the best place to start learning for maemo? I have just installed ubuntu and the sdk. | 20:40 |
| * V13 just created a somehow complex threading app just to make the led flash | 20:40 | |
| SpeedEvil | V13: /etc/mce/mce.conf has how mce sets things up | 20:41 |
| SpeedEvil | to get lower level info - look at the drivers | 20:41 |
| V13 | I've seen mce.ini | 20:41 |
| V13 | but i supposed (wrong) that mce was interpreting the sequences. | 20:42 |
| V13 | any idea on where I get the source of mce or the source of the driver ? | 20:42 |
| SpeedEvil | drivers/i2c/chips/lp5521.c | 20:43 |
| SpeedEvil | the kernel is linked off maemo.org | 20:43 |
| V13 | found this: http://wiki.maemo.org/LED_patterns | 20:43 |
| V13 | thanks... I'll have a look | 20:43 |
| SpeedEvil | also - the datasheet for the above - lp5521 on national.com | 20:44 |
| SpeedEvil | http://www.national.com/pf/LP/LP5521.html | 20:45 |
| simoneb_ | mj_: http://maemo.nokia.com/developers/ is a good starting point, imho. check out the "get started" section | 20:45 |
| V13 | lp5521.c is not in mainline kernel. right ? | 20:46 |
| SpeedEvil | no | 20:47 |
| SpeedEvil | http://mxr.maemo.org/fremantle/source/kernel/drivers/i2c/chips/twl4030-madc.c#397 | 20:47 |
| SpeedEvil | is a cross reference of the kernel that's on device | 20:47 |
| SpeedEvil | there is a tarball and a patch file on the maemo site somewhere | 20:47 |
| V13 | thanks! | 20:48 |
| * ruskie wonders if he should post the modified digital nature theme on t.m.o | 20:50 | |
| V13 | why not? | 20:50 |
| *** tealbird has quit IRC | 20:50 | |
| V13 | gotit: /sys/class/leds/lp5523:b/device/engine1_mode | 20:51 |
| V13 | I mean:/sys/class/i2c-adapter/i2c-2/2-0032/engine1_mode | 20:51 |
| V13 | do you know if 2-0032 is constant or changes between reboots? | 20:51 |
| SpeedEvil | I think 2-0032 refers to a hardware address that won't change | 20:52 |
| SpeedEvil | what are you trying to do? | 20:52 |
| V13 | create a custom notification program | 20:52 |
| V13 | To be able to configure any kind of notification for distinct events | 20:53 |
| V13 | *especially* for mails | 20:53 |
| V13 | e.g. disable mail notification but have sms notification. | 20:53 |
| SpeedEvil | ah | 20:53 |
| mj_ | simoneb: thanks | 20:53 |
| SpeedEvil | is mce open-source? | 20:54 |
| *** kamui__ has quit IRC | 20:54 | |
| V13 | dunno | 20:54 |
| V13 | I've made a plugin-based app. no gui yet. works pretty well for now but it doesn't use hardware for the led | 20:54 |
| V13 | (only checks for im) | 20:55 |
| *** guido_g has joined #maemo-devel | 21:05 | |
| V13 | ok.. here is how the led works: In the above sysfs dir there are 3 files coresponding to 3 programable engines | 21:13 |
| V13 | engine[123]_mode | 21:13 |
| V13 | if you write "load" in engine1_mode, 2 more files are shown: engine1_leds and engine1_load | 21:14 |
| V13 | the first control the leds that will be used. The second accepts the string that is described in mce.ini | 21:14 |
| SpeedEvil | ah | 21:14 |
| V13 | after that you echo "run" to engine1_mode and it starts running | 21:14 |
| V13 | to stop it you echo "disabled" to engine1_mode | 21:14 |
| V13 | now.. I need to understand the engine[123]_leds | 21:15 |
| SpeedEvil | the above datasheet may be useful on national.com | 21:15 |
| V13 | lets see | 21:16 |
| DocScrutinizer51 | is the led contoller the same as in N810? | 21:16 |
| V13 | mce says LystiRX51 | 21:17 |
| V13 | that RX51 seems like N900 only | 21:18 |
| V13 | but there is another "NJoyRX48" which may be similar | 21:18 |
| SpeedEvil | work out which one is the lp* chip | 21:18 |
| V13 | find /sys -name lp\* | 21:20 |
| SpeedEvil | I mean in mce | 21:21 |
| DocScrutinizer51 | I've seen commands somewhere in init to start charge notification that looked like those 'programs' for the N810 chip (forgot the exact name - we adoped it for OM GTA03 though) | 21:22 |
| *** shinkamui has joined #maemo-devel | 21:27 | |
| V13 | OK, I updated http://wiki.maemo.org/LED_patterns with this info | 21:34 |
| *** mj_ has quit IRC | 21:39 | |
| villager | seems neither curl nor soup are built to respect the N900's proxy settings, guess I have to make my frontend fetch the settings or something before launching syncevolution | 21:46 |
| *** sleipnir has quit IRC | 21:47 | |
| V13 | got it... | 21:48 |
| V13 | the engineX_load has 9 bits: 0000rgb00 | 21:48 |
| V13 | rgb control the led :) | 21:48 |
| V13 | and cyan is really nice :) | 21:49 |
| *** simoneb_ has quit IRC | 21:55 | |
| lardman | :) | 21:59 |
| *** guido_g has quit IRC | 22:24 | |
| *** rsalveti has joined #maemo-devel | 22:48 | |
| *** woglinde has joined #maemo-devel | 23:09 | |
| *** GNUton-BNC has joined #maemo-devel | 23:12 | |
| woglinde | hi gnuton | 23:16 |
| *** VDVsx has quit IRC | 23:34 | |
| *** VDVsx has joined #maemo-devel | 23:35 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!