I'm trying to come up with a database and schema for a Qt APRs client
based on xastir. It's technically not a port, although the intent is
to offer it as an example xastir V2.
I'm vague on the differences between standard and spatially enabled
SQL databases, especially on the user interface
On Mon, Jan 25, 2010 at 12:13 PM, Curt, WE7U curt.w...@gmail.com wrote:
As I understand it, and my understanding is pretty iffy here, the
spatially-enabled databases add extra functions for doing searches
based on latitude/longitude bounding boxes.
That is my (incredibly limited)
On Mon, 25 Jan 2010 10:31:09 -0600
Jason KG4WSV kg4...@gmail.com wrote:
I'm vague on the differences between standard and spatially enabled
SQL databases, especially on the user interface side. If it is
implemented in standard postgres will I have trouble switching to
postGIS?
Spatially
On 01/25/2010 11:51 AM, Jason KG4WSV wrote:
On Mon, Jan 25, 2010 at 12:13 PM, Curt, WE7U curt.w...@gmail.com wrote:
As I understand it, and my understanding is pretty iffy here, the
spatially-enabled databases add extra functions for doing searches
based on latitude/longitude bounding boxes.
Separating the gui and backend completely would go a long way toward making
it more portable for sure. I've been thinking about android apps lately.
One can build libraries in c but the gui must be written in java or webkit
(html/js). So, gui separation may be more useful/interesting than just
