I like Address Field as the code is clean and it focuses on doing one thing well using modern D7 best practices. I also like the new Countries module (http://drupal.org/project/countries) for similar reasons. I'd like to see both become the go-to modules for their problem space ala. Date.

My open ended question is how do you see Addresses relating to solutions such as Countries. There is minor overlap in that both list countries, which are taken from core's ISO list. Countries allows you to modify the list of available countries and makes Countries entities. Do you see any integration points here with Address Field should Countries be enabled? On similar grounds do you see value in Address Field providing a Forms API element for address fields or should fields be used in all cases?

Sorry if this is a bit open ended. I'm interested in the problem space and am watching how the D7 contrib space evolves to provide go-to solutions to these common problems.

Comments

Alan D.’s picture

Subscribe. (I'm the maintainer of the Countries module)

I'm not sure if there is any overlap with the existing Countries module. The simple enabled flag used by the Countries module is the integration point between the two modules, albeit a crude flag.

IE: This module uses country_get_list() to get the countries list and the country module alters this list to only include the enabled countries and change their text.

I've had a play at creating a regions sub-module (#1142410: Country regions), but this is very generic and doesn't conform to a simple single level country - region model that the addressfield module uses. As such, it is doesn't really overlap too much.

However, integration could be used to provide a rich autocomplete functionality to this module. For example if cities were added on top of the regional data, then an autocomplete could in theory prepopulate not only the city, but also the administrative region and country using a single action.

Damien Tournoud’s picture

Status: Active » Fixed

This discussion concluded that there is no real overlap.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.