[Xastir-dev] A likely direction?

[Jason KG4WSV]

On Tue, Aug 17, 2010 at 3:40 PM, Curt, WE7U <curt.we7u at gmail.com> wrote:
> Any further comments on this thread?


I think Qt is a good way to go, but I think I've made that point before.

My concern with Marble would be the dependencies and the performance
on slower devices (e.g. ARM systems, etc).

Are there other mapping options?  Would something like the rendering
engine from tangoGPS be a viable option?

I have wondered at the usefulness of porting the non-mapping part of
xastir to Qt, leaving the existing map rendering in place.  Would
there be any advantage to such a split, as opposed to a fresh start?

We're planning another go with an xastir V2 project in our software
engineering course in the spring.  I learned a great deal about how
_not_ to specify requirements for the project. :|

-Jason
kg4wsv