This repository was archived by the owner on Feb 5, 2025. It is now read-only.
This repository was archived by the owner on Feb 5, 2025. It is now read-only.
Groups should have some kind of location #4
Activity
maxrothman commented on Aug 7, 2014
Shouldn't events have locations instead?
nedbat commented on Aug 14, 2014
I thought of the group as a recurring event. So instead of having each event have a location, the group would have a location. Maybe that's not a good way to do it?
maxrothman commented on Aug 14, 2014
In that case, wouldn't groups need to have information to indicate when the next meeting is as well?
To devil's-advocate for a moment, meetup.com users are already familiar with the ideas of "groups" and "events", and using "group" to mean "recurring event" might be confusing.
nedbat commented on Aug 14, 2014
You make a good point. Let me think about that.
AlexFrazer commented on Sep 24, 2014
I am working on this now. However, google places seems to have a limit on the number of requests which could be made, and that limit is very small (200). I was thinking of having a database model which stored a google places json, but not sure if that is the best decision (I am but a lowly college student beginner).
Suggestions? Should I just keep the location model generic and without use of external libraries?
maxrothman commented on Sep 24, 2014
I think you're overcomplicating things. You can just link to google maps (or embed it), then the user is making the request and there's no request limit. Just store something you can use to make a google maps URL out of.
Here are some examples of valid google maps URLs:
Metadata
Metadata
Development
No branches or pull requestsIssue actions