rragan

I have written the whole of this section this evening. Look over it and provide feedback (or edit typos, bad grammar, etc.). I tried to cover the experience as it would be seen leading a newbie through the process.
http://www.cach.ly/help/index.php/Getting_Started_with_Cachly
Editorial note: I didn't realize how painful geocaching.com's limit of 3 caches a day could be until I randomly picked one, loaded the full details and discovered it had 5 DNF's in a row. One cache load wasted on one I'm not likely to find. Sigh!

Instances of Page and Left Arrow changed

I put together a simple "Table of Contents" for a modified possible structure for the document. It reflects the top few heading levels. Most of the pages currently stay the same but some material is moved around. Is this better, worse, .... Suggestions and feedback.
http://www.cach.ly/help/index.php/Structure

From a practical point if view it might be better to save you logs while out caching and when you get home go to the list in Pending Logs and look at each log again before submitting. 
I find that useful as I find I want to edit the message on a few caches, add some pictures and let my TBS visit a cache or two once I get home and have more time to consider the logs 

I think there is a question of audience that affects organization. New geocaching users likely want a hand holding tutorial. Folks coming from other apps or outgrowing geocaching.com want to know how you do X in Cachly. Finally, there is the reference document that covers everything about the app you might want to lookup. 

Currently this isn't part of the geocaching.com API that we use. Hoping it can be in the future!

I would just follow what Wikipedia would do. Which I think would be to not duplicate information but to link to it from other parts of the site.

Sure, that is how the DeepDive link in the Waypoints page gets to the Corrected Coordinates section on the How Tos page.
[[How Tos#Add a corrected coordinate to a Puzzle/Unknown Cache|More on corrected coordinates]]
e.g. [[Page Name#Section name on page|Link test]]

Good deal - added it and it seems to be working fine. 
http://www.cach.ly/help/index.php/Navigating_Around_the_App
 

Thank you!

I was assuming it would be internal. I guess looking at each beta changes would be one way and we wouldn't need a separate list. 

Sure. Will change it. 

Wiki changes are moderated/reviewed by Nic. Once he is comfortable you are a good guy, he can turn moderation off. Thanks for contributing. 

This is painfully slow.
I am rewriting the entire interface and background downloading for updating caches. This will be in the next beta.
I tested updating 1,000 full caches and got the following:
Basic Update: 3.8 seconds
Full Update: 39.8 seconds
It has been a while since I revisited the old code that is currently downloading/updating caches so it was time for a rewrite.

Find count is supported but find count today is also useful. Text like "5555 finds and find 5 today" become possible. Also an easy reminder to Cacher of how many finds so far. 

I dithered on my opinions on this one earlier. Having hiked for a 54 stage multi yesterday, I keenly felt the inability to spot other caches along the way to the next waypoint. Overall map view did not show the next waypoint of the multi and what opportunities might lie along the way. Getting back to the original multi to plot the current waypoint after diverting to find a nearby cache was not easy. 
I think what would have served is
a setting on global map view to you show all waypoints a way to highlight a waypoint so I could spot the currently sought one quickly in map view with context about what was nearby on the way to it. This suggests waypoints could have a small set of associated data like highlight and a note field to record info for multi step field puzzles Better coupling of a displayed Waypoint to its cache. E.g. Option on Waypoint press to open the waypoints screen of the parent to see it and other waypoints. I should be able to get from a waypoint to the parent Cache to do things like see the description, hint, etc. This becomes more important with all waypoints shown on map as it also helps to determine the cache the WP belongs to.  Sorry if this wandered off off into a longish list of Waypoint features but each step seemed to open up further needs. 
 
 

Recanting my comment. I really would appreciate having my log on a cache kept in the local DB. I realize it is not on the server but having it there is invaluable when you get a Phone A Friend plea for help. The log can trigger key memories. I would only put detailed info about the hide and container into a cache note lest I create a spoiler log. I only do that for some noteworthy ones though. That's when the log is handy. 

Thank you for the education. I had forgotten about the logging features as I usually don't cache with the fervor one does at a Mega. For Power Trail like caching with the right setup, a cache is logged by: Log This Cache and Send Now. You can't beat that. 

I default my log type to Found which, if I'm correctly following your steps, would cut the clicks in half.

Thanks. This is something that we have on the list for a future version.

One thing I would like to have as a feature in the app is to be able to have multiple offline lists on/active at the same time.

The TBScan app can OCR trackables, verify validity of scanned code and more. OCR is a hard problem. I've beta tested TBScan and watch it improve but it is a complex thing and you'll never get it fully accurate. I'm ok with a separate app devoted to that. 

Wow! That was fast. I just tried it in the new beta and I love it. Thanks

Sounds great. Just add a space after each chunk of text. I often use name plus code when sending info to someone else and many taps to generate otherwise. I'll use this for sure. Re-entering the view and first long press should clear the clip I guess. 

Once you have the final coordinates, add them as a waypoint and tap the Is Corrected Coordinate button. Save the waypoint. There will now be a red triangle on top of the cache icon so you can spot it. However, in Live view, the Geocaching.com API only returns caches based on published coordinates. You will still see the red triangle but only if the published Coords land in your search area. The displayed position will reflect the solved location. Offline lists always show the final Coords. I keep an offline list named "Solved" where I save all solved mystery caches. I can examine it and see what is in my Tour area easily.