Re: [MeeGo-dev] Meego Bugs Access Denied
Hi, On 3/31/11 12:05 AM, ext Andre Klapper aklap...@openismus.com wrote: On Wed, 2011-03-30 at 15:56 -0500, Gabriel M. Beddingfield wrote: Currently, when someone happens upon a restricted bug, they get a scary red web page that shouts something like Access Restricted! You are not authorized to view this bug. That page makes a person feel like they're an intruder, and are about to be escorted out of the building. Could this perhaps be toned down a little? Maybe add a link to this wiki page? +1 Feel free to file a request in bugs.meego.com against Bugzilla. Indeed, file a request so we make the warning more user friendly, thanks. andre -- Andre Klapper (maemo.org bugmaster) http://www.openismus.com Cheers, Eric Le Roux MeeGo EM Lead ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ 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] [SSO][PATCH] Signon: make authentication plugins log to syslog
Hi Alberto, I added some comments into gitorious. Regards, Tomi ext Alberto Mardegan wrote: Hi all, I've written some patches to address the issue described in the subject, and improved a bit the situation concerning the pollution of the TRACE() macros. Please see the last 7 commits in this branch: https://gitorious.org/accounts-sso/signon/commits/debug-cleanup Ciao, Alberto ___ 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] migration (back) to EDS - contacts and calendar
On Tuesday, March 29, 2011 05:35:04 pm ext Patrick Ohly wrote: Hello! Let's be more specific about identifying work which needs to be done. I've put together some thoughts here: http://wiki.meego.com/Architecture/planning/evolution-data-server http://wiki.meego.com/Architecture/planning/evolution-data-server/QtContact s_storage_plugin http://wiki.meego.com/Architecture/planning/evolution-data-server/eds-impr ovements The first page does include a very simplistic comparison of the different options. I thought about leaving out that part altogether, but decided otherwise because I believe that listing some of the pros and cons in public is useful. No flame wars, please. For contacts and calendar it is fairly obvious where the pain points are, so let's focus on that for now. I'm interested in getting feedback on the proposed EDS improvements. At this point, I have the QtContacts-EDS contact manager working for reading and writing contacts, as outlined in the page linked to above. Change notifications are missing. It's just proof of concept (non-)quality. I suspect that I need to get open source approval first before publishing it somewhere. I have not done any prototyping yet with KCalCore, but I expect that similar improvements as for contacts will be useful for that work, too. Hi, So far the calendar area hasn't been discussed, but I would like to comment on a few things... In the wiki it says: Disavantages of mKCal. * Only one coarse change method. There is not fine diff notifications. I agree, this can be improved, and I think it would be quite easy to implement. But was it requested anywhere? You are the promoter of FeatureZilla, where is the link? Nobody has ever heard of this feature request. * iCal support was faulty. Well yes it had some bugs, but most of them are closed only two are open and one assigned to you. Is the bug history a reason to dich a project? Has EDS a better history? This is FUD and I think having bugs and fixing them is a healthy symptom of a project. Where are the EDS advantages in the wiki? Because the problems of the current solution are stated. But why is eds better? Where are the reasons? About the partial loading of mKCal. Is it faulty? Please provide the bug number. Or is it FUD again? And as it is said in the wiki, eds holds everything into memory. I find this a problem. What happens if a manager type person with an average 4-6 events per day, and a two year calendar? (Roughly 54 weeks * 5days/week * 6 events = 1620 events. Do you need to keep all this in memory? Nowadays memory is cheap, so we could argue that. But, on every startup you have to read one iCalendar text file (as said on the wiki) with all that content?? So how long do you think the startup will be? mKcal also has a quite flexible plugin invitations handling. How do you plan to integrate the new backend with exchange or any other service? And with Buteo also, there was a way to add sync services. How is it planned now? Continuing with the statements on the wiki. As I said before KCalCore in meego is from upstream. The modifications are the patches we have implemented that haven't been sent to kde's git yet. (or the ones which hasn't been merged yet from their git). So again FUD. Your proposal says that you would use KCalCore for the iCal parsing and use it from EDS. Wasn't it said above that the iCal parsing was faulty? Concluding this email... As it has said before, there are no technical reasons to back up the decision of changing backeds. From all the stated ones, only one is valid and it could be implemented (isn't it that easier that creating something new?). Everything else is pure FUD to hide a political decision and change a project not invented here for another one that it is. Please provide real facts why the change is made. Álvaro ___ 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] Meego Bugs Access Denied
ext eric.le-r...@nokia.com eric.le-r...@nokia.com writes: Indeed, file a request so we make the warning more user friendly, thanks. Can't you just do it without having a request filed? ___ 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] Meego Bugs Access Denied
Hi Marius, On 3/31/11 10:07 AM, Marius Vollmer marius.voll...@nokia.com wrote: ext eric.le-r...@nokia.com eric.le-r...@nokia.com writes: Indeed, file a request so we make the warning more user friendly, thanks. Can't you just do it without having a request filed? Nope. As we have a distributed team to handle bugzilla it's way easier if we actually have a formal request... So it doesn't go into limbo if I or someone else don't do it immediately. Sorry for being _that_ demanding :P Cheers, Eric ___ 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] Meego Bugs Access Denied
Can we please add mandatory fields to such bug reports: - Why is it inaccessible. - ETA for opening bug report. Such that filing those bugs will be impossible without ? -Sivan On Thu, Mar 31, 2011 at 9:27 AM, eric.le-r...@nokia.com wrote: Hi Marius, On 3/31/11 10:07 AM, Marius Vollmer marius.voll...@nokia.com wrote: ext eric.le-r...@nokia.com eric.le-r...@nokia.com writes: Indeed, file a request so we make the warning more user friendly, thanks. Can't you just do it without having a request filed? Nope. As we have a distributed team to handle bugzilla it's way easier if we actually have a formal request... So it doesn't go into limbo if I or someone else don't do it immediately. Sorry for being _that_ demanding :P Cheers, Eric ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ 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] migration (back) to EDS - contacts and calendar
On Do, 2011-03-31 at 07:56 +0100, Alvaro Manera wrote: On Tuesday, March 29, 2011 05:35:04 pm ext Patrick Ohly wrote: So far the calendar area hasn't been discussed, but I would like to comment on a few things... In the wiki it says: Disavantages of mKCal. Okay, I knew it was a mistake to include such a comparison. Now that it is public, let's discuss it. * Only one coarse change method. There is not fine diff notifications. I agree, this can be improved, and I think it would be quite easy to implement. But was it requested anywhere? No. I was merely comparing the current status. * iCal support was faulty. Well yes it had some bugs, but most of them are closed only two are open and one assigned to you. Is the bug history a reason to ditch a project? It certainly leaves a bad impression that fixing bugs like https://bugs.meego.com/show_bug.cgi?id=6050 took 8 months and several false bug closed status changes (https://bugs.meego.com/show_activity.cgi?id=6050) before the fix eventually arrived in MeeGo. Now we all know that the situation for fixing bugs in MeeGo was difficult in the past. But can we be sure that it will be better in the future? Where are the EDS advantages in the wiki? Because the problems of the current solution are stated. But why is eds better? Where are the reasons? I'm not saying that EDS is necessarily better. It's better understood, we know how to fix it if we run into problems. That's all, but that matters. About the partial loading of mKCal. Is it faulty? Please provide the bug number. It was faulty: https://bugs.meego.com/show_bug.cgi?id=6061#c5 I still find it hard to use correctly. For example, which events need to be loaded to get a correct response for events falling into the time range 2011-03-31 00:00 Europe/Berlin until 2011-03-31 23:59 Europe/Berlin? Which API calls, which parameters? mKcal also has a quite flexible plugin invitations handling. How do you plan to integrate the new backend with exchange or any other service? Valid point, but not relevant yet. There is no Exchange support in MeeGo. The UIs on meego.com are barely able to handle basic calendar and email tasks. Handling meeting invitations is out of scope right now. Yes, it is a pity that the more capable UIs taking full advantage of mKCal and QMF capabilities are not in meego.com or the situation would be a lot different. And with Buteo also, there was a way to add sync services. How is it planned now? Who needs that? Let me know and I'll add it to SyncEvolution. I've said it before: MeeGo now needs to focus on the things for which there is a real need. Everything else just binds resources which are desperately needed elsewhere. Continuing with the statements on the wiki. As I said before KCalCore in meego is from upstream. The modifications are the patches we have implemented that haven't been sent to kde's git yet. (or the ones which hasn't been merged yet from their git). So again FUD. 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 It's minor, but I suspect that if the upstream KCalCore was used in MeeGo, it would break mKCal. I also don't see how upstream would accept such a patch or if they did, why MeeGo should have a different semantic than the upstream KDE version. Your proposal says that you would use KCalCore for the iCal parsing and use it from EDS. Wasn't it said above that the iCal parsing was faulty? Yes, and the ifdef above is part of the fix for one of these bugs. My hope is that once upstream KCalCore is used, it'll have no iCalendar handling issues. Everything else is pure FUD to hide a political decision and change a project not invented here for another one that it is. Minor correction: EDS was not invented at Intel or for Moblin/MeeGo. I'm also not trying to hide a political decision. I was told to investigate EDS for MeeGo, and that's what I am doing. If you disagree with that direction, then please talk to those who decided to go that way. That decision was made way above my head, so talking with me about it will gain you nothing except some clarifications about technical aspects. rantIn case folks on the list still haven't noticed, I'm sticking my neck out here because I believe that discussions should be open. So far the result is definitely not going to encourage others to do the same. Oh, and I'm on vacation today, I shouldn't even be reading your emails, much less responding to them./rant -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ___ MeeGo-dev mailing list
Re: [MeeGo-dev] Dialer Project meetings announcement
In an attempt to improve communication among the currently active (and increasing daily) dialer contributors and to increase general community awareness, I will be kicking off the first weekly Dialer Project meeting on #meego-meeting starting next Tuesday, April 5th, at 15:00 UTC (07:00 PST). Just wanted to say thank you for this. How about SMS application, anything similar going to happen? Jukka ___ 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] Meego Bugs Access Denied
In many cases the confidential information has been entered in a comment long after the original bug was filed as debug process progresses. -Original Message- Sivan Greenberg wrote: Can we please add mandatory fields to such bug reports: - Why is it inaccessible. - ETA for opening bug report. Such that filing those bugs will be impossible without ? -Sivan __ In many cases the confidential information has been entered in a comment long after the original bug was filed as debug process progresses. Joel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] tablet user experience source is now open...
Hi everyone, Today, we've made available the source code for the tablet user experience project. The tablet user experience project (http://meego.com/downloads/releases/1.2/meego-tablet-developer-preview), developed mostly in QML, is still under active development and considered pre-alpha code. It introduces a panels-based home screen as the core user experience navigation model, providing users with fast access to applications, settings, recent and favorite content. The tablet user experience includes a traditional application icon-grid view for application management. It also includes several built-in applications as part of the user experience: a touch optimized browser, based on Chromium; a Camera, Photo Viewer, Video Player and Music Player to capture, view, play and share media files; Calendar, Contacts, Email, Tasks and Notes applications to manage your personal information; a Chat application that supports instant messaging on Jabber and Google Talk networks; and a Clock application, which includes alarms, timers and multiple time zone displays. The tablet user experience also includes APIs for sharing content to social networks and other Web targets, adding third-party content into the panels, and centralizing Settings for built-in and installed apps. The tablet user experience runs on MeeGo 1.2 or later and currently has hardware adaptation support for the ExoPC, an Intel Atom based Pinetrail Platform. Few useful links: You can browse the source code on http://meego.gitorious.org/meego-ux, the development image is at http://meego.com/downloads/releases/1.2/meego-tablet-developer-preview, get started developing applications with the Tablet SDK (for Linux - http://wiki.meego.com/SDK/Tablet/MeeGo_Tablet_SDK_1.2_Preview_for_Linux, for Windows - http://wiki.meego.com/SDK/Tablet/MeeGo_Tablet_SDK_1.2_Preview_for_Windows), the MeeGo Tablet UI guidelines are here http://meego.com/sites/all/files/users/admin/meego_touch_ui_v1.2.pdf, and take a look at the MeeGo UX Components (source - http://meego.gitorious.org/meego-ux/meego-ux-components, wiki - http://wiki.meego.com/MeeGo_UX_Components). As always, we look forward to your feedback and contributions. Thanks imad ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Customizing Building MeeGo Image on local system
Hi, I want to download source packages of MeeGo and build it on my local machine running Ubuntu operating system.Please provide details of procedure for doing so. do I need to use OBS(open suse build services) for building MeeGo Image.I want to customize MeeGo, I want to remove UI and use my own. Please assist on how to customize MeeGo.After customization I want build it for ARM. Pls provide details. I am very new in Linux, aslo provide URL where to get source code. Thanks, Vyankatesh ___ 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] Customizing Building MeeGo Image on local system
On Thu Mar 31 2011 11:09:54 AM CEST, Vyankatesh VD vyankatesh...@in.bosch.com wrote: Hi, I want to download source packages of MeeGo and build it on my local machine running Ubuntu operating system.Please provide details of procedure for doing so. do I need to use OBS(open suse build services) for building MeeGo Image.I want to customize MeeGo, I want to remove UI and use my own. Please assist on how to customize MeeGo.After customization I want build it for ARM. Pls provide details. I am very new in Linux, aslo provide URL where to get source code. Hi, You indeed need OBS but I would advise against building complete MeeGo. In most cases you don't need or want to. You need a workflow around these lines: * set up a OBS server for your development work * try to create a image for your target with MeeGo image creator using a kickstart file (.ks) * Remove the package groups the UI consists of, from the .ks file * develop your customizations with OBS, resulting in repositories that you can add with 'repo' lines in the .ks * add your customization package names to %packages section of the .ks * build a new image with your new .ks * enjoy the result (repeat last 4 steps as needed) /Carsten Thanks, Vyankatesh ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ 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] tablet user experience source is now open...
On 03/31/2011 12:16 PM, Sousou, Imad wrote: Today, we've made available the source code for the tablet user experience project. [...] As always, we look forward to your feedback and contributions. Is there a mailing list specifically for this project? Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ 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] tablet user experience source is now open...
Hi, On 31 March 2011 11:24, Alberto Mardegan ma...@users.sourceforge.net wrote: Is there a mailing list specifically for this project? I don't think so. Admittedly, I've been mostly just using #meego on IRC/gitorious for my work on it so far :) Wouldn't it be in more or less the same boat as accounts SSO? (Start here, spin it off if it gets sufficient volume) -- Robin Burchell http://rburchell.com ___ 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] [Accounts] Fixes: NB#204950 - Account::verify and Account::verifyWithTokens() returns TRUE, all the time irrespective of whether Account::sign() called or not.
Hi,
On 03/30/2011 01:55 PM, ext Alberto Mardegan wrote:
On 03/30/2011 12:07 PM, Lucian Horga wrote:
diff --git a/libaccounts-glib/ag-account.c b/libaccounts-glib/ag-account.c
index a2354ba..21273a1 100644
--- a/libaccounts-glib/ag-account.c
+++ b/libaccounts-glib/ag-account.c
@@ -41,6 +41,10 @@
#include ag-service.h
#include ag-util.h
+#ifdef HAVE_AEGISCRYPTO
+ #include aegis_crypto.h
+#endif
+
#include string.h
#define SERVICE_GLOBAL global
@@ -303,6 +307,7 @@ ag_account_watch_int (AgAccount *account, gchar *key,
gchar *prefix,
return watch;
}
+#ifdef HAVE_AEGISCRYPTO
static gboolean
got_account_signature (sqlite3_stmt *stmt, AgSignature *sgn)
{
@@ -311,6 +316,7 @@ got_account_signature (sqlite3_stmt *stmt, AgSignature
*sgn)
return TRUE;
}
+#endif
static gboolean
got_account_setting (sqlite3_stmt *stmt, GHashTable *settings)
@@ -2085,6 +2091,7 @@ ag_account_store_blocking (AgAccount *account, GError
**error)
return TRUE;
}
+#ifdef HAVE_AEGISCRYPTO
static gboolean
store_data (gpointer key, gpointer value, gpointer data)
{
@@ -2169,6 +2176,8 @@ signature_data (AgAccount *account, const gchar *key)
return g_string_free (data, FALSE);
}
+#endif
+
/**
* ag_account_sign:
* @key: the name of the key or prefix of the keys to be signed.
@@ -2179,10 +2188,13 @@ signature_data (AgAccount *account, const gchar *key)
void
ag_account_sign (AgAccount *account, const gchar *key, const gchar *token)
{
+#ifdef HAVE_AEGISCRYPTO
AgSignature *sgn;
AgAccountPrivate *priv;
AgServiceChanges *sc;
gchar *data;
+struct aegis_signature_t signed_data;
+gchar *signed_raw_data;
g_return_if_fail (key != NULL);
g_return_if_fail (token != NULL);
@@ -2192,17 +2204,34 @@ ag_account_sign (AgAccount *account, const gchar
*key, const gchar *token)
g_return_if_fail (data != NULL);
-/* TODO: sign data with token - depends on libmaemosec */
+aegis_crypto_result result_sign =
+ aegis_crypto_sign (data,
+ strlen (data) + 1,
+ token,
+ signed_data);
signed_data - signature
Do you want the name changed from signed_data to signature or you want to
select the signature field from signed_data?
The function takes struct aegis_signature_t as parameter, and this struct does
not have any signature field:
typedef struct aegis_signature_t {
unsigned char d[SIGNATURE_LENGTH]; /** The actual signature bytes */
} AEGIS_SIGNATURE_T;
Do you have some reason to add 1 to the string length?
I assumed the string to be null-terminated.
-priv = account-priv;
-sc = account_service_changes_get (priv, priv-service, TRUE);
+aegis_crypto_finish ();
Don't call aegis_crypto_finish() here, you are using more agis-crypto
function just below.
Fixed.
+g_free (data);
+g_return_if_fail (result_sign != aegis_crypto_ok);
+
+aegis_crypto_signature_to_string (signed_data,
+ aegis_as_base64,
+ token,
+ signed_raw_data);
signed_raw_data - signature_string
Same question as above.
sgn = g_slice_new (AgSignature);
-sgn-signature = data; //signed_data;
+sgn-signature = g_strdup (signed_raw_data); //signed_data;
remove the comment, it's obsolete now.
Ok.
+g_free (signed_raw_data);
sgn-token = g_strdup (token);
+priv = account-priv;
+sc = account_service_changes_get (priv, priv-service, TRUE);
+
g_hash_table_insert (sc-signatures,
g_strdup (key), sgn);
+#else
+g_warning (ag_account_sign: aegis-crypto not found! Unable to sign the
key.);
+#endif
}
/**
@@ -2219,13 +2248,20 @@ ag_account_sign (AgAccount *account, const gchar
*key, const gchar *token)
gboolean
ag_account_verify (AgAccount *account, const gchar *key, const gchar
**token)
{
+#ifdef HAVE_AEGISCRYPTO
AgAccountPrivate *priv;
AgServiceSettings *ss;
guint service_id;
gchar *data;
gchar *sql;
AgSignature sgn;
-
+GString *sql_str;
+aegis_system_mode_t made_in_mode;
+aegis_crypto_result result_verify;
+aegis_crypto_result result_convert;
+struct aegis_signature_t signature;
+char *token_name;
+
g_return_val_if_fail (AG_IS_ACCOUNT (account), FALSE);
priv = account-priv;
@@ -2235,7 +2271,7 @@ ag_account_verify (AgAccount *account, const gchar
*key, const gchar **token)
service_id = (priv-service != NULL) ? priv-service-id : 0;
-GString *sql_str;
+
sql_str = g_string_sized_new (512);
_ag_string_append_printf (sql_str,
SELECT signature, token FROM Signatures
@@ -2246,16 +2282,44 @@ ag_account_verify (AgAccount *account, const gchar
Re: [MeeGo-dev] [Accounts] Fixes: NB#204950 - Account::verify and Account::verifyWithTokens() returns TRUE, all the time irrespective of whether Account::sign() called or not.
On 03/31/2011 01:40 PM, ext-lucian.ho...@nokia.com wrote: Do you want the name changed from signed_data to signature or you want to select the signature field from signed_data? Just rename. Do you have some reason to add 1 to the string length? I assumed the string to be null-terminated. It is, but I don't see why we should encrypt the terminator as well. Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ 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] tablet user experience source is now open...
On Thu, Mar 31, 2011 at 10:16, Sousou, Imad imad.sou...@intel.com wrote: [snip] take a look at the MeeGo UX Components (source - http://meego.gitorious.org/meego-ux/meego-ux-components, wiki - http://wiki.meego.com/MeeGo_UX_Components). There's been some confusion, and I hope to get this clarified before everyone's scratching their head: * What is the relationship between MeeGo UX Components and Qt Components[1]? I can undestand that something is necessary to present the right UX, but is it API compatible? *Please* don't say that the developer story for Qt MeeGo has now changed again, and that Qt Components should be used for Symbian MeeGo Handset, and MeeGo UX Components for Tablet UX. Up until recently the developer story was good: * Use Qt * Use Qt SDK * Use Qt Quick * Use Qt Components which is coming along and being developed in the open (ish) Now there's the MeeGo SDK, a different SDK for the Tablet UX, a new set of UI controls. WTF is going on? This constant shifting on how to write a portable Qt application targetting MeeGo primarily and Maemo and Symbian secondarily is confusing and frustrating. Thanks in advance, Andrew [1] http://qt.gitorious.org/qt-components -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ ___ 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] tablet user experience source is now open...
Hi, On 31/03/11 11:57, Andrew Flegg wrote: There's been some confusion, and I hope to get this clarified before everyone's scratching their head: * What is the relationship between MeeGo UX Components and Qt Components[1]? I talked (briefly) with Rusty on IRC about this last night, and was told that the MeeGo UX components' long term future so to speak lies with Qt Components. Relevant part of discussion snipped below: 03/30@23:57:43 rustylynch if the re-layout was faster (so the user didn't notice it), then this wouldn't be an issue 03/30@23:58:00 w00t_ that's true 03/30@23:58:10 w00t_ ideally, we need to tell the app we're about to show it 03/30@23:58:11 rustylynch i know the new meego-ux-components has a much better implementation for this, but i haven't verified if it's good enough to hide the relayout 03/30@23:58:21 w00t_ ooh 03/30@23:58:23 w00t_ is this in git? 03/30@23:58:25 rustylynch yea, we need an about-to-show signal 03/30@23:58:26 w00t_ I can probably poke it 03/30@23:58:39 rustylynch yes, there is a meego-ux-components project 03/30@23:59:02 rustylynch this is what we actually want to use, and are in process of migrating stuff out of meegolabs-ux-compnoents 03/30@23:59:36 rustylynch meegolabs-ux-components (imported as MeeGo.Labs.Components) is what we started with, before qt-components was far enough along to build off Day changed to 31 Mar 2011 03/31@00:00:12 rustylynch i'm being told by the maintainers that they are ready to start doing a massive porting of the apps 03/31@00:00:28 w00t_ okay, and what's meego-ux-components then? an implementation of the Qt Components APIs? 03/31@00:00:46 rustylynch it builds on top of it 03/31@00:00:53 w00t_ cool Best regards, -- Robin Burchell http://rburchell.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] file system partitioning meego 1.2
Hi, I would like to know how the file system will be partitioned in MeeGo 1.2 tablet. I beleive file system will be written into both NAND and eMMC unlike MeeGo 1.1 Regards, Sam ___ 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] Customizing Building MeeGo Image on local system
Carsten Munk carsten@... writes: On Thu Mar 31 2011 11:09:54 AM CEST, Vyankatesh VD Vyankatesh.VD at in.bosch.com wrote: Hi, I want to download source packages of MeeGo and build it on my local machine running Ubuntu operating system.Please provide details of procedure for doing so. do I need to use OBS(open suse build services) for building MeeGo Image.I want to customize MeeGo, I want to remove UI and use my own. Please assist on how to customize MeeGo.After customization I want build it for ARM. Pls provide details. I am very new in Linux, aslo provide URL where to get source code. Hi, You indeed need OBS but I would advise against building complete MeeGo. In most cases you don't need or want to. You need a workflow around these lines: * set up a OBS server for your development work * try to create a image for your target with MeeGo image creator using a kickstart file (.ks) * Remove the package groups the UI consists of, from the .ks file * develop your customizations with OBS, resulting in repositories that you can add with 'repo' lines in the .ks * add your customization package names to %packages section of the .ks * build a new image with your new .ks * enjoy the result (repeat last 4 steps as needed) /Carsten Thanks, Vyankatesh ___ MeeGo-dev mailing list MeeGo-dev at meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev at meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines Hi Carsten, Thank you very much for posting reply to my post. but I have few doubt. -Can you provide detail step (some Reference URL) regarding how to use OBS Server, bcoz I am new to OBS. -Can I install OBS server on Ubuntu as Development platform ? -As you suggested not to build code, but my requirement is I would like to have complete source code of MeeGo alongwith it's build enviornment so that I can customize it at low level (replacing UI, Kernel, middleware) -Then build it for other platform (cross-platform) like ARM. Appreciating your assistance. With Best Regards, Vyankatesh ___ 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] migration (back) to EDS - contacts and calendar
* Only one coarse change method. There is not fine diff notifications. I agree, this can be improved, and I think it would be quite easy to implement. But was it requested anywhere? No. I was merely comparing the current status. Then it is quite unfair to do so unless you want to bias the readers. * iCal support was faulty. Well yes it had some bugs, but most of them are closed only two are open and one assigned to you. Is the bug history a reason to ditch a project? It certainly leaves a bad impression that fixing bugs like https://bugs.meego.com/show_bug.cgi?id=6050 took 8 months and several false bug closed status changes (https://bugs.meego.com/show_activity.cgi?id=6050) before the fix eventually arrived in MeeGo. Now we all know that the situation for fixing bugs in MeeGo was difficult in the past. But can we be sure that it will be better in the future? I also believe that many things can be done to improve that. I'm not saying that EDS is necessarily better. It's better understood, we know how to fix it if we run into problems. That's all, but that matters. Quite understandable, but isn't it that we are trying to create a platform? Why then are we sticking to a solution that is not the best one? Wouldn't it be better trying to get a nice solution? And with this I am not saying that mKcal is the best one. If there is a better option, taking into account functionality and time, lets go for it. About the partial loading of mKCal. Is it faulty? Please provide the bug number. It was faulty: https://bugs.meego.com/show_bug.cgi?id=6061#c5 I still find it hard to use correctly. For example, which events need to be loaded to get a correct response for events falling into the time range 2011-03-31 00:00 Europe/Berlin until 2011-03-31 23:59 Europe/Berlin? Which API calls, which parameters? You need to create a KDateTime with those start and end times. Make sure that the storage has that range loaded storage-load(start, end); and the recurringIncidences also of course. You can query the calendar, for those dates also. calendar-incidences(start, end); And then you ExtendedCalendar::ExpandedIncidenceList expanded = calendar-expandRecurrences(newNotes, KDateTime(start), KDateTime(end), numberDays, hitLimit); To get the full expanded set. mKcal also has a quite flexible plugin invitations handling. How do you plan to integrate the new backend with exchange or any other service? Valid point, but not relevant yet. There is no Exchange support in MeeGo. The UIs on meego.com are barely able to handle basic calendar and email tasks. Handling meeting invitations is out of scope right now. Yes, it is a pity that the more capable UIs taking full advantage of mKCal and QMF capabilities are not in meego.com or the situation would be a lot different. Well I think it is quite relevant, that even if there is no Exchange in MeeGo we want to have the enablers so vendors can extend the core features. And the same goes to the next question. How is it planned to enable vendors to extend the current solution? I think it is a very valid point that should be addressed. 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. And most of them are IOP issues that we have found that are not 100% standard but we believe that need to be supported anyway. There are only two as the one you have pointed, and most likely can be fixed somewhere else. Yes, and the ifdef above is part of the fix for one of these bugs. My hope is that once upstream KCalCore is used, it'll have no iCalendar handling issues. Wishful thinking. And you can easily try building your own copy of KcalCore without that flag and see for yourself. But at least the two open bugs, won't be affected at all. Minor correction: EDS was not invented at Intel or for Moblin/MeeGo. I'm also not trying to hide a political decision. I was told to investigate EDS for MeeGo, and that's what I am doing. If you disagree with that direction, then please talk to those who decided to go that way. That decision was made way above my head, so talking with me about it will gain you nothing except some clarifications about technical aspects. I know that wasn't you, and I think it is a waste of time to try to talk to the one who made the change. But I believe that in an Open Project, doing the changes how they have been done it is not the way to go. And the technical aspects is what I want to hear. But so far, except very few based complaints about mKCal, everything else was far from
Re: [MeeGo-dev] migration (back) to EDS - contacts and calendar
On Do, 2011-03-31 at 10:59 +0200, Patrick Ohly wrote: On Do, 2011-03-31 at 07:56 +0100, Alvaro Manera wrote: On Tuesday, March 29, 2011 05:35:04 pm ext Patrick Ohly wrote: * iCal support was faulty. Well yes it had some bugs, but most of them are closed only two are open and one assigned to you. Forgot to comment on that: https://bugs.meego.com/show_bug.cgi?id=6049 is the meta bug where I described how to test iCalendar 2.0 import/export in MeeGo, before filing individual bug reports about every problem found that way. I'll close it once #6054 is resolved. In #6054 I asked about unexpected behavior in mKCal, which hasn't been answered yet. About the partial loading of mKCal. Is it faulty? Please provide the bug number. It was faulty: https://bugs.meego.com/show_bug.cgi?id=6061#c5 I still find it hard to use correctly. For example, which events need to be loaded to get a correct response for events falling into the time range 2011-03-31 00:00 Europe/Berlin until 2011-03-31 23:59 Europe/Berlin? Which API calls, which parameters? Incidentally, that's the same question that I asked before in 6061#c5, without getting a reply. I'm still interested in the answer, so I hope we can discuss it now here on the list. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ___ 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] tablet user experience source is now open...
Em quinta-feira, 31 de março de 2011, às 11:57:13, Andrew Flegg escreveu: * What is the relationship between MeeGo UX Components and Qt Components[1]? The base API is supposed to be compatible, from what I understand. If it isn't compatible, it's a mistake and should be fixed. There's an API tester as part of components that can be used to verify compatibility. The higher-level API, especially when considering the full layouting and flow may not be compatible, as the UX itself is not compatible. Things like the requirement for a hardware key or how multiple pages should be represented. But it should be similar at least, so as to reuse knowledge as much as possible, like having the same names for properties referring to similar concepts. We may be able to converge later on these when the UXes settle a bit. Right now, it's very hard to do it as they are in flux and one of them, the Harmattan one, is not public, so we can't discuss it. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ 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] migration (back) to EDS - contacts and calendar
Hi, -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Patrick Ohly Sent: Wednesday, March 30, 2011 9:57 AM To: virot...@viroteck.net Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] migration (back) to EDS - contacts and calendar * In the past, meego.com was a dumping ground for technology developed and used elsewhere. Often it wasn't properly tested there. I have heard arguments that this testing can't be done without the apps in MeeGo using the middleware. IMHO this is just a lame excuse for not doing proper QA on middleware compoments, and leads to situations as with Dialer/libcommhistory were an app developer would have to stop working on his main task to investigate problems in someone else's code. Not cool. If no bugs were filed and no questions asked by mail, any efforts made to take that technology into use are indistinguishable from not even trying. Sure, Nokia bumbled on getting the actual component developers participate directly in MeeGo, but at least some QA feedback could help prioritizing efforts, especially as we were not expected to contribute client applications. I hope collaborative processes in MeeGo will be more transparent in the future. Best regards, Mikhail ___ 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] libmeegotouch abi comparation
Em quinta-feira, 31 de março de 2011, às 12:11:58, miroslav.s...@tieto.com escreveu: Hi, we have a bit discussion if we can integrate newer libmeegotouch to Meego 1.2. Attached is report between integrated 0.20.89 and proposed current upstream 0.20.100. So any comments welcomed. High risk issues: - MApplication::notify( QObject*, QEvent* ) False positive, checker tool bug. This is not a new virtual, this is an overridden virtual from QCoreApplication. Overriding existing virtuals is permitted, provided that calling of the old method by more-derived classes is acceptable. - MSortFilterProxyModel::lessThan( QModelIndex const, QModelIndex const ) const False positive, checker tool bug, same reason. - MWidgetViewPrivate size change Private class, so size changes are not issues. Medium risk issues: - MStyleSheetParser::StylesheetFileInfo::fromMapedMemory I'm going to guess that this is an older, obsolete method that was removed due to the misspelling (maped - mapped). If no one was using it, it's ok to remove. But it is a BC change. Low risk issues: - MStyleSheetPrivate::SelectorInfoList::selectorInfos Private class, no issue. - MStyleSheetParser::StylesheetFileInfo Seems like a real issue, unless this is a private class. - MTextEdit::retranslateUi( ) No issue. - MToolBarView::orientationChangeEvent( MOrientationChangeEvent* ) No issue. - MWidgetViewPrivate Private class, no issue. - MStyleSheetSelector Incompatible change, unless this is a private class. So I'd say check whether the stylesheet parser in MTF is public API or not. If it's public API, these are BIC changes. Otherwise, the upgrade is completely safe. Even if it's BIC, there was no BC promise for MTF, so the upgrade can be done provided everything linking to MTF is recompiled. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ 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] file system partitioning meego 1.2
On 3/31/2011 5:04 AM, sam sam wrote: Hi, I would like to know how the file system will be partitioned in MeeGo 1.2 tablet. I beleive file system will be written into both NAND and eMMC unlike MeeGo 1.1 ? it's up to the person doing the preload image how things get partitioned, but I would be highly surprised if people split the filesystem between raw NAND and eMMC. In fact I would be highly surprised if people would use raw NAND at all, it's not performance or cost effective nowadays. ___ 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] tablet user experience source is now open...
Em quinta-feira, 31 de março de 2011, às 15:28:22, Thiago Macieira escreveu: The base API is supposed to be compatible, from what I understand. If it isn't compatible, it's a mistake and should be fixed. To be very clear here: I'm told that compatibility is intended, so divergences are unintentional. Also note that a divergence can be solved by adding the same API in the regular Components API spec if there's need for it. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ 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] tablet user experience source is now open...
On Thu, Mar 31, 2011 at 6:16 AM, Sousou, Imad imad.sou...@intel.com wrote: Hi everyone, Today, we've made available the source code for the tablet user experience project. [] As always, we look forward to your feedback and contributions. Will the development continue only on public repositories? Thanks imad ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ 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] tablet user experience source is now open...
2011/3/31 Leonardo Luiz Padovani da Mata leonar...@syst.com.br: On Thu, Mar 31, 2011 at 6:16 AM, Sousou, Imad imad.sou...@intel.com wrote: Hi everyone, Today, we've made available the source code for the tablet user experience project. [] As always, we look forward to your feedback and contributions. Will the development continue only on public repositories? I think that's pretty clear from http://meego.gitorious.org/meego-ux (look at the news feed) BR Carsten Munk Thanks imad ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ 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] tablet user experience source is now open...
On Thu, Mar 31, 2011 at 11:35 AM, Carsten Munk cars...@maemo.org wrote: 2011/3/31 Leonardo Luiz Padovani da Mata leonar...@syst.com.br: On Thu, Mar 31, 2011 at 6:16 AM, Sousou, Imad imad.sou...@intel.com wrote: Hi everyone, Today, we've made available the source code for the tablet user experience project. [] As always, we look forward to your feedback and contributions. Will the development continue only on public repositories? I think that's pretty clear from http://meego.gitorious.org/meego-ux (look at the news feed) Not at all, the development process of this version happened inside Intel, It's not a teasing question, i really like to know what are the plans for next versions of this UX. Thanks BR Carsten Munk Thanks imad ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ 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] usbmoded?
Hi all, Sorry for the very very late reply. I was waiting for the open sourcing of usb_moded to finally come through. On Fri, 2011-01-21 at 16:12 +0200, Roger Quadros wrote: On 01/11/2011 09:51 AM, ext Patrick Ohly wrote: On Mo, 2011-01-10 at 11:11 +, Luiz Augusto von Dentz wrote: Fine, but what is the situation for usb in meego, currently we depend on com.meego.usb_moded to detect cable plug/unplug, if that hasn't change then it is ok to integrate obexd as it is otherwise it would be nice to have it fixed e.g. by using udev directly. Something that needs to be done for usb_moded also, since the detection is done atm using Nokia internal battery/charging software. I have started working on udev support, but it has not been progressing due to the lack of documentation for udev/libudev (or I missed the useful manual/description) and having to allocate time on other more pressing internal matters. And also not finding a suitable kernel entry/device to check for. I have not found anything yet that will tell me if it is a cable or a charger that is getting connected. HAL can be used too, but that bit is not really nicest and the most flexible code. To be honest it is more a quick hack to get started. (I have re-added support to build with it) And as we all know HAL has been as good as dead since end of 2009... The last thing I heard was that usbmoded is not in MeeGo. Can someone from the architects clarify what the status is around it and what might take its place? Well finally it managed to pass all the legal checks etc within Nokia, so it is now available for use here: https://meego.gitorious.org/meego-middleware/usb_moded It still needs work to be more generically usable though, but most of the Nokia specific things can be compiled out already. Patches, comments and flames are welcome (although the last one a bit less;)). (I plan to add a document explaining the API and functionality soon). Cheers, Philippe ___ 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] usbmoded?
On 3/31/2011 8:06 AM, Philippe De Swert wrote: HAL can be used too, but that bit is not really nicest and the most flexible code. To be honest it is more a quick hack to get started. (I have re-added support to build with it) And as we all know HAL has been as good as dead since end of 2009... HAL is not part of MeeGo and never was.. so that's a non starter ___ 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] tablet user experience source is now open...
-Original Message- From: Leonardo Luiz Padovani da Mata [mailto:leonar...@syst.com.br] Sent: Thursday, March 31, 2011 7:34 AM To: Sousou, Imad Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] tablet user experience source is now open... On Thu, Mar 31, 2011 at 6:16 AM, Sousou, Imad imad.sou...@intel.com wrote: Hi everyone, Today, we've made available the source code for the tablet user experience project. [] As always, we look forward to your feedback and contributions. Will the development continue only on public repositories? Yes, the development will happen in the open repositories from here on out... Thanks imad ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ 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] tablet user experience source is now open...
-Original Message- From: Leonardo Luiz Padovani da Mata [mailto:leonar...@syst.com.br] Sent: Thursday, March 31, 2011 7:43 AM To: Carsten Munk Cc: Sousou, Imad; meego-dev@meego.com Subject: Re: [MeeGo-dev] tablet user experience source is now open... On Thu, Mar 31, 2011 at 11:35 AM, Carsten Munk cars...@maemo.org wrote: 2011/3/31 Leonardo Luiz Padovani da Mata leonar...@syst.com.br: On Thu, Mar 31, 2011 at 6:16 AM, Sousou, Imad imad.sou...@intel.com wrote: Hi everyone, Today, we've made available the source code for the tablet user experience project. [] As always, we look forward to your feedback and contributions. Will the development continue only on public repositories? I think that's pretty clear from http://meego.gitorious.org/meego-ux (look at the news feed) Not at all, the development process of this version happened inside Intel, It's not a teasing question, i really like to know what are the plans for next versions of this UX. Thanks Our plans is to develop this as we did (and doing) the Netbook user experience -- which is to continue the development in the open... BR Carsten Munk Thanks imad ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Leonardo Luiz Padovani da Mata International Syst S/A Metasys Tecnologia Software Engineer Metasys MeeGo Team leonar...@metasys.com.br +55-31-3503-9040 May the force be with you, always Nerd Pride... eu tenho. Voce tem? ___ 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] Customizing Building MeeGo Image on local system
Hi Vyankatesh, You can find an intro into MeeGo OBS here: http://wiki.meego.com/Build_Infrastructure. That won't answer all your questions but some. In response to your questions below: -Can you provide detail step (some Reference URL) regarding how to use OBS Server, bcoz I am new to OBS. The link above and the links branching from there can get you started. I am currently writing 3 whitepapers on OBS that will be published on the Linux Foundation's website some time after the LF Collaboration Summit next week. -Can I install OBS server on Ubuntu as Development platform ? Technically yes but you would have to install all components manually step by step which is quite some work. The best way is to use an OBS appliance which is an openSUSE image with OBS on it and run it in a VM such as VirtualBox on Ubuntu. I am doing that on my box which is Ubuntu. -As you suggested not to build code, but my requirement is I would like to have complete source code of MeeGo alongwith it's build enviornment so that I can customize it at low level (replacing UI, Kernel, middleware) You are working for Bosch Automotive? I understand where you are coming from and why you need that. You can load your OBS with the MeeGo sources and build everything from scratch (well kind of, you have to bootstrap the toolchain). We can take this offline. You will need to setup OBS infrastructure first and get your feet wet with it. -Then build it for other platform (cross-platform) like ARM. Yes, MeeGo OBS has all the necessary toolchain components to build for armv5el and armv7el. BTW, the Linux Foundation offers on-site OBS training (now I probably will get flagged for spamming the mailing list): http://training.linuxfoundation.org/courses/meego/building-meego. Rudi On Thu, Mar 31, 2011 at 5:28 AM, Vyankatesh VD vyankatesh...@in.bosch.comwrote: Carsten Munk carsten@... writes: On Thu Mar 31 2011 11:09:54 AM CEST, Vyankatesh VD Vyankatesh.VD at in.bosch.com wrote: Hi, I want to download source packages of MeeGo and build it on my local machine running Ubuntu operating system.Please provide details of procedure for doing so. do I need to use OBS(open suse build services) for building MeeGo Image.I want to customize MeeGo, I want to remove UI and use my own. Please assist on how to customize MeeGo.After customization I want build it for ARM. Pls provide details. I am very new in Linux, aslo provide URL where to get source code. Hi, You indeed need OBS but I would advise against building complete MeeGo. In most cases you don't need or want to. You need a workflow around these lines: * set up a OBS server for your development work * try to create a image for your target with MeeGo image creator using a kickstart file (.ks) * Remove the package groups the UI consists of, from the .ks file * develop your customizations with OBS, resulting in repositories that you can add with 'repo' lines in the .ks * add your customization package names to %packages section of the .ks * build a new image with your new .ks * enjoy the result (repeat last 4 steps as needed) /Carsten Thanks, Vyankatesh ___ MeeGo-dev mailing list MeeGo-dev at meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev at meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines Hi Carsten, Thank you very much for posting reply to my post. but I have few doubt. -Can you provide detail step (some Reference URL) regarding how to use OBS Server, bcoz I am new to OBS. -Can I install OBS server on Ubuntu as Development platform ? -As you suggested not to build code, but my requirement is I would like to have complete source code of MeeGo alongwith it's build enviornment so that I can customize it at low level (replacing UI, Kernel, middleware) -Then build it for other platform (cross-platform) like ARM. Appreciating your assistance. With Best Regards, Vyankatesh ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- *Rudolf J. Streif* Director of Embedded Solutions The Linux Foundation rudolf.str...@linuxfoundation.org Mobile: +1 858 583 1683 Skype: rudolfstreif Linux Foundation Events Schedule: events.linuxfoundation.org Linux Foundation Training Schedule: training.linuxfoundation.org ___ 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] usbmoded?
Hi Philippe, On Thu, Mar 31, 2011 at 6:06 PM, Philippe De Swert philippe.de-sw...@nokia.com wrote: Hi all, Sorry for the very very late reply. I was waiting for the open sourcing of usb_moded to finally come through. On Fri, 2011-01-21 at 16:12 +0200, Roger Quadros wrote: On 01/11/2011 09:51 AM, ext Patrick Ohly wrote: On Mo, 2011-01-10 at 11:11 +, Luiz Augusto von Dentz wrote: Fine, but what is the situation for usb in meego, currently we depend on com.meego.usb_moded to detect cable plug/unplug, if that hasn't change then it is ok to integrate obexd as it is otherwise it would be nice to have it fixed e.g. by using udev directly. Something that needs to be done for usb_moded also, since the detection is done atm using Nokia internal battery/charging software. I have started working on udev support, but it has not been progressing due to the lack of documentation for udev/libudev (or I missed the useful manual/description) and having to allocate time on other more pressing internal matters. And also not finding a suitable kernel entry/device to check for. I have not found anything yet that will tell me if it is a cable or a charger that is getting connected. HAL can be used too, but that bit is not really nicest and the most flexible code. To be honest it is more a quick hack to get started. (I have re-added support to build with it) And as we all know HAL has been as good as dead since end of 2009... The last thing I heard was that usbmoded is not in MeeGo. Can someone from the architects clarify what the status is around it and what might take its place? Well finally it managed to pass all the legal checks etc within Nokia, so it is now available for use here: https://meego.gitorious.org/meego-middleware/usb_moded It still needs work to be more generically usable though, but most of the Nokia specific things can be compiled out already. Patches, comments and flames are welcome (although the last one a bit less;)). (I plan to add a document explaining the API and functionality soon). Can you take a look at this thread: http://www.mail-archive.com/meego-dev@meego.com/msg07699.html -- Luiz Augusto von Dentz Computer Engineer ___ 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] tablet user experience source is now open...
On 03/31/2011 03:27 AM, Robin Burchell wrote: Hi, On 31 March 2011 11:24, Alberto Mardeganma...@users.sourceforge.net wrote: Is there a mailing list specifically for this project? I don't think so. Admittedly, I've been mostly just using #meego on IRC/gitorious for my work on it so far :) Wouldn't it be in more or less the same boat as accounts SSO? (Start here, spin it off if it gets sufficient volume) Personally I would be fine with using the existing meego development mailing list using some kind of prefix to help sort my inbox. If we end up flooding the list then we can always create a new mailing list. --rusty ___ 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] Customizing Building MeeGo Image on local system
Hi Vyankatesh There is some information on the MeeGo Wiki at http://wiki.meego.com/Build_Infrastructure that you may find somewhat helpful. It is somewhat lacking in specific details, but it may help fill in some of the gaps. In particular, you may be interested in the Packagers/Developers section. If you haven't already, you will want to get access to at least the Community Build Service. Some info on that here: http://wiki.meego.com/Build_Infrastructure/Community_Builder Some info on installing tools, and in particular the OBS command line interface (osc): http://wiki.meego.com/Build_Infrastructure/Packagers_Developers/CLI_Part_1 You will also likely find this useful: http://wiki.meego.com/Image_Creation Hopefully that gives you a little more to get started with. We are always happy to answer questions, too. :) Tracy -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Vyankatesh VD Sent: Thursday, March 31, 2011 5:29 AM To: meego-dev@meego.com Subject: Re: [MeeGo-dev] Customizing Building MeeGo Image on local system Carsten Munk carsten@... writes: On Thu Mar 31 2011 11:09:54 AM CEST, Vyankatesh VD Vyankatesh.VD at in.bosch.com wrote: Hi, I want to download source packages of MeeGo and build it on my local machine running Ubuntu operating system.Please provide details of procedure for doing so. do I need to use OBS(open suse build services) for building MeeGo Image.I want to customize MeeGo, I want to remove UI and use my own. Please assist on how to customize MeeGo.After customization I want build it for ARM. Pls provide details. I am very new in Linux, aslo provide URL where to get source code. Hi, You indeed need OBS but I would advise against building complete MeeGo. In most cases you don't need or want to. You need a workflow around these lines: * set up a OBS server for your development work * try to create a image for your target with MeeGo image creator using a kickstart file (.ks) * Remove the package groups the UI consists of, from the .ks file * develop your customizations with OBS, resulting in repositories that you can add with 'repo' lines in the .ks * add your customization package names to %packages section of the .ks * build a new image with your new .ks * enjoy the result (repeat last 4 steps as needed) /Carsten Thanks, Vyankatesh ___ MeeGo-dev mailing list MeeGo-dev at meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev at meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines Hi Carsten, Thank you very much for posting reply to my post. but I have few doubt. -Can you provide detail step (some Reference URL) regarding how to use OBS Server, bcoz I am new to OBS. -Can I install OBS server on Ubuntu as Development platform ? -As you suggested not to build code, but my requirement is I would like to have complete source code of MeeGo alongwith it's build enviornment so that I can customize it at low level (replacing UI, Kernel, middleware) -Then build it for other platform (cross-platform) like ARM. Appreciating your assistance. With Best Regards, Vyankatesh ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ 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] Meego Bugs Access Denied
-Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Marius Vollmer Sent: Thursday, March 31, 2011 12:08 AM To: ext eric.le-r...@nokia.com Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] Meego Bugs Access Denied ext eric.le-r...@nokia.com eric.le-r...@nokia.com writes: Indeed, file a request so we make the warning more user friendly, thanks. Can't you just do it without having a request filed? These things need to be tracked. Please file a request. Ryan ___ 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] Insights into network flakyness in MeeGo 1.2 Netbook
On Wed, Feb 23, 2011 at 7:42 PM, Niels Mayer nielsma...@gmail.com wrote: https://bugs.meego.com/show_bug.cgi?id=13778 Bug 13778 - Wireless connection loses router setting for Static-IP https://bugs.meego.com/show_bug.cgi?id=13780 Bug 13780 - Wired connection stops working when transferring lots of data Also: https://bugs.meego.com/show_bug.cgi?id=13653 Bug 13653 nor, Medium, 1.3, sameo, ASSI, ConnMan applet disconnect does not disconnect ipv6 https://bugs.meego.com/show_bug.cgi?id=5202 Bug 5202 - Connman deletes the (2nd) static IP while renewing DHCP lease https://bugs.meego.com/show_bug.cgi?id=11083 Bug 11083 - [REG] Ethernet/Wifi is not available in Control Panel https://bugs.meego.com/show_bug.cgi?id=9007 Bug 9007 - [REG]network notification pop up about every 5 minutes https://bugs.meego.com/show_bug.cgi?id=7529 Bug 7529 - [REG]network notification pop up about every 5 minutes etc. Clued by https://bugs.meego.com/show_bug.cgi?id=13778#c34 , I got tired of waiting to see connman 0.71 in the images, so googled for an RPM and found http://download.meego.com/live/devel:/connectivity:/latest/Trunk/i586/ Here's how I installed it and a few potential dependencies (?). $ sudo zypper ar http://download.meego.com/live/devel:/connectivity:/latest/Trunk meego-latest-connectivity Adding repository 'meego-latest-connectivity' [done] Repository 'meego-latest-connectivity' successfully added Enabled: Yes Autorefresh: No URI: http://download.meego.com/live/devel:/connectivity:/latest/Trunk/i586/ $ ##following needed only if you've done, e.g., 'sudo zypper mr --priority 2 oss' $ sudo zypper mr --priority 1 meego-latest-connectivity $ sudo zypper clean --all $ sudo zypper --gpg-auto-import-keys --no-gpg-checks refresh $ zypper up bluez bluez-libs connman connman-test ofono ofono-test The above update installs connman-0.72-1.1.i586 connman-test-0.72-1.1.i586 bluez-4.91.23.g6f7add5-1.1.i586 bluez-libs-4.91.23.g6f7add5-1.1.i586 ofono-0.45.134.gb2e3a47-1.1.i586 ofono-test-0.45.134.gb2e3a47-1.1.i586. At least connman-0.72 seems to fix a lot of problems with the networking -- I can actually use the wired network for the first time since I installed 1.2. My issues with static IP on both wired and wireless ipv4 networks seems to have been mostly resolved. I'm still seeing the wired connection disconnect from the local network after several hours, even though it can route to the internet. The GUI connection manager lists the subnet mask as being 255.255.255.255 in this condition. When it's corrected back to a /24 netmask, it'll either be uncorrectable until next reboot, or it manages to reconnect and just works. The original problem in connman 0.69 (in *all* meego 1.2 netbook/tablet releases) of garbage text (as if memory error) showing up in the static IP Router field doesn't happen anymore. Nor do some of the other disconnections and connection manager errors I've been experiencing. Unfortunately, even the latest release still includes the buggy connman 0.69: http://repo.meego.com/MeeGo/builds/1.1.90/1.1.99.0.20110330.3/repos/oss/ia32/packages/i586/ With the updated connman, a suspend/resume cycle (e.g. closing lid on lenovo s10-3t) allows the wired network to almos survive At least the workaround to accidentally closing the cover doesn't mean rebooting ... It only requires correcting the subnet mask field back to 255.255.255.0 from 255.255.255.255 ... The same thing seems to be required on each boot, requiring the network mask to be corrected from .255 to .0 . --- Any suggestions on keeping this fixed to the correct value?? Attempting to fix the easy way aka: $ sudo zypper in http://download.meego.com/live/devel:/ux:/netbook/Trunk/i586/meego-panel-networks-1.3.2-33.1.i586.rpm ... didn't fix the netmask resetting problem on suspend or reboot (not sure why it would, but wanted to replace as much of the buggy networking stuff w/ fixes). -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Bugzilla changes for tablet user experience open sourcing
Hi everyone, MeeGo Bugzilla (https://bugs.meego.com) has been changed to align with MeeGo Tablet User Experience open source. In addition, we take this chance enhanced some bug fields' definition. Here are the change details: 1. One new product MeeGo User Experience has been created for QML based Tablet User Experience bug reporting. Here is the new bug quick link to this product (https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20User%20Experience); 2. Old Platform is renamed to Profile. This is to make the field name more meaningful to reflect the value list Handset, Tablet etc belong to; 3. New field Platform is created to record hardware platform information in bug report. Welcome your feedbacks and suggestions! Thanks Shuang ___ 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] Bugzilla changes for tablet user experience open sourcing
On Thursday, March 31, 2011 09:06:51 pm Wan, Shuang wrote: MeeGo Bugzilla (https://bugs.meego.com) has been changed to align with MeeGo Tablet User Experience open source. Thank you! -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
