Maemo

fooishbar has added a photo to the pool:

The maemo team has just released a development version of a new browser engine, built on open source and Mozilla technologies. Testers and contributors are welcome. This version runs and is available for download. It works on the Nokia N800 with the ... [More] latest Internet Tablet OS 2007. Try it out! Sharing the same key components than Firefox, this new browser engine has the capability to deliver advanced web technologies inside a pocketable form factor. The newest internet services will function on the Nokia N800, thanks to best-of-breed open standards support including full-AJAX, and integrated Adobe Flash 9. This also allows the creation of add-on’s to personalize the browsing experience.  How to download and give feedback Feedback is very helpful for the ongoing development and testing work. The application is ready for would be testers: just install the browser engine with a couple of taps and restart the browser. After installation the Mozilla based browser engine will be set as default. The user interface of the open browser engine is shared with the official Opera browser, although a couple of new features and changes are included with this release. Most differences should be in core browsing functionality and behavior. Users can switch back to the official Opera browser engine through the 'Set Engine' menu in the browser application menu. You can also uninstall the open browser engine from Application Manager at any time, without losing bookmarks or other settings made for Opera. You can submit feedback about bugs to bugs.maemo.org. Advanced users, developers and potential contributors can find more details in maemo.org/browser. Add-ons and extensions Thanks to the open standard support and shared code base with Firefox, developers are able to easily port add-ons and extensions available in mozilla.org. Firefox extensions are not directly usable, though. More detailed information on add-on development can be found on maemo.org/browser and mozilla.org An opportunity for the future is to extend the use of web technologies outside of the basic browser environment, for widgets and even application development. Contributors welcome We encourage other parties to join the development of this browser engine or use it in their products. Testers and developers are welcome to bring this beta to a final release and improve this browser engine through add-on's, extensions and new functionality. You can either directly get involved upstream at the mozilla.org projects or join the browser development project at maemo.org/browser. The browser development is being done with active synchronization with the Mozilla browser engine code-base. Nokia is also contributing the modifications and improvements back to the Mozilla Foundation to evolve Mozilla in a totally new frontier, pocketable browsing. In the future, we will continue to work on our browser solutions in active co-operation with the Mozilla browser work. To avoid any confusion, note that this browser engine is not coming from the Minimo project. The Minimo project targets mobile devices with a reduced set of features, but bases on the same Mozilla components as the new browser for tablets. Specifications Hypertext Markup Language (HTML) and Extensible Hypertext Markup Language (XHTML): HTML 4.01 and XHTML 1.0/1.1 JavaScript 1.7, based on ECMA-262, revision 3: ECMA-262 Asynchronous JavaScript and XML (AJAX) Cascading Style Sheets (CSS): CSS Level 1, CSS Level 2 and parts of CSS Level 3 Document Object Model (DOM): DOM Level 1, DOM Level 2 and parts of DOM Level 3 Extensible Markup Language (XML): XML 1.0, Namespaces in XML, Associating Style Sheets with XML Documents 1.0, Fragment Identifier for XML XSL Transformations (XSLT): XSLT 1.0 XML Path Language (XPath): XPath 1.0 [Less]

maemo 4.0 Chinook is the next stable release in our plans after the recently released maemo 3.2 Bora. Even if this is a major release bringing deep changes and enhancements, it is fully supported by the Nokia N800 Internet Tablet hardware. It is ... [More] also confirmed that Diablo, the next release after Chinook, will be also supported by the Nokia N800. We will provide compatibility details about Elephanta and next releases as soon as we confirm them. Platform stability and compatibility are a top priority in the current maemo roadmapping process. There are still some obstacles in order to get a consolidated platform aligned with upstream development, these are the main reason of the maemo 4.0 API break. After Chinook, the default setting is to provide API compatibility with an emphasis in backward compatibility in new maemo versions. There might be still exceptions in the mid term, due to deep hardware related challenges and upstream decisions, but we will make our best announcing them as soon as possible, providing details, tools and time for developers to react. Our aim is to provide a platform as stable and compatible as PC developers are used to in the main operating systems. The fact is, though, that PC hardware and core PC software components have a longer history and in many cases a less constrained environment than the Internet Tablets. We deal with this young and demanding context, we understand the direct comparisons and we do our best to match these expectations. It is not a simple task, though. Reasons for an API break in Chinook As announced previously, Chinook is a major release that will bring an API break mainly to align with two key upstream components: GTK and Glibc. Other libraries tagged as DEPRECATED in previous releases will be dropped, pushing the applications still using them to the new versions in order to be compatible with maemo 4.0. All in all the upgrade offers many improvements (also in the way we are handling it) compared to the past maemo 3.0 API break. As opposed to that break, the main reasons in Chinook are external. Alignment with the GNOME & Linux baseline is a top priority for us, and this is why maemo is moving to GTK 2.10 and Glibc 2.5. The move to GTK 2.10 brings better code and more functionality to the platform. It also puts maemo where the current development happens. maemo's GTK 2.6 is heavily patched and in fact it keeps us away from the upstream developers, forcing us to backport relevant improvements. By breaking the maemo API compatibility we gain GTK API compatibility, and this benefits developers in the short and long run. At a platform level it is easier to receive from the community and give back. At an application level life is easier for desktop developers porting to maemo and the GNOME Mobile context. The move forward opens also the door to the integration of all the wow effects provided by Cairo. Time to prepare the upgrade  We are making public the decision and the details about the API break months in advance, as soon as the first and unstable developments are released. The GTK API break was visible first through Sardine and the Hildon documentation. “maemo 4.0 Chinook” and the API break was communicated in LinuxTag in June. We are doing the full announcement now during GUADEC, providing technical details and tools, right after the 3.2 release. We have just released the maemo 4.0 alpha SDK, with partial functionality. It's still not functional to port/develop completely but it is a useful tool for developers to figure out where are the focus of attention in their applications. Connected with Sardine, the SDK puts developers in the current 4.0 baseline (as for today on the desktop components only, though). Hildon information publicly available  The Hildon project, where most of the changes happen in maemo 4.0, has already released extensive documentation for developers and a tool to audit your code and detect use of obsolete API. Glibc 2.5 brings multithreads to the maemo platform, but this change is very likely to affect only a minority of applications. We welcome any feedback to bugs.maemo.org and the maemo-developers list to improve this documentation and tools. This is the main reason why we are releasing now the alpha SDK, so beta testers in the future will get already a well consolidated path for porting to and developing for Chinook. [Less]

Nokia has just released the maemo 4.0 Chinook alpha SDK. This a preview of the next maemo stable release. This SDK is not fully functional but helps developers to understand and get familiar with the new APIs. Read more about the maemo 4.0 API break at maemo 4.0 Chinook API break and Nokia N800 support.

Nokia has announced the development version release of the Internet Communications Software Update for maemo 3.2. This update brings you the latest developments in Internet messaging and call destined for the next Internet Tablet OS release. ... [More] The software release is under development and therefore is not suitable for end users and serious personal use. However, if you are interested in helping improve it, the update should be fairly usable and we encourage to try it. What is it? Internet Communications Software is a subsystem in the Internet tablet OS 2007 and running on the Nokia N800 that handles presence, chat, VoIP and video call. It is based on Telepathy framework and components as explained at http://telepathy.freedesktop.org/ What is new? A number of things have improved since the last update (Internet tablet OS 2007): SIP support Basic one-to-one VoIP calls Messaging (using the MESSAGE method of SIMPLE). Video call between two N800 devices. NAT traversal using STUN. XMPP support enhancements Avatars support Presence status message Google Talk relay support User interface updates Updates in the Internet call UI Updates in the Chat UI Updates in the Account configuration UI Updates in the Addressbook UI New APIs Telepathy Mission Control Accounts Telepathy-glib   Download and screenshots http://rtcomm.garage.maemo.org/ Open the download link in the N800 browser and go to the Install section. Packages The following packages are updated in the release: libtelepathy 0.0.55-0osso3 telepathy-gabble 0.5.12-0osso4 telepathy-mission-control 4.26-1beta2 telepathy-stream-engine 0.3.23-0osso2.2 telepathy-sofiasip 0.3.25-0osso1 telepathy-glib 0.5.13-0osso2 telepathy-feed 0.26-1 sofia-sip 1.12.6-0osso4 evolution-data-server 1.4.2.1-20070628 eds-sync 2.20070706 galago-daemon 0.5.1-0osso2 libgalago 0.5.2-0osso5 farsight 0.1.21-0osso1.9 gst-plugins-farsight 0.12.2-0osso1.7 libscw 0.4.6-1osso109 loudmouth 1.3.1-0osso3 libjingle 0.3.11-0osso3 libosso-rtcom 2.0.12-1beta1 libimlogger 0.6-1 osso-mission-control 2.29-1beta osso-accounts 3.13-1beta9 osso-rtcom-icons 0.0.1 osso-addressbook 2.20070706-beta5 osso-applet-presence 2.0.3-1beta osso-statusbar-presence 2.0.13-1beta3 osso-contact-plugin 2.0.9-1beta1 osso-chat-ui 2.0.28-1beta1 osso-voip-ui 2.0.42-1beta5   Limitations UI Helps are missing It only speaks English Theming is missing (only default one is supported) SIP Calls fail to establish media streams when the device is behind a symmetric NAT and the proxies do not deploy transparent media relaying. Calls forked to multiple endpoints may fail to establish media streams. Video is not interoperable with other implementations. DTMF (RFC4733) is not reliable.   Feedback You are welcome to give your feedback on this software to: maemo-devel mailing list: [email protected] maemo bugzilla, RTCom component: http://bugzilla.maemo.org/ Rtcomm mailing address: [email protected] Thanks and enjoy! [Less]

There's never been a better time to upgrade your internet tablet to a Nokia N800. By ordering online today you can get a 15% discount on the price.

New material available in the Presentations section. Check it out! Nokia Internet Tablet Power Management Current implementation, work in progress and future plans for power management on the Nokia Internet Tablets. ... [More] These slides have been presented by Klaus K. Pedersen and Igor Stoppa at the Linux PM-Summit, held before the Linux Symposium (Ottawa, June 2007). Download the PDF or view online clicking the image. [Less]

Nokius has added a photo to the pool:

Nokius has added a photo to the pool:

Nokius has added a photo to the pool: