Well, unless someone is willing to finish that, let us not look back and slow down. :)<br><br>In any case the icons must be available from whoever designed them.<br>That is a great beginning. <br><br>Secondly, the screenshots of panels need to be annotated before posting (e.g. attach numbers that are explained in the text). I think I saw a German wiki for Blender like that.<br>
<br>I guess we will need OCR of each captured screen also, so that we can paste the text in a table and then just add a column to explain what each control does. That will finish the work much faster than having to look at each screenshot and enter all that text manually.<br>
<br>So we may not have lost much (if anything at all).<br><br>Let's do it!<br><br>-Regards,<br>Narayan<br><br><br><div class="gmail_quote">On Thu, May 19, 2011 at 11:10 AM, Tom M <span dir="ltr"><<a href="mailto:letterrip@gmail.com">letterrip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">speaking of bulk screenshots, ideasman i think had an intent to<br>
automatically capture every panel, subpanel, icon, etc. as indvidual<br>
screenshots automatically.<br>
<br>
That never seemed to happen.<br>
<br>
LetterRip<br>
<div><div></div><div class="h5"><br>
On Wed, May 18, 2011 at 9:20 PM, Raindrops From Sky<br>
<<a href="mailto:raindrops.fromsky@gmail.com">raindrops.fromsky@gmail.com</a>> wrote:<br>
> I would like to be in this team.<br>
><br>
> In addition to coordination, I can also author pages, take bulk screenshots<br>
> (so that others can focus on authoring), make charts to explain concepts,<br>
> and make short videos.<br>
><br>
> ***<br>
> If we think of this as a (sprint) project, then it would be relevant to look<br>
> for a "project charter" at this point:<br>
><br>
> How much freedom is given to the team?<br>
><br>
> Is this going to be strictly authoring exercise, or are we allowed to review<br>
> the suitability of platform (e.g. whether to use mediawiki)?<br>
> Are we allowed to review/edit the TOC for the User Manual?<br>
> Are we allowed to review/change the template for wiki?<br>
><br>
> What are the constraints and scope of work?<br>
><br>
> What are the things that are already fixed; and so must not be changed (e.g.<br>
> wiki structure, authoring rules)<br>
><br>
> People with defined authorities in specific areas.<br>
> (e.g. what the webmasters are authorized for)<br>
> Existing resources: People who are already part of the team; and how they<br>
> would like to contribute (authoring, screenshots, illustrations, videos,<br>
> etc.)<br>
> People who are going to provide infrastructural support to the coordination<br>
> team (in setting up web pages, writing scripts, configuring modules)<br>
><br>
> ***<br>
> IMHO videos would be an important medium for education in future. In that<br>
> context, a new version of Wink (designed for HTML 5) is under development. I<br>
> can get new features developed specifically for Blender wiki.<br>
><br>
> Thanks.<br>
><br>
> Regards,<br>
> Narayan<br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> Bf-docboard mailing list<br>
> <a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
><br>
><br>
_______________________________________________<br>
Bf-docboard mailing list<br>
<a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-docboard</a><br>
</div></div></blockquote></div><br>