waiting of pay Market in Germany

by gsmbernie » Fri, 13 Mar 2009 01:47:34 GMT


Sponsored Links
 Globale Wirtschaftskrise... ??? mchte Applikationen erwerben.. geht
jedoch nicht in Germany

.. restricted Market !!!

how long no interest on Germany Market User ???

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. scalable vector graphics scalable vector graphics scalable vector graphics

etc...

this quote from this blog says it clearly.  the lack of hardware
acceleration for androids 2D graphics API, oand for any resolution
independent way of defining your UI is a showstopper.

http://unqualified-reservations.blogspot.com/2007/11/five-problems-with-google-android.html

"Third, Android's graphics framework uses pixel coordinates and
immediate-mode 2D drawing.

Now this is just a mistake. I was looking at the doc and I could have
sworn that someone had mischievously linked me to the Xlib manpages.
WTF, guys? Is there a timewarp in Mountain View I don't know about? I
know you're on the old SGI campus, but really...

The idea that, in 2007, anyone is writing 2D UIs with pixel drawing
functions just burns me up. The right way to draw a UI is to construct
a vector data structure, a la SVG or whatever, that represents the
visual state of the screen in resolution-independent coordinates, and
then just render the fscker. No, you don't have to actually construct
an SVG text file. You even have a GL library in there! You can just
treat 2D as a special case of 3D! People!

This is not just an esoteric developer issue. It has real usability
ramifications.

I don't know anything about the iPhone's software stack, but I'm
pretty sure it uses Quartz, in which all coordinates are device-
independent. But I didn't even need to know this. The whole UI just
screams "vector." As soon as I saw the demos, my first thought was
"now no one will ever write another GUI which uses raster graphics."
Little did I know that down in Mountain View, a crack team of hotshot
Googlers was busy recreating the Athena toolkit.

With a lot of work, with good layout and compositing and so forth, it
is possible to make a raster UI look pretty good. The Android UIs look
pretty good. But they don't look anywhere near as slick as the iPhone.
When you don't isolate device coordinates completely from the
programmer, they leak everywhere. You are constantly deciding whether
that line is 1 pixel or 2 pixels thick. And your designers curse you
all day long.

You do need a couple of things to build a pure vector UI. You need a
high-resolution screen, a fast CPU, and hopefully some kind of GPU.
But - as the iPhone proves - all of these are available in products
shipping today. There is simply no excuse for creating a new platform
in which applications are not isolated from device-dependent screen
coordinates.
"
--~--~---------~--~----~------------~-------~--~----~

2. (D)GPS good to 10 cm

Different folks are different ages and have taken valid snap shots of
GPS locating precision at different points in its development.

Our perception of precision guides our judgment as to what
applications are viable and what potential market sizes are for
software that we offer.  I found this link helpful:

http://en.wikipedia.org/wiki/Differential_GPS

What this means in a practical sense, for me at least, is that the
merchant beacon used to help people find items at open air markets can
also be used to help people find specific items on grocery store
shelves in the US. That makes the market for software of this type a
lot larger. Some of the applications may include stores mounting the
phone to the cart and letting shoppers with ordinary phones download a
list. Other applications might be used in any warehouse where kitting
is done. The list of items gets organized for efficient pickup using
the established preferred direction of travel for each aisle.

Everything gets calibrated at the entrance to the store. The merchant
beacon becomes an item beacon.  It is just coordinates in a data base.

Is there enough resolution in the Android  GPS data types at present
to do this?

Sometimes data type resolution is determined with a snapshot in time
assessing what is needed. People don't always remember to change them
when technology improves.

Does Android have enough precision in its location data types to be
useful at this granularity?


--~--~---------~--~----~------------~-------~--~----~

3. How to detect item selected in Spinner View as selecting different items

4. AutoCompleteTextView - does not display content

5. How to make screen scroll horizontally

6. RTP/RTSP

7. Ode to Team Android