What about when pictures get out-of-sync with the text?  New buttons
that aren't described, etc.  I think this is one of those things that
is better communicated human-to-human.  The pictures should be part of
a cohesive whole.  We should just update the screens manually.  They
don't change often or much, and now they're Theme-dependent anyway, we
can't really program a "correct" aesthetic.

On Fri, Nov 18, 2016 at 2:57 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Hi,
>
>     I'm stuck here in the stonestown Apple Store waiting to get my daughter's iPhone in for repair (had to reschedule because they need her Apple ID and password to disable find my iPhone but I had to wait until a friend could contact her for the info because...she doesn't have her iPhone, I do).  So I'm checking out the new MBP and surfing Squeak.org etc.  one thing I notice is ancient screen shots in documents on the wiki.  This isn't just because it's time consuming to rewrite the docs; it's also a manual process to generate the images.  It strikes me that we could automate deriving pictures of browsers etc, by using the vm command line to script opening a specific browser in an image and exporting an image.
>
> Wouldn't it be great if there was a github project that did this that one could check out and extend and would comprise both the set of scripts to generate the images and the generated images.  It would then be reasonably straight-forward to update the images when a new release would come out.  The images could be uploaded to some server so that web docs can refer to the most up-to-date images via a static URL.
>
> Student project anyone?
>
> _,,,^..^,,,_ (phone)
>