Re: Standard widget spacing and padding?
On Wed, 2007-04-11 at 18:38 +0300, Kuosmanen Tuomas (Nokia-M/Helsinki) wrote: On Fri, 2007-04-06 at 15:11 +0200, ext Murray Cumming wrote: On Wed, 2007-03-28 at 18:11 +0200, Murray Cumming wrote: I can't find anything in the various Maemo documents about the standard spacing that Maemo applications should have between and around widgets. For instance, for the GNOME HIG, this is usually 6 pixels between widgets and 12 pixels padding around the window: http://developer.gnome.org/projects/gup/hig/2.0/design-window.html This seems like something that should be in the Maemo porting guide http://www.maemo.org/platform/docs/howtos/howto_porting_to_maemo_bora.html as well as the UI specification: http://www.maemo.org/community/hildon_ui.html Anyone? I'm sure that Nokia has some kind of standard somewhere for this. Heya! The margin default padding is 6 pixels, and if a bigger padding is desired, either margin double (6x2 = 12px) or triple (6x3 = 18px) is used. If a smaller margin is needed, margin half (3px) is there for you. So basically using 12px paddings between widgets should be a good starting point. Currently our theme adds this weird padding around the window anyway, so I think apps should not use much padding around themselves. I'll check this and the widget padding tomorrow when there are more people in the office in the morning, and will correct it if I am assuming wrong. Thanks, but is there any official documentation for this, or is it just an informal standard? Btw, I'll be happy to assist with layout of your application if you want - poke me on irc (tigert on #maemo in freenode) or send email. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
Re: Moving windows in Maemo
On Apr 13, 2007, at 3:43 AM, Eero Tamminen wrote: #2 of course might have to be modal depending on the operation. But #1 NEVER has to be modal, I don't understand. Infoprints are never modal, they don't even take focus. No, you're right, they're never modal, at least from my current testing. But they do interfere with operations, covering widgets (like the scroll-up button and thumb) and material on-screen, and causing a significant cognitive wait period, hesitating until they go away because you can't dismiss them. If you'd like them hanging around that long they should be placed somewhere that has less effect: my top choice is the right 2/3 of the menu title bar. Note that some of the dialogs have static sizes because Gtk doesn't always handle automatic resizing well enough. This is only a problem with text ellipsizing though I think. Gtk has only concepts of minimum (for ellipsizable text=...) and full size of a widget, as getting something reasonable in between would need a lot of iterating (slowdown) for the widget sizes. Why do your windows need to have live resizing? I'm not talking about user resizes, but calculating the dialog sizes. Why is this an issue? It would seem to me that ellipsizing is O(1). Size as you like, then if you can't fit everything, draw, then erase back N characters, or a word, and stick in the I get the feeling that GTK's got some more coding ickiness here. I've already found another example -- try putting two TextViews inside an HPaned, fill them with a lot of text, and then drag the HPaned. This should be smooth but it's freaks them out badly. This kind of behavior is unacceptably slow for a modern GUI: it looks like someone's hacked in a bad algorithm out at RedHat. Did palms or Newtons ellipsize too long strings or were they only available in English? :-) Can't say about Palms. Newtons did not ellipsize: but generally Newton windows were movable but did not have resize widgets (not that there was a prohibition against it). But more importantly, MacOS X does not ellipsize, so at least in English it's not seen as all that important. If it's highly costly, why not dump it? Sean ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
N800 satellite/terrestrial/wimax demos at NAB 2007
Hi Folks, Just a little annoucement that we will be showing a demo at NAB next week at our booth using a few N800s as a end-point uPnP streamer and multicast FLUTE data receivers, for files and multicast data packaged and tagged by our headend applications and received by our edge routers over simulated satellite/digital terrestrial (ATSC/DVB-T)/WiMax signal paths. More info on the show is here - http://www.nabshow.com (our booth is C8148). If you are there please stop by. I will post pics to the IT flickr group with an update for anyone who misses it. (sorry, hackers and their enthusiasm.. you know how it goes) ;-) Cheers Kon ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
Re: 0xFFFF: GPL-licensed flasher for n770 and n800
On Fri, 13 Apr 2007 21:47:47 +0200 Visti Andresen [EMAIL PROTECTED] wrote: On Fri, 13 Apr 2007 09:47:01 +0300 Igor Stoppa [EMAIL PROTECTED] wrote: Depends on what you mean by 'from scratch'. If the unit does not have a bootloader _at all_, then you need to flash a bootloader via JTAG. But that's mildly convoluted. Serial console is the usual way to go. There is rom code that provides this facility. Of course a serial programmer (aka flasher) is needed. Are you telling me that the N770 has a ROM (not EEPROM or FLASH) that allows one to rewrite the Flash no matter how badly you screwed any part of the programmable memory? I'm asking as I have until now been quite cautious in my experiments with the Nokia, knowing that there is a way to recover the device (by my self) would put my mind at ease :) If it has such a marvellous ROM bootloader, is it by any chance one with any documentation regarding the protocol? Something like UBoot would really nice :) I have been digging around and it actually seems that a omap1710 has a boot rom? On some development boards one has to move a jumper for the bootloader to be run (changes the memory map), and it isn't uboot but an iboot/ihost bootloader, capable of flashing over usb? Do we have to hold down some button in order for the boot loader to start(at powerup)? An omap1710 could be seen as an OMAP5912 according to http://focus.ti.com/general/docs/wtbu/wtbusplashcontent.tsp?templateId=6123contentId=4753 http://focus.ti.com/docs/prod/folders/print/omap5912.html contains data sheets for this processor http://tree.celinuxforum.org/CelfPubWiki/FlashRecoveryUtility seems to be an open source iboot a like program to be able to flash an omap cpu over USB. The protocol seems quite straight forward ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
Re: 0xFFFF: GPL-licensed flasher for n770 and n800
On Sat, 2007-04-14 at 19:39 +0200, ext Visti Andresen wrote: On Fri, 13 Apr 2007 21:47:47 +0200 Visti Andresen [EMAIL PROTECTED] wrote: On Fri, 13 Apr 2007 09:47:01 +0300 Igor Stoppa [EMAIL PROTECTED] wrote: Depends on what you mean by 'from scratch'. If the unit does not have a bootloader _at all_, then you need to flash a bootloader via JTAG. But that's mildly convoluted. Serial console is the usual way to go. There is rom code that provides this facility. Of course a serial programmer (aka flasher) is needed. Are you telling me that the N770 has a ROM (not EEPROM or FLASH) that allows one to rewrite the Flash no matter how badly you screwed any part of the programmable memory? I'm asking as I have until now been quite cautious in my experiments with the Nokia, knowing that there is a way to recover the device (by my self) would put my mind at ease :) If it has such a marvellous ROM bootloader, is it by any chance one with any documentation regarding the protocol? Something like UBoot would really nice :) I have been digging around and it actually seems that a omap1710 has a boot rom? It's a feature common to many SoC. I don't know how detailed the information available in the public TRM is, but i would recommend googling for web sites devoted to phone hacking. Note that it's up to you to figure out if tampering with the device at such level is legal in your country. I really have no clue. The outcome could be at worst a dead device (not bricked, you can really kill the processor if you get the connection wrong or exceed the voltage levels) or anyway a device bricked in such a way that will probably void the warranty and make it necessary to get it re-flashed by the service point. On some development boards one has to move a jumper for the bootloader to be run (changes the memory map), and it isn't uboot but an iboot/ihost bootloader, capable of flashing over usb? Do we have to hold down some button in order for the boot loader to start(at powerup)? No, i wish it was so simple. Unfortunately the internet tablets have inherited some legacy features from the phones, features that are purposefully intended to prevent or at least make it difficult to do a cold-flash. Incidentally this detail comes in the way of disclosing informations since they would be useful also for hacking phones (which has significant legal implications). An omap1710 could be seen as an OMAP5912 according to http://focus.ti.com/general/docs/wtbu/wtbusplashcontent.tsp?templateId=6123contentId=4753 http://focus.ti.com/docs/prod/folders/print/omap5912.html contains data sheets for this processor http://tree.celinuxforum.org/CelfPubWiki/FlashRecoveryUtility seems to be an open source iboot a like program to be able to flash an omap cpu over USB. The protocol seems quite straight forward iirc usb flashing requires a different hw configurations (done by connecting resistors of a certain value to the proper pads) we should have OMAP configured for serial port so i don't think that option is viable. So maybe we have here something to add to the wishlist for maemo, albeit i'm not sure that it includes hw features. I think the opinion from the internet tablet hackers would be valuable. -- Cheers, Igor Igor Stoppa [EMAIL PROTECTED] (Nokia Multimedia - CP - OSSO / Helsinki, Finland) ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
Re: N800 satellite/terrestrial/wimax demos at NAB 2007
Kon - Where is this working - what country / cities? Is this a proof of concept or can we plan on trying it out in the near future. Can't make NAB, but very interested... Thanks, JG On 4/14/07, Kon Wilms [EMAIL PROTECTED] wrote: Hi Folks, Just a little annoucement that we will be showing a demo at NAB next week at our booth using a few N800s as a end-point uPnP streamer and multicast FLUTE data receivers, for files and multicast data packaged and tagged by our headend applications and received by our edge routers over simulated satellite/digital terrestrial (ATSC/DVB-T)/WiMax signal paths. More info on the show is here - http://www.nabshow.com (our booth is C8148). If you are there please stop by. I will post pics to the IT flickr group with an update for anyone who misses it. (sorry, hackers and their enthusiasm.. you know how it goes) ;-) Cheers Kon ___ maemo-users mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-users -- Jonathan Greene m 917.560.3000 AIM / iChat - atmasphere gtalk / jabber - [EMAIL PROTECTED] Gizmo - JonathanGreene blogs - http://www.atmasphere.net/wp / http://www.maemoapps.com ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
RE: SoC: 5 preliminary slots
My proposal/plans are available at http://maemo.org/maemowiki/GeoClue Thanks! I know there's still six weeks until the official start and some students may actually have busy schedules until that point, but it can't hurt to start communicating early... These previous weeks are there *exactly* to start crating the infrastructure, get the students familiar with the project, the community and the tools. This way once the SoC projects officially start everybody and everything is in place, with some inertia already. Students and mentors, can you please get in touch create your garage projects? Maybe the Japanese/Chinese project can be hosted in the current garage project for CJK support, as you prefer. Quim ___ maemo-developers mailing list [EMAIL PROTECTED] https://maemo.org/mailman/listinfo/maemo-developers
