ext Arjan van de Ven <[email protected]> writes: > could you give a bit more information of what it does, if it exposes > APis to other pieces etc etc....
This now falls into my area of architectural responsibility (on the Nokia side). I still have to 'make it my own' and can't say much authoritative things about it, but I would be the guy to yell at about the future of profiled. With that out of the way: profiled is a middleware component that manages the typical "device profiles" of a mobile phone, such as "General", "Silent", "Outdoors", etc. (It's got nothing to do with profiling code for optimization purposes. ;) It stores the attributes of a number of profiles, and maintains which is current, supports "factory reset", etc. As far as I can see, it does not actually cause anything to happen: You can not tell it that a message has come in and expect it to play the right sound or vibrate the vibrator, according to the current profile. It will only tell you which sound you should play and you have to play it yourself, somehow. The medium term plan is to eventually and carefully get rid of profiled again, and use the general Settings machinery instead (such as GConf, or probably later dconf). We might need to add features to the Settings machinery for this, such as access control or the ability to store slightly richer structures than just key value pairs, but that should be to everyones benefit. _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
