Talk:Transport Toolbar

Peter 25Nov14: The red-bordered image (as per Bill's suggestion( will either need to be implemented or removed.
 * Gale 26Nov14: I think the red-bordered image is un-necessary given we have Toolbars_red-boxed_in_context . Why not just link the original image to Toolbars_red-boxed_in_context?
 * Peter 26Nov14: We are trialling the red-boxed image here to see what it looks like as Bill said he might prefer to avoid having the Toolbars_red-boxed_in_context page by having in context images on each Toolbar page. The questions are a) do we like the look of the red-bordered image on the Xxx Toolbar pages and b) would this way also fulfill Koz' original request from the email thread that kicked all this off. I can live  with a) quite happily, I rather like the context on the Xxxx Toolbar page.  For b) I suspect the answer is yes - in fact it's probably better than having Toolbars_red-boxed_in_context as it provided the context followed by the detail of the Toolbar. I would vote +1 for Bill's suggestion.
 * Peter 27Nov14: Following feedback from Gale in the related Forum thread I have removed the trialled red-bordered image - but I have made the toolbar image link to the in-context page.
 * Gale 27Nov14: I did see the point that this could replace Toolbars_red-boxed_in_context but it would have been too confusing without having original and context image plus extra text. I am still (just about) OK with Toolbars_red-boxed_in_context but (yet again) I would suggest the supposed "problem" of context is a problem of helping less able users on the Forum. Because this is not a problem in the Manual (now we have a context image on Toolbars Overview), Toolbars_red-boxed_in_context looks odd/pointless. We could just as easily store these context images in the Forum, and not create pages for the sake of it in the Manual.
 * Peter 27Nov14: Personally I really do see the point of the red-boxed in-context page. It is not just "a Forum issue" - one of the key target audiences for this Manual is Newbies and they need all the help they can get with the fairly complex GUI that we now have.  Furthermore I, personally, would prefer to maintain such images here in the Manual where we operate the P1/P2 schema to note and manage important GUI changes.  So my vote is +1 for retaining it.
 * Gale 27Nov14: We could still have a page like Linked but for images that are linked. I suggested on Toolbars red-boxed in context that to reduce the oddity we could have a thumbmail context image on each toolbar's page linking to the full-sized image and not to a page containing only an image. The image would be embedded in the Forum reply (much better for naive users than giving them a link they very likely won't click). We still give them a link to the actual Manual page that has useful content, and then they don't have to find the link on the page for the image to the page that actually has the content.
 * Peter 27Nov14: Having just seen that Leland had removed his "rack" from the Edit Toolbar and realized that many images would need to be updated I am coming round to the idea of losing the Toolbars red-boxed in context page in favour of an annotated green-boxed top tooldock image or "Toolbars Overview", not least because we'll have the work to do all over again once 2.1.0 is released and the rack returns for the 2.1.1 alphas.
 * Bill 27Nov2014: I'm not concerned about the work required to re-do the in-context images for 2.1.1. It's just that I really don't like the in-context page as currently implemented, and as I've commented on that page. I could live with a separate in-context page for each toolbar that has nothing but the image and a link back to the toolbar's page. That way users could see the toolbar in context without the explosion of red-boxed toolbar images (it will be crystal clear where that specific toolbar lives), we could like to each of those pages in the forum if required and once a forum user goes to that page they have a link to the toolbar's main page.
 * Peter 27Nov14: +1 to Bill's proposal. That was the way I was going originally but thought at the time that a consolidated page might have got better acceptance - should've stuck to my original plan ...   I will do some work on this tomorrow.