[Meego-handset] Nemo steering group minutes 1/11/2011
#meego-meeting: Nemo steering group meeting 1/11/2011 Meeting started by Stskeeps at 12:01:48 UTC (full logs and minutes at http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-11-01-12.01.html) Important details: We are moving to #nemomobile IRC channel instead of #meego-arm (Stskeeps, 12:39:19) Full name of Nemo is Nemo Mobile (Stskeeps, 12:15:40) Meeting summary Status (Stskeeps, 12:02:46) so we've produced pre pre alpha Nemo images, http://repository.maemo.org/meego/Nemo/0.20111020.1.CE.2011-10-25.1/images/ (Stskeeps, 12:03:20) See source code on https://build.pub.meego.com , Projects, and CE:* projects (Stskeeps, 12:03:45) Veskuh has listed some of the current issues in those images, http://wiki.meego.com/User:Vesku (Stskeeps, 12:04:29) We've also combined N900/N950 SGX stack finally (Stskeeps, 12:05:05) Naming (Stskeeps, 12:11:01) Full name of Nemo is Nemo Mobile (Stskeeps, 12:15:40) Infra (Stskeeps, 12:16:13) wiki can be done initially in Mer wiki and moved out when we grow more up (Stskeeps, 12:26:13) dm8tbr offers hosting bugzilla vm (without performance guarantees) (Stskeeps, 12:26:53) AOB (any other business) (Stskeeps, 12:27:28) other Mer-related projects news: (Stskeeps, 12:31:03) http://bug10738.openaos.org/images/beagleboard/README.txt Beagleboard port (Stskeeps, 12:31:09) http://www.youtube.com/watch?v=qs3RnK9aHXk - Plasma active on beagleboard, https://picasaweb.google.com/100825745639484086218/ - asus transformer (Stskeeps, 12:31:53) http://www.youtube.com/watch?v=EjsxKEacIkU qtmediahub on trimslice (Stskeeps, 12:32:03) http://twitpic.com/792kwz QtDesktop on trimslice, (Stskeeps, 12:32:19) http://meegonetwork.fi/events/metawatch-nov-2011 (still on the old domain as devaamo CMS is not up yet) (dm8tbr, 12:37:14) We are moving to #nemomobile IRC channel instead of #meego-arm (Stskeeps, 12:39:19) Meeting ended at 12:41:20 UTC (full logs). Action items (none) People present (lines said) Stskeeps (79) veskuh (17) dm8tbr (13) alterego (7) iekku (5) w00t (3) MeeGoMeetBot (2) Generated by MeetBot 0.1.4. ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] Mer breadth (Was Naming of Community Edition)
2011/10/12 Andrew Flegg and...@bleb.org: On Wed, Oct 12, 2011 at 20:55, Carsten Munk cars...@maemo.org wrote: Initially the project will be developing a Core for basing products on and will split UX and hardware adaptations out into seperate projects within the community surrounding the Core. -- hence the there's no the Mer Handset UX. There's some reasons why this split. [...] Thanks makes sense and is well explained. Having said that, I'd be concerned that a small Core with a few hackers won't be possible to gain enough momentum to capture a new middle-tier-or-above vendor. Honestly, I think where success lies is with small to medium vendors instead. That's who will have the most strength from this. Of course, the solutions that we intend to provide will be usable for bigger organisations too. 2) We want to move much of the politics out of the Mer project and motivate people to create and build their own projects, though basing on Mer, much in the same way site projects are based upon Apache httpd. - we can't and don't want to govern projects utilizing the core, let them innovate on their own terms. Apache's an interesting choice of example given there *is* an overarching Apache project and brand under which projects like JCL, Tomcat, HTTPD, Commons Lang, Commons Collections and so on all operate. Agreed, perhaps Linux would be a better comparison There was a discussion about same topic some days back on IRC and the conclusion we reached was: [...] It's a little disappointing that so much is happening in realtime on IRC, preventing those who can't participate 24x7 from contributing. It's still a massive step-up on private conference calls within MeeGo, but it is still a barrier to openness when ad-hoc discussions result in decisions without any pre-prepared agenda. Even post-communication to the mailing lists would be sufficent. Agreed - we had a hiccup with DNS so that's blocking Mer mailing lists for a little bit. Well put. But what is the success criteria? My suggestion would be that a vendor is looking for an ecosystem-in-a-box whilst providing the differentiation capabilities they feel they need to succeed in their market. That means a good core; points where they can integrate either an off-the-shelf OSS UI or build their own differentiating one; good tools (both for app developers and their own developers looking to adapt to their hardware) and an assurance that some things (e.g. security updates for some packages) will be got for free. Let's face it - if giant companies have difficulties making ecosystems, we'll have even more difficulties. What I think really has value is the fact that you can avoid hiring a lot of Linux people to maintain a simple stack. That it's easy to get things made - want an alarm clock? here, take a beagleboard and an LCD and some speakers, write some QML, there you go. A bootstrapping project which delivers a tight Linux userland with Qt might not provide sufficient leg up for it to appear on a list of options compared with the perceived weight of Ubuntu/Debian/... (or even, heaven forbid, Tizen). The problem is, again that if those solutions are really so great and easy, why aren't people having an easy time building products using these things? With Tizen, it's vaporware right now. But we intend on utilizing Tizen in the core where possible - our angle is just ease through Qt instead and a open innovative process. So, I suppose my question is: what's the perceived problem? How does Mer address it? How is success measured? And is Core the focus because it's the right answer for the perceived problem or because it's pragmatically the thing which can be delivered now? Success for Mer is measured in people using it to innovate and for people to make prototypes and products using it. The Core is the focus as this is the simple thing many really lust for is a simple, easy-to-port working Linux platform, openly developed and governed that doesn't rely on the whims of corporate choices and roadmaps, that you can build your business on without risking bankruptcy at every new keynote opportunity. Success for myself is if I have a stable foundation for my business to make products in a world like in http://www.youtube.com/watch?v=6Cf7IL_eZ38 - and having fun developing the core at same time. BR Carsten Munk Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] Naming of Community Edition - community discussion
Hi all, As you know, there has been a lot of news regarding MeeGo, introducing the Tizen project, Mer, etc. We (as in the steering group) like to query the community for ideas on what to call the Community Edition in the future. Currently our splash screens says MeeGo 1.3 Community Edition which will be increasingily inaccurate as we're working to rebase CE on top of the Mer Core Some limitations: * Can't include trademarks or company names, such as MeeGo / Tizen, Nokia, etc. * Can't include Mer within it as Mer's a core and CE is not the Mer UX (nor is anything) All suggestions welcome! BR Carsten Munk ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] CE steering group minutes 4/11/2011
#meego-meeting: CE Steering Group meeting 4/10/2011 Meeting started by Stskeeps at 11:01:14 UTC (full minutes and logs at http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-10-04-11.01.html ) Meeting summary As announced, the new steering group is Jukka Eklund (jukkaeklund), Marko Saukko (Sage), Carsten Munk (Stskeeps), Tom Swindell (alterego) and Vesa-Matti Hartikainen (veskuh) (Stskeeps, 11:02:30) The fall release has been published, getting great reception from community and we even have a IA32 image that people are playing with on Intel devices and tablets. (Stskeeps, 11:03:29) Name (Stskeeps, 11:04:17) ACTION: stskeeps start naming discussion/competition to meego-handset@ (Stskeeps, 11:09:36) Content (Stskeeps, 11:10:01) http://www.youtube.com/watch?v=xl7Djukoysc (w00t, 11:18:30) as some of you have noted, we launched the Mer project (www.merproject.org ), http://lists.meego.com/pipermail/meego-dev/2011-October/484215.html (Stskeeps, 11:21:46) Releasing (Stskeeps, 11:29:15) infrastructure (Stskeeps, 11:35:42) ACTION: alterego bugzilla setup, iekku admins/lays it out (Stskeeps, 11:39:41) Challenges (Stskeeps, 11:43:06) additional challenge, SDK and sysroots (Stskeeps, 11:45:56) AOB (Stskeeps, 11:48:17) Steering group terms limited to 3 months (Stskeeps, 11:54:15) Offer from meego.com community IT for hosting of VMs (Stskeeps, 11:59:54) Next meeting 11 October 2011 same time (Stskeeps, 12:02:16) Meeting ended at 12:02:22 UTC (full logs). Action items stskeeps start naming discussion/competition to meego-handset@ alterego bugzilla setup, iekku admins/lays it out Action items, by person alterego alterego bugzilla setup, iekku admins/lays it out iekku alterego bugzilla setup, iekku admins/lays it out People present (lines said) Stskeeps (121) alterego (59) w00t (27) xruxa (26) veskuh (23) iekku (21) lbt_hel (17) dm8tbr (11) Sage (8) rantom (4) X-Fade (3) matrixx (3) slaine (2) MeeGoMeetBot (2) msugano (2) jarnoteivas (1) SpeedEvil (1) Generated by MeetBot 0.1.4. ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] Towards open governance in the Community Edition for MeeGo
2011/9/21 Carsten Munk cars...@maemo.org: Hence, we'd like the members of the community surrounding CE to nominate people (by responding to this mailing list post) you'd like to see in this steering group along with descriptions of their merit and contributions to the project. I would like to nominate two people to the steering group: 1) alterego/Thomas Swindell alterego has been instrumental in contributing to the dialer in CE and has shown overall involvement in the project. He has good ideas, initiative and I think he'd be a good part of the SG to help guide us through future challenges 2) rantom / Tomi rantom has been one of the best of the testers that has been involved from general community side - happily taking on any snapshot image no matter how broken and submissing so many accurate bug reports it's been too much to handle ;) He brings a unique user point of view to the mix and well, we do all have to use CE as a day to day device and he helps to make this happen. I believe that when you develop and use a product at the same time, you grow blind to it's failures - that's why QA and user testing is important. Rantom could be the person that helps establish priorities and noting where our biggest user problems are. BR Carsten Munk ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] CE adaptation meeting minutes 15/9/2011
Full logs + minutes can be seen at http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-09-15-08.03.html #meego-meeting Meeting Meeting started by Stskeeps at 08:03:18 UTC (full logs). Meeting summary News (Stskeeps, 08:03:57) Status (Stskeeps, 08:08:13) worked with sage towards 1.3 suitable SGX packages, took a look at the recent qt5 refactor. Got BME/DSME booting. there is a conflict with bq27x00_battery module so there's no battery meter in UI currently. (Stskeeps, 08:09:32) made a script that can rebase derived packages (useful for CE), worked towards autogenerated N950/N9 fiasco images with Sage. (Stskeeps, 08:10:05) http://repository.maemo.org/meego/n900-de/daily/1.2.90.3.0.20110909.81.CE.2011-09-13.1/images/ latest image (Sage, 08:10:24) http://lists.meego.com/pipermail/meego-handset/2011-September/000685.html Information and thoughs about the 1.3 status. (Sage, 08:10:27) New image will be created today at some point probably around 17:00 UTC+3. (Sage, 08:10:30) With new 1.3 branch we will start using Project:CE:Trunk[:Testing] project. NOTE: _CE_ (Sage, 08:10:33) Currently the staging area is in Project:DE:Trunk:Testing:1.3 which will be removed when the Project:CE:* projects are ready. (Sage, 08:10:36) camera ui: I have been moved to other project, I can still use some of my working hours for this project if needed (joonasta, 08:11:55) camera ui: integrating camera ui with harmattan qt-components was in progress, I hope to finish this some day (although probably not mandatory, just nice to have) (joonasta, 08:12:05) camera ui: no other mandatory tasks to do in camera ui/qtm camera backend side at the moment, MeeGo 1.3 and new qt version may bring need to rebase/re-implement qtm camera patches (joonasta, 08:12:13) Workaround patch added for bug 22161 to correct call answering on n950. done (jpeltonen, 08:15:17) packaging locationing for n950 (done) (tkeisala, 08:15:54) : camera: plan is to evolve kernel api's towards the ones upstreamed, would like to get patches in Fall release. userspace seems ready enough to support both devices with same binaries. Related submitting for fall realease still ahead. Please point out your concerns on this, if any. (theodor, 08:33:34) BR Carsten Munk ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] Changes in the MeeGo Bugzilla for Handset User Experience
2011/7/15 jukka.ekl...@nokia.com Just one question, does this mean we won't have vanilla N900 handset releases for 1.3?; it's been a while since we don't get a new image for it. Remember, there wasn't Handset release even for 1.2. Images are built however for N900, not for IA though it seems. Community Edition continues supporting ARM and N900, and also N950/N9 quite soon. You are right, so, what I actually wonder is if the armv7hl images will stop being generated soon from upstream. Hope not. Doubt it, at least core images should always flow. For 1.3 we're still working on the base level stuff. /Carsten About Handset UX, how about making a community-driven UX? There is already a such initiative, see: http://wiki.meego.com/Yet_Another_GUI_Project. Really interesting :) Where is the main discussion happening for this project?, a mailing list?, some IRC channel? In IRC probably, look for 'jnwi' and ask. Jukka ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] [N900] Common software meeting minutes 5/5/2011
#meego-meeting: Nokia N900 DE common software meeting 5/5/2011 == Meeting started by Stskeeps at 08:00:06 UTC. The full logs are available at http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-05-08.00.log.html . Meeting summary --- * General info (Stskeeps, 08:00:37) * LINK: https://bugs.meego.com/show_bug.cgi?id=15062#c7 (srikanth_rst, 08:01:26) * Status (Stskeeps, 08:14:43) * LINK: https://bugs.meego.com/buglist.cgi?priority=Highkeywords=n900query_format=advancedkeywords_type=allwordsfield0-0-0=flagtypes.namebug_severity=criticalbug_status=NEWbug_status=NEEDINFObug_status=INDEFINITIONbug_status=ASSIGNEDbug_status=ACCEPTEDbug_status=WAITING%20FOR%20UPSTREAMbug_status=WAITINGbug_status=REOPENEDtype0-0-0=anyexactvalue0-0-0=MeeGo_N900DE_Release_Blocker%2Bknown_name=N900DE%20TOP%2010 (jukkaeklund, 08:15:48) * Rebased DE to 1.2 branch (some excepted, bug with linkpac), worked a bit on DE long term plan suggestion with david greaves. Made release plan for sf2011. Got waylandGL working with proper colors. Got qmlviewer working with GL acceleration as well. (Stskeeps, 08:16:41) * Investigated bug 15953 (lock key). Got solved by lamikr. (Ronksu, 08:19:08) * Will look at bug 14990 (proximity in call) to figure out if MCE can be made to listen to ofono instead of waiting for someone to inform it about call state changes. (Ronksu, 08:20:09) * camera ui: BMC#15324 (Camera's settings are reversed to stock when exiting the application) fixed (joonasta, 08:20:51) * camera ui: Currently working with BMC#15770 (Camera Hardware key and lens are not working). We have to implement tempoary fix for meego de only. We are planning to start meegocamera to background without UI and make it to listen lens cover/camera button events and display the UI when needed. (joonasta, 08:21:00) * LINK: http://stskeeps.subnetmask.net/wayland/20110503_002.jpg , 7-8fps with completely unoptimized path, getting 12fps after some minor optimization. (Stskeeps, 08:21:11) * A couple of good fixes gone in to sms, a new version should come to obs today or tomorrow. (aruravi, 08:22:45) * Prestarting SMS might take some more time, as we have not yet agreed on the fix for this. (aruravi, 08:23:27) * Fixing package build warnings and missing changelog on location stack (tkeisala, 08:33:55) * Tried OBS instructions on wiki and it seems to be ok for the setup part. Build part is missing. (tkeisala, 08:33:58) * More power saving patches integrated to kernel (kimju, 08:34:32) * backport of wlan ad-hoc mode patches in testing (kimju, 08:34:57) * integrating banner notifications into tablet ux (selesnie, 08:36:31) * LINK: https://bugs.meego.com/show_bug.cgi?id=9940#c5 (mirek2, 08:37:02) * made some cleaning for code APN UI, adding soon that to some DE place? (jsjarvi, 08:37:22) * AOB (Stskeeps, 08:46:18) * LINK: https://bugs.meego.com/buglist.cgi?query_format=advancedfield0-0-0=flagtypes.namebug_status=NEWbug_status=NEEDINFObug_status=ASSIGNEDbug_status=WAITING%20FOR%20UPSTREAMbug_status=REOPENEDtype0-0-0=anyexactvalue0-0-0=MeeGo_N900DE_Release_Blocker%2B (jukkaeklund, 08:50:09) Meeting ended at 08:56:35 UTC. BR Carsten Munk Nokia N900 hardware adaptation maintainer ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] [N900 DE] DE Architecture discussions in the future
Hi all, We'd like to start some discussion how to handle architecture type questions in the future. My idea would be that we set up a small team, open to everyone, who debates any architectual questions specific to DE in the open and contributes to the general MeeGo debate as well. Please indicate on the mailing list if you'd be interested in contributing to this work. If you know anyone who'd like to contribute some of their free time with experience and knowledge within the field to be improving DE and MeeGo on handsets, please refer them to this mailing list thread as well. What are your thoughts? Best regards, Carsten Munk Nokia N900 hardware adaptation maintainer ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] [N900DE] Rebased to MeeGo:1.2:oss/non-oss source links and week 18 delta
Hi, I've rebased the links in Project:DE:Trunk so they now point at MeeGo:1.2:oss instead of Trunk. We ran into a problem in OBS software while doing so, Bug 16942 - Cannot check out older version of package from MeeGo:1.2:oss (https://bugs.meego.com/show_bug.cgi?id=16942 ) and this is being investigated. Because of that bug, the following packages are still holdouts for rebasing and hence pointing to MeeGo Trunk at the moment: pulseaudio-modules-nokia, pointing towards MeeGo.com:Trunk:non-oss pulseaudio-modules-n900 meego-handset-configs meego-ux-settings pulseaudio As well as one pointing to devel:devices:n900 (can probably be rebased to MeeGo:1.2:oss now) The delta currently towards MeeGo:1.2:oss is: Package: generic-backgrounds Index: generic-backgrounds.changes === --- generic-backgrounds.changes (revision 1) +++ generic-backgrounds.changes (revision 3) @@ -1,3 +1,6 @@ +* Thu Apr 14 2011 Carsten Munk cars...@maemo.org - 0.6 +- Add DE specific splash screens + * Tue May 11 2010 Anas Nashif anas.nas...@intel.com - 0.6 - Provide meego-desktop-backgrounds (bmc #1985) Package: meego-handset-configs Index: meego-handset-configs.changes === --- meego-handset-configs.changes (revision 7) +++ meego-handset-configs.changes (revision 2) @@ -1,4 +1,9 @@ +Thu Apr 14 15:15:00 UTC 2011 - cars...@maemo.org +- Fix icons to be using new theme names. + +Thu Apr 14 14:25:00 UTC 2011 - cars...@maemo.org +- Fix icon grid according to Jukka's wishes. + Package: meego-handset-icon-theme Index: meego-handset-icon-theme.changes === --- meego-handset-icon-theme.changes (revision 9) +++ meego-handset-icon-theme.changes (revision 3) @@ -1,8 +1,9 @@ +* Wed Apr 13 2011 Fathi Boudra fathi.bou...@nokia.com - 0.0.7 +- Add the N900 DE icons -Thu Feb 22 2011 Miroslav Safr miroslav.s...@tieto.com.com 0.0.7.2 +* Thu Feb 22 2011 Miroslav Safr miroslav.s...@tieto.com - 0.0.7 - .spec file regenerated by spectacle 0.22 (BMC#12975 - libmeegotouch Package: meego-handset-photos Index: meego-handset-photos.changes === --- meego-handset-photos.changes (revision 20) +++ meego-handset-photos.changes (revision 3) @@ -1,3 +1,10 @@ +* Tue Apr 26 2011 Daniil Chuikodaniil.chu...@digia.com -0.0.29 + - fixes: Meegophotos crash after closing application (BMC-14309) + - fixes: Only half of the Search button is visible in Photo viewer when in Portrait mode (BMC - 14993) + +* Thu Apr 21 2011 Daniil Chuikodaniil.chu...@digia.com -0.0.29 + - fixes: meegophotos crash after trying to open photo (BMC-14135) + Package: meego-ux-settings warning: your urllib2 version seems to be broken. Using a workaround for http://bugs.python.org/issue9639 Index: meego-ux-settings.changes === --- meego-ux-settings.changes (revision 5) +++ meego-ux-settings.changes (revision 4) @@ -1,5 +1,6 @@ -* Wed Apr 26 2011 Kevron Rees kevron.m.r...@intel.com - 0.2.5 -- fixed time setting issue +* Wed Apr 27 2011 Tapio Rantala ext-tapio.rant...@nokia.com 0.2.5 +- Removed zone.alias hack +- Added dependency to tzdata-timed Package: meegotouch-compositor Index: meegotouch-compositor.changes === --- meegotouch-compositor.changes (revision 19) +++ meegotouch-compositor.changes (revision 3) @@ -1,3 +1,32 @@ +* Thu Apr 14 2011 Fathi Boudra fathi.bou...@nokia.com - 0.8.9 +- added BMC14405_xterm_menu_bar_has_unwanted_behavior.patch (BMC#14405) + to remove no more usable property statusBar-property(sharedPixmapHeight) + +* Thu Apr 07 2011 Miroslav Safr miroslav.s...@tieto.com.com - 0.8.9 +- updated to 0.8.9 (BMC#15199) +- re-added mdecorator.desktop on ARM (BMC#15038) +- disabled Introduce-_MEEGOTOUCH_SKIP_ANIMATIONS-window-propert.patch +- moved org.maemo.mcompositor.context and recovery.qm from -devel to + meegotouch-compositor package + +* Fri Mar 25 2011 Miroslav Safr miroslav.s...@tieto.com.com - 0.8.8 +- updated to 0.8.8 + It solves flashing issues and unnecessary compositing (BMC#5275) +- removed patches: + add_Xext_lib_to_windowctl.patch - merged upstream Package: meegotouch-home Index: meegotouch-home.changes === --- meegotouch-home.changes (revision 17) +++ meegotouch-home.changes (revision 6) @@ -1,3 +1,7 @@ +* Thu Apr 14 2011 Fathi Boudra fathi.bou...@nokia.com - 0.23.10 +- added quick_launch_button.patch to fix the icons on the quick-launcher placed + too low. They are only 50% visible. + Package: meegotouch-systemui Index: meegotouch-systemui.changes === --- meegotouch-systemui.changes
[Meego-handset] [N900] Fennec pre-starting
Hi,
I had an item on my todo to describe how to do faststart/prestarting
in Fennec. My old package is broken so can't just as easily make a
patch but here's steps for someone to implement:
Add to mozconfig.(x86, arm):
ac_add_options --enable-faststart
Add file fennec-faststart.desktop to package:
[Desktop Entry]
Name=Fennec faststart
Exec=/usr/bin/fennec -faststart-hidden
Terminal=False
Type=Application
In %install phase, SOURCE6 should be whatever SOURCEX
fennec-faststart.desktop is.
mkdir -p %{buildroot}/etc/xdg/autostart
cp %{SOURCE6} %{buildroot}/etc/xdg/autostart/fennec-faststart.desktop
and then in %files add:
/etc/xdg/autostart/fennec-faststart.desktop
.. and that's prestarting of Fennec, back in the version I had.
/Carsten
___
MeeGo-handset mailing list
MeeGo-handset@lists.meego.com
http://lists.meego.com/listinfo/meego-handset
[Meego-handset] [N900] Best practices for team work in MeeGo
Hi all, A long time back I made a proposal for some best practises for team work in MeeGo that are properly open and encourages collaboration and contribution from everyone. Now that we are ramping up our DE efforts I would like to recommend everyone, especially team leads to read this through to get inspiration on how to shape their daily work. We have used these principles succesfully in the N900 hardware adaptation teams and allowed us to work together across many different physical locations and gather community interest. The proposal can be read at http://wiki.meego.com/MeeGo_team_best_practices Best regards, Carsten Munk MeeGo Nokia N900 hardware adaptation maintainer ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [N900] Improving startup times of meego apps
2011/3/14 vesa-matti.hartikai...@nokia.com: Hi, I was taking a quick look at the apps on MeeGo images. It seems that none of the current apps utilize launcher (booster) for improving the startup time. Previously, I've seen that using launcher can improve startup time of meego touch based apps 1-2s, I do not know yet how much the improvement would be on N900. There is also no memory penalty in using launcher, it may even save some memory. Prestarting is different thing. Please see: http://apidocs.meego.com/git-tip/mtf/launcher.html on more info about the launcher. BTW; This might be EasyFix improvement in some of the app cases, where apps code is simple. I think that it is more than an EasyFix - there's the 'catch' the applications are made such that they derive their 'main' class from MAppplication such as DialerApplication. And booster can't instiatiate subclasses. We had a conversation regarding this at some point in an e-mail exchange, Arun has been working with it and Pertti Kellomäki and had this to say: I'm afraid that if you inherit from MApplication, then you cannot really use the meegotouch booster. The booster process creates an MApplication, and there is no way to turn it into an SmsApplication after the fact. My hunch is that the other problems you are seeing may be related to this. That said, you could still get some benefits (e.g. shared library loading) by using the qt booster. Using the booster also helps in saving system memory by sharing memory copy-on-write between processes. (Pertti) As well as Shane mentioning the change from DialerApplication to a DialerContext of sorts would be quite an invasive change to the current code and possibly conflict with efforts to make Dialer headless. BR Carsten Munk ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] [N900] Improving startup times of meego apps
2011/3/14 Shane Bryan shane.br...@linux.intel.com: On Mon, 14 Mar 2011 16:34:09 +0100 Carsten Munk cars...@maemo.org wrote: 2011/3/14 vesa-matti.hartikai...@nokia.com: I was taking a quick look at the apps on MeeGo images. It seems that none of the current apps utilize launcher (booster) for improving the startup time. Previously, I've seen that using launcher can improve startup time of meego touch based apps 1-2s, I do not know yet how much the improvement would be on N900. There is also no memory penalty in using launcher, it may even save some memory. Prestarting is different thing. It was also my understanding that the booster/pre-launch combo was also really only of benifit to ARM, since the IA platform can efficiently use PMIC ... though I confess this is not an area of expertise for me. My point is, if it helps ARM but hurts IA, then it's a non-starter. Likewise, if it helps IA and hurts ARM, I suspect the same is true. We really need to find appropriate mechanisms that work well across architectures, or clear documentation on how to re-write apps in a manner that allows them to be conditionally compiled per arch, if it makes sense to do so. Shane actually brings up a relevant point regarding booster here. Let me try to explain.. The booster part is that in effect, the booster preloads some libraries/does the initialization phase of Qt/MTF/whatever once and then receives requests to open a application and then dlopen() the application. The application is compiled with -fPIC and linked with -pie -rdynamic to be able to do this. The problem on X86, or Atom specifically is the problem shown in this article: http://software.intel.com/en-us/blogs/2010/10/12/avoid-short-functions-on-atom/ Now of course the discussion would be if the startup performance is more important and if the application hit is in practice that bad. Considering that Qt is built with -fPIC on X86 (and hence have the performance hit already) the hit for rest of application shouldn't be that bad. I think startup performance is more important than runtime, considering it takes like 5s for dialer to start up even on X86. BR Carsten Munk ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
