Re: Unincorporated communities and Census Designated Places
Ron Johnson <ron.l.johnson <at> cox.net>
2015-08-01 23:38:38 GMT
On 08/01/2015 04:34 PM, Nick Hall
On 01/08/15 19:25, Ron Johnson wrote:
Before a search is carried out, you want a tree based on the default
place. That sound like a good idea.
What is a top level nested place?
I'm not sure that I fully understand your place selection.
How can a top-level place be nested?
What would you display if a city was selected as the default place?
Only the places *enclosed by* the city that match your search
Say I have two *different* places both named "100 Main St.":
"100 Main St." <- Footown <- Bar County, Texas <- USA
"100 Main St." <- Spaztown <- Fraggle County, Colorado <-
Without a default place (or... make "Earth" a Place that encloses
all Places that are currently top-level), a search for Name = "100
Main St." will return both of those places.
If the default place is Footown, then the same search would only
return the "100 Main St." that's enclosed by Footown.
Where would you want to display search results?
I've not explained myself well.
If a Default Place is set, then to the user, the Select Place window
would work *exactly* as it currently does, except that the program
would only search that part of the tree starting with the Default
If Earth were the (hidden to the user) top-level which
encloses all of the places that are currently the multiple top level
Places, then, searching (and displaying results from) any part of
the tree works the same.
Making Earth the real (but hidden) top level would genericize your
Places tree operations, and the Default Place would just be a
pointer to a node where you start walking the tree.
- Not setting a Default Place means that (internally) Earth is
the Default Place, and a search would display results just
as it does now (but what it *really* means, internally, is
"walk the tree starting at node /Earth/, displaying all results
- Setting (by definition, lower than "Earth") a new Default
Place (for example, /Bar County, Texas/ would... display results
just as it does now (but what it *really* means,
internally, is "walk the tree starting at node /Bar County,
Texas/", displaying all results under /Bar County, Texas/).
I'm assuming that there's some sort of directed graph that
maintains the tree structure, and you internally traverse that
graph when searching for places...
(Are you seeing my bolded text? Is nabble stripping it out of their
"Where it is a duty to worship the sun it is pretty sure to be a
crime to examine the laws of heat." Christopher Morley
Gramps-users mailing list
Gramps-users <at> lists.sourceforge.net