Staging talk:Debugging With Trace

Comments on Staging:Debugging With Trace -

DanRinkes said ...

 * The Trace use cases heading is a little difficult to differentiate between the Trace Debug Use Cases and Examples. Why is the Trace Use Cases content linked to, while the Trace debug Use Cases and Examples are contained completely in the page.  The headings seem to be on the same level, so this is confusing to a user.  Perhaps an introduction to what each section is should be contained on this page, and then the meat of the content should be on the linked page.  We have a Labeled Section Transclusion extension that will allow you to embed parts of one page in another.  See the details here.  http://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion
 * I think we can create an extension to embed the camtasia video directly into the wiki page, rather than having to open up another page to view it.
 * The camtasia videos are great, especially for beginners, but I think we still need text to explain the process. A camtasia video is not going to show up in a generated PDF.  Text can be translated to other languages using Google Translator.  The camtasia videos are of no user to Chinese users that are using the offline wiki because they don't have internet access.
 * Need links to ETBLIB and DSPTraceLib. This page is heavily viewed by CI customers who are familiar with DCILib.  There will be questions about the differences, the future support of DCILib.  These customers who are heavily invested in using DCILIB will need some
 * Where did all the info about trigger builders go? There should, at the very least be a link for users looking for AET information.  Somewhere there should be a link to AET_Logic
 * I've been pointing customers to this Article and pointing out how much information there is in it. I just sent the link to Cisco yesterday, as they were very interested in using trace.  I worry that on Monday, they're going to follow the link, and it's going to look like there is a lot less information there.
 * What about links to the Trace Limitations page? This like the Super Gap issue, and the SPLOOP issue are left completely out.
 * I felt like we had a nice document that someone could print as a .pdf and go off and find whatever they wanted to work with trace. Now, if a user merely prints a copy of the Debugging_With_Trace article, what do they actually have? Not enough to do too much.  They can manually navigate and add the list of all the linked pages and create a book, but still, they get none of the camtasia content.
 * Many users want to be able to have the instructions in front of them while they are trying to use trace. If you don't have 2 monitors, it's difficult to watch a video and use CCS at the same time.  And, also, what if there was one point that they wanted to look up?  It's much easier in a printed document that trying to find that location in a video.
 * I think this article might be better served as a new "Getting Started With Trace" article, rather than a reworked "Debugging with Trace" article. We can tweak the debugging with trace article, and maybe reformat a bit, but a wholesale change like this is not likely to be well received.  In the past 90 days, t"debugging with Trace" is in the top 20% as far as hits go.  That's a good thing!  Especially considering the fact that we're focused on such a small group of target users.  The top pages are ones like "Main Page", "XDS100", "Download CCS", which are of interest to a MUCH wider variety of users.  The users that do follow this page will likely be upset if it is re-architected in this way.

Dan Rinkes 23:42, 2 September 2010 (UTC)