On 07/08/2011 02:26 PM, Daniel Drake wrote:
On 15 June 2011 16:01, Esteban Bordón wrote:
This patch show the build number in the name page for first boot (see
attached file). It's very useful to test the correct massive flashing for
technical team.
I have a lot of experience handing out lapto
On Fri, Jul 08, 2011 at 01:26:40PM +0100, Daniel Drake wrote:
> On 15 June 2011 16:01, Esteban Bordón wrote:
> > This patch show the build number in the name page for first boot (see
> > attached file). It's very useful to test the correct massive flashing for
> > technical team.
>
> It may sound
On 15 June 2011 16:01, Esteban Bordón wrote:
> This patch show the build number in the name page for first boot (see
> attached file). It's very useful to test the correct massive flashing for
> technical team.
I have a lot of experience handing out laptops to our target first
time users (young c
On Fri, Jun 24, 2011 at 07:08:36PM +0200, Simon Schampijer wrote:
> I have been thinking about it some more - I am not a big fan of
> putting build information into the naming screen. This takes focus
> from it's purpose, people might not know what it means etc.
I don't think this will take focus,
On 06/20/2011 02:21 PM, Esteban Bordón wrote:
011/6/18 Sascha Silbe
Nice idea. As for the patch, I wonder why you use different code than
what's in extensions/cpsection/aboutcomputer/model.py. I'm not sure
whether importing or copying is the better option here, but different
code altogether de
011/6/18 Sascha Silbe
>
> Nice idea. As for the patch, I wonder why you use different code than
> what's in extensions/cpsection/aboutcomputer/model.py. I'm not sure
> whether importing or copying is the better option here, but different
> code altogether definitely isn't. We need to show the sam
Excerpts from Esteban Bordón's message of Wed Jun 15 17:01:55 +0200 2011:
> This patch show the build number in the name page for first boot (see
> attached file). It's very useful to test the correct massive flashing for
> technical team.
Nice idea. As for the patch, I wonder why you use differe
On Thu, Jun 16, 2011 at 09:12:26AM +0200, Simon Schampijer wrote:
> thanks for your patch. I would like to add the build information to
> the startup screen [1]. This gives you the information earlier when
> booting and does not only give you the information the first time.
Good, but Esteban's ide
On 06/15/2011 05:01 PM, Esteban Bordón wrote:
This patch show the build number in the name page for first boot (see
attached file). It's very useful to test the correct massive flashing for
technical team.
Hi Esteban,
thanks for your patch. I would like to add the build information to the
sta
On Wed, Jun 15, 2011 at 11:10:03PM -0400, Frederick Grose wrote:
> Once the particular "massive flashing" protocol has been tested and
> debugged, is the information really needed at that point?
The teams that do this don't have time to debug. They want to know
whether the install worked, by chec
On Wed, Jun 15, 2011 at 10:56:23PM -0400, Frederick Grose wrote:
> To keep with Sugar's design, it would be good to put the text in gray,
> and in the lower left corner, so as to de-emphasize it in relation to
> the Learner's primary activity on that screen,
Hmm, it's not that the Learner ever see
On Wed, Jun 15, 2011 at 10:56 PM, Frederick Grose wrote:
> On Wed, Jun 15, 2011 at 8:28 PM, James Cameron wrote:
>
>> On Wed, Jun 15, 2011 at 12:01:55PM -0300, Esteban Bord?n wrote:
>> > This patch show the build number in the name page for first boot (see
>> > attached file). It's very useful t
On Wed, Jun 15, 2011 at 8:28 PM, James Cameron wrote:
> On Wed, Jun 15, 2011 at 12:01:55PM -0300, Esteban Bord?n wrote:
> > This patch show the build number in the name page for first boot (see
> > attached file). It's very useful to test the correct massive flashing
> > for technical team.
>
> I
On Wed, Jun 15, 2011 at 12:01:55PM -0300, Esteban Bord?n wrote:
> This patch show the build number in the name page for first boot (see
> attached file). It's very useful to test the correct massive flashing
> for technical team.
I like it.
One small technical change though ...
> @@ -86,7 +86,20
This patch show the build number in the name page for first boot (see
attached file). It's very useful to test the correct massive flashing for
technical team.
Index: orig/window.py
===
--- orig.orig/window.py
+++ orig/window.py
@@ -8
15 matches
Mail list logo
