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
Problem statement:
In .su we have up to 4-5 blocks of different description related to the cache. For example: Area Description (copy-paste from wikipedia about the cityseeing stuff near the cache or some history), Cache Description (general description related to finding cache, i.e. steps necessary, questions and so on), Virtual Question (even for Traditional caches we may have virtual question) and Traditional description (how to find the box)
So when all of them are put together, it makes some mess. That's why I introduced blocks, so description is now separated.
I'm not sure how applicable is it for other services, but if there is some similar pattern on other websites, feel free to reuse this approach.
The text was updated successfully, but these errors were encountered:
Interesting.
At the moment I don't think any of the other services have such thing.
From OC I do know only the support of different languages...but I would rather not use such blocks to show all of them but just match to the device language (another open issue AFAIR).
gc.com had (*) short description and description fields. The names of those fields are a little misleading, as you can enter everything you like, not necessarily a short description. Only the length of the first field is limited.
(* Those fields are still available for older caches, but newly created caches (starting somewhere in 2017, IIRC) only get a single description field.)
See commit cb588ff for SU.
Problem statement:
In .su we have up to 4-5 blocks of different description related to the cache. For example: Area Description (copy-paste from wikipedia about the cityseeing stuff near the cache or some history), Cache Description (general description related to finding cache, i.e. steps necessary, questions and so on), Virtual Question (even for Traditional caches we may have virtual question) and Traditional description (how to find the box)
So when all of them are put together, it makes some mess. That's why I introduced blocks, so description is now separated.
I'm not sure how applicable is it for other services, but if there is some similar pattern on other websites, feel free to reuse this approach.
The text was updated successfully, but these errors were encountered: