Tags: fremantle, maemo
Some of you are bound to have realized that there is a new update for the N900, PR1.3. This is primarily a consumer update containing many tweaks and improvements to the N900 user experience. It also aligns the Qt application and UI framework with the planned version for the MeeGo 1.1 platform (Qt 4.7). Qt Mobility 1.0.2 APIs for mobile development are also included.
Software development using scratchbox for the new platform will be supported right away. For those using the Nokia Qt SDK, we have tested Qt 4.6 applications on PR1.3 and did not encounter any major problems, so you can continue to distribute apps developed with the current toolset. Support for new N900 apps with the Qt4.7 framework will be available with a Nokia Qt SDK update that will be available soon. Until then, Ovi Store will accept applications built using Qt4.6.
Qt 4.7 comes with Qt Declarative libraries and QML support. This cutting edge technology allows the fast creation of impressive application UIs. It also supports interaction with C++ objects, allowing developers to create dynamic UIs in QML and link them to background C++ code. There have been many examples of Qt Quick already posted at maemo.org and at qt.nokia.com. Full Qt Creator support for Qt Quick development will be available when Nokia Qt SDK 1.1 is released.
After the major update of the device software to PR 1.2, you can update your development environment today as well. Three updates for you:
There is a new version of the technical preview of MADDE available, so that you can cross-compile easily your Qt and C/C++ application on OS X, Linux or Windows. The update is based on PR 1.2 and contains as well the QtMobility API’s. Now you can develop your application based on QtMobility, upload it to extras and the libraries will be installed automatically on every PR 1.2 device. The description, what MADDE is, how to use it with QtCreator and more you will find in the wiki.
A new update of the platform SDK is available for download. Everything around that you will find in the installation instructions. If you are interested in the changes to the last release, have a look into the release notes. A major update compared to the release is, that it contains the QtMobility libraries.
Maemo Community, tell us how it is!
How is Maemo developer documentation? How should it be improved?
We want to hear it straight from You.
Maemo developer documentation survey consists of 16 questions. Take a few minutes to think about the developer documentation available for Maemo (in Maemo.org, for example) and answer the questions at: http://www.surveymonkey.com/s/2Y8TDXD
The survey will be available until 6 April 2010.
Your feedback is appreciated!
Nokia has just released the Maemo 5 SDK 1.2 available here. The release contains many different additions/deletions/updates and features the Qt4.6 library. It also contains package updates required for software designed for the next Maemo product software update coming out soon.
The release notes are available here.
Some time ago, we published a tech preview of MADDE as a new cross-compilation tool, which runs on Windows, Linux and Mac OSX. MADDE is a command line tool, which allows to compile C/C++ and Qt applications for Maemo5. We got a lot of positive feedback, as the tool is easy to set up and to use. It smoothes the set up of the development environment, significantly for Windows-users.
Now the tech preview is extended by adding another feature. During the next week, we will give you instructions on how to integrate MADDE into QtCreator, step by step, and for each system – Windows, Linux and Mac OS X. It will work with a preview of QtCreator, but all the instructions you will find in the maemo.org wiki. With today’s post we published already the instructions for Windows users. Check them out and feel free to let us know what you think about it.
Hopefully some of you find time to be at the Mobile Dev Camp in Helsinki tomorrow, to chat about your thoughts and experiences with Maemo development.
A month ago, we offered a first tech preview of a new cross-compilation toolkit for Maemo5. Madde is a command line tool, which makes the development for Maemo much smoother. It runs on Linux, Windows and Mac, is easy to install and contains the Qt 4.5 libraries by default. Further there is a first preview of a client for the N900 available, which helps to transfer and test the code on the device.
Since then we received a lot of positive feedback. Especially Windows users like the idea of being able to develop and cross-compile applications within their native environment. The feedback helped us to improve the software further. Now there is an updated version of Madde tech preview (0.6.14) available for download. The biggest changes are the updated target to PR1.1 and the change of the toolchain, which matches now the Maemo5 SDK. Here are all the changes and improvements, compared to the “X-mas-edition”:
- Fremantle target updated to PR.1.1
Toolchain changed for Fremantle. Now it matches with Maemo5 SDK. cc command fixed.
- Windows target creation performance improved.
- Maemo Desktop files added to Qt example and base64 command added to support that.
- Qt library example fixed.
- Following https://bugs.maemo.org/buglist.cgi?component=madde bugs fixed.
- 8415 Cannot install MADDE to different directory than the default
- 7637 pscreate writes a localized, invalid trailer line into de…7821 Library search path wrong
- 7350 MADDE 0.5’s dpkg replacement does not work with –search …
- 7774 Can’t run GLES applications under madde environment
- 8623 hildon-1 pkg-config configuration broken.
- Minor buf fixes and improvements.
With this new preview, we want to keep you up-to-date on the development process. Please feel free to give it a try and to let us know, what you think. You can do that on different channels – Bugzilla has a component called Madde and there is a talk-thread, where Madde developer are active and open for your comments.
A request to DNS management has been sent to start pointing maemo.org to the new infrastructure tomorrow at 8:00 UTC and it was acknowledged and scheduled.
After the change there is about a 6-24 hour period in which the DNS change propagates all over the world.
To do things in a sensible way and to minimise downtime, the old site will go to read only (off-line for garage) mode tomorrow morning. Then the last changes are synced over to the new site and the new site will then be opened to public.
When you see the new site naturally depends on the DNS propagation speed, but 3-12 hours seems to be normal based on the smaller moves done earlier.
Things you will experience are:
- Read only on the site before and during the move
- Garage will show a ‘we are moving page’
- No wiki editing during the move
- No git and svn work during the move
Things you might experience are:
- Some data loss is possible, but we’ll try to avoid it
- The site will look strange for a while as the changes take place and the static content is pointing wrong for a while
Things you should not have problems with:
- talk.maemo.org Talk will be open to public all the time, it is on separate hardware and not moving
- bugs.maemo.org Bugs moved last week, it’s there waiting for the other services
- Mailing lists moved to the new hardware some weeks back
After the DNS change propagates the services will start appearing normally again, and naturally there will be notices posted.
When everything is done, please be patient with the service, and open bugs on anything that looks odd or doesn’t work. Raising issues on this post, the community mailing list and on talk will also help. But bugs are a sure way to make an issue known (also remember that more bugs is more work for Andre, so please check for duplicates before opening).
And then a huge thanks to the people who have been hard at work throughout the move! Ferenc and Niels have done the bulk of the work. Ed, Jeremiah, Eero and Bergie pitched in. Much appreciated everyone! Naturally not forgetting the people at the new ISP, it was a crash course into the infra needs of maemo.org for them 🙂
So tomorrow we’ll see how the site moves!
You, like I, may have noticed that PR 1.1 is out as of this morning!
It is a big update and if you get a complaint of too little space, you may need to uninstall some applications. If you run into issues, please post a comment here, ask for help on talk.maemo.org thread or the #maemo IRC channel on freenode.net.
You can find the proper change log in the wiki. The changelog includes a full list of fixed bugs that the community reported against the initial product release. A big thank you to everyone who opened a bug!
The flashable images will be available in the usual location, tablets-dev during today. So you can also flash your device, if the SSU update for some reason fails.
Enjoy the new release!
P.S. it seems that talk.maemo.org got overrun by traffic. Need to get that back on-line again.
Sampo’s thesis will revolve around (surprise) writing and porting software for the Maemo platform. All details are still pretty firmly floating in the air, it’s his third workday, and he just got a desk to put his laptop on.
As eCoach was first implemented for Maemo 4 and has been available for Maemo 5 for some time now, it is natural that it will be used as the case for the thesis. And if anyone is wondering, this won’t affect Sampo’s work on eCoach, rather the opposite. We want to have eCoach out there as an open source project in the future too, it’s a popular application and a good example of what the N900 can do.
Good luck to Sampo for the thesis!
Everyone has seen that the servers at maemo.org are not up to the task anymore. Yes we know and people, especially Ferenc, Niels, Jeremiah, Eero and Ed have been working on the new infrastructure for some time now.
Moving maemo.org has taken some time due to the interwoven nature of the services in maemo.org. Especially the core services for developers (main site, garage, git, builder, repositories) are tied to each other on various levels. These ties have been cleaned during the move to make things ready for the future too. Also those ties mean that moving one part at a time is hard.
The current server infra was taken into use several years ago, when Maemo was becoming something more than a cool idea in a lab at Nokia. Back in those days the visitor numbers were small and the site was much different. Many of the services did not exist and the ones that did weren’t so popular as they are now.
Then the site slowly grew and more people found it. To accommodate this, some changes were made to the hardware, the main maemo.org site got better servers and the database back-end was updated. This was ok for the majority of last year.
Then Nokia introduced the N900.
As plain statistic, in June 2009 only the main site maemo.org (not including talk, wiki or anything else, just the main site) got roughly 2.5 million page hits a month. This changed to 40 million a month by December 2009.
We expected a growth in traffic, but not a 15 fold increase. The site could have taken about half of that and still performed.
The plan to update the servers was in place early, but unfortunately it was not pushed into action early enough. That’s pretty much my fault, I made the decision to postpone the move until after the Maemo Summit. With 20/20 hindsight: bad decision.
As it happened the ISP that was chosen could not deliver everything in the schedule they optimistically promised. Again my mistake for not scrutinising their delivery capability.
The delays piled up and we ended up in the middle of a massive growth in usage, for which the hardware was not designed for. Services slowed to a crawl like everyone can see.
While things started crawling we had the additional problem of keeping the old system somehow going and building the new one at the same time. No one wants to do that. Double work is always useless.
When will this all be better?
Hopefully next week.
There are two things in the way anymore. The first one is ssh (scp) connections for git and dput. To make things cleaner, we need one more machine to handle incoming ssh traffic, and that is still in the works. The other thing is a complex issue involving a firewall, a load balancer, apache and ssl connections. There’s a solution for that, but it still needs a bit more problem solving to make all the pieces fit together.
Some things have moved already. You might have noticed the mails from Ferenc stating that the list servers are on the new infra. Yes, after some last minute changes (done after the dns change was put through) the mail and list servers are now in the new premises. You might have also noticed that the builder suddenly got faster and your packages don’t spend hours in queue any more. The builder is now a machine that is more up to the task. Also the maemo.org test environments are set up in the new hardware and in use there. Those just aren’t seen by the public, as they are used for testing changes to the site (no, you do not change the live site without testing first).
And of the things that have not moved, many are set up in the new environment. The thing is that moving services requires that the databases move too. And if the databases move, then the services depending on them need to move… Which leads to the situation where most things will move in one big dns change.
So this week you will still see slowness and crawling servers, but next week that should be gone.
I’ll inform when the big dns change is going to hit the site. During a period of roughly 3-12 hours after the change there may be some erratic behaviour, but after that things should calm down.
Thanks for your patience up till now. Hang on a bit longer and things will improve.