<br><br><div class="gmail_quote">On Mon, Jul 14, 2008 at 7:47 PM, Benjamin M. Schwartz <<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div class="Ih2E3d">Jameson "Chema" Quinn wrote:<br>
| It is desirable for Sugar to be able to compare versions and<br>
| guess which one is newer.<br>
<br>
</div>"Newer" means "more recent". If this capability is important to you, then<br>
we may simply include a datestamp in each bundle, separate from the<br>
version. However, I do not know of any planned Sugar feature that would<br>
require the ability to determine which bundle was created most recently.</blockquote><div><br></div><div>I'm not sure that has to be what we mean by "newer", and if it is, we need to find a better word. Dates are *not* the criteria we want for newness. Code maturity is closer to the intended meaning, and I think is the newness that Jameson is also referring to.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d"><br>
| If, as is the current plan, multiple versions of<br>
| an activity can coexist on an XO, it is reasonable to want sugar to present<br>
| these in some sane order, and possibly give hints and/or aid if the user<br>
| wants to update and/or garbage collect. Otherwise, we might as well just be<br>
| using activity hash, which can be calculated without being explicitly<br>
| included in <a href="http://activity.info" target="_blank">activity.info</a>.<br>
<br>
</div>I favor including a version string with every bundle. I favor displaying<br>
this string in places where it is needed to disambiguate multiple versions<br>
of an Activity. I'm merely suggesting that the system not attempt to<br>
parse it.<br>
<br>
You mention ordering. The Journal designs have long called for all<br>
columns to be sorted, with the user selecting the order of sorting<br>
precedence. One intermediate position would be for the Version column to<br>
be sorted according to a best-effort ordering that attempts to do<br>
something sane when faced with any of the common version string conventions.<br>
<div class="Ih2E3d"></div></blockquote><div><br></div><div>I guess the point here is that performing intelligent string comparisons on several of these schemes requires parsing the string. ;)</div><div><br></div><div>- Eben</div>
<div> </div></div>