[maemo-developers] Info on FIASCO components/hackers' guide to the N770
Hi all, and thank you Nokia for finally getting my lovely new 770 to me. I'm still in the process of familiarizing myself w/ the device and the Maemo/N770 environment. Let me first complement all of the people who have made this impressive little device so usable and compelling already. Great job. One of the first things I generally do when I get a new Linux-capable device is remove all proprietary software, and replace it with Free Software or Open Source alternatives if possible (or otherwise do without). I'm still running the stock image on the 770, but I've been investigating over the last week what it would take to rip out all of the proprietary stuff, and how much customization of the device is possible. One thing I've noticed is there seems to be lack of a comprehensive set of documentation for the device at the how it all works level, from processor beings executing code at location 0x to this is how you assemble a FIASCO image. I can kind of understand why this information might not be available. Nokia no doubt wants us to concentrate on developing useful end-user applications which enhance rather than replace the existing functionality and environment. However, given the existence of the information at [1] and [2], it seems that the djinn is already half out of the bottle. For instance, I've already been able, using the resources cited above on the maemo.org website, to unpack a FIASCO image and determine that the initfs and rootfs are JFFS2 images, and that the remaining components aren't. So, I was wondering if it would be possible to have such a Hacker's Guide to the N770 and Maemo. Something which describes the function of the various FIASCO components and the recipe for creating a valid custom FIASCO image (obviously certain components couldn't be replaced). I'm most interested in creating my own kernel, initfs and rootfs images and sewing them back together, and flashing them to the device without breaking anything. I'd love to know what Nokia's position is on this as well as what other developers here think about it. Also, is flasher a supported way to upgrade to the latest system image from Nokia's support site? Thanks in advance. Dave ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: testing pango with 770
ext Federico Mena Quintero wrote: This is interesting, since pango-1.11.1 has our recent optimizations in it. You mentioned that you were using gettimeofday(). Can you please test the pango-profile module from CVS? It has a slightly more sophisticated timer, using times(). I've found it to be quite reliable, and it gives reproducible results. I've been running pango-language-profile now aswell, also produced new results with fs-tests BUT then when I made tests with x86 I found out with callgrindkcachegrind that quite much of the time was spent on typecasts and checks ... so actually I've been running stuff with debug turned on (instead of 'minimal' in stable release) :-/ With x86 this does not seem to make much difference but with arm I'd expect results with new pango to be better. I'm sorry for my misconclusions, I'll run the tests again and post results! // Tapani ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] non-maemo apps in toolbar
On Wednesday 04 January 2006 21:53, Aaron Levinson wrote: As a general rule, building and running strictly X applications isn't going to cut it on the 770, and a true port of a GUI application to the maemo platform requires some programming, quite possibly extensive programming if the original application is only written using X. I'm discovering this with my port of rdesktop. I have a (very early) alpha running which lets you enter some basic data through a messy GTK+ dialog then runs rdesktop full-screen. The mouse stuff is all fine (although double-clicking takes some effort!) but the big problem is that it's all written in X11 code. I'm going to have to completely rewrite the X stuff for Hildon, replacing the event loop etc (it was difficult enough to port the make to autogen!) This is a good example of how the unique nature of the 770's architecture can get you close on a port - but still miles away! :-) Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] non-maemo apps in toolbar
Hi Simon, Did you take a look at the Qt user interface implementation for rdesktop? Shouldn't be too difficult to port to GTK, and it's likely easier to port the Qt code than to port the X user interface implementation, since the Qt code already deals with higher level user interface concepts. You could even start from the QtE (Qt Embedded) implementation. I initially tried something similar with VNC to what you did for rdesktop, but I gave up. Mixing X and GTK tended to cause lots of problems. However, the nice thing about the rdesktop source code is that the user interface implementation is kept separate from the underlying communication protocol implementation, which is not the case for RealVNC's vncviewer implementation. Aaron On Thu, 5 Jan 2006, Simon Guerrero wrote: On Wednesday 04 January 2006 21:53, Aaron Levinson wrote: As a general rule, building and running strictly X applications isn't going to cut it on the 770, and a true port of a GUI application to the maemo platform requires some programming, quite possibly extensive programming if the original application is only written using X. I'm discovering this with my port of rdesktop. I have a (very early) alpha running which lets you enter some basic data through a messy GTK+ dialog then runs rdesktop full-screen. The mouse stuff is all fine (although double-clicking takes some effort!) but the big problem is that it's all written in X11 code. I'm going to have to completely rewrite the X stuff for Hildon, replacing the event loop etc (it was difficult enough to port the make to autogen!) This is a good example of how the unique nature of the 770's architecture can get you close on a port - but still miles away! :-) Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] non-maemo apps in toolbar
Hi, What exactly are the other issues that I mentioned? Here's a list that is likely incomplete (and doesn't mention those issues already discussed): If user cannot switch to an application already having a window open, that should be filed as a bug. I did a quick search on Maemo bugzilla, but didn't find anything. Didn't anybody consider this as a bug??? As to the input method, maybe the program could depend from xkbd (AFAIK doesn't support unicode, but as it works by synthetizing key events with XTest extension it should work with all X programs) and launch it when the program itself is started? 1. Full screen support That doesn't need Gtk or Maemo support. Just the use of the EWMH standard window property for fullscreen. See: http://www.freedesktop.org/wiki/Standards_2fwm_2dspec Fullscreen key is sent as a normal X key event so that shouldn't be a problem either. 2. Proper menus, toolbars, titles. These are only look layout issues, not problems functionality wise. Menu key is also sent as a normal X key event. 3. Integration with libosso (refer to libosso APIs for more information). I think the only real problem here is that program shouldn't use CPU (*at all*) if it's not visible (either untopped or screen is blanked) and it's not doing something for the user (e.g. playing music). Otherwise it will drain the battery pretty quickly. This shouldn't be any problem for apps that react only to user input and don't do any polling. Other applications (and games), could check either: - if they lose focus (e.g. in fullscreen SDL game) - Matchbox X property for topmost app window (e.g. in Xlib programs), see: http://projects.o-hand.com/matchbox/documentation/developers/matchbox-key.txt And then pause their polling... 4. And finally, behaving in a way that 770 users expect, based on the already existing software on the device and developed for the device. Well, one can't get everything. :-) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] non-maemo apps in toolbar
Hi; Have you tried setting the StartupWMClass key of the apps .desktop file to whatever ace of penguins sets as its WM_CLASS window prop to ( you can find this out with xprop ) ? If it dont set it, you may have to hack ace of penguins so it does. -- Matthew On 1/4/06, Mark Arrasmith [EMAIL PROTECTED] wrote: Because the 770 uses X11 I was interested in porting some X11 and fltk apps for fun. I compiled Ace of Penguins ( http://www.delorie.com/store/ace/ ) for the 770. Ace of Penguins is a X11 based card game suite that includes solitaire, freecell, taipei, and others. Basically it is the same thing I did with the Agenda VR3 with I got that years ago. So anyway, solitaire runs very fast (it is up and running as soon as the stylus leaves the screen) and is only 80K. But, it doesn't show up in the left toolbar when running. Which makes minimizing it kind of worthless. I have the X-HildonDesk-ShowInToolbar=true set in the .desktop file. Is there anything else I need to do? - mark -- A career is great, but you can't run your fingers through its hair. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] non-maemo apps in toolbar
Hi; On 1/5/06, Eero Tamminen [EMAIL PROTECTED] wrote: As to the input method, maybe the program could depend from xkbd (AFAIK doesn't support unicode, but as it works by synthetizing key events with XTest extension it should work with all X programs) Xkbd is dead dead dead. Use matchbox-keyboard instead ( its a complete much needed rewrite ), it supports full UTF8 but lacks a couple of minor things like images on keys and themeing. Oh and its svn only :( See; http://svn.o-hand.com/repos/matchbox/trunk/matchbox-keyboard/README and launch it when the program itself is started? To make an input window work in maemo env ( this is different to defualt mb input win handling ) you need to have it set its transiency to the window its entering data for. matchbox-keyboard doesn't do this. but you could just embed matchbox-keyboard via XEMBED in some kind of wrapper of your toolkit of choice that handles the transiency or just avoid input windows all togeather and embed it direct in your app. -- Matthew ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] bluetooth settings in debian
Hi all, I have Linux Debian 2.6, bluetooth Bluez already installed. But I don't know how to change setting for bluetooth (like friendly name services). How / Where can I find those settings? I want to make program like rfcomm server that can receive connection upto 7 client and then sending messages between them. Doesbluezsupport this ? Maybe anyone has documentation or sample programfor this ? Thanks Ronny ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
