![]() |
2010-11-02
, 14:37
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#912
|
The Following User Says Thank You to Capt'n Corrupt For This Useful Post: | ||
![]() |
2010-11-02
, 14:41
|
Posts: 1,097 |
Thanked: 650 times |
Joined on Nov 2007
|
#913
|
<br />
<br />
This could be done with mobilehotspot. Or joikuspot if you're in the mood for a paid app.
I might try later with wife's Tab to see if it gets the wifi cloud from my N900.
![]() |
2010-11-02
, 14:45
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#914
|
The Following User Says Thank You to Capt'n Corrupt For This Useful Post: | ||
![]() |
2010-11-02
, 14:50
|
Posts: 1,097 |
Thanked: 650 times |
Joined on Nov 2007
|
#915
|
The Following User Says Thank You to nilchak For This Useful Post: | ||
![]() |
2010-11-02
, 15:02
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#916
|
I guess the problem with embedding the 3G radios in ALL devices is that
1) Mfrs cannot use this as a way to price 3G devices higher for better profit margins (obvious).
2) the Carriers will raise hell as they dont want all that competition (as users can now switch carriers easily as it becomes a ubiquitous presence in all devices)
3) Carriers will have to run the gamut of 3G tests to insure that their network security isnt "compromised" (the bogeyman argument that carriers always use to thwart any innovation).
But I guess some day soon this might be broken just as many other walls have slowly been torn down in the world of carrier-mfrs nexus.
The Following User Says Thank You to Capt'n Corrupt For This Useful Post: | ||
![]() |
2010-11-02
, 15:14
|
Posts: 1,179 |
Thanked: 770 times |
Joined on Nov 2009
|
#917
|
The Following 3 Users Say Thank You to etuoyo For This Useful Post: | ||
![]() |
2010-11-02
, 15:14
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#918
|
![]() |
2010-11-02
, 15:21
|
Posts: 1,179 |
Thanked: 770 times |
Joined on Nov 2009
|
#919
|
![]() |
2010-11-02
, 15:22
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#920
|
I suspect Samsung has effectively set the pricing for high end android tablets by basically copyng like for like Apple's ipad pricing. When the ipad came out people were all saying it was way too expensive. However, it proved to be a huge success so Apple was somewhat justified in its pricing. Now Samsung decided that the general public accepts that as sensible pricing.
Unless the Tab is a huge commercial failure (which with a huge company like Samsung behind it it is unlikely to be) other manufacturers will just follow the Tab's pricing. Which means we are not going to see any sensibly priced android tablets for a long long time. Of course you will still be able to get affordable tablets from people like archos but I am talking of fully speced tablets from companies like HTC, Sony or Motorola.
Shame.
The Following User Says Thank You to Capt'n Corrupt For This Useful Post: | ||
![]() |
Tags |
android envy, buzz..buzz buzz, core failure, crapdroid, galaxy fap, galaxy tab, ipad killer, samsung, tab trolls, tablet envy |
|
http://developer.android.com/guide/t...ng-layout.html
http://developer.android.com/referen...uteLayout.html
The API reveals that the relative/absolute layout UI object, you can pretty much subdivide and arrange the screen however you want, create floating elements, or non-grid organizations. Further more, you can easily listen to resize events and create/hide/resize views as required (eg. screen orientation change, or smaller devices).
What's more is that it appears as though it's extensible by filling frames with other more canvas-like primitives. For example, a game that shows the graphics in a large right pane, and a chat client in the upper left, and world statistics in the lower left.
This is not only is incredibly flexible, it shows that Android has been 'tablet ready' for quite some time, and has a very robust and simple UI system that can handle a variety of screen-subdividing situations. That developers haven't taken advantage of this is more likely a result of Android being -- until recently -- exclusive to smartphones that have smaller screens and thus fewer subdivision possibilities.
Also, in fairness, the UI APIs seem tilted towards linear lists. Many of the layout elements are for linear lists/grids of objects, which may add to why they're more frequently used. But I must state that it is indeed possible to display segmented UIs easily without UI hacking/edge code.
I think the ignorance surrounding the understanding about Android being 'tablet ready' comes from a long smartphone lineage and lack of examples showing these less-known UI features -- and Engadget. The bottom line is, however, that it will be *very* easy to make apps tablet aware, with only a few lines of XML code in many cases defining new and unique view structures to suite the larger displays.
According to Tweetdroid, it only took 2 developers to port their app to Android. And twidroyd made their app tablet aware in the bargain. Expect more apps to quickly follow this trend.
Last edited by Capt'n Corrupt; 2010-11-02 at 15:12. Reason: Corrected error