I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list
Activity versions that were *older* than those listed for plain
G1G1.
That's exactly as it is supposed to work. G1G1 lists dev versions,
G1G1/8.2 the stable versions tested with 8.2.
I did say 'o.k.' to this explanation
On Sat, Jan 10, 2009 at 8:15 AM, Mikus Grinbergs mi...@bga.com wrote:
WHERE are they supposed to look to determine whether a newer
version of an Activity is available for their (e.g., 657) builds ?
[Their builds are __older__ than 8.2.]
Unfortunately, we do not have any page set up for this,
Daniel Drake wrote:
On Sat, Jan 10, 2009 at 8:15 AM, Mikus Grinbergs mi...@bga.com wrote:
WHERE are they supposed to look to determine whether a newer
version of an Activity is available for their (e.g., 657) builds ?
[Their builds are __older__ than 8.2.]
For 8.1,
On 10.01.2009, at 12:53, S Page wrote:
If the activity developer has somehow learned how to update activity
versions (again I ask *is this documented anywhere?!*)
The canonical documentation AFAIK is the update_url section of
the .info file in bundles:
Mikus Grinbergs wrote:
I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list
Activity versions that were *older* than those listed for plain
G1G1.
That's exactly as it is supposed to work. G1G1 lists dev versions,
G1G1/8.2 the stable versions tested with 8.2.
I second... on the idea of checking for network, before putting up the
'software update' dialog box. It certainly annoys me to no end, when my
network needs a manual key and the dialog box covers over the network view
so I can't connect to my access point.
Or even another idea, is not showing
On Thu, Dec 25, 2008 at 6:42 AM, Mikus Grinbergs mi...@bga.com wrote:
The software update facility assumes that a connection to the
network is already available when it gets to run. If conditions are
such that the network connection has *not* been set up when booting
completes, should the
The software update facility assumes that a connection to the
network is already available when it gets to run. If conditions are
such that the network connection has *not* been set up when booting
completes, should the action bar to request software update still
be automatically presented
On 07.01.2009, at 18:31, Mikus Grinbergs wrote:
I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list
Activity versions that were *older* than those listed for plain
G1G1.
That's exactly as it is supposed to work. G1G1 lists dev versions,
G1G1/8.2 the stable versions tested with
I have seen the wiki.laptop.org/go/Activities/G1G1/8.2 page list
Activity versions that were *older* than those listed for plain
G1G1.
That's exactly as it is supposed to work. G1G1 lists dev versions,
G1G1/8.2 the stable versions tested with 8.2.
o.k.
My intuitive thinking (from the
On Thu, Dec 25, 2008 at 1:42 AM, Mikus Grinbergs mi...@bga.com wrote:
Visited a friend, and helped him install a new build in his XO. The
first time the new build completed booting, he was presented with an
action bar (to request software update) near the top of Home View.
It so happened
If your friend had waited, (while the xo first looks for a mesh, three times,
then connects wifi), then hits 'try again' the updater would work. Is there
a way to set the default for what the xo looks for to connect with on start
up? After booting, if I go in Neighborhood view and select my
On Tue, Jan 6, 2009 at 9:55 PM, genesee genesee@gmail.com wrote:
If your friend had waited, (while the xo first looks for a mesh, three times,
then connects wifi), then hits 'try again' the updater would work. Is there
a way to set the default for what the xo looks for to connect with on
Visited a friend, and helped him install a new build in his XO. The
first time the new build completed booting, he was presented with an
action bar (to request software update) near the top of Home View.
It so happened that the XO had not automatically connected to my
friend's wireless AP -
14 matches
Mail list logo
