You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, maybe it's just me but I feel that the entities. mechanics and wording in general do not match with my brain.
An adventure for me is something that is not just an alias to a location. It can be a thing in the past with a specific start and end date or it can be something I want to do some time in the future but may not know exactly when (and if). Examples: cycling from Germany to Portugal, visiting North Cape or traveling around the world.
A location is then is something I can visit during one or more adventures. That can be a single tree in a specific wood or it can be a whole continent and therefore be an area or a point. Example: Let's have New Zealand as a location (area) that I visited twice in the past (two different adventures) and may visit again in an upcoming adventure.
A trip is an adventure that took place. A trip contains locations, routes, photos, a journal, etc. There is probably enough overlap with adventure to omit this entity and have it merged. For me it is important to connect memories (photos and stuff) with a trip/adventure instead of a location.
What do you think? How can we make AdventureLog more flexible to different use cases and minds?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, maybe it's just me but I feel that the entities. mechanics and wording in general do not match with my brain.
An adventure for me is something that is not just an alias to a location. It can be a thing in the past with a specific start and end date or it can be something I want to do some time in the future but may not know exactly when (and if). Examples: cycling from Germany to Portugal, visiting North Cape or traveling around the world.
A location is then is something I can visit during one or more adventures. That can be a single tree in a specific wood or it can be a whole continent and therefore be an area or a point. Example: Let's have New Zealand as a location (area) that I visited twice in the past (two different adventures) and may visit again in an upcoming adventure.
A trip is an adventure that took place. A trip contains locations, routes, photos, a journal, etc. There is probably enough overlap with adventure to omit this entity and have it merged. For me it is important to connect memories (photos and stuff) with a trip/adventure instead of a location.
What do you think? How can we make AdventureLog more flexible to different use cases and minds?
Beta Was this translation helpful? Give feedback.
All reactions