Nokia has published a demo application for N900, available in extras-devel repository, that shows a preview of Maemo 6 (Harmattan) user interface. Here there are some screenshots of the demo:
Demo application main window
Question dialog
Text entry dialog
Progress indicator
Information banner
Event banner
You can find more pictures in my Flickr album. Please note that installing this demo will also install Qt 4.6.2 on the N900 and about 52 Mb are required.
Being one of the developers who received the discount to buy a N900, during these days I contacted the DDP customer care to have more informations and details. I'll publish here both my original question and the official reply.
1) The price of N900 is 250€ and I've read of people who paid it this price. Anyway here you say that the VAT is not included:
https://pro.forum.nokia.com/site/global/tech_resources/discounted_devices/l_ddp.jsp
so it should costs 300€ not 250€, right?
The VAT applies only for Finnish developers, for the others the price is the price they see in the eStore, no VAT is added to that.
So, all non-finnish european people, will pay 250€ for the N900.
2) How much time can I wait before ordering it? In this moment I'm in Valencia (Spain) and I won't come back to Italy before Christmas. I'd like the order to be shipped to my home in Italy (I registered as italian user and I want italian keyboard layout), but I'd like to wait to order it, because since there's no warranty and I need to tell you about any problem within a week, if I order it now I will be able to check it only at the end of december when I'll come back to Italy.
I guess this should not be a problem.
This part is not confirmed yet, since Quim told us to hurry up to buy it.
3) How many devices can I buy at that price? Here you say I can buy two:
https://pro.forum.nokia.com/site/global/tech_resources/discounted_devices/l_ddp.jsp
but here you say I can buy one: https://pro.forum.nokia.com/showProduct.do?product_id=5096
I don't want two devices, but another friend of mine, who help me in a project for the Maemo Community, would like to be able to buy one for the same price (he wasn't able to get the discount because his karma is still low).
As far as I know, you can only purchase 1x device per person, regarding MAEMO N900.
4) Where can we find the new firmware? In the FAQ you say: DDP does not flash devices. It's ok, I can do it, but there's no public firmware for N900 at the moment.
To update N900, can possibly be using NSU. Nokia software updater.
5) Is it possible to have a device with localized keyboard (for example italian one) ?
All N900 will have EURO variant, Italian language is one option.
Note: even these replies come from the official customer care, I don't assume any responsability if they shouldn't be all exact. If you have any doubt, please contact them directly at DDP.program@nokia.com
Quim Gil just confirmed the UX hackfest in Barcelona for 4, 5, 6 december: http://talk.maemo.org/showthread.php?t=33719
What is UX hackfest?
It's a three days meeting for Maemo developers, UX experts and people who want to learn about designing good user interfaces.
When?
On 4, 5, 6 december 2009
Where?
Barcelona, Spain. The exact location has still to be confirmed, but it should be http://citilab.eu
How many people invited?
About 50 people invited (Maemo developers, UX experts, ecc....)
If you are a Maemo developer and you have good user interface designer skills, this is the place for you.
If you are a Maemo developer and you are not a UX expert, this IS anyway the place for you: you'll have the possibility to talk with experts and improve your knowledge about UI design.
Anyone interested, please join the discussion here: http://talk.maemo.org/showthread.php?t=33719
Update 3/11/2009 - 16:00: a wiki page with all information has been created here: http://wiki.maemo.org/Maemo-Barcelona_Long_Weekend
please add your name/data to the page if you requested to join the UX hackfest.
During next Maemo Summit we will have at least 2 hours (one on saturday and another one on sunday) of lightning talks, about 20 talks where people will try to explain or present something in just 5 minutes.
Last year, during Maemo Summit 2008, I did a lightning talk too and I must admit: even if I knew a lot about the subject of my talk and even if I had already done many other talks, I think it wasn't so good as I expected.
This year I've been selected again (more details will follow) to give a 5 minutes talk and with this great news the kind Dave Neary also suggested me a link with an article about some best practices when giving lightning talks. I'll try to resume the most important points, hoping this will be useful for people who is going to give a short presentation at Summit.
Go straight to the point: five minutes finish sooner than you can expect. You have to talk about the main topic of your talk within the two first minutes, else you risk to talk too much about the rest and you couldn't have the time for the most important thing.
Leave details away: people will never remember too many details explained in so little time. It's better to leave them away and put them in a more detailed blog post that you can link within your slides.
Slides: for a five minute talk you can avoid preparing slides, but if this can help you to concentrate on points you have to talk about, please prepare them. Two or three slides can be useful to introduce yourself, to write any reference of what you're talking about many other things. Another important thing, make sure your slides are ready before starting your presentation: people don't want to wait 20-30 seconds it takes to start Open Office or any other similar application.
Consider any eventuality: the presentation file could be damaged (be sure to have a copy of it, better in PDF format), your laptop could have no more battery (make sure you've a copy of your slides in a USB key), aliens could take you away, ecc... (ok, this last eventuality is remote).
Concluding your talk: don't worry if you finish one or two minutes before, people won't bother about it. It's better to finish one minute before than 30 seconds later. If you want to leave an URL where people can find more details, how to contact you, put it in every slide so people will be able to take note of it from the first minute.
I hope to have resumed the most important points of the original article. If you think there are any other important things to say, please leave me a comment and I'll add them. I really hope you will enjoy Maemo Summit and its lightning talks!
In the last post of this series, we saw how to write a simple binding and we finished to build and install it manually. This is of course not a good way to manage the building/installation procedure.
In Python we can use a library called distutils that let us to automatize the building and installing process. I'll use the foo source code to create the package, so it will be easier to understand.
All we have to do is to write a setup.py file similar to this one:
from distutils.core import setup, Extension
foomodule = Extension('foo', sources = ['foo.c'])
setup (name = 'Foo',
version = '1.0',
description = 'This is a package for Foo',
ext_modules = [foomodule])
As you can see, we have to first import needed modules with: from distutils.core import setup, Extension
then we create an entry for each module we have (in this case just one, "foomodule"). We then call the setup() method passing it all the parameters and our setup.py is complete.
To test it we can try to build the package in this way:
python2.5 setup.py build
if we want to install the module in our system:
python2.5 setup.py install
The PyMaemo team is pleased to announce the second beta release of PyMaemo for Fremantle!
This new release is available through the extras-devel repository, see installation instructions in
http://pymaemo.garage.maemo.org/sdk_installation.html#fremantle
Python for Maemo (PyMaemo for short) main objective is to make possible to use Python programming language as the scripting and development language for Maemo Platform, providing a better alternative for fast prototyping and programming in Maemo environment besides the C programming language.
Python is for serious programming and to have fun. Python has a nice syntax, it is easy to learn and powerful enough for a vast range of applications, this is why we choose Python for Maemo.
New packages:
Updated packages:
Bugs fixed: MB#4530 [3], MB#4450 [4], MB#4629 [5], MB#4628 [6],
MB#4647 [7], MB#4632 [8], MB#4646 [9], MB#4750 [10], MB#4749 [11],
MB#4791 [12]
MB#4782 [13]: osso.Context causes segmentation fault
MB#4821 [14]: Cannot create HildonTouchSelector with single text column
MB#4824 [15]: python-mafw: source_browsing.py example does not work
MB#4839 [16]: python-mafw: mafw.Registry lacks list_plugins() method
MB#4849 [17]: python-mafw: MafwPluginDescriptorPublic structure is missing
We will not migrate to python2.6 in fremantle due to a (unresolved) bug (MB#4734 [18]), where a core SDK package explicitly conflicts with python >= 2.6, preventing any further upgrades from the 2.5.x series.
This release is supposed to be compatible with previous releases. If you have any issues regarding building your Python application on Fremantle, feel free to report it on the pymaemo-developers mailing list [19].
Thanks to everybody who helped making this release possible.
Bug reports, as always, should go to our Bugzilla [20]. Use the pymaemo-developers mailing list for help, feedback or suggestions.
[1] https://garage.maemo.org/projects/mafw/
[2] http://www.clutter-project.org/
[3] https://bugs.maemo.org/show_bug.cgi?id=4530
[4] https://bugs.maemo.org/show_bug.cgi?id=4450
[5] https://bugs.maemo.org/show_bug.cgi?id=4629
[6] https://bugs.maemo.org/show_bug.cgi?id=4628
[7] https://bugs.maemo.org/show_bug.cgi?id=4647
[8] https://bugs.maemo.org/show_bug.cgi?id=4632
[9] https://bugs.maemo.org/show_bug.cgi?id=4646
[10] https://bugs.maemo.org/show_bug.cgi?id=4750
[11] https://bugs.maemo.org/show_bug.cgi?id=4749
[12] https://bugs.maemo.org/show_bug.cgi?id=4791
[13] https://bugs.maemo.org/show_bug.cgi?id=4782
[14] https://bugs.maemo.org/show_bug.cgi?id=4821
[15] https://bugs.maemo.org/show_bug.cgi?id=4824
[16] https://bugs.maemo.org/show_bug.cgi?id=4839
[17] https://bugs.maemo.org/show_bug.cgi?id=4849
[18] https://bugs.maemo.org/show_bug.cgi?id=4734
[19] https://garage.maemo.org/mailman/listinfo/pymaemo-developers
[20] https://bugs.maemo.org/enter_bug.cgi?product=PyMaemo
This post was possible thanks to Anderson Lizardo, from PyMaemo team, who posted these informations on pymaemo-developers mailing list.
I must admit, I wasn't using Maemo email client, because I did find it was simply unusable, at least with my GMail account.
I tried both POP3 and IMAP, but having about 25.000+ messages in my account, downloading just the headers was a job that the client simply couldn't manage.
Yesterday I knew about "recent mode" support in POP3, a functionality that GMail supports too. This mode allow you to download only last 30 days messages (in my case, no more than 1000) so the client can manage them without any problem.
All you have to do to enable this mode is put the "recent:" string before the username. For example: if your username is "username@gmail.com" you have to write "recent:username@gmail.com". Important: this mode only works with POP3, not with IMAP.
To conclude, let me say thank you to the kind guy who let me discover this mode. Thank you Sergio! Now there is another thing I can do with my tablet!
As I promised in the preceding post, I'll provide a very easy example of a python binding. Let's suppose we don't want to use the methods included in Python to sum two integer values and we want to do it in C and then call the add method from a python script. I'll write the complete source code first and then I'll explain all the parts of it.
#include <Python.h>
static PyObject *foo_add(PyObject *self, PyObject *args)
{
int a;
int b;
if (!PyArg_ParseTuple(args, "ii", &a, &b))
{
return NULL;
}
return Py_BuildValue("i", a + b);
}
static PyMethodDef foo_methods[] = {
{ "add", (PyCFunction)foo_add, METH_VARARGS, NULL },
{ NULL, NULL, 0, NULL }
};
PyMODINIT_FUNC initfoo()
{
Py_InitModule3("foo", foo_methods, "My first extension module.");
}
First of all we have to include Python.h in our C file. This allows us to write an extension for Python language. To be able to include this header, we must have the python development packages installed in our system. For example in Debian based distributions we can install them with this command:
sudo apt-get install python2.5-dev
Every module has at least three parts. In the first part we write methods we want to call from the final python module: in this case we have a method called foo_add where "foo" is the name of the module and "add" the name of the method. Every method is declared as static PyObject. The method does anything particular except calling PyArg_ParseTuple to validate the input (we'll discuss this later), adding the two passed numbers and returning the result.
In the second part we have something like a dictionary, defined as static PyMethodDef and called foo_methods (where "foo" again is the name of the module). For each method we want to expose in our python module, we have to add something like this:
{"add", (PyCFunction)foo_add, METH_VARARGS, NULL}
where "add" is the name of the method we want to be visible in our module, (PyCFunction)foo_add is a pointer to our foo_add method, implemented in the C module, METH_VARARGS means that we want to pass some parameters to the function and the last one would be the description of the method (we can leave it NULL if we want).
Third part allows us to register the defined method/s and the module:
Py_InitModule3("foo", foo_methods, "My first extension module.");
The PyArg_ParseTuple function extracts arguments from the PyObject passed as parameter to the current method and follows almost the sscanf syntax to parse parameters (in this case we had "ii" for two integers). You can fin the complete reference here: http://docs.python.org/c-api/arg.html
To build the module, we have to be in the source directory and execute this command:
gcc -shared -I/usr/include/python2.5 foo.c -o foo.so
then we've to copy the generated module to the python's modules directory:
cp foo.so /usr/lib/python2.5/site-packages/
Testing the module is really easy. We've to start a python shell or create a python script with the following source code:
import foo print foo.add(2, 3)
if all is working fine, the printed result should be 5
MAFW is a new multimedia framework that will be used in Fremantle.
The PyMaemo team is currently working on writing bindings for Python
language for this library and at the moment we've released a 0.1
version of python-mafw that you can install directly from Scratchbox
repository.
Not all the methods are implemented (you can manage the Registry and
the Playlist, but nothing more), because even if we're using codegen
to generate bindings (and it's helping us a lot), we've seen that at
least 30-40 methods have to be overridden by hand so it's taking us
more time than we expected and we're trying to organize how to
continue this work.
We would like to get feedback from python application developers and
also from C application developers that are currently using MAFW so we
can work on a "roadmap" that reflects what developers want:
Come on developers! We're waiting for your feedback 
This summer I'm having the pleasure of working in Igalia (a spanish free software company) for a couple of months and they assigned me to an interesting project: developing Python bindings for MAFW library (a Maemo multimedia library that will be used in Fremantle release).
Having the opportunity to work both with C (yes, Python bindings are almost C code) and Python (it's a good practice to write unittest of all implemented methods) it's a good way to improve my knowledges in both languages and since I wasn't able to find much documentation about these kind of things, I'm going to share my own experiences.
What is a Binding?
A binding is a Python module, written in C language, that allows Python developers to call functions from existing C libraries from their python applications. It's just like a "bridge" from C world to Python one.
Why writing bindings?
There are a couple of reasons to write python bindings instead of writing a library in python language from scratch.
First of all I don't think is good duplicating code, so if a library already exists and it's written in C, why writing it again in another language? There's no reason. A lot of code already exist in C world and all we have to do is to create a bridge with python world.
Another good reason, in particular when a C library doesn't exist yet, is the fact that python code is slower than C code for some tasks (for example multimedia codecs). In these cases is good to implement the core library in C language and then create a python binding for it.
Coming next
As the title of this post says, this is only an introduction to the subjects I'm going to write about. If you have any particular request about any argument you would like to read, please feel free to leave me a comment. Next posts will talk about these things:
Recent Comments