<div dir="ltr">Woops, sent this from the wrong email address. Apologies if this gets double-posted, but certainly let me know how I can help with the remix.<br><br>Anne<br><br><div class="gmail_quote">On Thu, Sep 4, 2008 at 8:33 AM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">Let me know how I can help. <br><br>The %INCLUDE{manual.chapter}% code should work well here (allowing within-chapter nesting) and Adam Hyde can walk you through it. <br>
<br>As you point out, Seth, the special keys for views and Networking are good candidates for this type of remixing. I'd prioritize networking smoothness over the keyboard - seems like once users "get" the keyboard use for views, they don't have to be reminded of it much more, but that might just be me. :)<br>
<br>Thanks for all the energy here everyone. <br>Anne<div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote">On Thu, Sep 4, 2008 at 4:40 AM, adam hyde <span dir="ltr"><<a href="mailto:adam@flossmanuals.net" target="_blank">adam@flossmanuals.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">hey Seth,<br>
<br>
want to skype/irc?<br>
<br>
adam<br>
<br>
<br>
On Wed, 2008-09-03 at 23:29 -0400, Seth Woodworth wrote:<br>
> Adam,<br>
><br>
> I think that we're making a lot of progress here. Overall I am<br>
> amazingly happy with the quality of the documentation. I'm working<br>
> with our dev team going over sections, smoothing out some of the<br>
> technicalities. I'm also working with a few other volunteers to<br>
> really polish the text and formatting of some of the final sections.<br>
> It's really coming together. We're hoping to have our shipable-html<br>
> by Saturday.<br>
><br>
> But if we're going to get there we're going to need your help. The<br>
> next 50+ hours around here are going to be crunch time. We're<br>
> committed to finishing our end of the work by the end of the week.<br>
> We've been running into some issues, but I think we have a way to<br>
> smooth things out.<br>
><br>
> In the short term, we're having some issues in the extreme separation<br>
> of the XO hardware manual and the Sugar software manual. The problem<br>
> is that the chapters, as written, don't mix into a single whole<br>
> manual. The XO manual explains a good deal of the Sugar networking<br>
> system, but the good Network View diagrams are deep in the Sugar<br>
> manual. Also, the UI elements like the View Keys in the frame<br>
> directly relate to the keys on the top row of the keyboard. And it's<br>
> important in a well-structured manual to be able to really show the<br>
> connection between these two elements.<br>
><br>
> Some of the current chapters, as organized now, don't allow for this<br>
> to happen by chapter-remix. The important sections are much smaller<br>
> than that. We've picked out six or seven chapters from the current<br>
> sugar manual that we need to inject Hardware elements into directly.<br>
><br>
> Now we're very committed to the single-source concept. That's why the<br>
> manual has been kicking around FM since the start of the year. And it<br>
> makes continued sense for OLPC and Sugar to have somewhat separate<br>
> manuals. But in the very-short-term we need to try something a little<br>
> different.<br>
><br>
> If I'm understanding your tools correctly, the best way to facilitate<br>
> this is to create a fresh book for organization. Into this new book<br>
> we pull in around 6 chapters from the Sugar manual and most of the XO<br>
> manual. We take elements from the hardware sections, integrate them<br>
> into the Sugar chapters and generate the changed chapters we need, all<br>
> to be remixed into the overall OLPC: Sugar+XO output that we'll ship.<br>
><br>
> Come next week, after we produce our short term goal, we can work to<br>
> segregate out the hardware sections into chapters that flow better<br>
> with the Sugar narrative. Also, by looking at some of your export<br>
> tools, it looks possible to place some of the XO sections in Sugar in<br>
> <span id=>'s. That way they can easily be scripted to be pulled out<br>
> or included based on the export needs of a given manual. (ie, sugar<br>
> can dump the <span id=>'s that don't match what they want to export).<br>
><br>
> We're working on a very tight schedule here. Can we ask you to set up<br>
> this new manual right away? Things are going to be moving very<br>
> quickly tomorrow. We would also like if Adam Holt and I can get<br>
> twiki-admin, so we can publish our changes and make any remixes of the<br>
> TOC that might come up? This manual can sit on the back end,<br>
> non-public (or public) just so long as we can export new edits quickly<br>
> after we make them. I don't want to screw up the polished Sugar<br>
> manual that's sitting on the front of the site.<br>
><br>
> --Seth<br>
><br>
> Also, could we talk in the morning about your .css? I need to start<br>
> creating stand-alone navigation for our bundle.<br>
><br>
><br>
> On Wed, Sep 3, 2008 at 6:26 PM, adam hyde <<a href="mailto:adam@flossmanuals.net" target="_blank">adam@flossmanuals.net</a>><br>
> wrote:<br>
> hey Seth,<br>
><br>
> How are you thinking of doing the layout? You are doing this<br>
> by hand? We<br>
> have a nifty remix mechanism that will make your life a lot<br>
> easier...<br>
><br>
> adam<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Library mailing list<br>
> <a href="mailto:Library@lists.laptop.org" target="_blank">Library@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/library" target="_blank">http://lists.laptop.org/listinfo/library</a><br>
><br>
><br>
<br>
</blockquote></div><br><br clear="all"><br></div></div>-- <br>Anne Gentle<br>email: <a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a><br>blog: <a href="http://www.justwriteclick.com" target="_blank">www.justwriteclick.com</a><br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Anne Gentle<br>email: <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>blog: <a href="http://www.justwriteclick.com">www.justwriteclick.com</a><br>
</div>