> But, in the framework we want to include a full customizable events > system, that will be useful when you want to programs context rules, > like : when I enter into my house, set profile to Silent, etc... > So the moment we use this mechanism to start and stop the ring tone. > Maybe in the future we will move that out of the framework, but the > events manager system will stay, because it has many other uses. > >> Surely if the exact same steps are performed before building the >> software, it will be much easier for many more people. >> It just seem insane to be hardcoding references to sound files for >> functions that people will habitually want to change. >> >> > Yes, that is why I say, the software should decide of the way it reacts > to an incoming call. > >> Ring tone is probably the first item of customisation a new user will >> want to change, and they will expect it to be intuitive. >> >> On another note, the rule.yaml file looks intresting, where can I find >> out more about that ? >> >> > Well, it is very new, I just added this to the framework a few days ago. > It uses the yaml syntax [0] that I like a lot . If you want to see the > code, download the framework daemon [1], and have a look at the files in > subsystems/oeventsd/ It is all in python and there is enough > documentation to get the idea. > As soon as the framework team accepts this thing, I will create a > tutorial on how to create custom rules in the freesmartphone wiki [1] > > [0] http://www.yaml.org/ > [1] http://git.freesmartphone.org/?p=framework.git;a=summary > [2] http://www.freesmartphone.org/index.php/Tutorials > > Charlie > > Very interesting indeed. And there is a profile switcher planned I hope?
_______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
