**** BEGIN LOGGING AT Sat Sep 27 02:59:57 2008 Sep 27 05:30:12 freesmartphone.org: 03jluebbe 07framework * r55c9246002fc 10/framework/subsystems/ogpsd/om.py: ogpsd: use the persist module for storing aiding data Sep 27 05:30:12 freesmartphone.org: 03jluebbe 07framework * r6d461349a3a9 10/ (etc/freesmartphone/persist/README setup.py): conf: add readme file for the persist directory and ship it Sep 27 06:43:45 freesmartphone.org: 03mickey 07framework * r5736992b5130 10/ (ChangeLog conf/example/frameworkd.conf framework/config.py): support configurable global debug log destination Sep 27 09:47:04 Hey Sep 27 10:18:09 Ainulindale, how are you? :) Sep 27 10:21:27 Fine and there Sep 27 10:23:01 fine, too Sep 27 10:23:16 Sorry, forgot to ask, I just woke up =) Sep 27 10:23:29 Going to fix myself a coffee to survive some more Sep 27 10:23:39 hehe :) Sep 27 10:25:49 do have some minutes over the course of your day to talk about the ophonekitd - libphonegui api? :) Sep 27 10:26:28 I have now Sep 27 10:26:49 (Mainly because it's saturday and my girlfriend is exceptionnaly working today) Sep 27 10:27:48 ah, fine Sep 27 10:28:21 I got the IncomingMessage callback working. I changed the bus from sms to sim Sep 27 10:28:41 There was a discussion about that a while ago Sep 27 10:30:21 when ophonekitd detects an incoming message it should call a function of libframeworkd-phonegui, right? I'm asking because till now all functions (phonegui_incoming_call_show(), phonegui_incoming_call_ui_hide()) had a hide() complement, but this doesn't make sense for message display, right? Sep 27 10:30:46 You're wrong :-) Sep 27 10:31:01 It doesn't make sense to you because you already know how you want to warn the user Sep 27 10:31:10 What if I want to display a messagebox with a close button ? Sep 27 10:31:15 Which is stupid of course but could happen Sep 27 10:31:28 And what if I want to close it automatically after 10 seconds through ophonekitd ? Sep 27 10:32:33 hm, but ophonekitd has no signal which indicates something like "call released". What do you think about? Sep 27 10:32:50 Yes there is Sep 27 10:32:55 For call released Sep 27 10:33:01 There's the call status handler Sep 27 10:33:08 yes, but not for "message released" Sep 27 10:33:42 (I knew you would lead the conversation to that :-p) Sep 27 10:34:35 Even if the event isn't currently implemented nor will eventually exist Sep 27 10:34:37 call show/hide makes sense, but not for messages Sep 27 10:34:49 And even if, and I agree, it could make no sense Sep 27 10:35:01 As a big part of the library will be show/hide Sep 27 10:35:08 and they're functionnaly simple to understand Sep 27 10:35:34 I would like to duplicate this logic for everything even if it implies to intentionnaly write empty functions Sep 27 10:35:55 I didn't thought this through though so once again I'm open to discussion Sep 27 10:37:07 messageSent would be another candidate Sep 27 10:37:29 Anyway writing what I just wrote gave me the impression of being an ass Sep 27 10:38:01 why that? ;) Sep 27 10:38:22 Because I didn't find the logical reasons I came with yesterday when I thought a bit about that Sep 27 10:38:35 I guess that's because beer was helping the thinking process Sep 27 10:56:22 Hi Ainulindale quickdev Sep 27 10:56:28 hi o/ Sep 27 10:56:39 hey w_erase Sep 27 10:57:24 Who's working on boot speed up ... this framebuffer is a pain .... What about a bootsplash (which could be reverted by pressing aux bt while splash ? ) Sep 27 10:59:26 someone is working on it afaik, but it would be fine if you add your results to the wiki :) Sep 27 11:00:27 I plan to do that is the idea is good, is it ? Sep 27 11:01:31 is much time spent on loading the bootsplash? Sep 27 11:03:36 bootsplash could just be a black screen with a progress bar ... so no time spent . A background image can be appended in the kernel itself. Sep 27 11:04:37 how much time is currently spent on it? Sep 27 11:05:18 Ainulindale, http://rafb.net/p/AlS4Z538.html - is it possible to write this more compact? Sep 27 11:05:51 I seriously don't know :-) Sep 27 11:06:17 quickdev, at the moment I'm reconfiguring the kernel to do that ... When I boot it I'll answer you Sep 27 11:06:34 w_erase, ok, inform us about your progress :) Sep 27 11:06:37 sure Sep 27 11:38:36 Ainulindale, could you quickly review my ophonekitd? Sep 27 11:42:59 Yep Sep 27 11:45:17 Did you commit it ? Sep 27 11:45:54 no, may I? Sep 27 11:46:10 Don't you want to have a general look before? Sep 27 11:47:08 we could revert it then - I commit it now Sep 27 11:50:20 Ainulindale, it's committed Sep 27 11:58:12 Ainulindale, don't hesitate to criticise the style ;) Sep 27 12:06:33 Ainulindale, phonegui_load() and phonegui_get_function() should be moved to libframeworkd-glib, because the same code is used in openmoko-dialer3 and it will be used in openmoko-messages3 Sep 27 14:11:43 has anyone booted 2.6.26? Sep 27 16:35:04 Hey AndreasD_ Sep 27 16:37:32 hi quickdev Sep 27 18:10:06 yay, my builds are working again Sep 27 18:16:54 freesmartphone.org: 03mickey 07framework * rb0723b23405d 10/ (4 files in 3 dirs): Sep 27 18:16:54 freesmartphone.org: rules: Add IdleState DBus trigger and SetDisplayBrightness action Sep 27 18:16:54 freesmartphone.org: We are handling the display dimming solely through the rules now. Sep 27 18:16:54 freesmartphone.org: (Yes, the rules files is device specific nowadays...) Sep 27 18:54:18 freesmartphone.org: 03jluebbe 07framework * r188cefece5d3 10/framework/subsystems/ousaged/ (generic.py helpers.py): ousaged: reorder imports and get rid of unused helpers module Sep 27 18:54:20 freesmartphone.org: 03jluebbe 07framework * rb7455bd5b9c6 10/framework/subsystems/ousaged/generic.py: ousaged: report time used for enabling and disabling a resource Sep 27 18:54:21 freesmartphone.org: 03jluebbe 07framework * red4b8cf98db3 10/framework/subsystems/ousaged/generic.py: ousaged: annouce new resources Sep 27 19:49:59 greetings... I'd like to ask some smallish openembedded question... Is there a way to force it to build the whole environment with some given cflags? Sep 27 19:50:12 exporting CFLAGS is not enough as it seems... Sep 27 19:50:31 I'm trying with both FSO makefile and openmoko makefile, and both fail with some weird errors related to fnctl.h Sep 27 19:50:35 read bitbake.conf a bit Sep 27 19:50:43 there you'll find default values for our flags Sep 27 19:50:49 and it is because ubuntu 8.10 defines -D_FORTIFY_SOURCE=2 Sep 27 19:50:58 which makes gcc crash when compiling, for instance Sep 27 19:51:01 or libxml Sep 27 19:51:04 hmmm ok Sep 27 19:53:15 should I make modifications in that file, or in local.conf? I don't really understand how the configuration files interact (just using Mokomakefile and the like...) Sep 27 20:12:13 use bitbake -D -D -D to see the order in which conf files get parsed Sep 27 20:12:20 read a bit up on = and ?= Sep 27 20:12:27 gnight Sep 27 20:23:55 ok, txs, I'm on it Sep 27 23:45:17 hey **** ENDING LOGGING AT Sun Sep 28 02:59:57 2008