Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Third Internet Tablet spotted on FCC

    Reply
    Page 24 of 25 | Prev | 14   22     23   24   25   | Next
    tso | # 231 | 2007-10-02, 23:24 | Report

    Originally Posted by Milhouse View Post
    I get the hanging problem in Micro-B when I click the "go to newest post" link (which is too small on NITs - another issue being ignored by Admin!) The page appears to load, then the browser hangs for several seconds - up to 30 seconds or so - and then finally the browser snaps to the correct place in the post (ie. the newest post). It seems like it may be a problem with anchor processing, or perhaps the rendering engine in Micro-b hogs the CPU and no longer listens to touchscreen/scroll events while it grinds it's way through the HTML. Either way, it's horribly unresponsive.
    iirc, microb does full javascript and similar processing. opera does the minimal or something like that. in other words, microb is much, much more pedantic about how it deals with webpages. thats also why you will see things pop into view and resize maybe 2-3 times before its settles down in opera. microb waits for the whole html to be loaded before it starts the processing, opera does some some guesswork and then redoes it when it gets more data from the server.

    i also recall a about:config setting that controlled the default wait before showing anything of a page in firefox. im guessing that said setting could also be in effect in microb.

    basically, microb (and the rest of the mozilla family) by default puts correctness ahead of user responsiveness.

    or in other words, it may not have anything with the power of the device, but how the browser is coded.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Texrat | # 232 | 2007-10-02, 23:47 | Report

    Originally Posted by tso View Post
    or in other words, it may not have anything with the power of the device, but how the browser is coded.
    And as an adjunct to that, how the site itself is constructed.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    YoDude | # 233 | 2007-10-03, 00:40 | Report

    Originally Posted by tso View Post
    iirc, microb does full javascript and similar processing. opera does the minimal or something like that. in other words, microb is much, much more pedantic about how it deals with webpages. thats also why you will see things pop into view and resize maybe 2-3 times before its settles down in opera. microb waits for the whole html to be loaded before it starts the processing, opera does some some guesswork and then redoes it when it gets more data from the server.

    i also recall a about:config setting that controlled the default wait before showing anything of a page in firefox. im guessing that said setting could also be in effect in microb.

    basically, microb (and the rest of the mozilla family) by default puts correctness ahead of user responsiveness.

    or in other words, it may not have anything with the power of the device, but how the browser is coded.

    Bingo!


    ***

    BTW, awhile back in this thread I saw talk of a new OS or one that is specific to the new device.

    That would suck on so many levels.

    Again, my hope is that the additional hardware will only encourage third party development of new apps that can also be used on the N800 by those that have already enhanced their devices with add on GPS and/or keyboards.

    In addition, Nokia themselves may develop more/better utilities that can be used by the current tablet(s) like mapping for the 12 or thirteen buttons on the dang thing. BT connectivity can also use some help.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    SD69 | # 234 | 2007-10-03, 01:06 | Report

    Originally Posted by EIPI View Post
    I'm no electrical/computer type, but is there anything in the FCC filings to suggest that the new IT is 802.11N compatible? My current thought is that the new tablet has wifi-N and built in gps. Still optomistic that it also has WiMax.

    Trying to steer the thread back on course....
    Yes, not much discussion of 802.11N, although that would be a logical next step, the number of 802.11n hotspots is currently miniscule.

    I appreciate your optimism, but for the umpteenth time, the WiMax version will not be until 2008!!!

    Nokia has only just recently done the procurement for the WiMax silicon. Search and read the WiMax thread.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    tso | # 235 | 2007-10-03, 07:26 | Report

    and even then, so far we only know that nokia will supply n800 (or similar) with wimax to sprint in usa. for use with sprint's mobile wimax based network.

    we do not know if there will be a N800 like device with wimax for the general public yet. and i dont think we will see it any time soon as there at not many places you have use for a portable wimax device. besides sprint's upcoming network, i only know of south korea having wibro (their take on mobile wimax iirc) up and running, with some samsung devices made specific for it. outside of that, wimax is mostly used as a last-mile solution where laying new copper or fiber would be to expensive.

    now, if/when 4G/LTE comes around, then we may well see more of it. basically thats what sprint is trying to get a head start on iirc.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Roc Ingersol | # 236 | 2007-10-03, 15:23 | Report

    Originally Posted by SD69 View Post
    Yes, not much discussion of 802.11N, although that would be a logical next step, the number of 802.11n hotspots is currently miniscule.
    Miniscule... but in my office and home. So =p
    N is more important to me than WiMax. By a lot.

    Of course, some OS updates, better UI performance, better camera, GPS, better D-pad, better button configurations, etc -- those are all more important than N.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    vvaz | # 237 | 2007-10-04, 18:41 | Report

    If built-in hardware keyboard is true it opens many possibilities. One drawback for 800 and 770 was requirement of specific toolkit to make on-screen keyboard work. With hardware solution I believe this is no longer necessary. This one plus usb host can turn "N900" into really good UMPC. I hope Nokia will keep 400 price tag - although $400 = E400 is really ugly for European customers

    Edit | Forward | Quote | Quick Reply | Thanks

     
    TA-t3 | # 238 | 2007-10-09, 15:06 | Report

    Originally Posted by vvaz View Post
    One drawback for 800 and 770 was requirement of specific toolkit to make on-screen keyboard work. With hardware solution I believe this is no longer necessary.
    This assumption is unfortunately false. A hardware keyboard has a fixed layout, what you see is what you get. I find myself routinely switching language layouts on the on-screen keyboard simply because I need access to both national letters as well as characters only available on another (say, US) layout.

    The only way to achieve that with a small-size hardware keyboard is through a bunch of awkward secret key combinations. As on my Zaurus. This is practically useless (I can't remember these combinations). As a result I never use it (I use the on-screen one instead). So, even with a slide-out keyboard it wouldn't be smart to remove the on-screen one.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    vvaz | # 239 | 2007-10-09, 15:15 | Report

    I wasn't speaking about layouts. Non latin1 users are screwed either way I was speaking of special binding of text fields and on screen keyboard. That was mentioned in one of discussions about KDE. Usage of programs built around non-special edition of GTK(?) is awkward because binding between textfields and on-screen keyboard is done on really low level. For example if you focus in some textarea on web form in native browser on-screen keyboard will automatically pop-up. With non-native solutions input of text is more complicated.

    This sounds like small thing but this is major block for every day usage.

    With hardware keyboard this limitation vanishes - I believe.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    SD69 | # 240 | 2007-10-10, 12:23 | Report

    Originally Posted by vvaz View Post
    I was speaking of special binding of text fields and on screen keyboard. That was mentioned in one of discussions about KDE. Usage of programs built around non-special edition of GTK(?) is awkward because binding between textfields and on-screen keyboard is done on really low level. For example if you focus in some textarea on web form in native browser on-screen keyboard will automatically pop-up. With non-native solutions input of text is more complicated.

    This sounds like small thing but this is major block for every day usage.

    With hardware keyboard this limitation vanishes - I believe.
    I'm not sure what you mean. My BT keyboard works seamlessly with original firmware.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 24 of 25 | Prev | 14   22     23   24   25   | Next
vBulletin® Version 3.8.8
Normal Logout