|
|
2007-10-02
, 23:47
|
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#232
|
or in other words, it may not have anything with the power of the device, but how the browser is coded.
|
|
2007-10-03
, 00:40
|
|
|
Posts: 2,869 |
Thanked: 1,784 times |
Joined on Feb 2007
@ Po' Bo'. PA
|
#233
|
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.
|
|
2007-10-03
, 01:06
|
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#234
|
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....
|
|
2007-10-03
, 07:26
|
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#235
|
|
|
2007-10-03
, 15:23
|
|
Posts: 65 |
Thanked: 6 times |
Joined on Apr 2007
|
#236
|
Yes, not much discussion of 802.11N, although that would be a logical next step, the number of 802.11n hotspots is currently miniscule.
|
|
2007-10-04
, 18:41
|
|
Posts: 356 |
Thanked: 231 times |
Joined on Oct 2007
|
#237
|
|
|
2007-10-09
, 15:06
|
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#238
|
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.
|
|
2007-10-09
, 15:15
|
|
Posts: 356 |
Thanked: 231 times |
Joined on Oct 2007
|
#239
|
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.|
|
2007-10-10
, 12:23
|
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#240
|
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 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.