Re: ncurses-base for OS 2008 (n800)
Hi, ext Jaeyeon Jung wrote: Awesome! Thank you very much Andrew. Simple two steps fixed the problem. 1. uninstall nano that I had on my n800 2. add the Chinook repository and apt-get install nano On Jan 4, 2008 3:31 PM, Andrew Godwin [EMAIL PROTECTED] wrote: ncurses-base itself is in the main repositories now (well, I have nano installed on OS2008, and I certainly didn't port it this time). I think the appropriate catalogue is 'Maemo Chinook': web addr: http://repository.maemo.org/ distrib: chinook components: free non-free Let me know if that's the one; if not, I'll have to track down where it actually comes from. ncurses-base is a Debian essentials package (meaning: Debian/Ubuntu package don't declare dependency to it although they use it), so I think it would be appropriate if it would be on the device in future releases. If somebody wants to make a bug about this, please put me on CC. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Fwd: CFP for embedded room at FOSDEM
woops forgot the list again... -- Forwarded message -- From: nick loeve [EMAIL PROTECTED] Date: Jan 7, 2008 10:53 AM Subject: Re: CFP for embedded room at FOSDEM To: Kees Jongenburger [EMAIL PROTECTED] On Jan 6, 2008 6:53 PM, Kees Jongenburger [EMAIL PROTECTED] wrote: On Dec 17, 2007 3:27 PM, Philippe De Swert [EMAIL PROTECTED] wrote: Hi, This might be of interest to developers in the Free Software/Open Source world. FOSDEM is looking for speakers for the embedded track again. Anyone who thinks he/she has somebody interesting to share with other embedded developers please take a look at the call for papers. Hi What about maemo and FOSDEM. I would like to talk about maemo and meet other maemo hackers. I don't have many ideas about what would be interesting presentation because I don't fully gasp the gome/maemo relationship. but given some diirection I am not scarred to pressent anything . Did anybody apply for a talk or stand at maemo? Just showing the nokia + canola + efl + mamona would already be a very sexy presenation IMHO. Could be a good lightning talk... http://fosdem.org/2008/lightningtalks greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Nick Loeve www.trickie.org -- Nick Loeve www.trickie.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Announcement: OS2008 2.2007.50-2 source repository
On Monday 07 January 2008 06:11:49 Terje Bergström wrote: For the next version we are designing a new repository structure that will accomodate SDK, SDK sources, firmware sources, updates to firmware sources, and updates to SDK in a uniform way. One thing to bear in mind for the new repository structure: once you release a shipped version of the OS, and its respective SDK, make sure that it is always possible to build applications that will still install for a user who has not updated from that release. The issue is that if release 200X.0 has version A of a particular library, and release 200X.1 has version B of a library, then applications built against the SDK for version 200X.1 will have dependencies of the form libwhatever = B and will not install on 200X.0. To my mind there are two solutions to this: 1) Never update any SDK for a released version (beta test versions are not a problem). Once the chinook SDK is released it always remains the same. If an update to the SDK is needed a new codename is created and a complete new SDK released. That way, the developer has an easy way to control which SDK they are building with. 2) Allow installing packages to upgrade the Nokia-supplied libraries transparently, without user involvement. In the case of my example above, a user with 200X.0 installed who installs my application built against 200X.1 ends up with version B of the library (and, of course, ends up with a system which is part way between 200X.0 and 200X.1 as a result). Nokia could even decide to combine these two. You could make the Application Manager refuse to upgrade certain packages (for example packages marked essential or something) but be willing to upgrade others (for example libraries to do with the camera or GPS for example). Then you would only need to create a new SDK, with a new name, if you had a new version of one of the non-upgradeable libraries. There is a third option: make the process of upgrading the tablet so easy (risk free, and fairly fast) that people will always be able to come up to the latest version with no hassle. That has the advantage for developers that we can just build with the latest stuff and when a user complains it won't install we just tell them update to the latest OS. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Announcement: OS2008 2.2007.50-2 source repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Graham Cobb wrote: To my mind there are two solutions to this: There is a third option: make the process of upgrading the tablet so easy The fourth option would be to assure the shlibs -files of said libraries always contained at most the version of the first release. To do this, however, it is not enough to keep ABI compatibility, but you cannot introduce any new functions either -- or then you need to create a better shlibs-system. ;) - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFHggWGX9Rc0+po4p0RAiv3AJdiWskVT/zMYPHo6N2KWaDWRZ94AJ9PCLEV FfPEZ7IrC4jRrKCmuq5jqg== =au3U -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build Evince on Maemo
On Fri, 2008-01-04 at 14:10 -0800, ext Albert Hosin wrote: Hi, I am trying to build latest Evince on Maemo. Much appreciated if any one can point me somewhere. Or if you have already built it, would you share the process that you did and the difficulities that you met. Thanks. Which version do you work with? I manage to build evince 2.21.1 yesterday with all possible backends. Didn't run it on the device and didn't hildonize it yet. Should we open a project for it on garage? -- Ed Bartosh [EMAIL PROTECTED] Nokia-M/Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: bsddb module for maemo-python ?
Hi Fred, We had somebody asking for this[1] on PyMaemo mailing list. The main reason for bsddb module's absence is that Maemo platform doesn't provide bsddb support. Regards, Luciano [1] https://garage.maemo.org/pipermail/pymaemo-developers/2007-March/21.html ext Fred Pacquier wrote: Hi, Does anyone have the bsddb module for maemo-python, or know where to find it ? I don't know why it's been excluded from the maemo distribution : it's not that big, and its absence means some existing software cannot be reused easily on the tablets - like the very interesting Gluon: http://mdp.cti.depaul.edu/ It should at least be available in the dev package, or as a separate download, but I don't see it anywhere, even in Red Pill Mode. Thanks for any pointers, fp ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: python2.5 - unnecessary multiple processes forked
Hi, ext Jayesh Salvi wrote: On 1/3/08, Jayesh Salvi [EMAIL PROTECTED] wrote: Thanks for all the info. I am planning to run the FileChooserDialog in a different process than my rest of the app. That may sound weird, but it fits my application's context alright. My pygtk app will run as a service, so that it can be invoked by other applications as well. FileChooserDialog is just one entry point into my app. Detail of my app if you are interested: It is a pygtk GUI that lets you upload images to Flickr or Picasaweb. I have already published the code as Gimp, Inkscape pluginshttp://code.google.com/p/altcanvas/wiki/GimpPublishr. Now I am putting the same code on maemo. I will soon release a .deb file once I iron out some wrinkles. I found out that the sluggishness observed was because of the Microb engine. Last night when I tried by switching to Opera engine, it worked very fast. So it's not the multiple threads that hildon or GTK fork, that cause performance issues. You could also try disabling Flash from the Browser to see whether it helps. - Eero Thanks, Jayesh On 1/2/08, Eero Tamminen [EMAIL PROTECTED] wrote: Hi, ext Jayesh Salvi wrote: I'm not sure but think it is because of gnome-vfs. Don't know proper terminology but maybe each vfs 'provider' in the dialog (like mmc, phone etc.) starts new process or something like that. That sounds correct. I experimented with other dialogs that do no involve filesystem access (NamePasswordDialog, SortDialog), and they do not fork any extra processes. They are not processes, but gnome-vfs worker threads (you don't want the UI to freeze e.g. until network timeouts). So this behavior seems valid for FileChooserDialog. But then I should be able to cleanup those extra processes when I am done with the FileChooserDialog. I called destroy() on the dialog object, but that doesn't help. They remain in the gnome-vfs thread pool even after the UI component is destroyed. The memory usage issue is elsewhere. You could look into your program Private_Dirty memory usage in /proc/PID/smaps file. Or run the same program on your PC under Valgrind Massif plugin: http://maemo.org/development/tools/doc/valgrind http://valgrind.org/docs/manual/ms-manual.html I'm not sure how well that tells about issues in Python code. Is there any memory profiler for Python applications? - Eero -- --- Jayesh ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: [maemo-users] 'Locking down' software installation
Hi, I want to start this thread again from the long past discussion on lock-down meta-package. At that time, the discussion was mostly centered around system upgrade using the meta-package. The 'locking-down' part wasn't so much discussed and I believe we need to rethink that portion. While preparing for rtcomm software update release, it came to my attention that there is the said meta-package osso-software-version package that completely 'nails' the system packages to fixed versions. This has created the very obvious problem of not being able to update any of those packages, such as during the recent rtcomm dev update 2 (in red-pill mode, of course). We had to remove the package from the device to make it work. This, of course, means that the user is not going to see any future OS updates coming through that meta package [1]. If the purpose of the package is just to deliver future updates bound under a single meta-package, why isn't the dependency versions set with 'equal-to-or-greater-than'? If the purpose of the package is *also* to prevent the user from screwing his device by installing some 3rd party updates, isn't that already taken care by red/blue pill modes? Then this package is redundant in protecting the user's device. Even in red-pill mode, this package doesn't prevent anything because the installing package can simply remove it and go happy. Here are three things about that: 1) As claimed by the original mail from Marius, the 'red-pill' does not really override this lock-down. The meta-package needs to be hackishly removed or 'replaced' regardless of whatever pill mode. Is there any other way? 2) The lock down of those packages already taken care by 'blue-pill' mode so no need to lock-down versions. 3) It creates a bad situation for every 3rd party to compete in overthrowing the locking meta-package, like mentioned in [1]. So I believe we should fix that meta-package to take '=' and not '=='. Comments? Thanks. Regards, -Naba [1] Of course, there is another dirty way of coming around it -- Prepare another micro-build-incremented update of osso-software-version package (with corrected dependencies, of course) and replace the existing one. This preserves the user device for getting OS updates later. But, seriously, why all these hops? This is how current rtcomm update 2 is supplied. Marius Vollmer wrote: Hi, we are planning to put some features into the Application Manager that will make it more restrictive when handling the packages that make up the operating system itself (as opposed to third party applications). We would like to get your feedback on these plans, both from the end-user point of view and from the point of view of package developers. In the future, we hope to be able to provide official updates to the operating system itself via packages, and we need to give the end-users the confidence that when they intend to install a Nokia provided operating system update, they actually get what they think they are getting. As for the concrete plan: There is going to be a 'meta' package that represents the whole operating system. Updates to the OS are done by updating this meta package in the Application Manager. The meta package will have dependencies on all packages with their exact versions that make up the official OS releases. The Application Manager will not allow the removal of the meta package. This means that the Application Manager will not allow you to update individual OS packages (or to install third party applications that require this), since you would have to remove the meta package for that. It is still possible to install additional 'system' packages, just not to upgrade already installed ones. A second new feature is that the Application Manager will distinguish between trusted sources and non-trusted sources (based on the key used to sign the corresponding repository). A package that has originally been installed from a trusted source will only be allowed to be updated (or replaced) from a trusted source. The flash image is also treated as a trusted source, so you will only be able to update packages that are pre-installed in the device from trusted sources. This makes it easier for the user to be sure that he doesn't pick up unwanted system software updates by accident. The set of trusted sources will be under control of a power-user: you can just add some GPG keys to the right place, but there is no UI to do it. You can also switch the whole lock-down machinery off by going to red-pill mode. So whaddaya think? Useful? Too painful? Too difficult to escape from? Some variants that come to mind: The meta package could depend on 'this version or later' of a package instead of on exactly this version'. That would allow it to control the update just as much, but would not lock down the configuration of the device so much. The motivation for this lock-down of the
Re: Build Evince on Maemo
Hi, On Jan 4, 2008 7:10 PM, Albert Hosin [EMAIL PROTECTED] wrote: Hi, I am trying to build latest Evince on Maemo. Much appreciated if any one can point me somewhere. Or if you have already built it, would you share the process that you did and the difficulities that you met. Thanks. It will depend on your needs. If you're aiming to read PDF files only, you'll need to build poppler[1] as well. For PS it was just introduced the libspectre[2] dependency for Evince instead of the gs binary. To build Evince itself you need to adjust the configure flags: --without-libgnome will definitely be necessary. Best Regards, Etrunko. [1] http://poppler.freedesktop.org [2] http://libspectre.freedesktop.org -- Eduardo de Barros Lima INdT - Instituto Nokia de Tecnologia [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build Evince on Maemo
On Jan 7, 2008 8:41 AM, Ed Bartosh [EMAIL PROTECTED] wrote: Should we open a project for it on garage? I don't think it is necessary to do so. There is already a bug[1] in GNOME bugzilla regarding the Maemo/Hildon patch. Unfortunately it is quite outdated, but I think we should host it there. Best Regards, Etrunko. -- Eduardo de Barros Lima INdT - Instituto Nokia de Tecnologia [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build Evince on Maemo
On Jan 7, 2008 11:20 AM, Eduardo Lima (Etrunko) [EMAIL PROTECTED] wrote: I don't think it is necessary to do so. There is already a bug[1] in GNOME bugzilla regarding the Maemo/Hildon patch. Unfortunately it is quite outdated, but I think we should host it there. Best Regards, Etrunko. And the link: http://bugzilla.gnome.org/show_bug.cgi?id=324644 -- Eduardo de Barros Lima INdT - Instituto Nokia de Tecnologia [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build Evince on Maemo
Thank you , ED. I am using version 2.21 too. But it got the following error while it was running ./configure checking for LIB... configure: error: Package requirements (gtk+-2.0 = 2.8.15 libgnomeui-2.0 = 2.14.0 libxml-2.0 = 2.5.0) were not met: No package 'libgnomeui-2.0' found Did you need to modify config flags for libgnome as mentioned by Eduardo in his previous mail: To build Evince itself you need to adjust the configure flags: without-libgnome will definitely be necessary. Best Regards, Etrunko. But I don't want to use Hildon right now. Do you know what was the problem? Thanks! Albert - Original Message From: Ed Bartosh [EMAIL PROTECTED] To: ext Albert Hosin [EMAIL PROTECTED] Cc: maemo-developers@maemo.org Sent: Monday, January 7, 2008 6:41:44 AM Subject: Re: Build Evince on Maemo On Fri, 2008-01-04 at 14:10 -0800, ext Albert Hosin wrote: Hi, I am trying to build latest Evince on Maemo. Much appreciated if any one can point me somewhere. Or if you have already built it, would you share the process that you did and the difficulities that you met. Thanks. Which version do you work with? I manage to build evince 2.21.1 yesterday with all possible backends. Didn't run it on the device and didn't hildonize it yet. Should we open a project for it on garage? -- Ed Bartosh [EMAIL PROTECTED] Nokia-M/Helsinki Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
Hi, Ditto. I just tried, and used the shop link given in the Nokia mail. Code invalid. Both new and old, in fact. Same here. Too bad. Regards, Hanno ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
Hanno Zulla wrote: Same here. Too bad. Yeah, it's still non-working for me, too. Given that the mail suggests we talk to the shop team instead of the Maemo team at this point (I assume they've given up on poking them out of frustration ;-), I guess we have to start calling that 14ct/minute support hotline to try and build up an awareness there. Regards, Hanno -- Regards, Eike Hein, [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eike Hein escreveu: Hanno Zulla wrote: Same here. Too bad. Yeah, it's still non-working for me, too. Given that the mail suggests we talk to the shop team instead of the Maemo team at this point (I assume they've given up on poking them out of frustration ;-), I guess we have to start calling that 14ct/minute support hotline to try and build up an awareness there. One thing that's worrying me is that the email says the code will be valid until the end of february and the US store won't have the N810 in stock until the middle of february (16th IIRC) which creates a narrow window if we have to compete with all the people who wants the device in US. I could have chosen a number of different stores around the world but, as Murphy dictates, I made the worse possible choice... :( []s Adilson. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHglNm2cB5Bt7H7YARArieAKCbnNEBAQuOjq0rMaUa9HG/wEhlOACdHuak 5dCel4+8AzgRANRsNptZAE0= =C0de -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
Adilson Oliveira wrote: One thing that's worrying me is that the email says the code will be valid until the end of february and the US store won't have the N810 in stock until the middle of february (16th IIRC) which creates a narrow window if we have to compete with all the people who wants the device in US. I might be the wide-eyed optimistic here, but I guess I wouldn't worry about that. It would be rather embarass- ing for Nokia, not to mention unfair, if they don't find a way to get devices into the hands of US developers in the event that you can't order in time because the de- vices aren't in stock. I'd expect the Maemo team to root for those who'd fall victim to that anyway, since rewar- ding and motivating developers is the whole point of the discount program in the first place. As for Germany, the device is currently reported as in stock in the shop, and has been for the whole of Christ- mas and New Year. The codes don't work independently of that. Adilson. -- Regards, Eike Hein, [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eike Hein escreveu: I might be the wide-eyed optimistic here, but I guess I wouldn't worry about that. It would be rather embarass- ing for Nokia, not to mention unfair, if they don't find a way to get devices into the hands of US developers in the event that you can't order in time because the de- vices aren't in stock. I'd expect the Maemo team to root for those who'd fall victim to that anyway, since rewar- ding and motivating developers is the whole point of the discount program in the first place. I hope so as I just checked the website again and it says 19 and not 16 as I wrote before :( As for Germany, the device is currently reported as in stock in the shop, and has been for the whole of Christ- mas and New Year. The codes don't work independently of that. That's awful. []s Adilson. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgldy2cB5Bt7H7YARAraLAJ0fW9I5d132LLXNgCIW9hKGU8EzRgCfVzL5 4nPVASvNi29qdeh/jLahHOc= =I4Ll -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build Evince on Maemo
On Mon, 2008-01-07 at 11:20 -0300, ext Eduardo Lima (Etrunko) wrote: On Jan 7, 2008 8:41 AM, Ed Bartosh [EMAIL PROTECTED] wrote: Should we open a project for it on garage? I don't think it is necessary to do so. There is already a bug[1] in GNOME bugzilla regarding the Maemo/Hildon patch. Unfortunately it is quite outdated, but I think we should host it there. Are you suggesting to just maintain a patch in GNOME bugzilla instead of open a project on garage? From my point of view having project on garage is a bit more than just that. It's also the place for history of your changes, request tracker, news and so on, so it's more convenient for users. What do you think about this? -- Ed Bartosh [EMAIL PROTECTED] Nokia-M/Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Eike Hein schrieb: Given that the mail suggests we talk to the shop team instead of the Maemo team at this point (I assume they've given up on poking them out of frustration ;-), I guess we have to start calling that 14ct/minute support hotline to try and build up an awareness there. I just did and gave up after 22 minutes. That is getting too expensive! BTW if you want to waste your money too, this is the number which is not /that/ easily found on their site: 01805-258266542 Tilman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHgl3n9ZPu6Yae8lkRAugAAJ4gVsuqdCfxAa7rmyu9E6otTmCFqwCgpqQY b6ExVWi2b0+HQY7PPrDbiyM= =XS0I -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Build Evince on Maemo
Hi, On Jan 7, 2008 1:47 PM, Ed Bartosh [EMAIL PROTECTED] wrote: On Mon, 2008-01-07 at 11:20 -0300, ext Eduardo Lima (Etrunko) wrote: Are you suggesting to just maintain a patch in GNOME bugzilla instead of open a project on garage? Kind of... The goal is to integrate the Maemo/Hildon patch to Evince source tree, just as it was done before for Abiword and Gnumeric for instance. So, GNOME bugzilla is the right place for that. From my point of view having project on garage is a bit more than just that. It's also the place for history of your changes, request tracker, news and so on, so it's more convenient for users. What do you think about this? What I wouldn't want was to maintain a separate source tree for Evince. Once the patch is officially integrated to the tree it would become useless. Best Regards, Etrunko. -- Eduardo de Barros Lima INdT - Instituto Nokia de Tecnologia [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
Tilman Vogel wrote: I just did and gave up after 22 minutes. That is getting too expensive! Since the support hotline won't pick up, I've written them using the contact form asking when they expect the German codes to be come active. I've included links to the Maemo announcement and so on, since I expect that the support personnel will not necessarily be aware that there's a dis- count program going on and this way they might at least ask someone higher up in the chain (who might then remember he had to enter some codes somewhere ...). -- Regards, Eike Hein, [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Undoing a gtk_widget_tap_and_hold_setup()
Hi all, is there any way to undo a gtk_widget_tap_and_hold_setup? I mean, at some point, I don't want a button that had a tap and hold menu to show it. I tried a tap_and_hold_setup passing a NULL argument to unset it but it didn't work. Thanks -- Alberto García González http://people.igalia.com/berto/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
developer program discount code does not work
Three days ago I received a message that I have until February to use my developer program discount code for the N810. Strangely enough it was actually a different discount code than the one I had received before. And neither one is working. Possibly because I don't want to have it sent to my address in Italy (I'm moving to the Netherlands next week and receiving packages in Italy is far from ideal). Who should I contact? Or should I just wait a bit and try again later? cheers, Kasper -- http://guaka.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: developer program discount code does not work
Hi, 2008/1/7, Kasper Souren [EMAIL PROTECTED]: Three days ago I received a message that I have until February to use my developer program discount code for the N810. Strangely enough it was actually a different discount code than the one I had received before. And neither one is working. Possibly because I don't want to have it sent to my address in Italy (I'm moving to the Netherlands next week and receiving packages in Italy is far from ideal). Who should I contact? Or should I just wait a bit and try again later? when you signed the form, you had to choose the country where you would have bought it. If you did choose Italy, the code is valid only for italian shop. -- Andrea Grandi email: a.grandi [AT] gmail [DOT] com website: http://www.ptlug.org PGP Key: http://www.ptlug.org/andreagrandi.asc ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Whats the purpose of libegg
On 06/01/2008, Bin Chen [EMAIL PROTECTED] wrote: I searched the internet for libegg and found some tips but still can't got whats libegg working for? Is it another useful widget lib? After I check out the libegg and catch the README: - All features are intended to end up in a stable platform library when they're ready. Whats the meaning? My understanding is that libegg is for code that is useful enough to be shared, but experimental enough to exclude it from a package like GTK or GLib that promises API stability. Eventually, as consensus forms about its design and implementation, the code gets migrated to the appropriate package, but in the meantime, you just copy and paste libegg code into your source. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: CFP for embedded room at FOSDEM
Just showing the nokia + canola + efl + mamona would already be a very sexy presentation IMHO. Could be a good lightning talk... http://fosdem.org/2008/lightningtalks Done, lets hope they like it.. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Suggestions for storing data for Python based Maemo application
Hi all, We are developing an application for Maemo which is if you like a custom data collection application for a local firm. The application is being written in Python 2.5 against the Chinook framework and is expected to create upto about 200 records (all up). Are there any general suggestion for what we should use to store data? At this stage thoughts/options are - Python object serialization - XML file - SQLite database Thanks for your time. -- I never look back darling, it distracts from the now, Edna Mode (The Incredibles) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eike Hein schrieb: Since the support hotline won't pick up, I've written them using the contact form asking when they expect the German codes to be come active. I've included links to the Maemo announcement and so on, since I expect that the support personnel will not necessarily be aware that there's a dis- count program going on and this way they might at least ask someone higher up in the chain (who might then remember he had to enter some codes somewhere ...). Good luck, I wrote them a few weeks ago and again when the now active mail came, but never got any reply. I am not sure that this contact form is not just going to /dev/null. Please let us know if you get any reply! Thanks, Tilman -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHgqf49ZPu6Yae8lkRAqVsAJ0Rh15b0xDmU3/XaOFFvy+p1fRgkACdHST8 m039tfmkl8uq8X9MBP4bPeo= =Zf/N -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
Did someone considered to write a mail to Quim Gil? Perhaps he can make them take a notice of the problem. Greetz, Massimo Mund ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Contribution code, ...
Massimo Mund wrote: Did someone considered to write a mail to Quim Gil? Perhaps he can make them take a notice of the problem. Well, first of I expect Quim to read this list in any case, and second the mail did state that we should talk to the shops directly at this point. Greetz, Massimo Mund -- Regards, Eike Hein, [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Maemo Program/USA Store
Nokia Folks, I would really appreciate some kind of response or information from Nokia for the folks in the US. The recent N810 maemo program instructions email was not clear about us and I am concerned that with what appears to be poor device availability and poor Nokia to developer community communication that I may loose my chance at getting a device and thus being able to contribute to the platform. My project idea _really_ needs a real device for development. Sadly, I feel something is broken in this process and is making things needlessly confused and frustrating. I sincerely hope for everyone involved that things get better shortly as I am struggling to continue to be excited about the platform with the way things are going. -- John P. Mitchell [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: developer program discount code does not work
2008/1/7, Andrea Grandi [EMAIL PROTECTED]: Hi, 2008/1/7, Kasper Souren [EMAIL PROTECTED]: Three days ago I received a message that I have until February to use my developer program discount code for the N810. Strangely enough it was actually a different discount code than the one I had received before. And neither one is working. Possibly because I don't want to have it sent to my address in Italy (I'm moving to the Netherlands next week and receiving packages in Italy is far from ideal). Who should I contact? Or should I just wait a bit and try again later? when you signed the form, you had to choose the country where you would have bought it. If you did choose Italy, the code is valid only for italian shop. I have received too a different code in last email from nokia. I have used that code in the italian nokia shop without problems and I'm currently waiting my n810. I stated of course my preference for the italian shop formerly. Cheers, roberto. Andrea Grandi email: a.grandi [AT] gmail [DOT] com website: http://www.ptlug.org PGP Key: http://www.ptlug.org/andreagrandi.asc ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
