Re: [maemo-developers] Battery Management X Maemo
On 12/22/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi all! > I have a problem: > I need to discover the level of available battery of the device. I return > this value to an application that it aims at to save energy. I have only > two problems: > 1. I do not have Nokia 770 :P > 2. The directory that could contain the information, > /proc/acpi/battery is empty - why it will be? XP If you are talking about the one showing up in scratchbox, that's you machines "real" proc you are looking at. It shows the battery on this laptop just fine, but AFAIK will be of no use on the 770. > Well, is possible to get these information in the Maemo? You can listen to certain dbus signals to find out a rough number (I think it was in four or five steps of battery level?), but I'm afraid anything more detailed than that is not available. Someone with the approperiate signals at hand and more details should probably add it to the wiki, this feels like a thing that will be of interest to many... -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] [libgtkhtml-2.0] HtmlDocument not receiving mouse clicks
Hi Philippe, On 12/21/05, Philippe De Swert <[EMAIL PROTECTED]> wrote: I have used gtkhtml-3.0 before in GPE. There everything was working fine(except that it had a pretty large footprint) I have some trimmed down gtkhtml sourc here : http://stag.mind.be/gpe-helpviewer.html. Mainly I reduced thedependencies in this one.Hope this is of any use to you. Thank you for your suggestion. It seems gtkhtml-3.0 is very different from 2.0. If I use your lite-version, then I think I would need to use webcore too. Right now, I plan to concentrate on finishing the current version of the application. After that I'll try to convert it to gtkhtml-3.0 and compare the footprint. Regards, Henry ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
On 12/21/05, Luc Pionchon <[EMAIL PROTECTED]> wrote: > Hi koen, rusty, > > You are correct regarding UI and screen size. It shows where it breaks. > (There is no surprised here). But *porting* Maemo to other devices will > show assumptions based on 770 others than just screen size, we may have > surprises. +1 While I think that we should think general, I also think that we should work on problems when we come to them. Right now maemo have other kind of problems that we may solve, some are general and will help other fronts, like making things a bit faster and better PIM and its integration with various desktops and operating systems. OT: I'm going nuts until my device doesn't arrives!!! I want to give it a try with PIM and help out with problems... I really want to replace my Palm Vx with something better! And as I'll be in vacation for about 2 months, I'll have much time to work on this! -- Gustavo Sverzut Barbieri -- Computer Engineer 2001 - UNICAMP Mobile: +55 (19) 9165 8010 Phone: +1 (347) 624 6296; [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] ICQ#: 17249123 MSN: [EMAIL PROTECTED] GPG: 0xB640E1A2 @ wwwkeys.pgp.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
Hi koen, rusty, You are correct regarding UI and screen size. It shows where it breaks. (There is no surprised here). But *porting* Maemo to other devices will show assumptions based on 770 others than just screen size, we may have surprises. What's about dedicated hardkeys? iPAQ and 770 have different sets. Maemo assumes at least home|menu|cancel|fullscreen|zoom. How do you zoom in fullscreen mode on an iPAQ? iPAQs could use softkeys. Zaurus has full qwerty keyboard. Can Maemo run on a 32Mo iPAQ? etc. In short how much Maemo is tight to 770 hardware? The more devices/configurations are tested the more we can fix Maemo to make it "ready for any device". We would be pleased to hear from other experiments. iPAQ is a good target to start with. So if you play with Maemo on other devices, let us know! Br, luc On Wed, 2005-12-21 at 10:18 -0500, ext Russell Geldmacher wrote: > Right, you don't even need the Zaurus for that ... just change your > Xephyr resolution to 640x480 and you'll see the same effect (makes it > easier for developers to see the problem). > > rusty > > On 12/21/05, Koen Kooi <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Luc Pionchon wrote: > > > Hi, > > > > > > On Tue, 2005-12-20 at 16:29 +0100, ext Erik Bågfors wrote: > > > > > >>My first thinking when it comes to this is to port maemo to an > > >>existing machine, such as a IPAQ which already runs linux and today > > >>GPE. > > > > > > > > > Sounds like a great idea. > > > > > > Did anyone out there give it a try already? > > > > It's as easy as pointing $DISPLAY to your handheld: > > http://dominion.kabel.utwente.nl/koen/blog/pyblosxom.cgi/2005/May/29 > > > > regards, > > > > Koen > > > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.1 (Darwin) > > > > iD8DBQFDqVi+MkyGM64RGpERAveKAJ9b9K8gIy1y2ePBylxVtUHCY4YlUACeIg1e > > C6JzxrdrXmck7OPHZYMqBZ0= > > =Vc2D > > -END PGP SIGNATURE- > > ___ > > 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Battery Management X Maemo
Hi all! I have a problem: I need to discover the level of available battery of the device. I return this value to an application that it aims at to save energy. I have only two problems: 1. I do not have Nokia 770 :P 2. The directory that could contain the information, /proc/acpi/battery is empty - why it will be? XP Well, is possible to get these information in the Maemo? I do not go to be able to monitor these values, but while I do not have the device, at least to compile the program! (the 770 are well expensive...) Efforts! Francisco Geovane Alves da Silva Laboratório de Redes de Computadores e Segurança - Larces Universidade Estadual do Ceará - UECE ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
Hi, > If maemo had a notion of DPI this would be much easier, but as > Tommi pointed out, requires us to fix most of the internets css files I don't quite see what CSS files have to do with changing theme font sizes. Why you cannot just change the font sizes listed by: grep font_name /usr/share/themes/*/gtk-2.0/gtkrc grep "font " /usr/share/themes/*/matchbox/theme.xml ? (And note that there's no way you could handle this just by DPI or font sizes if you care about looks quality. The font size is supposed to match with the theme gfx, such as the fairly constant colored area in titlebars so that text appears properly centered to it, not too small compared to the reserved space etc.) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] [libgtkhtml-2.0] HtmlDocument not receiving mouse clicks
Hi Henry, > > Has this software been tested on the desktop with a touchscreen? > > With touch screen there are very few mouse moves compared to non- > > touchscreen displays. => I don't know if libgtkhtml-2.0 has been tested on the desktop with a > touchscreen. It's the first time I use that library. I'll try and see if I > can get more info on the gnome mailing list later on. > > For now, I've implemented a workaround by using the button-press-event of > the surrounding HtmlView. I have used gtkhtml-3.0 before in GPE. There everything was working fine (except that it had a pretty large footprint) I have some trimmed down gtkhtml sourc here : http://stag.mind.be/gpe-helpviewer.html. Mainly I reduced the dependencies in this one. Hope this is of any use to you. Regards, Philippe | Philippe De Swert | | GPE developer: http://gpe.handhelds.org | Emdebian developer: http://www.emdebian.org | | Please do not send me documents in a closed | format.(*.doc,*.xls,*.ppt) | Use the open alternatives. (*.pdf,*.ps,*.html,*.txt) | http://www.gnu.org/philosophy/no-word-attachments.html --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eero Tamminen wrote: > Hi, > > >>that an interesting screenshot because it illustrates some basic >>scalablility issues even at 640x480 which isn't that different from >>the 770. > > > Is there anything that couldn't be fixed just by finetuning the > theme files i.e. without touching any code? > > The titlebar is just single large image. By: > - changing titlebar gfx to uglier tiled one, and > - setting statusbar panel to more suitable position > in the Matchbox theme should fix the most obvious problems. > > There would still be the problem that application title will have > very little space to show the text. > > > >>Porting Maemo to a common 240x320 PDA will be challenging > > > I think you'll need completely new application layouts, or > in case the physical screen size is the same, just make the font > much smaller and fine-tune the theme files. If maemo had a notion of DPI this would be much easier, but as Tommi pointed out, requires us to fix most of the internets css files :( regards, Koen > > > - Eero > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDqXRiMkyGM64RGpERAvzwAKCOvxnmexTQ4AmJ0VEVtFXEqBU35gCeNLT7 7TE72WvHWxcxd8WWU4RsxwA= =kGX6 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
Hi, > that an interesting screenshot because it illustrates some basic > scalablility issues even at 640x480 which isn't that different from > the 770. Is there anything that couldn't be fixed just by finetuning the theme files i.e. without touching any code? The titlebar is just single large image. By: - changing titlebar gfx to uglier tiled one, and - setting statusbar panel to more suitable position in the Matchbox theme should fix the most obvious problems. There would still be the problem that application title will have very little space to show the text. > Porting Maemo to a common 240x320 PDA will be challenging I think you'll need completely new application layouts, or in case the physical screen size is the same, just make the font much smaller and fine-tune the theme files. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
Right, you don't even need the Zaurus for that ... just change your Xephyr resolution to 640x480 and you'll see the same effect (makes it easier for developers to see the problem). rusty On 12/21/05, Koen Kooi <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Luc Pionchon wrote: > > Hi, > > > > On Tue, 2005-12-20 at 16:29 +0100, ext Erik Bågfors wrote: > > > >>My first thinking when it comes to this is to port maemo to an > >>existing machine, such as a IPAQ which already runs linux and today > >>GPE. > > > > > > Sounds like a great idea. > > > > Did anyone out there give it a try already? > > It's as easy as pointing $DISPLAY to your handheld: > http://dominion.kabel.utwente.nl/koen/blog/pyblosxom.cgi/2005/May/29 > > regards, > > Koen > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.1 (Darwin) > > iD8DBQFDqVi+MkyGM64RGpERAveKAJ9b9K8gIy1y2ePBylxVtUHCY4YlUACeIg1e > C6JzxrdrXmck7OPHZYMqBZ0= > =Vc2D > -END PGP SIGNATURE- > ___ > 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] Updated rootfs.packages available?
Wow, I thought I had done that step but missed it in my haste ;-) Anyway it works now... pushing onward! Thanks! rusty On 12/21/05, Janne Kataja <[EMAIL PROTECTED]> wrote: > Russell Geldmacher wrote: > > >Hi all, > > > >I'm playing around with rebuilding the root file system and am running > >into trouble with some packages listed in rootfs.packages (gotten from > >https://stage.maemo.org/svn/integration/trunk/rootfs/) > > > Some binaries need to be downloaded separately. Untar them to > workarounds -directory. > > Nokia Binary Components for maemo Development Platform > http://maemo.org/downloads/d2.php > > > > > Janne > > -- > Janne Kataja, Movial Corporation > Porkkalankatu 13 J, FI-00180 Helsinki > Mobile +358 40 550 9801, Tel +358 9 8567 6400 > Fax +358 9 8567 6401 > www.movial.fi > > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
Hi, Koen Kooi wrote: > It's as easy as pointing $DISPLAY to your handheld: > http://dominion.kabel.utwente.nl/koen/blog/pyblosxom.cgi/2005/May/29 that an interesting screenshot because it illustrates some basic scalablility issues even at 640x480 which isn't that different from the 770. Porting Maemo to a common 240x320 PDA will be challenging, but i really want to have support for this in future! Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] [libgtkhtml-2.0] HtmlDocument not receiving mouse clicks
On 12/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:-- Forwarded message -- From: Eero Tamminen <[EMAIL PROTECTED]>To: maemo-developers@maemo.orgDate: Wed, 21 Dec 2005 15:14:32 +0200 Subject: Re: [maemo-developers] [libgtkhtml-2.0] HtmlDocument not receiving mouse clicksHi,> I'm working on a chm viewer based on chmlib and libgtkhtml-2.0 (built> with --disable-accessibilty). Everything is working fine inside > scratchbox, but on the actual device I notice that the link_clicked> callback on the HtmlDocument widget is not working. Looking further, I> notice that the all dom_mouse_* events are working except > dom_mouse_click.Has this software been tested on the desktop with a touchscreen?With touch screen there are very few mouse moves compared to non-touchscreen displays. - Eero I don't know if libgtkhtml-2.0 has been tested on the desktop with a touchscreen. It's the first time I use that library. I'll try and see if I can get more info on the gnome mailing list later on. For now, I've implemented a workaround by using the button-press-event of the surrounding HtmlView. Regards, Henry ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] testing pango with 770
On 12/21/05, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > On 12/21/05, Kalle Vahlman <[EMAIL PROTECTED]> wrote: > > On 12/21/05, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > > > On 12/21/05, Tapani Pälli <[EMAIL PROTECTED]> wrote: > > > > * What is causing slowness? > > > > > > It's disappointing that with every release gtk gets slower... > > > > Where's the numbers for that? Or is this the fabled "user experience" > > that can't be measured but is always right, no matter what is proved? > > > > (sorry for being a smart-ass, but I want those numbers so GNOME can be > > "fixed" in this regard so nobody has to whine about it anymore...) > > What Tapani sent wasn't numbers? As you may see from them, as pango > and glib versions increased, things got slower. Guess I misinterpeted you then, I thought you were blaming increasing Gtk+ version for that... Sorry anyway. > Ok, I'm also from the crew that thinks that things should be optimized > just after you get the system working and if it's necessary. Pango is > full-featuread and mature, since it's a core component, it needs some > optimizations. So we need to optimize it. > > One might think "why don't this guy optimize it?" Answer is simple: > it's easier to pango developers to know where to optimize, they know > what to optimize and they know the code. So a week or so in feature > freeze dedicated to "speeding up" will give more results than me > spending a whole semester looking at it. And as I pointed out, this has been happening. Wether or not the performance improvements apply for the 770 (which has no FP etc) is another thing though. -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] additional deb repositories for the N770
hi, I am new to the list, so I sorry if it is an FAQ. I was looking for extra repositories for N770 packages for ARM and PC: I am also unfortunately new to debian (using gentoo and suse). Thus telling me how to add a new repository would be kind. It would be cool if anyone could add the information to the wiki. e.g. under *http://maemo.org/maemowiki/DeveloperInfo * Thanks at lot, Stefan * * ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] testing pango with 770
On 12/21/05, Kalle Vahlman <[EMAIL PROTECTED]> wrote: > On 12/21/05, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > > On 12/21/05, Tapani Pälli <[EMAIL PROTECTED]> wrote: > > > * What is causing slowness? > > > > It's disappointing that with every release gtk gets slower... > > Where's the numbers for that? Or is this the fabled "user experience" > that can't be measured but is always right, no matter what is proved? > > (sorry for being a smart-ass, but I want those numbers so GNOME can be > "fixed" in this regard so nobody has to whine about it anymore...) What Tapani sent wasn't numbers? As you may see from them, as pango and glib versions increased, things got slower. Ok, I'm also from the crew that thinks that things should be optimized just after you get the system working and if it's necessary. Pango is full-featuread and mature, since it's a core component, it needs some optimizations. So we need to optimize it. One might think "why don't this guy optimize it?" Answer is simple: it's easier to pango developers to know where to optimize, they know what to optimize and they know the code. So a week or so in feature freeze dedicated to "speeding up" will give more results than me spending a whole semester looking at it. -- Gustavo Sverzut Barbieri -- Computer Engineer 2001 - UNICAMP Mobile: +55 (19) 9165 8010 Phone: +1 (347) 624 6296; [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] ICQ#: 17249123 MSN: [EMAIL PROTECTED] GPG: 0xB640E1A2 @ wwwkeys.pgp.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] testing pango with 770
On 12/21/05, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > On 12/21/05, Tapani Pälli <[EMAIL PROTECTED]> wrote: > > * What is causing slowness? > > It's disappointing that with every release gtk gets slower... Where's the numbers for that? Or is this the fabled "user experience" that can't be measured but is always right, no matter what is proved? (sorry for being a smart-ass, but I want those numbers so GNOME can be "fixed" in this regard so nobody has to whine about it anymore...) > someone > that works with pango should take a look at this and try to run gprof > to check for bootlenecks. They have. Check blogs for behdad or federico for example, or the archives for the GNOME performance-list at: http://mail.gnome.org/archives/performance-list/ -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] testing pango with 770
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tapani Pälli wrote: > Hello, > * I will happily try running other tests aswell, don't hesitate to answer I'm wondering if the slowndown is being caused by excessive use of floating points. To test this you could run these tests on a cpu with floating point, or make a softfloat maemo-image. regards, Koen > > * What is causing slowness? > > // Tapani > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDqVoyMkyGM64RGpERAgkEAKC1hb+K7siBQiel+042sNux2lVpVgCfSWDz Zh2IXA1qvvEHe2LK4iKs8kw= =KQ+R -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Luc Pionchon wrote: > Hi, > > On Tue, 2005-12-20 at 16:29 +0100, ext Erik Bågfors wrote: > >>My first thinking when it comes to this is to port maemo to an >>existing machine, such as a IPAQ which already runs linux and today >>GPE. > > > Sounds like a great idea. > > Did anyone out there give it a try already? It's as easy as pointing $DISPLAY to your handheld: http://dominion.kabel.utwente.nl/koen/blog/pyblosxom.cgi/2005/May/29 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDqVi+MkyGM64RGpERAveKAJ9b9K8gIy1y2ePBylxVtUHCY4YlUACeIg1e C6JzxrdrXmck7OPHZYMqBZ0= =Vc2D -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] testing pango with 770
On 12/21/05, Tapani Pälli <[EMAIL PROTECTED]> wrote: > * What is causing slowness? It's disappointing that with every release gtk gets slower... someone that works with pango should take a look at this and try to run gprof to check for bootlenecks. -- Gustavo Sverzut Barbieri -- Computer Engineer 2001 - UNICAMP Mobile: +55 (19) 9165 8010 Phone: +1 (347) 624 6296; [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] ICQ#: 17249123 MSN: [EMAIL PROTECTED] GPG: 0xB640E1A2 @ wwwkeys.pgp.net ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] testing pango with 770
Hello, Here are test results for Pango performance on 770 : === TEST : Pango performance on 770 === Test programs are made by OpenedHand, all tests are measuring fullscreen write speed. Timestamps are taken using gettimeofday() after rendering and issuing XSync(). Short description on tests (api, rendering function) : *test-pango: xlib,pango_xft_render *test-pango-gdk: gtk/gdk, pango_xft_render *test-pango-gtk: gtk, pango_xft_render *test-pango-layout : gtk, gdk_draw_layout Text 'abcdefghijklmnopqrstuvwxyz' is rendered to 20 rows 100 times using 'sans serif-18' font. (Each test is renderering 52000 glyphs.) using 770 macroboard, latest sw-build. -test-1-- - glib 2.6.2 - pango 1.8.1 test-pango: Total time 6254 ms, approx 8314 glyphs per second test-pango-gdk: Total time 6292 ms, approx 8264 glyphs per second test-pango-gtk: Total time 6313 ms, approx 8236 glyphs per second test-pango-layout : Total time 7383 ms, approx 7043 glyphs per second test-gtk-layout : Total time 7782 ms, approx 6682 glyphs per second -test-2-- - glib 2.9.1 - pango 1.10.2 test-pango: Total time 6787 ms, approx 7661 glyphs per second test-pango-gdk: Total time 6610 ms, approx 7866 glyphs per second test-pango-gtk: Total time 6569 ms, approx 7915 glyphs per second test-pango-layout : Total time 8038 ms, approx 6469 glyphs per second test-gtk-layout : Total time 8593 ms, approx 6051 glyphs per second -test-3-- - glib 2.9.1 - pango 1.11.1 test-pango: Total time 6979 ms, approx 7450 glyphs per second test-pango-gdk: Total time 6899 ms, approx 7537 glyphs per second test-pango-gtk: Total time 6893 ms, approx 7543 glyphs per second test-pango-layout : Total time 8064 ms, approx 6448 glyphs per second test-gtk-layout : Total time 8423 ms, approx 6173 glyphs per second Notes : * Gtk was not built with new glib, I was using the same gtk (2:2.6.4-1.osso76) all the time. There might be some speed differences to tests using gtk then. * 'test-pango' is the most accurate figure here, since it's not using gtk. * Packages were made using upstream tarballs and applying maemo-patches (glib 5, pango 1) on top * I will happily try running other tests aswell, don't hesitate to answer * What is causing slowness? // Tapani ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] [libgtkhtml-2.0] HtmlDocument not receiving mouse clicks
Hi, > I'm working on a chm viewer based on chmlib and libgtkhtml-2.0 (built > with --disable-accessibilty). Everything is working fine inside > scratchbox, but on the actual device I notice that the link_clicked > callback on the HtmlDocument widget is not working. Looking further, I > notice that the all dom_mouse_* events are working except > dom_mouse_click. Has this software been tested on the desktop with a touchscreen? With touch screen there are very few mouse moves compared to non- touchscreen displays. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] What will be your next Maemo device
Hi, On Tue, 2005-12-20 at 16:29 +0100, ext Erik Bågfors wrote: > My first thinking when it comes to this is to port maemo to an > existing machine, such as a IPAQ which already runs linux and today > GPE. Sounds like a great idea. Did anyone out there give it a try already? > > But Maemo is so much nicer than GPE. Working on both Maemo and GPE, I won't comment this ;) (besides that each could learn from the other at several levels) I extended a bit the list with more thoughts, see http://maemo.org/maemowiki/MaemoScalability Br, luc > The screen is really different > on the IPAQ and the 770. And changing the orientation between > landscape or not, is very important on the IPAQ. > > /Erik > > > 2005/12/20, Luc Pionchon <[EMAIL PROTECTED]>: > > Hi, > > > > What will be your next Maemo device? I do not know, really. > > > > My major concern is, will Maemo be ready for it? > > > > Bigger screen? Smaller like S60 phones? Two screens like Communicators? > > Landscape? Portrait? What's about input methods? A full keyboard? A > > reduced keyboard like standard phones? Or an improved virtual keyboard? > > What's about dedicated hardware buttons? And Softkeys? 2 like phones? 4 > > like Communicators? More? Oh! Shall we play more with available > > technology? Rotate and resize on the fly? Display migration? > > Applications should reorganize their layout depending of the screen(s) > > configuration. Can we reasonably use SVG icons? > > > > OK, I stop here. You got my point. Whatever is the device of your > > dreams, we want to be ready to support it by making Maemo as scalable as > > possible. > > > > Let's stretch, shrink, whirl, squeeze Maemo UI! > > > > Here is a raw list of technical items related to scalability. > > Feel free to experiment, comment and extend! > > > > http://maemo.org/maemowiki/MaemoScalability > > > > Br, > > luc > > ___ > > 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] Updated rootfs.packages available?
Russell Geldmacher wrote: Hi all, I'm playing around with rebuilding the root file system and am running into trouble with some packages listed in rootfs.packages (gotten from https://stage.maemo.org/svn/integration/trunk/rootfs/) Some binaries need to be downloaded separately. Untar them to workarounds -directory. Nokia Binary Components for maemo Development Platform http://maemo.org/downloads/d2.php Janne -- Janne Kataja, Movial Corporation Porkkalankatu 13 J, FI-00180 Helsinki Mobile +358 40 550 9801, Tel +358 9 8567 6400 Fax +358 9 8567 6401 www.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] [libgtkhtml-2.0] HtmlDocument not receiving mouse clicks
Hi, I'm working on a chm viewer based on chmlib and libgtkhtml-2.0 (built with --disable-accessibilty). Everything is working fine inside scratchbox, but on the actual device I notice that the link_clicked callback on the HtmlDocument widget is not working. Looking further, I notice that the all dom_mouse_* events are working except dom_mouse_click. As I mentioned before, everything is working fine inside scratchbox. This is only happening on the 770 itself. Is there anything that I've overlooked? Regards, Henry ps. this is my first maemo application, so it could be something trivial... ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
