Re: [Meego-handset] [dialer] New branch pushed for "headless" work
See inline On Tue, Mar 22, 2011 at 9:50 AM, Shane Bryan wrote: > On Tue, 22 Mar 2011 17:04:04 +0200 > Arun Ravindran wrote: > >> 1) the dialer.desktop file changes as described in the README.txt are >> not working. I had to comment >> X-Osso-Service=com.meego.dialer, to make it work from the application >> launcher (desk/home screen) > > Micheal, ideas on this? I thought you showed it was working, but maybe > I didn't get all the patches merged? I do not know what the difference is here. But I need to have the X-Osso-Service=com.meego.dialer defined or it will not launch. There must be some stale bits in my netbook configuration or possibly something has changed in the new image > >> 3) With pre-started dialer, i could never receive incoming call, as >> no alert dialog is shown. I am still investigating to see what is the >> issue. > > Michael, any comments on this one too? It was working but now I too am not getting the call notification.. However interestingly I do get the missed call status notification > > Anyway, all of this is why it's still a branch ;) > > Shane.. > -- Michael Demeter Sr. Software Engineer Open Source Technology Center - SSG Intel Corporation ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [dialer] New branch pushed for "headless" work
Hi, > Hard to know which one is the "right" one since they are both running > on meego images and the MTF docs refer to applifed as the control > mechanism for pre-start apps. > > Can you please explain the difference, or point to documentation that > describes them both and under what conditions we would want to use one > over the other? > > IIRC, older sample configs for applifed had a "call" entry for > starting the Nokia call manager app, so I figured that was the "Right > Thing" (TM) to do ;) > Launcher is for boosting app startup (optimizations such as cached version of > generic classes, > use preload libs, etc.). Applifed is the actual full prelaunch daemon. So if > the purpose was to fully preload the app > then this was correct approach. > Obviously the docs and examples are at gitorius. For applifed: > http://meego.gitorious.org/meegotouch/meegotouch-applifed/trees/master > And for launcher: > http://meego.gitorious.org/meegotouch/meegotouch-applauncherd/trees/master As per the MTF docs, these two (launcher, and prestart) are the ways to speed up the application startup (http://apidocs.meego.com/git-tip/mtf/faststart.html, could be a bit old documentation.) of which the launcher is at least mentioned as the primary method. Launcher: Preloads libraries, and creates MApplication and MApplicationWindow before main() is called. The disadvantage is that some of the MT and QT command line options are not supported. Prestart: Meant for applications with low initialization time, where the application is started but no UI component is shown. Th documents also says this is meant for system critical applications. Boot time prestart is part of platform-specific configuration and are not provided in application packages. This "platform-specific" could be why the nokia.conf is a hard coded configuration. For Dialer and SMS applications in meego, we need to improve on the startup time and also dialer needs a boot time startup and probably needs this as part of application package. My feeling (by looking at the logs during startup) is that the ofono access, seaside and some un known UI issues are the three things which are taking time in dialer. In meego images, launcher is used more often than applifed. But i do not have any data to compare the startup times of these two methods, and documentation is not saying anything in that line. But it mentions we can use combination of these. regards Arun ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [dialer] New branch pushed for "headless" work
On 22.3.2011, at 18:50, ext Shane Bryan wrote: > Hard to know which one is the "right" one since they are both running > on meego images and the MTF docs refer to applifed as the control > mechanism for pre-start apps. > > Can you please explain the difference, or point to documentation that > describes them both and under what conditions we would want to use one > over the other? > > IIRC, older sample configs for applifed had a "call" entry for > starting the Nokia call manager app, so I figured that was the "Right > Thing" (TM) to do ;) Launcher is for boosting app startup (optimizations such as cached version of generic classes, use preload libs, etc.). Applifed is the actual full prelaunch daemon. So if the purpose was to fully preload the app then this was correct approach. Obviously the docs and examples are at gitorius. For applifed: http://meego.gitorious.org/meegotouch/meegotouch-applifed/trees/master And for launcher: http://meego.gitorious.org/meegotouch/meegotouch-applauncherd/trees/master BR, Vesku ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [dialer] New branch pushed for "headless" work
On Tue, 22 Mar 2011 17:04:04 +0200 Arun Ravindran wrote: > Hi Shane, > > > Michael and Arun, others who care... > > > > I have pushed Michaels patchset to a new public branch called > > "topic/headless", and am requesting that you guys coordinate your > > respective work towards the eventual merge into master on this > > branch. > > > > For others that have been waiting (alterego for one) this is where > > you can start basing future new features, espcially UI related > > changes, as this branch will be the most likely place what Views > > will begin to be teased apart from the models and controller. > > > > Depending on how drastic or dynamic any new UI work turns out to > > be, I *may* start a new topic branch for UI changes, stay tuned. > > > > Regards, > > > The latest code is using applifed, and not launcher (applauncherd). > Any reasons? Hard to know which one is the "right" one since they are both running on meego images and the MTF docs refer to applifed as the control mechanism for pre-start apps. Can you please explain the difference, or point to documentation that describes them both and under what conditions we would want to use one over the other? IIRC, older sample configs for applifed had a "call" entry for starting the Nokia call manager app, so I figured that was the "Right Thing" (TM) to do ;) > I took the branch, but had to make a few changes to make make it work > in N900. > > 1) the dialer.desktop file changes as described in the README.txt are > not working. I had to comment > X-Osso-Service=com.meego.dialer, to make it work from the application > launcher (desk/home screen) Micheal, ideas on this? I thought you showed it was working, but maybe I didn't get all the patches merged? > 2) /etc/prestart/nokia.conf needed the following to start the dialer > automatically. > Yes, this was known, but since applifed does not read additional config files and is hard coded to read the nokia.conf file, we can't really add our own. Likewise, it would be bad form to modify this file as part of a post-install script. So do you have suggestions on solving it? Ideally we should file a bug with applifed to make this config dir based or at least able to do something like "#include /etc/prestart/services.d/*.conf". That is if we continue to use applifed. > 3) With pre-started dialer, i could never receive incoming call, as > no alert dialog is shown. I am still investigating to see what is the > issue. Michael, any comments on this one too? Anyway, all of this is why it's still a branch ;) Shane.. ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [dialer] New branch pushed for "headless" work
Hi Shane, Michael and Arun, others who care... I have pushed Michaels patchset to a new public branch called "topic/headless", and am requesting that you guys coordinate your respective work towards the eventual merge into master on this branch. For others that have been waiting (alterego for one) this is where you can start basing future new features, espcially UI related changes, as this branch will be the most likely place what Views will begin to be teased apart from the models and controller. Depending on how drastic or dynamic any new UI work turns out to be, I *may* start a new topic branch for UI changes, stay tuned. Regards, The latest code is using applifed, and not launcher (applauncherd). Any reasons? I took the branch, but had to make a few changes to make make it work in N900. 1) the dialer.desktop file changes as described in the README.txt are not working. I had to comment X-Osso-Service=com.meego.dialer, to make it work from the application launcher (desk/home screen) 2) /etc/prestart/nokia.conf needed the following to start the dialer automatically. 3) With pre-started dialer, i could never receive incoming call, as no alert dialog is shown. I am still investigating to see what is the issue. regards Arun ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [dialer] New branch pushed for "headless" work
Thanks Shane... On Mon, Mar 21, 2011 at 5:28 PM, Shane Bryan wrote: > Michael and Arun, others who care... > > I have pushed Michaels patchset to a new public branch called > "topic/headless", and am requesting that you guys coordinate your > respective work towards the eventual merge into master on this branch. > > For others that have been waiting (alterego for one) this is where you > can start basing future new features, espcially UI related changes, as > this branch will be the most likely place what Views will begin to be > teased apart from the models and controller. > > Depending on how drastic or dynamic any new UI work turns out to be, I > *may* start a new topic branch for UI changes, stay tuned. > > Regards, > > Shane... (aka sabotage) > -- Michael Demeter Sr. Software Engineer Open Source Technology Center - SSG Intel Corporation ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
