<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Jul 14, 2008 at 8:29 PM, Mikus Grinbergs <<a href="mailto:mikus@bga.com">mikus@bga.com</a>> 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 class="Ih2E3d">>>>> If, as is the current plan, multiple versions of<br>
</div>>>>> an activity can coexist on an XO, ...<br>
<div class="Ih2E3d">> Two use cases:<br>
> 1. I have a journal object. I want to choose which activity to open it with.<br>
> I am presented with a multilevel menu: the top level has all activities<br>
> which open the mime type, the next level has all major versions of those<br>
> activities, the next level minor versions, etc. If click without bothering<br>
> to move over to the sublevels, I get the default version from the sublevel<br>
> of my current menu, which is the starred version (if it exists) or the<br>
> highest version (applied recursively down the sublevels).<br>
<br>
</div>I'm sorry, but my mind boggles at the thought of a four-year old<br>
clicking on a Journal entry and being presented with a palette of<br>
seventeen different versions of 'TamTam' -- so that he may choose<br>
which of those versions is appropriate for whatever upgrade the<br>
adults had made to that XO last week.<br>
<font color="#888888"><br>
mikus<br>
</font><div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote><div><br>This is not, of course, the default behavior - if you just "click on a journal entry", it opens with whatever version created it, or the starred version (if the creator version is not marked as creating incompatible entries), whichever is more mature. All that logic happens with no need for human interaction (and yes, we need Glucose to understand something about versions for that to work).<br>
<br>Nevertheless, the behavior I described is my best understanding of the approximate consensus of <a href="http://wiki.laptop.org/go/User:Mstone/Bundle_commentary">several</a> <a href="http://wiki.laptop.org/go/User:Mstone/Commentaries/Bundles_2">discussions</a> (+2 more) I have had on IRC about this matter. I myself would (and did) advocate for more automatic updating, and no decision is set in stone; but no matter how automatic and smart we make things, we are going to have to choose at some point between having a manual fallback, or having some things break because we don't have a manual fallback. I'd rather have the fallback, and I think that if we do, we should be hiding it in heirarchical menus as much as possible (so that even if you DO need the fallback and even if you DO have 6 installed versions of TamTam, Glucose is at every moment hiding as many of them as possible until you deliberately, by hovering, ask it to show you more).<br>
<br>If you have a better idea of how Glucose should handle these issues, please share it. Simplifying assumptions are good, even if they're not 100% valid. <br></div></div></div>