[MeeGo-dev] [SSO] Fixing Backup/Sestore Functionality
Hi, Please review the following. 1) Helper common definitions Helper functions for setting file permissions and ownership in the signon core. https://gitorious.org/accounts-sso/signon/commit/9fdf07dcbdc13b28ff9375a5c4179879c05610ce 2) Fixed backup and restore processes. - If a backup is created after boot time, prior to any signond start, create the storage directory tree with the right file permissions. - If a restore is made, make sure the restored files have the right permissions. - Implementation of the file permissions and ownership setting helper functions. https://gitorious.org/accounts-sso/signon/commit/c8ac60247893dde5ccb65da145d410733a0f09c9 3) Setting the right ownership for the crypto mount target. https://gitorious.org/accounts-sso/signon/commit/d96c90fdff43666e7019f23122597751929b845b 4) Setting the right file permissions and ownership for the crypto container. https://gitorious.org/accounts-sso/signon/commit/1594f1057629f26618e01bf4e8fbc93dde0cff3a 5) Setting the right file permissions and ownership for the storage directory. Also the same are set for the meta data DB file. https://gitorious.org/accounts-sso/signon/commit/558d1743a27f6b685f06f88993b6faafda2537c9 6) Cherry-Picked: CryptoManager: add fileSystemIsSetup() This method replaces the CredentialsAccessManager::fileSystemDeployed(). Also, rename fileSystemMounted to fileSystemIsMounted, for consistency. https://gitorious.org/accounts-sso/signon/commit/a2eb04cbf880ae27be0f9aec95f4610de4e06827 This commit is to be partially overwritten by the initial one in branch `keymodel` from where it was initially cherry picked and a bit modified due to a physical and conceptual conflict. Br, Aurel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] [SSO] Fixing Backup/Restore Functionality
Hi, Please consider the following merge request: https://gitorious.org/accounts-sso/signon/merge_requests/3 Br, Aurel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] KCalCore API changes (was: Re: migration (back) to EDS - contacts and calendar)
Hello! I believe MeeGo KCalCore API semantic differs from upstream KDE in the interpretation of the endDate value. See below for the details. I would like to have this fixed *before* releasing MeeGo 1.2 with the modified API semantic. It's not part of the official platform API, but does get used and thus fixing it later just means more code will have been written against the modified API. Alvaro, can you comment on why the API semantic was changed? If I misunderstand the situation or lack certain information, then let's better resolve such a misunderstanding. ;-} Sirisha, you would have to adapt the MeeGo UX calendar app. Doable? Michael, how about QtMobility Organizer? Anyone else depending on the KCalCore end date semantic? Bye, Patrick On So, 2011-04-03 at 21:18 +0100, Patrick Ohly wrote: On Fr, 2011-04-01 at 11:29 +0200, Patrick Ohly wrote: I beg to disagree here. The MeeGo version of KCalCore is compiled differently than the upstream version: #if !defined(KCALCORE_FOR_MEEGO) endDate = kdt.date().addDays( -1 ); #else endDate = kdt.date(); #endif Go to the kde git, and you will see those there. So the code, as I said, is from upstream. My point is that the MeeGo version of KCalCore is functionally different from the one in KDE. That the code is upstream is irrelevant as long as ifdefs are used for more fundamental changes than merely getting the code to compile on a different platform. My suspicion all along was that these defines around end date change the semantic of KCalCore. To verify that, I modified the test program from BMC #6050 such that it imports an iCalendar 2.0 all-day event and prints its start/end date after importing into KCalCore. Code attached, compile/run with: rm -rf ~/.calendar \ g++ -g test-allday-semantic.cpp `pkg-config --cflags --libs libmkcal ` \ ./a.out In MeeGo with KCalCore 4.1.18 I get start QDate(Wed Apr 5 2006) end QDate(Thu Apr 6 2006) After recompiling that version without KCALCORE_FOR_MEEGO I get: start QDate(Wed Apr 5 2006) end QDate(Wed Apr 5 2006) In other words, the patch changes the semantic of dtEnd() for applications. Upstream KDE uses dtEnd() is inclusive, the MeeGo version uses dtEnd() is exclusive. The latter is closer to iCalendar 2.0, but is that a good enough justification to break compatibility with apps ported from KDE? I don't think so. Another possible justification would be that the original semantic cannot express an empty all-day event (start == end). Again I would consider not modifying the API as more important than this cleanup. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Is there any compliance document of UI for Meego Netbook?
Hi, Is there any compliance document of UI for Meego Netbook/Tablet? There is compliance document for Handset-UI, but not for netbook. Any updates on it? Thanks, Rohit ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Is there any compliance document of UI for Meego Netbook?
There is a Netbook profile (it's about a page in the main compliance document), and one could expect a Tablet profile in the next generation of the Compliance Spec. But note that the User Experience (UX) layer is outside the scope of compliance, since it's considered replaceable if a vendor wants to do so. Is that the question you're asking? -- mats From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Rohit Baravkar Sent: Monday, April 18, 2011 6:38 AM To: meego-dev Subject: [MeeGo-dev] Is there any compliance document of UI for Meego Netbook? Hi, Is there any compliance document of UI for Meego Netbook/Tablet? There is compliance document for Handset-UI, but not for netbook. Any updates on it? Thanks, Rohit ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Is there any compliance document of UI for Meego Netbook?
On Mon, 18 Apr 2011, Wichmann, Mats D wrote: There is a Netbook profile (it's about a page in the main compliance document), and one could expect a Tablet profile in the next generation of the Compliance Spec. But note that the User Experience (UX) layer is outside the scope of compliance, since it's considered replaceable if a vendor wants to do so. Is that the question you're asking? I think he's talking about this: http://meego.com/developers/ui-design-guidelines Where there are only Handset UI guidelines However, he's mistakenly calling it a compliance document... which it is not. -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] how to return to main panel
Hi: I am doing some development with the MeeGo tablet image. It looks like the panel is responsive to the Window Start key from my keyboard and will pop up a panel chooser. That is a convenient way for me to go back to the main UI panel from any application. Is there a sure way for me to bring up this panel chooser or go back to the UI panel if and when the Window Start key is not available or when I actually want to trigger to go back to main panel operation from my application? thanks Mark ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to return to main panel
On 04/18/2011 03:04 PM, Mark S. Townsley wrote: Hi: I am doing some development with the MeeGo tablet image. It looks like the panel is responsive to the Window Start key from my keyboard and will pop up a panel chooser. That is a convenient way for me to go back to the main UI panel from any application. Is there a sure way for me to bring up this panel chooser or go back to the UI panel if and when the Window Start key is not available or when I actually want to trigger to go back to main panel operation from my application? From your app just minimize your window. --rusty ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Dialer Project meeting minutes for Tuesday 4/12
#meego-meeting: MeeGo Dialer Project Meeting started by sabotage at 15:00:31 UTC. Online minutes: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-15.00.html Full IRC meeting log: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-15.00.log.html Meeting summary --- * VoiceSMS meetings and Dialer meetings (sabotage, 15:02:45) * msugano can manage coordination of VoiceSMS DE team activities with Dialer team (sabotage, 15:06:38) * LINK: http://lists.meego.com/pipermail/meego-handset/2011-April/000321.html comment from msugano (on the 2 projects) (msugano, 15:10:10) * AGREED: Dialer and DE VoiceSMS teams will combine meetings (sabotage, 15:13:31) * ACTION: discuss on meego-handset ML nominations for additional chairs to the Dialer Project meetings (sabotage, 15:15:12) * Sirpa has been working on a QML PIN query UI (akiniemi_, 15:17:26) * AGREED: discuss PIN query UI in this meeting forum (sabotage, 15:20:13) * Wireframes (sabotage, 15:20:33) * ACTION: sabotage to ping Intel again for details on wireframe availability (sabotage, 15:22:14) * bugs, merge-requests and patch status (sabotage, 15:26:14) * QML porting (sabotage, 15:29:56) * ACTION: add thoughts to Dialer QML port wiki page (sabotage, 15:40:22) * LINK: http://wiki.meego.com/Project/Dialer/QMLMigration (sabotage, 15:41:23) * Headless dialer (sabotage, 15:41:48) * ACTION: aruravi to start a wiki page to detail plans and status of Dialer Headless branch (sabotage, 15:48:31) * Any Other Business (sabotage, 15:49:25) * Next meeting is Tuesday, April 19th at 14:00 UTC (sabotage, 15:52:52) * LINK: http://summit.meegonetwork.fi/live (timoph, 15:54:34) * LINK: http://summit.meegonetwork.fi/live (sabotage, 15:54:54) * Sabotage submitted a session proposal for SF2011 conference (sabotage, 15:56:46) * LINK: http://sf2011.meego.com/program/sessions/mr-bell-meet-mr-goldberg-state-meego-dialer (sabotage, 15:56:53) Meeting ended at 15:59:41 UTC. Action Items * discuss on meego-handset ML nominations for additional chairs to the Dialer Project meetings * sabotage to ping Intel again for details on wireframe availability * add thoughts to Dialer QML port wiki page * aruravi to start a wiki page to detail plans and status of Dialer Headless branch Action Items, by person --- * aruravi * aruravi to start a wiki page to detail plans and status of Dialer Headless branch * sabotage * sabotage to ping Intel again for details on wireframe availability * **UNASSIGNED** * discuss on meego-handset ML nominations for additional chairs to the Dialer Project meetings * add thoughts to Dialer QML port wiki page People Present (lines said) --- * sabotage (152) * alterego (51) * msugano (38) * aruravi (15) * crevetor (14) * akiniemi_ (14) * essi (8) * timoph (4) * Stskeeps (3) * w00t (2) * MeeGoMeetBot (2) * apaila (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
