Distinguishing projects: Addresses from Location
karunadave - August 27, 2008 - 14:26
| Project: | Addresses |
| Version: | 6.x-1.0-alpha2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | brmassa |
| Status: | closed |
Jump to:
Description
Hi
I am wondering what distinguishes this project from the Location project, why I would better choose one over the other. Are the feature sets distinct enough to support two separate development streams?
Cheers
-Dave
#1
Dave,
well, i was a Location module developer (800+ commits), but the team and i had some differences about the project, so i forked. The differences are:
* Addresses focus primarily on physical addresses. Location has this AND geocoding. Its important when you run a e-Commerce site or other site that only need address and you dont want to have download updates to maintain geocoding and mapping.
* Addresses has an API that allows other modules to add new address's fields, like longitude/latitude, map, phone. Location doesnt.
* Addresses has both user and node/cck addresses. Location doesnt.
* Addresses has (only and by design) Drupal 6 code. Location has a D5 and will be ported in the future to D6.
* Addresses has 65.88 KB. Locations has 1.63 MB.
* Addresses export ALL data to Views. Location doesnt.
* Addresses DOESNT have (yet) any geocoding and mapping integration. I will do this till next year. If you need today, use Location. If you need today AND in a D6 site, there is no solution!
* Location is much more used than Addresses and has much more related modules.
regards,
massa
#2
Automatically closed -- issue fixed for two weeks with no activity.