Hi Jim:
That's fine. You don't have to use any feature you feel compromises your safety if ever they were to implement it. For me, at airports like SFO, I like the idea of being able to draw the taxi path on the Diagram. Since I'm not moving when I copy my taxi clearance, it's not a safety issue for me.
Rather, I think having a good path drawn out at an intimidating airport is a safety enhancement. I was simply thinking outside the box (perhaps way outside - but so did Steve Jobs) of how cool it would be if I could simply tap the intersections at the Controller reads them to me, and iFly would automagically trace out the path for me. Automation.
Actually, I envision it rubber banding on a mini "fight" plan. When the controller says "Taxi to Rwy 4R" you would begin by tapping at the departure end of 4R. A series of line segments figure their way from current position to Rwy 4R. (Like current car maps.) As the Controller clarifies (or tightens up) your taxi instruction, you tap where he says to turn. The line segments automagically rubber band to accommodate. (Recalculate.) The hardest part of the problem, as I see it, is when the controller gives you an intersection departure. (Hard because it's kind of in backward order and I'm not sure how iFly would be smart enough to redraw the end point.)
Whatever, car navigation seems able to do most of this already.
Of course, when iFly does voice recognition, understands the Ground Controller and draws out your taxi path, that will be even better. :-)