<div><span class="gmail_quote">On 8/6/08, <b class="gmail_sendername">Eben Eliason</b> <<a href="mailto:eben.eliason@gmail.com">eben.eliason@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Wed, Aug 6, 2008 at 7:10 AM, Build Announcer v2 <reinier@heeres.eu> wrote:<br>> --- Changes for sugar 0.81.8-2.20080806git0fc57309f3.olpc3 from 0.81.8-1.fc9 ---<br>
> + 7495 open cp software-updater on first boot after an update<br><br>I don't want this! I keep shouting about it and no one seems to be<br>listening! Home absolutely needs to be home base, especially after an<br>
update. I'm fine with tossing up a non-modal alert at boot which<br>prompts the user to update right away, with a button which reveals the<br>software update control panel module, but I'm NOT OK with anything<br>
which, unbeknownst to the user, flits them away to some other part of<br>the system without his/her consent.</blockquote>
<div> </div>
<div>+1</div>
<div> </div>
<div>Initially I was all for such first-boot features (especially with regard to G1G1 and the help-activity). But after thinking about Eben's arguments in both cases I agree that user should definitely see the home-view as the first thing when they boot the machine. Especially the Sugar-Control-Panel and its overlay above the home-view (which IIRC isn't used anywhere else in Sugar except for the Journal object chooser instead of the traditional file-choose dialogue) could be quite confusing.</div>
<div> </div>
<div>Cheers,</div>
<div>Christoph</div>
<div> </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">- Eben<br>_______________________________________________<br>Sugar mailing list<br><a href="mailto:Sugar@lists.laptop.org">Sugar@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/listinfo/sugar</a><br></blockquote></div><br><br clear="all"><br>-- <br>Christoph Derndorfer<br>co-editor, olpcnews<br>url: <a href="http://www.olpcnews.com">www.olpcnews.com</a><br>
e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a>