On Tue, 23 Oct 2007, Jason Winningham wrote: > > *) DATABASE: The initial database is probably going to be > > PostgreSQL with PostGIS extensions. > > I'll have to admit I'm a bit torn on this one - I like to keep things > simple, and IMO xastir's fairly large number of external support > packages required are a weak point. On the other claw, if a GIS- > aware database results in performance and features worth the effort, > then bring it on.
For some of the handheld devices we need a different back-end, so berkeley db files or SQLite might be the way to go there. > I wouldn't mind seeing a native Mac OS X port (is that Aqua?). Yes, let's keep that in mind as well. > 1), and the two versions are incompatible! This is a serious > management headache, and something that should not be inflicted on > end users. Yep. I'm all for stability and less dependencies. > some of us with > some processing horsepower and storage could convert to the xastir > internal format and distribute those converted maps for folks who > don't want to do a "full" build. We could also allow for distributed map databases, where the users could get their vector or raster maps via external servers. > Another worthy goal would be to allow for binary distributions. I > know this can get ugly, but it will increase the user base (and > hopefully the developer base along with it). Yep. I'm already distributing SuSE RPM's and LSB binaries. I used to be against distributing binaries for a variety of reasons, but many people want them. -- Curt, WE7U: <www.eskimo.com/~archer/> XASTIR: <www.xastir.org> "Lotto: A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U The world DOES revolve around me: I picked the coordinate system! _______________________________________________ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir