Re: Some debian questions

2008-11-03 Thread Guillaume Chereau

   On Tue, 2008-10-28 at 14:51 +0100, Benedikt Bär wrote:
 Hmm... Indeed a problem. Maybe there could be a function to
 activate/deactivate the given rule, and have it parsed if activated.
 
 Is the rules manager that flexible yet? Maybe you can point me in the
 right direction there and I could come up with a patch for that :)
 
 Let me know your thoughts.
I think we need to rethink the policy of the profile / rule interaction.

Maybe a rule should have a special attribute that specify the profiles
that activate it, or just rely on the rule filter for that and we don't
use the rules configuration file at all.

An other way : we could make the rule actual DBus object, with a DBus
path.
So the preferences can still refer to the rules by there name, and a
client that create a new rule can refer to it by its DBus path.

Cheers,

Guillaume/Charlie


signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Some debian questions

2008-11-03 Thread Guillaume Chereau
On Sat, 2008-11-01 at 19:29 +0100, Michael 'Mickey' Lauer wrote:
 Hi Charlie,
 
 I have just added a skeleton for org.freesmartphone.Events in the specs 
 repository, please fill it with some docs when you have a chance.
 
Thanks Mickey, I started to fill it. Of course the oeventsd API is very
small.
I also stared the opimd spec documentation.

Cheers,
Charlie


signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Some debian questions

2008-11-01 Thread Michael 'Mickey' Lauer
Am Wednesday 29 October 2008 04:21:01 schrieb Guillaume Chereau:
  You can already add new rules using the dbus call :
  org.freesmartphone.Events.AddRule(s)
 
  the string should be in the same format than the rules in the rules
  file.
 
  For the way to modify rules, it is planned. Rules can have name (using
  'name' attribute in the rules file.)
  I will take some time today to add a RemoveRule, so that you can add and
  remove rules.

 Ok I added the RemoveRule method to oeventsd, you can check oevents.py
 in the framework tests directory to see how to add and remove rules.

Hi Charlie,

I have just added a skeleton for org.freesmartphone.Events in the specs 
repository, please fill it with some docs when you have a chance.

-- 
:M:

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: opreferences rules (was Re: Some debian questions)

2008-10-30 Thread Benedikt Bär
On Thu, 2008-10-30 at 01:06 +0100, Luca Capello wrote:
 Hi there!
 
 Please continue this discussion on the smartphones-standards mailing
 list [1], I think it belongs there and I set R-T and M-F-T accordingly.
 
 On Wed, 29 Oct 2008 04:21:01 +0100, Guillaume Chereau wrote:
  On Wed, 2008-10-29 at 10:29 +0800, Guillaume Chereau wrote:
  On Tue, 2008-10-28 at 14:51 +0100, Benedikt Bär wrote:
   I am currently setting up a debian system on my FreeRunner, but I have
   some questions. :)
 
 The Debian FSO Team [2] mainly uses the smartphones-* mailing lists [1]
 for discussions, please direct your questions there whenever you develop
 on Debian and/or for Debian.

Yes, but the first part of my message was more about the framework than
Debian. We're not looking for a Debian specific way of adding rules, but
a general one, which Debian could use.

But agreed, the second point probably belongs to the other list, but
that is not my priority right now. Not going to reboot the FR every
day :)

 
   1) I'm writing some python programs to interact with the FSO framework.
   I have seen there's now support for a rules file, which seems quite a
   nice idea.
   
   Now, I would like to be able to modify these rules via my program. That
   way, for example, I could set a screen blanking / suspend timeout but my
   program wouldn't have to listen to events. It would automatically be
   done by the framework.
   
   Is this possible? If not, any plans to implement something like a D-BUS
   interface for modifying rules?
 
  You can already add new rules using the dbus call :
  org.freesmartphone.Events.AddRule(s)
 
 Is there any already-coded program that do that?  Something like
 update-frameworkd-rules, for the end-user.

That would be interesting to do as an addition to the framework
functions. The program could be a python script accessing the framework
over D-BUS for adding/deleting/activating rules.

 
  the string should be in the same format than the rules in the rules
  file.
 
 Is there a way to know which rules are available?  IMHO the above
 update-frameworkd-rules should have a --show/--list option for that
 (this reminds me of `git config` [3]...).

+1, but maybe this is already implemented in the framework. I haven't
had time to test the rules interface yet, but I will do as soon as I
can.

 
  For the way to modify rules, it is planned. Rules can have name (using
  'name' attribute in the rules file.)
  I will take some time today to add a RemoveRule, so that you can add and
  remove rules.
 
  Ok I added the RemoveRule method to oeventsd, you can check oevents.py
  in the framework tests directory to see how to add and remove rules.
 
  BUT, it makes me realize a problem : the rules manager only activates
  the rules that are specified in the rules preference file (e.g [0])
 
  So if you add a new rule with a name, the rule won't be activated unless
  you also specify that the rule is activated in the preference file. that
  is not very good and we need to solve this problem.
 
 The whole story above led me thinking about how Debian should manage
 these rules.  The main problem here is that Debian must ship a working
 setup, which at the same time should be configurable through Debian
 packages, as I explained at [4].

The above program you've mentioned would come in handy there. :)

Cheers,
Benedikt

 
 What's upstream plan?  Having one unique rules file or splitting the
 configuration into single and more specific ones?  Something like
 sounds.yaml (ring- and message-tones plus volumes), etc.?
 
 Thx, bye,
 Gismo / Luca
 
   [0] :
  http://git.freesmartphone.org/?p=framework.git;a=blob;f=etc/freesmartphone/opreferences/conf/rules/default.yaml;h=e0066eff76973b5597d879bf81b0e0f490660bdb;hb=HEAD
 [1] http://www.freesmartphone.org/index.php/Infrastructure#Mailing_Lists
 [2] http://wiki.debian.org/Teams/DebianFSO
 [3] http://www.kernel.org/pub/software/scm/git/docs/git-config.html
 [4] 
 http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-October/000327.html


signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Some debian questions

2008-10-29 Thread Benedikt Bär
On Wed, 2008-10-29 at 11:21 +0800, Guillaume Chereau wrote:
 On Wed, 2008-10-29 at 10:29 +0800, Guillaume Chereau wrote:
  On Tue, 2008-10-28 at 14:51 +0100, Benedikt Bär wrote:
   Hi all,
   
   I am currently setting up a debian system on my FreeRunner, but I have
   some questions. :)
   
   1) I'm writing some python programs to interact with the FSO framework.
   I have seen there's now support for a rules file, which seems quite a
   nice idea.
   
   Now, I would like to be able to modify these rules via my program. That
   way, for example, I could set a screen blanking / suspend timeout but my
   program wouldn't have to listen to events. It would automatically be
   done by the framework.
   
   Is this possible? If not, any plans to implement something like a D-BUS
   interface for modifying rules?
  You can already add new rules using the dbus call :
  org.freesmartphone.Events.AddRule(s)
  
  the string should be in the same format than the rules in the rules
  file.
  
  For the way to modify rules, it is planned. Rules can have name (using
  'name' attribute in the rules file.)
  I will take some time today to add a RemoveRule, so that you can add and
  remove rules.
 
 Ok I added the RemoveRule method to oeventsd, you can check oevents.py
 in the framework tests directory to see how to add and remove rules.

Wow... That was quick! :) I'll check this out tonight! Thanks a lot.

 BUT, it makes me realize a problem : the rules manager only activates
 the rules that are specified in the rules preference file (e.g [0])
 
 So if you add a new rule with a name, the rule won't be activated unless
 you also specify that the rule is activated in the preference file. that
 is not very good and we need to solve this problem.

Hmm... Indeed a problem. Maybe there could be a function to
activate/deactivate the given rule, and have it parsed if activated.

Is the rules manager that flexible yet? Maybe you can point me in the
right direction there and I could come up with a patch for that :)

Let me know your thoughts.

Cheers,
Benedikt

 
 cheers,
 Guillaume
 
  [0] :
 http://git.freesmartphone.org/?p=framework.git;a=blob;f=etc/freesmartphone/opreferences/conf/rules/default.yaml;h=e0066eff76973b5597d879bf81b0e0f490660bdb;hb=HEAD
 


signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Some debian questions

2008-10-28 Thread Benedikt Bär
Hi all,

I am currently setting up a debian system on my FreeRunner, but I have
some questions. :)

1) I'm writing some python programs to interact with the FSO framework.
I have seen there's now support for a rules file, which seems quite a
nice idea.

Now, I would like to be able to modify these rules via my program. That
way, for example, I could set a screen blanking / suspend timeout but my
program wouldn't have to listen to events. It would automatically be
done by the framework.

Is this possible? If not, any plans to implement something like a D-BUS
interface for modifying rules?

2) I now have nice text scrolling by on boot, which is fine. However,
I'd like to have a splash screen for my non-tech friends :).

I've already installed splashy, however, it fails to use /dev/fb0.
However, the file seems to be there and according to dmesg a FB driver
is loaded.

I've also modified my u-boot environment to add splash and vga=317 to
the kernel command line, however it still doesn't seem to work.

Any ideas? Are there special parameters or so to activate this?
I see this with both mwester's last kernel and the OM2008.9 latest
kernel (which seems to have a splash?).

Thanks to all,
-  
Benedikt

www.relamp.tk

This e-mail is digitally signed by a PGP key, to verify it's authenticity.
If you received this e-mail without key the e-mail may not be authentic.

The information contained in this transmission may contain privileged and 
confidential information.
It is intended only for the use of the person(s) named above. If you are not 
the intended recipient,
please contact the sender by reply e-mail and destroy all copies of the 
original message. To reply to
our e-mail administrator directly, please send an e-mail to [EMAIL PROTECTED]



signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Some debian questions

2008-10-28 Thread Guillaume Chereau
On Tue, 2008-10-28 at 14:51 +0100, Benedikt Bär wrote:
 Hi all,
 
 I am currently setting up a debian system on my FreeRunner, but I have
 some questions. :)
 
 1) I'm writing some python programs to interact with the FSO framework.
 I have seen there's now support for a rules file, which seems quite a
 nice idea.
 
 Now, I would like to be able to modify these rules via my program. That
 way, for example, I could set a screen blanking / suspend timeout but my
 program wouldn't have to listen to events. It would automatically be
 done by the framework.
 
 Is this possible? If not, any plans to implement something like a D-BUS
 interface for modifying rules?
You can already add new rules using the dbus call :
org.freesmartphone.Events.AddRule(s)

the string should be in the same format than the rules in the rules
file.

For the way to modify rules, it is planned. Rules can have name (using
'name' attribute in the rules file.)
I will take some time today to add a RemoveRule, so that you can add and
remove rules.

- Guillaume/Charlie


signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Some debian questions

2008-10-28 Thread Guillaume Chereau
On Wed, 2008-10-29 at 10:29 +0800, Guillaume Chereau wrote:
 On Tue, 2008-10-28 at 14:51 +0100, Benedikt Bär wrote:
  Hi all,
  
  I am currently setting up a debian system on my FreeRunner, but I have
  some questions. :)
  
  1) I'm writing some python programs to interact with the FSO framework.
  I have seen there's now support for a rules file, which seems quite a
  nice idea.
  
  Now, I would like to be able to modify these rules via my program. That
  way, for example, I could set a screen blanking / suspend timeout but my
  program wouldn't have to listen to events. It would automatically be
  done by the framework.
  
  Is this possible? If not, any plans to implement something like a D-BUS
  interface for modifying rules?
 You can already add new rules using the dbus call :
 org.freesmartphone.Events.AddRule(s)
 
 the string should be in the same format than the rules in the rules
 file.
 
 For the way to modify rules, it is planned. Rules can have name (using
 'name' attribute in the rules file.)
 I will take some time today to add a RemoveRule, so that you can add and
 remove rules.

Ok I added the RemoveRule method to oeventsd, you can check oevents.py
in the framework tests directory to see how to add and remove rules.

BUT, it makes me realize a problem : the rules manager only activates
the rules that are specified in the rules preference file (e.g [0])

So if you add a new rule with a name, the rule won't be activated unless
you also specify that the rule is activated in the preference file. that
is not very good and we need to solve this problem.

cheers,
Guillaume

 [0] :
http://git.freesmartphone.org/?p=framework.git;a=blob;f=etc/freesmartphone/opreferences/conf/rules/default.yaml;h=e0066eff76973b5597d879bf81b0e0f490660bdb;hb=HEAD



signature.asc
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community