Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Unless it's the passenger doing that it's entirely impractical for someone driving to manage all of that. That's where GPS receivers are useful. A driver interacts directly with the information displayed. You're asking for a situation far worse than a driver talking on a cell phone. You're asking for a driver to concentrate on small print on a screen, 'pinch' to enlarge the map (last I checked that requires two hands) and then determine a route on the fly. About this time the car will have driven through the front of a Starbucks.

The only practical way for your method to work is to pull over, determine your location and then orient yourself against the displayed map and then reorient the map to your location. There's nothing you said that couldn't be done more efficiently with a paper map. You don't have to 'pinch' a paper map to zoom into a location.

What exactly would you do with Google Map's automatic routing system if it doesn't actually know where you are? You're sitting at the corner of Main and Chestnut but the map seems to think you're on a highway 2/3 of a mile away. All of its directions would be completely incorrect for your vantage point. You're right back to being better off with a real map. There's no flicking, scrolling, zooming or pinching.

If if this was a passenger doing it then that pretty much alleviates the true usefulness of the product. You could have just handed the person a map. After all, if you're moving and the passenger is pinching, zooming, scrolling and flicking then the EDGE connection is going to have to be able to keep up with the map display changes. Have you actually tried scrolling arround Maps and watching the refresh? It takes a while. Not particularly useful unless the application is predicting where the vehicle is going to be next and that won't work since the applet thinks you're somewhere else than you actually are.

OH MY God....Would you please read the whole conversation...I am TOTALY against any digital item being used while driving...to include programing a friggin GPS. I have been nothing but consistant on this if you would read all of my posts.

Number two...I NEVER said that the iPhone was the only way to navigate, I have mentioned in previous posts that I prefer MAPs and a Compass. My statement was that the iPhone and Google Maps is still a useful tool and how it can be utilized, my lord...don't take things so friggin personal.

If you read your google map and look at those little letters...they actually spell out street names...if you have street names and you know that you are somewhere with in 3300 feet of any given location then by simple elimination you can find that dang street that you are "PARKED" on and get back on track.

Wow...I will insure to never piss on your parade again. Sorry for being so insulting to your lack of intelligence!
 
I did read your whole post. You gave an example of how it could be used which is entirely impractical.

You SAID:

I am TOTALY against any digital item being used while driving...to include programing a friggin GPS.

but you previously said:

If the map plots you to within a 3300 foot circle and you use the pinch method to enlarge you will be able to see street names within that circumfrence. At this point you can look out your vehicle window at the street sign or look up at the cross walk, find where you are and look back at your map.

You really need to make up your mind. You just contradicted yourself in two consecutive posts.

Then you say:

If you read your google map and look at those little letters...they actually spell out street names...if you have street names and you know that you are somewhere with in 3300 feet of any given location then by simple elimination you can find that dang street that you are "PARKED" on and get back on track.

Really? Do you park at a lot of crosswalks (see above) or see street signs (again, see your statement above) in parking places (you normally find street signs at intersections) not in the middle between blocks where parking spaces are.

You can't have it both ways. I'm sorry you took offense but your statements contradict and the practicality is non-existent. If you don't know the area then you're going to have to re-park with every turn or after many blocks to reorient yourself to your next turn because you know nothing about what's going to come next. THAT, would require going back, scrolling, refreshing and reorienting yourself.

By the way...

OH MY God....Would you please read the whole conversation...

Apparently you don't know what a conversation is because you weren't conversing with anyone. You made one reply and I responded to it. I guess you meant to say you wanted me to read the whole post, which I did. That's what the post was all about.

And you talk about lack of intelligence? Nice. I never insulted you by the way. I merely disagreed with your view of its practicality with a detailed description of my view. After all, your first post started out that you disagree with someone else's post. Apparently you don't like when someone disagrees with you.
 
just stop bitching.

last i checked when you were in a vechicle it wasn't THAT hard to pull off to the side of the road and use your iPhone to get directions. Driving and looking up directions is besides the point of this thread.


I think 1.1.3 comes out right after Mac world, and Jobs will also explain heavily on the next iPhone that will be released, as well as the SDK, that will probably start functioning in March.
 
just stop bitching.

last i checked when you were in a vechicle it wasn't THAT hard to pull off to the side of the road and use your iPhone to get directions.

I guess you don't do much big city driving. Try to find a parking space.
 
I guess you don't do much big city driving. Try to find a parking space.

And then when you're stopped in traffic, do it then.

I use my phone and drive all the time. Not hard to manage a car while paying attention, and at the same time turn my iphone on, slide to unlock it, and press the maps button. Or maybe it's because i can do it without looking ;)
 
It's possible that 1.1.3 will never see the light of day.

(The features will be rolled into the bigger update that's likely to be announced on the 15th).

So i have no idea how inside builds work .. but would they name it a real name (like 1.1.3) instead of some inside code name (like how the build number is a bunch of letters and numbers)
 
So i have no idea how inside builds work .. but would they name it a real name (like 1.1.3) instead of some inside code name (like how the build number is a bunch of letters and numbers)

Not sure what you mean but I'd say that the features they could easily add this month might warrant a 1.2 or higher name (as the update would be more of a major release). This is especially true if the firmware is capable of securely hosting 3rd party applications (sandboxed) with signing.
 
Not sure what you mean but I'd say that the features they could easily add this month might warrant a 1.2 or higher name (as the update would be more of a major release). This is especially true if the firmware is capable of securely hosting 3rd party applications (sandboxed) with signing.

if 1.1.3 was only made to be kept inside apple and not released to the public ... would they still call it 1.1.3 and not something else...
 
So i have no idea how inside builds work .. but would they name it a real name (like 1.1.3) instead of some inside code name (like how the build number is a bunch of letters and numbers)

I supposed since we went from 1.0.x to 1.1.x that, yes, there is a potential that they will call it a somewhat major build and progress it to 1.2. Normally the x.x.X would only indicate a minor alteration. There really wasn't all that much of a change from 1.1.1 to 1.1.2.

Since there is supposed to be (if we believe the video) a major function change with the "Wiggles," drag and drop, potential cut and paste it would make sense that Apple may progress it to 1.2. It's certainly not a 2.0able change.
 
if 1.1.3 was only made to be kept inside apple and not released to the public ... would they still call it 1.1.3 and not something else...

Yes. It's also possible that this was a revision that missed it's release window.

All speculation I know but this is a rumour site :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.