From martin at ohanlonweb.com  Wed Dec  2 10:45:19 2015
From: martin at ohanlonweb.com (Martin O'Hanlon)
Date: Wed, 2 Dec 2015 15:45:19 +0000
Subject: [Microbit-Python] Bluetooth Access?
In-Reply-To: <CANw+MzkiFfZ5Ek_-PQAb0=K0vC11VfV96-Erd3htGYfSzvDnzA@mail.gmail.com>
References: <CAD64x+bZvh-BC327KgKQy1cEu9isxmbcwboUj8XKs62BmFmYtQ@mail.gmail.com>
 <565C5886.6080302@ntoll.org>
 <CANw+MzkiFfZ5Ek_-PQAb0=K0vC11VfV96-Erd3htGYfSzvDnzA@mail.gmail.com>
Message-ID: <CAD64x+Y2eVMRhPNUWv6SiGWNfFwLdYYN+wux=pyAXatU8uEjiA@mail.gmail.com>

Damien, Interestingly Im not sure what Im interested in! I was just looking
for project inspiration in the specs, saw Bluetooth and thought "if I could
use that - I could probably create something interesting".

I like the idea of a portable BLE beacon, announcing your presence to other
BLE devices with a Hi.

Martin

On 30 November 2015 at 14:38, Damien George <damien.p.george at gmail.com>
wrote:

> Martin, what BLE features are you interested in?
>
> As Nicholas said, MicroPython can't currently expose the underling BLE
> features.  It's something we are working on!
>
> On Mon, Nov 30, 2015 at 2:09 PM, Nicholas H.Tollervey <ntoll at ntoll.org>
> wrote:
> > Hi Martin,
> >
> > The answer are:
> >
> > * No you can't yet. This is because BLE imposes memory constraints that
> > make it hard to use Python (apparently the BLE stack takes up 12k of the
> > 16k RAM).
> >
> > * Damien has a genius plan for how we might get around this. I'll let
> > him describe it.
> >
> > * As far as I can tell, there's not a lot you can usefully do with BLE
> > *right now* - given some onerous flash memory constraints that we've
> > already exceeded you could re-flash the device.
> >
> > Sorry. :-(
> >
> > N.
> >
> > On 30/11/15 14:00, Martin O'Hanlon wrote:
> >> Can I access the Bluetooth functions on the MicroBit? If I can, how can
> >> I? If I cant, could I?
> >>
> >> --
> >>
> >> Blog - www.stuffaboutcode.com <http://www.stuffaboutcode.com>
> >>
> >> Twitter - @martinohanlon
> >> <http://twitter.com/intent/user?screen_name=martinohanlon>
> >>
> >>
> >>
> >> _______________________________________________
> >> Microbit mailing list
> >> Microbit at python.org
> >> https://mail.python.org/mailman/listinfo/microbit
> >>
> >
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>



-- 

Blog - www.stuffaboutcode.com

Twitter - @martinohanlon
<http://twitter.com/intent/user?screen_name=martinohanlon>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151202/4df561f4/attachment.html>

From mschafer at wireframe.biz  Thu Dec  3 02:44:29 2015
From: mschafer at wireframe.biz (Mark Schafer)
Date: Thu, 3 Dec 2015 20:44:29 +1300
Subject: [Microbit-Python] building a branch
Message-ID: <565FF2DD.8090305@wireframe.biz>

I'm having difficulty getting a branch to compile to a hex.

1. Ive got the https://github.com/bbcmicrobit/micropython cloned locally

2. I've done a "git checkout neopixel" to get the neopixel branch current
     - (There are only two branches: Master and neopixel) "git branch 
--list"
     - I've verified that the file modneopixel.cpp is in the source 
folder. So pretty sure I have correct branch.

3. I've built using yotta:
     - yt target bbc-microbit-classic-gcc-nosd
     - yt up
     - yt build

4. The resulting file, as indicated in the readme, is in:
     - build/bbc-microbit-classic-gcc-nosd/source/
     - as a hexfile

5. The instructions say to run "make" to add any changed qstrs
     - the resulting hex is in build/firmware.hex.
     - I've tried "make" and also "make -B", both initiated from the 
micropython directory

When I load this hex onto the Microbit. I don't see the neopixel module.
     - in the neopixel branch there is an additional file called 
modneopixel.cpp which exposes the neopixel object
     - so it should be visible.
     - No errors are shown on screen during the compile phases.


Can someone with more experience indicate which step in the process I 
have not done ?
Or how I might check further to see where problem lies ?
Thanks, Mark...

From ntoll at ntoll.org  Thu Dec  3 03:33:19 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Thu, 3 Dec 2015 08:33:19 +0000
Subject: [Microbit-Python] building a branch
In-Reply-To: <565FF2DD.8090305@wireframe.biz>
References: <565FF2DD.8090305@wireframe.biz>
Message-ID: <565FFE4F.4030706@ntoll.org>

Hi Mark,

Could you commit your work on the neopixel branch and push it to GitHub?
That way any of us will be able to recreate your local context and poke
it with a proverbial stick.

Alternatively, if you don't want to fanny-anny around with GitHub you
could send us the patch.diff file you'll get from running this command
on your neopixel branch:

git diff neopixel master > patch.diff

Hope this helps!

Nicholas.

On 03/12/15 07:44, Mark Schafer wrote:
> I'm having difficulty getting a branch to compile to a hex.
> 
> 1. Ive got the https://github.com/bbcmicrobit/micropython cloned locally
> 
> 2. I've done a "git checkout neopixel" to get the neopixel branch current
>     - (There are only two branches: Master and neopixel) "git branch
> --list"
>     - I've verified that the file modneopixel.cpp is in the source
> folder. So pretty sure I have correct branch.
> 
> 3. I've built using yotta:
>     - yt target bbc-microbit-classic-gcc-nosd
>     - yt up
>     - yt build
> 
> 4. The resulting file, as indicated in the readme, is in:
>     - build/bbc-microbit-classic-gcc-nosd/source/
>     - as a hexfile
> 
> 5. The instructions say to run "make" to add any changed qstrs
>     - the resulting hex is in build/firmware.hex.
>     - I've tried "make" and also "make -B", both initiated from the
> micropython directory
> 
> When I load this hex onto the Microbit. I don't see the neopixel module.
>     - in the neopixel branch there is an additional file called
> modneopixel.cpp which exposes the neopixel object
>     - so it should be visible.
>     - No errors are shown on screen during the compile phases.
> 
> 
> Can someone with more experience indicate which step in the process I
> have not done ?
> Or how I might check further to see where problem lies ?
> Thanks, Mark...
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151203/9bbec514/attachment.sig>

From mschafer at wireframe.biz  Thu Dec  3 03:50:05 2015
From: mschafer at wireframe.biz (Mark Schafer)
Date: Thu, 3 Dec 2015 21:50:05 +1300
Subject: [Microbit-Python] building a branch
In-Reply-To: <565FFE4F.4030706@ntoll.org>
References: <565FF2DD.8090305@wireframe.biz> <565FFE4F.4030706@ntoll.org>
Message-ID: <5660023D.5000306@wireframe.biz>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151203/f5c65fe7/attachment.html>

From ntoll at ntoll.org  Thu Dec  3 03:54:42 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Thu, 3 Dec 2015 08:54:42 +0000
Subject: [Microbit-Python] building a branch
In-Reply-To: <5660023D.5000306@wireframe.biz>
References: <565FF2DD.8090305@wireframe.biz> <565FFE4F.4030706@ntoll.org>
 <5660023D.5000306@wireframe.biz>
Message-ID: <56600352.5080607@ntoll.org>

Apologies, my misunderstanding.

I guess this is one for Damien since he was the last person to commit to
that branch.

:-/

N.

On 03/12/15 08:50, Mark Schafer wrote:
> its unmodified from the repo
> 
> On 12/3/2015 9:33 PM, Nicholas H.Tollervey wrote:
>> Hi Mark,
>>
>> Could you commit your work on the neopixel branch and push it to GitHub?
>> That way any of us will be able to recreate your local context and poke
>> it with a proverbial stick.
>>
>> Alternatively, if you don't want to fanny-anny around with GitHub you
>> could send us the patch.diff file you'll get from running this command
>> on your neopixel branch:
>>
>> git diff neopixel master > patch.diff
>>
>> Hope this helps!
>>
>> Nicholas.
>>
>> On 03/12/15 07:44, Mark Schafer wrote:
>>> I'm having difficulty getting a branch to compile to a hex.
>>>
>>> 1. Ive got the https://github.com/bbcmicrobit/micropython cloned locally
>>>
>>> 2. I've done a "git checkout neopixel" to get the neopixel branch current
>>>     - (There are only two branches: Master and neopixel) "git branch
>>> --list"
>>>     - I've verified that the file modneopixel.cpp is in the source
>>> folder. So pretty sure I have correct branch.
>>>
>>> 3. I've built using yotta:
>>>     - yt target bbc-microbit-classic-gcc-nosd
>>>     - yt up
>>>     - yt build
>>>
>>> 4. The resulting file, as indicated in the readme, is in:
>>>     - build/bbc-microbit-classic-gcc-nosd/source/
>>>     - as a hexfile
>>>
>>> 5. The instructions say to run "make" to add any changed qstrs
>>>     - the resulting hex is in build/firmware.hex.
>>>     - I've tried "make" and also "make -B", both initiated from the
>>> micropython directory
>>>
>>> When I load this hex onto the Microbit. I don't see the neopixel module.
>>>     - in the neopixel branch there is an additional file called
>>> modneopixel.cpp which exposes the neopixel object
>>>     - so it should be visible.
>>>     - No errors are shown on screen during the compile phases.
>>>
>>>
>>> Can someone with more experience indicate which step in the process I
>>> have not done ?
>>> Or how I might check further to see where problem lies ?
>>> Thanks, Mark...
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2016.0.7227 / Virus Database: 4477/11101 - Release Date: 12/02/15
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151203/81cf89db/attachment.sig>

From mschafer at wireframe.biz  Thu Dec  3 03:59:13 2015
From: mschafer at wireframe.biz (Mark Schafer)
Date: Thu, 3 Dec 2015 21:59:13 +1300
Subject: [Microbit-Python] building a branch
In-Reply-To: <56600352.5080607@ntoll.org>
References: <565FF2DD.8090305@wireframe.biz> <565FFE4F.4030706@ntoll.org>
 <5660023D.5000306@wireframe.biz> <56600352.5080607@ntoll.org>
Message-ID: <56600461.9080606@wireframe.biz>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151203/09b3ac48/attachment-0001.html>

From peter.inglesby at gmail.com  Thu Dec  3 04:27:11 2015
From: peter.inglesby at gmail.com (Peter Inglesby)
Date: Thu, 3 Dec 2015 09:27:11 +0000
Subject: [Microbit-Python] building a branch
In-Reply-To: <56600461.9080606@wireframe.biz>
References: <565FF2DD.8090305@wireframe.biz> <565FFE4F.4030706@ntoll.org>
 <5660023D.5000306@wireframe.biz> <56600352.5080607@ntoll.org>
 <56600461.9080606@wireframe.biz>
Message-ID: <CAENJrPkyfC-0AL62P+hHXzfkiEgTHi3vBhvQrAvCR9_G3vniaw@mail.gmail.com>

Hi Mark,

It looks like the neopixel module is missing from the list of modules in
mpconfigport.h
<https://github.com/bbcmicrobit/micropython/blob/neopixel/inc/microbit/mpconfigport.h>.
If you copy and adapt the references to `love_module`, you should get
something that you can import.

Hope that helps,

Peter.


On 3 December 2015 at 08:59, Mark Schafer <mschafer at wireframe.biz> wrote:

> any pointers on how to approach debugging this.
> I can find the .h and .c neopixel files in inc and lib. As well as the
> modneopixel.cpp
> All seems properly linked and the modneopixel.cpp seems well formed.
>
> I don't want Damien to have to do more work here.
> I want some pointers to how to approach it - maybe a similar approach has
> been used in another set of files ?
>
> Mark...
>
>
> On 12/3/2015 9:54 PM, Nicholas H.Tollervey wrote:
>
> Apologies, my misunderstanding.
>
> I guess this is one for Damien since he was the last person to commit to
> that branch.
>
> :-/
>
> N.
>
> On 03/12/15 08:50, Mark Schafer wrote:
>
> its unmodified from the repo
>
> On 12/3/2015 9:33 PM, Nicholas H.Tollervey wrote:
>
> Hi Mark,
>
> Could you commit your work on the neopixel branch and push it to GitHub?
> That way any of us will be able to recreate your local context and poke
> it with a proverbial stick.
>
> Alternatively, if you don't want to fanny-anny around with GitHub you
> could send us the patch.diff file you'll get from running this command
> on your neopixel branch:
>
> git diff neopixel master > patch.diff
>
> Hope this helps!
>
> Nicholas.
>
> On 03/12/15 07:44, Mark Schafer wrote:
>
> I'm having difficulty getting a branch to compile to a hex.
>
> 1. Ive got the https://github.com/bbcmicrobit/micropython cloned locally
>
> 2. I've done a "git checkout neopixel" to get the neopixel branch current
>     - (There are only two branches: Master and neopixel) "git branch
> --list"
>     - I've verified that the file modneopixel.cpp is in the source
> folder. So pretty sure I have correct branch.
>
> 3. I've built using yotta:
>     - yt target bbc-microbit-classic-gcc-nosd
>     - yt up
>     - yt build
>
> 4. The resulting file, as indicated in the readme, is in:
>     - build/bbc-microbit-classic-gcc-nosd/source/
>     - as a hexfile
>
> 5. The instructions say to run "make" to add any changed qstrs
>     - the resulting hex is in build/firmware.hex.
>     - I've tried "make" and also "make -B", both initiated from the
> micropython directory
>
> When I load this hex onto the Microbit. I don't see the neopixel module.
>     - in the neopixel branch there is an additional file called
> modneopixel.cpp which exposes the neopixel object
>     - so it should be visible.
>     - No errors are shown on screen during the compile phases.
>
>
> Can someone with more experience indicate which step in the process I
> have not done ?
> Or how I might check further to see where problem lies ?
> Thanks, Mark...
> _______________________________________________
> Microbit mailing listMicrobit at python.orghttps://mail.python.org/mailman/listinfo/microbit
>
>
>
> _______________________________________________
> Microbit mailing listMicrobit at python.orghttps://mail.python.org/mailman/listinfo/microbit
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7227 / Virus Database: 4477/11101 - Release Date: 12/02/15
>
>
>
> _______________________________________________
> Microbit mailing listMicrobit at python.orghttps://mail.python.org/mailman/listinfo/microbit
>
>
>
> _______________________________________________
> Microbit mailing listMicrobit at python.orghttps://mail.python.org/mailman/listinfo/microbit
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7227 / Virus Database: 4477/11101 - Release Date: 12/02/15
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151203/9d1b6653/attachment.html>

From damien.p.george at gmail.com  Thu Dec  3 05:07:49 2015
From: damien.p.george at gmail.com (Damien George)
Date: Thu, 3 Dec 2015 10:07:49 +0000
Subject: [Microbit-Python] building a branch
In-Reply-To: <CAENJrPkyfC-0AL62P+hHXzfkiEgTHi3vBhvQrAvCR9_G3vniaw@mail.gmail.com>
References: <565FF2DD.8090305@wireframe.biz> <565FFE4F.4030706@ntoll.org>
 <5660023D.5000306@wireframe.biz> <56600352.5080607@ntoll.org>
 <56600461.9080606@wireframe.biz>
 <CAENJrPkyfC-0AL62P+hHXzfkiEgTHi3vBhvQrAvCR9_G3vniaw@mail.gmail.com>
Message-ID: <CANw+Mzmo945RB68M13X=d+SSR3u0FFr7p7gdGXM9hZ4_7trrPw@mail.gmail.com>

Peter is right, neopixel is not in the global list of module.

I've now fixed it.  Be sure to "git pull" to get the latest neopixel branch.


On Thu, Dec 3, 2015 at 9:27 AM, Peter Inglesby <peter.inglesby at gmail.com> wrote:
> Hi Mark,
>
> It looks like the neopixel module is missing from the list of modules in
> mpconfigport.h.  If you copy and adapt the references to `love_module`, you
> should get something that you can import.
>
> Hope that helps,
>
> Peter.
>
>
> On 3 December 2015 at 08:59, Mark Schafer <mschafer at wireframe.biz> wrote:
>>
>> any pointers on how to approach debugging this.
>> I can find the .h and .c neopixel files in inc and lib. As well as the
>> modneopixel.cpp
>> All seems properly linked and the modneopixel.cpp seems well formed.
>>
>> I don't want Damien to have to do more work here.
>> I want some pointers to how to approach it - maybe a similar approach has
>> been used in another set of files ?
>>
>> Mark...
>>
>>
>> On 12/3/2015 9:54 PM, Nicholas H.Tollervey wrote:
>>
>> Apologies, my misunderstanding.
>>
>> I guess this is one for Damien since he was the last person to commit to
>> that branch.
>>
>> :-/
>>
>> N.
>>
>> On 03/12/15 08:50, Mark Schafer wrote:
>>
>> its unmodified from the repo
>>
>> On 12/3/2015 9:33 PM, Nicholas H.Tollervey wrote:
>>
>> Hi Mark,
>>
>> Could you commit your work on the neopixel branch and push it to GitHub?
>> That way any of us will be able to recreate your local context and poke
>> it with a proverbial stick.
>>
>> Alternatively, if you don't want to fanny-anny around with GitHub you
>> could send us the patch.diff file you'll get from running this command
>> on your neopixel branch:
>>
>> git diff neopixel master > patch.diff
>>
>> Hope this helps!
>>
>> Nicholas.
>>
>> On 03/12/15 07:44, Mark Schafer wrote:
>>
>> I'm having difficulty getting a branch to compile to a hex.
>>
>> 1. Ive got the https://github.com/bbcmicrobit/micropython cloned locally
>>
>> 2. I've done a "git checkout neopixel" to get the neopixel branch current
>>     - (There are only two branches: Master and neopixel) "git branch
>> --list"
>>     - I've verified that the file modneopixel.cpp is in the source
>> folder. So pretty sure I have correct branch.
>>
>> 3. I've built using yotta:
>>     - yt target bbc-microbit-classic-gcc-nosd
>>     - yt up
>>     - yt build
>>
>> 4. The resulting file, as indicated in the readme, is in:
>>     - build/bbc-microbit-classic-gcc-nosd/source/
>>     - as a hexfile
>>
>> 5. The instructions say to run "make" to add any changed qstrs
>>     - the resulting hex is in build/firmware.hex.
>>     - I've tried "make" and also "make -B", both initiated from the
>> micropython directory
>>
>> When I load this hex onto the Microbit. I don't see the neopixel module.
>>     - in the neopixel branch there is an additional file called
>> modneopixel.cpp which exposes the neopixel object
>>     - so it should be visible.
>>     - No errors are shown on screen during the compile phases.
>>
>>
>> Can someone with more experience indicate which step in the process I
>> have not done ?
>> Or how I might check further to see where problem lies ?
>> Thanks, Mark...
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2016.0.7227 / Virus Database: 4477/11101 - Release Date: 12/02/15
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2016.0.7227 / Virus Database: 4477/11101 - Release Date: 12/02/15
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From danny at orionrobots.co.uk  Thu Dec  3 07:42:48 2015
From: danny at orionrobots.co.uk (danny staple)
Date: Thu, 03 Dec 2015 12:42:48 +0000
Subject: [Microbit-Python] Halp! Reinstalled OS and can't build firmware
 anymore.
In-Reply-To: <5655B5AE.2030904@hastings.org>
References: <56440E0F.7000308@hastings.org> <56444D79.1000006@ntoll.org>
 <CAOBd=7=HhmM-TS++A5KfS=Frw9_MGJyQbvOySkw1xLntZdTHJQ@mail.gmail.com>
 <CANw+MznhF789gOiaxCQaYKK7ODUBqva_rtJv5qsE3w06=rNrhQ@mail.gmail.com>
 <5655B5AE.2030904@hastings.org>
Message-ID: <CAFcNDHSHQJTMOLT+AJd=pZiQUP-NB4VPaE3Z7Q7qXkB-Ktk9sQ@mail.gmail.com>

Hello,
Been lurking on the list since the day at pycon.

For this kind of build environment - it sounds like a docker or vagrant
setup to make a build environment would be a great idea. It would make it
reproducible and reduce friction for potential contributors. It also
separates it from the peculiarities of particular distributions or being
broken by an update to your OS (well as long as the VM/Container stuff
wasn't broken).

Thanks,
Danny

On Wed, 25 Nov 2015 at 13:20 Larry Hastings <larry at hastings.org> wrote:

>
>
> On 11/24/2015 07:38 AM, Damien George wrote:
>
> Larry, did you find a solution to this?  We have another report of the
> same problem: https://github.com/bbcmicrobit/micropython/issues/109
>
>
> I finally figured it out a week ago.  The problem is that Ubuntu also
> ships a gcc-arm-none-eabi, and they've marked their current release as
> version "15:4.9.3+svn227297-1".  Debian's apt sees the "15:" at the front
> and says "oh goody, that's the latest version, much more recent than
> "4.9.3.2015q3-1wily1".  So it picks the default one instead of the one from
> the Terry Guo PPA.
>
> To fix:
>
>    1. Run Synaptic.
>    2. Search for "gcc-arm-none-eabi".
>    3. If the package is installed, uninstall the package, letting it
>    uninstall whatever else it says it has to.
>    4. While still having the "gcc-arm-none-eabi" package selected, open
>    the menus and select "Package | Force Version...".
>    5. In the "Force Version" pop-up dialog box, choose the Terry Guo
>    version, currently "4.9.3.2015q3-1wily1", and install.
>    6. Finally, while still having the "gcc-arm-none-eabi" package
>    selected, open the menus and select "Package | Lock Version".
>
>
> Having done that, I can now build the micro:bit firmware on my laptop
> using the 64-bit workstation release of Ubuntu 15.10.
>
>
> Cheers,
>
>
> */arry*
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151203/26e1d2b8/attachment-0001.html>

From martin at ohanlonweb.com  Fri Dec  4 17:22:12 2015
From: martin at ohanlonweb.com (Martin O'Hanlon)
Date: Fri, 4 Dec 2015 22:22:12 +0000
Subject: [Microbit-Python] Getting a compiled hex
Message-ID: <CAD64x+ahpgy0jxREqMzmOwoD=qXO19ad9WsuAhggqFnkCkU5jw@mail.gmail.com>

Is there anywhere I can download the microbit micropython hex file without
building from source?

Mart

-- 

Blog - www.stuffaboutcode.com

Twitter - @martinohanlon
<http://twitter.com/intent/user?screen_name=martinohanlon>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151204/1b47da25/attachment.html>

From damien.p.george at gmail.com  Fri Dec  4 17:25:49 2015
From: damien.p.george at gmail.com (Damien George)
Date: Fri, 4 Dec 2015 22:25:49 +0000
Subject: [Microbit-Python] Getting a compiled hex
In-Reply-To: <CAD64x+ahpgy0jxREqMzmOwoD=qXO19ad9WsuAhggqFnkCkU5jw@mail.gmail.com>
References: <CAD64x+ahpgy0jxREqMzmOwoD=qXO19ad9WsuAhggqFnkCkU5jw@mail.gmail.com>
Message-ID: <CANw+MzmQjBzM6rbDnEcm0_Mxf6N+OCQeovbnbrmVbqiS=x=_1A@mail.gmail.com>

Mart: try http://dpgeorge.net/stuff/microbit-firmware.hex


On Fri, Dec 4, 2015 at 10:22 PM, Martin O'Hanlon <martin at ohanlonweb.com> wrote:
> Is there anywhere I can download the microbit micropython hex file without
> building from source?
>
> Mart
>
> --
>
> Blog - www.stuffaboutcode.com
>
> Twitter - @martinohanlon
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From martin at ohanlonweb.com  Fri Dec  4 17:39:46 2015
From: martin at ohanlonweb.com (Martin O'Hanlon)
Date: Fri, 4 Dec 2015 22:39:46 +0000
Subject: [Microbit-Python] Getting a compiled hex
In-Reply-To: <CANw+MzmQjBzM6rbDnEcm0_Mxf6N+OCQeovbnbrmVbqiS=x=_1A@mail.gmail.com>
References: <CAD64x+ahpgy0jxREqMzmOwoD=qXO19ad9WsuAhggqFnkCkU5jw@mail.gmail.com>
 <CANw+MzmQjBzM6rbDnEcm0_Mxf6N+OCQeovbnbrmVbqiS=x=_1A@mail.gmail.com>
Message-ID: <CAD64x+ZyE7Rz0pCPVBoLhAO-4TFn8jnZajhQU8pNEN3xS4Pj9A@mail.gmail.com>

Thank you

On 4 December 2015 at 22:25, Damien George <damien.p.george at gmail.com>
wrote:

> Mart: try http://dpgeorge.net/stuff/microbit-firmware.hex
>
>
> On Fri, Dec 4, 2015 at 10:22 PM, Martin O'Hanlon <martin at ohanlonweb.com>
> wrote:
> > Is there anywhere I can download the microbit micropython hex file
> without
> > building from source?
> >
> > Mart
> >
> > --
> >
> > Blog - www.stuffaboutcode.com
> >
> > Twitter - @martinohanlon
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>



-- 

Blog - www.stuffaboutcode.com

Twitter - @martinohanlon
<http://twitter.com/intent/user?screen_name=martinohanlon>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151204/261961b3/attachment.html>

From tom at viner.tv  Sat Dec  5 20:09:55 2015
From: tom at viner.tv (Tom Viner)
Date: Sun, 6 Dec 2015 01:09:55 +0000
Subject: [Microbit-Python] Battery connector and battery holder
Message-ID: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>

Hi all,

I've found the edge connector breakout board
<https://www.kitronik.co.uk/5601-edge-connector-breakout-board.html> and
the motor driver board
<https://www.kitronik.co.uk/5602-motor-driver-board-with-edge-connector.html>
but
I'm not sure exactly which to buy as a battery pack.

Something that can run for a while would be good, but blowing up the board (as
happened to poor Mahiri
<https://microworldtour.github.io/microbit/mahiri.html>) should be avoided!

If one of these does the job
<https://www.kitronik.co.uk/batteries-power/battery-holders.html>, I can
order my boards and battery connector in one go from Kitronik.

Incidentally Kitronik have a load of great micro:bit resources
<https://www.google.co.uk/search?q=site%3Akitronik.co.uk%2Fblog%2F%20microbit>
on their site.

Cheers,
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/9aaaf38d/attachment.html>

From ntoll at ntoll.org  Sun Dec  6 15:34:39 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Sun, 6 Dec 2015 20:34:39 +0000
Subject: [Microbit-Python] A native editor
Message-ID: <56649BDF.9030002@ntoll.org>

Basically, this:

https://www.youtube.com/watch?v=S8MGFVuZrrs

...is a first draft and the source code is here:

https://github.com/ntoll/python-native-editor

There's no documentation and I'll be working on it over the coming days
with a view to showing it on Wednesday to a bunch of teachers.

FYI - working out how to flash the device took several tortuous days.
Chrome has a USB API that was documented to appear to be exactly what I
needed (pushing file based data to the device). I spent far too much
time learning about USB and getting permission to write to the device to
work.

In the end I gave up when I realised there was a really easy hack that
was right in front of my nose... just copy the damn .hex file to the
device via the built-in file-system API.

It worked first time..! :-)

That's several hours of my time I'll never get back.

Early days. Collaboration welcome!

Best wishes,

Nicholas.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/005a01a4/attachment.sig>

From carlos.p.a.87 at gmail.com  Sun Dec  6 16:15:46 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Sun, 6 Dec 2015 21:15:46 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <56649BDF.9030002@ntoll.org>
References: <56649BDF.9030002@ntoll.org>
Message-ID: <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>

Excellent work Nicholas!

Will the pluggin also automatically work when the interface is accessed
from the https://www.microbit.co.uk/create-code python link? (once it is
implemented in the webiste).

As a small suggestion, probably with a low priority, is that having some
visual feedback on the page that the program is being flashed would be
ideal, even better if there was a tiny progress bar on the button.

Regards,
Carlos

On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Basically, this:
>
> https://www.youtube.com/watch?v=S8MGFVuZrrs
>
> ...is a first draft and the source code is here:
>
> https://github.com/ntoll/python-native-editor
>
> There's no documentation and I'll be working on it over the coming days
> with a view to showing it on Wednesday to a bunch of teachers.
>
> FYI - working out how to flash the device took several tortuous days.
> Chrome has a USB API that was documented to appear to be exactly what I
> needed (pushing file based data to the device). I spent far too much
> time learning about USB and getting permission to write to the device to
> work.
>
> In the end I gave up when I realised there was a really easy hack that
> was right in front of my nose... just copy the damn .hex file to the
> device via the built-in file-system API.
>
> It worked first time..! :-)
>
> That's several hours of my time I'll never get back.
>
> Early days. Collaboration welcome!
>
> Best wishes,
>
> Nicholas.
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/a9ad2aac/attachment.html>

From naomi.ceder at gmail.com  Sun Dec  6 17:09:38 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sun, 6 Dec 2015 16:09:38 -0600
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
Message-ID: <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>

Sadly I can't get the extension to work on either OSX or Linux - instead,
the extension reports

 There were warnings when trying to install this extension:

   - 'fileSystem.requestFileSystem' is not allowed for specified platform.


So the result for me is that the new, open, and save functions don't do
anything at all, and the repl says it can't find the microbit.

I'm not finding any explanations of line, but I've attached a screen shot
of the warning...

I'm also not seeing any setting for Chrome that would seem to help.

Cheers,
Naomi


On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:

> Excellent work Nicholas!
>
> Will the pluggin also automatically work when the interface is accessed
> from the https://www.microbit.co.uk/create-code python link? (once it is
> implemented in the webiste).
>
> As a small suggestion, probably with a low priority, is that having some
> visual feedback on the page that the program is being flashed would be
> ideal, even better if there was a tiny progress bar on the button.
>
> Regards,
> Carlos
>
> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
>
>> Basically, this:
>>
>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>
>> ...is a first draft and the source code is here:
>>
>> https://github.com/ntoll/python-native-editor
>>
>> There's no documentation and I'll be working on it over the coming days
>> with a view to showing it on Wednesday to a bunch of teachers.
>>
>> FYI - working out how to flash the device took several tortuous days.
>> Chrome has a USB API that was documented to appear to be exactly what I
>> needed (pushing file based data to the device). I spent far too much
>> time learning about USB and getting permission to write to the device to
>> work.
>>
>> In the end I gave up when I realised there was a really easy hack that
>> was right in front of my nose... just copy the damn .hex file to the
>> device via the built-in file-system API.
>>
>> It worked first time..! :-)
>>
>> That's several hours of my time I'll never get back.
>>
>> Early days. Collaboration welcome!
>>
>> Best wishes,
>>
>> Nicholas.
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/944054cb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2015-12-06 at 4.09.27 PM.png
Type: image/png
Size: 54048 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/944054cb/attachment-0001.png>

From carlos.p.a.87 at gmail.com  Sun Dec  6 17:25:13 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Sun, 6 Dec 2015 22:25:13 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
Message-ID: <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>

Looks like RequestFileSystem might only be supported in ChromeOS, is that
the platform you've been using Nicholas?

https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ

On 6 December 2015 at 22:09, Naomi Ceder <naomi.ceder at gmail.com> wrote:

> Sadly I can't get the extension to work on either OSX or Linux - instead,
> the extension reports
>
>  There were warnings when trying to install this extension:
>
>    - 'fileSystem.requestFileSystem' is not allowed for specified platform.
>
>
> So the result for me is that the new, open, and save functions don't do
> anything at all, and the repl says it can't find the microbit.
>
> I'm not finding any explanations of line, but I've attached a screen shot
> of the warning...
>
> I'm also not seeing any setting for Chrome that would seem to help.
>
> Cheers,
> Naomi
>
>
>
> On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:
>
>> Excellent work Nicholas!
>>
>> Will the pluggin also automatically work when the interface is accessed
>> from the https://www.microbit.co.uk/create-code python link? (once it is
>> implemented in the webiste).
>>
>> As a small suggestion, probably with a low priority, is that having some
>> visual feedback on the page that the program is being flashed would be
>> ideal, even better if there was a tiny progress bar on the button.
>>
>> Regards,
>> Carlos
>>
>> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org>
>> wrote:
>>
>>> Basically, this:
>>>
>>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>>
>>> ...is a first draft and the source code is here:
>>>
>>> https://github.com/ntoll/python-native-editor
>>>
>>> There's no documentation and I'll be working on it over the coming days
>>> with a view to showing it on Wednesday to a bunch of teachers.
>>>
>>> FYI - working out how to flash the device took several tortuous days.
>>> Chrome has a USB API that was documented to appear to be exactly what I
>>> needed (pushing file based data to the device). I spent far too much
>>> time learning about USB and getting permission to write to the device to
>>> work.
>>>
>>> In the end I gave up when I realised there was a really easy hack that
>>> was right in front of my nose... just copy the damn .hex file to the
>>> device via the built-in file-system API.
>>>
>>> It worked first time..! :-)
>>>
>>> That's several hours of my time I'll never get back.
>>>
>>> Early days. Collaboration welcome!
>>>
>>> Best wishes,
>>>
>>> Nicholas.
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
>
> --
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/719cf77c/attachment.html>

From naomi.ceder at gmail.com  Sun Dec  6 17:43:19 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sun, 6 Dec 2015 16:43:19 -0600
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
Message-ID: <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>

Thanks for the reference Carlos. That makes sense...

At any rate, when I removed that permission, the warning of course went
away. However it still coudn't find my micro:bit, since the port objects
have neither a productId nor a vendorId on my system, only a path. When I
matched on the path to what I knew to be the right path, I could get a repl
working just fine. Which would imply that a different way of finding the
right port is needed.

I suppose the next thing is to look at the load/save issue.

Cheers,
Naomi

On 6 December 2015 at 16:25, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:

> Looks like RequestFileSystem might only be supported in ChromeOS, is that
> the platform you've been using Nicholas?
>
>
> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>
> On 6 December 2015 at 22:09, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>
>> Sadly I can't get the extension to work on either OSX or Linux - instead,
>> the extension reports
>>
>>  There were warnings when trying to install this extension:
>>
>>    - 'fileSystem.requestFileSystem' is not allowed for specified
>>    platform.
>>
>>
>> So the result for me is that the new, open, and save functions don't do
>> anything at all, and the repl says it can't find the microbit.
>>
>> I'm not finding any explanations of line, but I've attached a screen shot
>> of the warning...
>>
>> I'm also not seeing any setting for Chrome that would seem to help.
>>
>> Cheers,
>> Naomi
>>
>>
>>
>> On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:
>>
>>> Excellent work Nicholas!
>>>
>>> Will the pluggin also automatically work when the interface is accessed
>>> from the https://www.microbit.co.uk/create-code python link? (once it
>>> is implemented in the webiste).
>>>
>>> As a small suggestion, probably with a low priority, is that having some
>>> visual feedback on the page that the program is being flashed would be
>>> ideal, even better if there was a tiny progress bar on the button.
>>>
>>> Regards,
>>> Carlos
>>>
>>> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org>
>>> wrote:
>>>
>>>> Basically, this:
>>>>
>>>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>>>
>>>> ...is a first draft and the source code is here:
>>>>
>>>> https://github.com/ntoll/python-native-editor
>>>>
>>>> There's no documentation and I'll be working on it over the coming days
>>>> with a view to showing it on Wednesday to a bunch of teachers.
>>>>
>>>> FYI - working out how to flash the device took several tortuous days.
>>>> Chrome has a USB API that was documented to appear to be exactly what I
>>>> needed (pushing file based data to the device). I spent far too much
>>>> time learning about USB and getting permission to write to the device to
>>>> work.
>>>>
>>>> In the end I gave up when I realised there was a really easy hack that
>>>> was right in front of my nose... just copy the damn .hex file to the
>>>> device via the built-in file-system API.
>>>>
>>>> It worked first time..! :-)
>>>>
>>>> That's several hours of my time I'll never get back.
>>>>
>>>> Early days. Collaboration welcome!
>>>>
>>>> Best wishes,
>>>>
>>>> Nicholas.
>>>>
>>>>
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>
>>
>> --
>> Naomi Ceder
>> https://plus.google.com/u/0/111396744045017339164/about
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/fed6fc28/attachment-0001.html>

From naomi.ceder at gmail.com  Sun Dec  6 17:53:47 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sun, 6 Dec 2015 16:53:47 -0600
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
Message-ID: <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>

Ooops! My apologies! I see from looking at the code that new, open and save
are not yet implemented, just stubbed out, it appears.

I misunderstood that. Never mind.

Naomi

On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com> wrote:

> Thanks for the reference Carlos. That makes sense...
>
> At any rate, when I removed that permission, the warning of course went
> away. However it still coudn't find my micro:bit, since the port objects
> have neither a productId nor a vendorId on my system, only a path. When I
> matched on the path to what I knew to be the right path, I could get a repl
> working just fine. Which would imply that a different way of finding the
> right port is needed.
>
> I suppose the next thing is to look at the load/save issue.
>
> Cheers,
> Naomi
>
> On 6 December 2015 at 16:25, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:
>
>> Looks like RequestFileSystem might only be supported in ChromeOS, is that
>> the platform you've been using Nicholas?
>>
>>
>> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>>
>> On 6 December 2015 at 22:09, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>>
>>> Sadly I can't get the extension to work on either OSX or Linux -
>>> instead, the extension reports
>>>
>>>  There were warnings when trying to install this extension:
>>>
>>>    - 'fileSystem.requestFileSystem' is not allowed for specified
>>>    platform.
>>>
>>>
>>> So the result for me is that the new, open, and save functions don't do
>>> anything at all, and the repl says it can't find the microbit.
>>>
>>> I'm not finding any explanations of line, but I've attached a screen
>>> shot of the warning...
>>>
>>> I'm also not seeing any setting for Chrome that would seem to help.
>>>
>>> Cheers,
>>> Naomi
>>>
>>>
>>>
>>> On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com>
>>> wrote:
>>>
>>>> Excellent work Nicholas!
>>>>
>>>> Will the pluggin also automatically work when the interface is accessed
>>>> from the https://www.microbit.co.uk/create-code python link? (once it
>>>> is implemented in the webiste).
>>>>
>>>> As a small suggestion, probably with a low priority, is that having
>>>> some visual feedback on the page that the program is being flashed would be
>>>> ideal, even better if there was a tiny progress bar on the button.
>>>>
>>>> Regards,
>>>> Carlos
>>>>
>>>> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org>
>>>> wrote:
>>>>
>>>>> Basically, this:
>>>>>
>>>>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>>>>
>>>>> ...is a first draft and the source code is here:
>>>>>
>>>>> https://github.com/ntoll/python-native-editor
>>>>>
>>>>> There's no documentation and I'll be working on it over the coming days
>>>>> with a view to showing it on Wednesday to a bunch of teachers.
>>>>>
>>>>> FYI - working out how to flash the device took several tortuous days.
>>>>> Chrome has a USB API that was documented to appear to be exactly what I
>>>>> needed (pushing file based data to the device). I spent far too much
>>>>> time learning about USB and getting permission to write to the device
>>>>> to
>>>>> work.
>>>>>
>>>>> In the end I gave up when I realised there was a really easy hack that
>>>>> was right in front of my nose... just copy the damn .hex file to the
>>>>> device via the built-in file-system API.
>>>>>
>>>>> It worked first time..! :-)
>>>>>
>>>>> That's several hours of my time I'll never get back.
>>>>>
>>>>> Early days. Collaboration welcome!
>>>>>
>>>>> Best wishes,
>>>>>
>>>>> Nicholas.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Microbit mailing list
>>>>> Microbit at python.org
>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>
>>>>
>>>
>>>
>>> --
>>> Naomi Ceder
>>> https://plus.google.com/u/0/111396744045017339164/about
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
>
> --
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
>



-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/fb682a44/attachment.html>

From tom at viner.tv  Sun Dec  6 18:11:04 2015
From: tom at viner.tv (Tom Viner)
Date: Sun, 6 Dec 2015 23:11:04 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
Message-ID: <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>

I'm opening python-native-editor/index.html in Chrome and I don't see how
to get any extension (and there doesn't appear to be unpacked extension to load
in developer <https://developer.chrome.com/extensions/getstarted#unpacked>
mode either).

I just get:
repl.js:75 Uncaught TypeError: Cannot read property 'sync' of undefined

on the line:
hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync);

On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com> wrote:

> Ooops! My apologies! I see from looking at the code that new, open and
> save are not yet implemented, just stubbed out, it appears.
>
> I misunderstood that. Never mind.
>
> Naomi
>
> On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>
>> Thanks for the reference Carlos. That makes sense...
>>
>> At any rate, when I removed that permission, the warning of course went
>> away. However it still coudn't find my micro:bit, since the port objects
>> have neither a productId nor a vendorId on my system, only a path. When I
>> matched on the path to what I knew to be the right path, I could get a repl
>> working just fine. Which would imply that a different way of finding the
>> right port is needed.
>>
>> I suppose the next thing is to look at the load/save issue.
>>
>> Cheers,
>> Naomi
>>
>> On 6 December 2015 at 16:25, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:
>>
>>> Looks like RequestFileSystem might only be supported in ChromeOS, is
>>> that the platform you've been using Nicholas?
>>>
>>>
>>> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>>>
>>> On 6 December 2015 at 22:09, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>>>
>>>> Sadly I can't get the extension to work on either OSX or Linux -
>>>> instead, the extension reports
>>>>
>>>>  There were warnings when trying to install this extension:
>>>>
>>>>    - 'fileSystem.requestFileSystem' is not allowed for specified
>>>>    platform.
>>>>
>>>>
>>>> So the result for me is that the new, open, and save functions don't do
>>>> anything at all, and the repl says it can't find the microbit.
>>>>
>>>> I'm not finding any explanations of line, but I've attached a screen
>>>> shot of the warning...
>>>>
>>>> I'm also not seeing any setting for Chrome that would seem to help.
>>>>
>>>> Cheers,
>>>> Naomi
>>>>
>>>>
>>>>
>>>> On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com>
>>>> wrote:
>>>>
>>>>> Excellent work Nicholas!
>>>>>
>>>>> Will the pluggin also automatically work when the interface is
>>>>> accessed from the https://www.microbit.co.uk/create-code python link?
>>>>> (once it is implemented in the webiste).
>>>>>
>>>>> As a small suggestion, probably with a low priority, is that having
>>>>> some visual feedback on the page that the program is being flashed would be
>>>>> ideal, even better if there was a tiny progress bar on the button.
>>>>>
>>>>> Regards,
>>>>> Carlos
>>>>>
>>>>> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org>
>>>>> wrote:
>>>>>
>>>>>> Basically, this:
>>>>>>
>>>>>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>>>>>
>>>>>> ...is a first draft and the source code is here:
>>>>>>
>>>>>> https://github.com/ntoll/python-native-editor
>>>>>>
>>>>>> There's no documentation and I'll be working on it over the coming
>>>>>> days
>>>>>> with a view to showing it on Wednesday to a bunch of teachers.
>>>>>>
>>>>>> FYI - working out how to flash the device took several tortuous days.
>>>>>> Chrome has a USB API that was documented to appear to be exactly what
>>>>>> I
>>>>>> needed (pushing file based data to the device). I spent far too much
>>>>>> time learning about USB and getting permission to write to the device
>>>>>> to
>>>>>> work.
>>>>>>
>>>>>> In the end I gave up when I realised there was a really easy hack that
>>>>>> was right in front of my nose... just copy the damn .hex file to the
>>>>>> device via the built-in file-system API.
>>>>>>
>>>>>> It worked first time..! :-)
>>>>>>
>>>>>> That's several hours of my time I'll never get back.
>>>>>>
>>>>>> Early days. Collaboration welcome!
>>>>>>
>>>>>> Best wishes,
>>>>>>
>>>>>> Nicholas.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Microbit mailing list
>>>>>> Microbit at python.org
>>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Microbit mailing list
>>>>> Microbit at python.org
>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Naomi Ceder
>>>> https://plus.google.com/u/0/111396744045017339164/about
>>>>
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>
>>
>> --
>> Naomi Ceder
>> https://plus.google.com/u/0/111396744045017339164/about
>>
>
>
>
> --
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/b15bce24/attachment-0001.html>

From naomi.ceder at gmail.com  Sun Dec  6 18:13:31 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sun, 6 Dec 2015 17:13:31 -0600
Subject: [Microbit-Python] A native editor
In-Reply-To: <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
Message-ID: <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>

Tom, use the entire base directory as the unpacked extension - that worked
for me.

Naomi

On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv> wrote:

> I'm opening python-native-editor/index.html in Chrome and I don't see how
> to get any extension (and there doesn't appear to be unpacked extension to load
> in developer <https://developer.chrome.com/extensions/getstarted#unpacked>
> mode either).
>
> I just get:
> repl.js:75 Uncaught TypeError: Cannot read property 'sync' of undefined
>
> on the line:
> hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync);
>
> On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>
>> Ooops! My apologies! I see from looking at the code that new, open and
>> save are not yet implemented, just stubbed out, it appears.
>>
>> I misunderstood that. Never mind.
>>
>> Naomi
>>
>> On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>>
>>> Thanks for the reference Carlos. That makes sense...
>>>
>>> At any rate, when I removed that permission, the warning of course went
>>> away. However it still coudn't find my micro:bit, since the port objects
>>> have neither a productId nor a vendorId on my system, only a path. When I
>>> matched on the path to what I knew to be the right path, I could get a repl
>>> working just fine. Which would imply that a different way of finding the
>>> right port is needed.
>>>
>>> I suppose the next thing is to look at the load/save issue.
>>>
>>> Cheers,
>>> Naomi
>>>
>>> On 6 December 2015 at 16:25, Carlos P.A. <carlos.p.a.87 at gmail.com>
>>> wrote:
>>>
>>>> Looks like RequestFileSystem might only be supported in ChromeOS, is
>>>> that the platform you've been using Nicholas?
>>>>
>>>>
>>>> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>>>>
>>>> On 6 December 2015 at 22:09, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>>>>
>>>>> Sadly I can't get the extension to work on either OSX or Linux -
>>>>> instead, the extension reports
>>>>>
>>>>>  There were warnings when trying to install this extension:
>>>>>
>>>>>    - 'fileSystem.requestFileSystem' is not allowed for specified
>>>>>    platform.
>>>>>
>>>>>
>>>>> So the result for me is that the new, open, and save functions don't
>>>>> do anything at all, and the repl says it can't find the microbit.
>>>>>
>>>>> I'm not finding any explanations of line, but I've attached a screen
>>>>> shot of the warning...
>>>>>
>>>>> I'm also not seeing any setting for Chrome that would seem to help.
>>>>>
>>>>> Cheers,
>>>>> Naomi
>>>>>
>>>>>
>>>>>
>>>>> On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Excellent work Nicholas!
>>>>>>
>>>>>> Will the pluggin also automatically work when the interface is
>>>>>> accessed from the https://www.microbit.co.uk/create-code python
>>>>>> link? (once it is implemented in the webiste).
>>>>>>
>>>>>> As a small suggestion, probably with a low priority, is that having
>>>>>> some visual feedback on the page that the program is being flashed would be
>>>>>> ideal, even better if there was a tiny progress bar on the button.
>>>>>>
>>>>>> Regards,
>>>>>> Carlos
>>>>>>
>>>>>> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Basically, this:
>>>>>>>
>>>>>>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>>>>>>
>>>>>>> ...is a first draft and the source code is here:
>>>>>>>
>>>>>>> https://github.com/ntoll/python-native-editor
>>>>>>>
>>>>>>> There's no documentation and I'll be working on it over the coming
>>>>>>> days
>>>>>>> with a view to showing it on Wednesday to a bunch of teachers.
>>>>>>>
>>>>>>> FYI - working out how to flash the device took several tortuous days.
>>>>>>> Chrome has a USB API that was documented to appear to be exactly
>>>>>>> what I
>>>>>>> needed (pushing file based data to the device). I spent far too much
>>>>>>> time learning about USB and getting permission to write to the
>>>>>>> device to
>>>>>>> work.
>>>>>>>
>>>>>>> In the end I gave up when I realised there was a really easy hack
>>>>>>> that
>>>>>>> was right in front of my nose... just copy the damn .hex file to the
>>>>>>> device via the built-in file-system API.
>>>>>>>
>>>>>>> It worked first time..! :-)
>>>>>>>
>>>>>>> That's several hours of my time I'll never get back.
>>>>>>>
>>>>>>> Early days. Collaboration welcome!
>>>>>>>
>>>>>>> Best wishes,
>>>>>>>
>>>>>>> Nicholas.
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Microbit mailing list
>>>>>>> Microbit at python.org
>>>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Microbit mailing list
>>>>>> Microbit at python.org
>>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Naomi Ceder
>>>>> https://plus.google.com/u/0/111396744045017339164/about
>>>>>
>>>>> _______________________________________________
>>>>> Microbit mailing list
>>>>> Microbit at python.org
>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Microbit mailing list
>>>> Microbit at python.org
>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>
>>>>
>>>
>>>
>>> --
>>> Naomi Ceder
>>> https://plus.google.com/u/0/111396744045017339164/about
>>>
>>
>>
>>
>> --
>> Naomi Ceder
>> https://plus.google.com/u/0/111396744045017339164/about
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/6a0f8236/attachment.html>

From nick.a.sarbicki at gmail.com  Sun Dec  6 16:15:45 2015
From: nick.a.sarbicki at gmail.com (Nick Sarbicki)
Date: Sun, 06 Dec 2015 21:15:45 +0000
Subject: [Microbit-Python] Is Bach Prelude in C the right example for the
 musical API?
Message-ID: <CAGuvt93xA5sGOUm3ocVKRKEzo-Njk5Xp+0A9NKyMRbuHKNcajg@mail.gmail.com>

Sorry if this has already been discussed. I've skimmed the previous threads
and haven't found anything on this.

I for one love Bach.

My 9 year old nephew only knows him from being forced to play Bach pieces
during piano lessons.

Most other kids I teach at the Dojo I'm fairly sure wouldn't have a clue.

Do we think it would be better to have a different song as the main
tutorial for the music API? My immediate thought was The Entertainer which
most kids are taught at school (they still are right? I'm not just getting
old?). But maybe even that is too old-fashioned.

If we want to actively address the gender imbalance in programming today we
could even put on "Let It Go" (that was a joke, please don't take it
seriously).

- Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151206/aeba365b/attachment.html>

From ntoll at ntoll.org  Mon Dec  7 03:59:51 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 08:59:51 +0000
Subject: [Microbit-Python] Is Bach Prelude in C the right example for
 the musical API?
In-Reply-To: <CAGuvt93xA5sGOUm3ocVKRKEzo-Njk5Xp+0A9NKyMRbuHKNcajg@mail.gmail.com>
References: <CAGuvt93xA5sGOUm3ocVKRKEzo-Njk5Xp+0A9NKyMRbuHKNcajg@mail.gmail.com>
Message-ID: <56654A87.702@ntoll.org>

Hi,

Where are you seeing this tutorial? I designed the music API and I've
not written a tutorial for it. There's a relatively old music example
but that can be easily changed.

Totally agree about the music being engaging and appropriate for the
target year group.

N.

On 06/12/15 21:15, Nick Sarbicki wrote:
> Sorry if this has already been discussed. I've skimmed the previous
> threads and haven't found anything on this.
> 
> I for one love Bach.
> 
> My 9 year old nephew only knows him from being forced to play Bach
> pieces during piano lessons.
> 
> Most other kids I teach at the Dojo I'm fairly sure wouldn't have a clue.
> 
> Do we think it would be better to have a different song as the main
> tutorial for the music API? My immediate thought was The Entertainer
> which most kids are taught at school (they still are right? I'm not just
> getting old?). But maybe even that is too old-fashioned.
> 
> If we want to actively address the gender imbalance in programming today
> we could even put on "Let It Go" (that was a joke, please don't take it
> seriously).
> 
> - Nick.
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/721970ca/attachment-0001.sig>

From ntoll at ntoll.org  Mon Dec  7 04:13:00 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 09:13:00 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
Message-ID: <56654D9C.3090401@ntoll.org>

Folks,

None of this is documented, it's unfinished and is basically a working
brain dump. Give me some time to write up what I've done..! (I was doing
this most evening's last week and over the weekend. By Sunday evening I
was sick of the site of the damn thing - especially after most of the
time I'd spent on it was wasted on the non-working USB API).

I'll get to it, but in the meantime:

This will be a Chrome App that you download and install from Google's
"App Store" thingamabob for Chrome Apps. When you download the app
you'll be walked through the permissions required (that you accept or
decline). I'm doing my work on Debian Jessie and it worked for me. This
is a very important user journey, but one that I can't test until we
have something semi-functional telling us what the permissions need to
be (currently, storage, serial and filesystem).

I'm using Google's "Chrome Dev Editor" to do this work
(https://chrome.google.com/webstore/detail/chrome-dev-editor-develop/pnoffddplpippgcfjdhbmhkofpnaalpg).
I suggest you use it too.

Like I said... a very early brain dump.

In an ideal world we'd have just a static .exe for Windows that gave us
something functionally equivalent to what I've done already. I might
take a look at some of the Puppy work myself, Dan Pope and Damien did to
see if this is possible.

Basically, all the amazing work on MicroPython should be easily
accessible. Teachers have a bad time of it. I want to fix that problem
and I'm doing so in public so those who want to help can dive in.

N.

On 06/12/15 23:13, Naomi Ceder wrote:
> Tom, use the entire base directory as the unpacked extension - that
> worked for me.
> 
> Naomi
> 
> On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv
> <mailto:tom at viner.tv>> wrote:
> 
>     I'm opening python-native-editor/index.html in Chrome and I don't
>     see how to get any extension (and there doesn't appear to be
>     unpacked extension to load in developer
>     <https://developer.chrome.com/extensions/getstarted#unpacked> mode
>     either).
> 
>     I just get:
>     repl.js:75 Uncaught TypeError: Cannot read property 'sync' of undefined
> 
>     on the line:
>     hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync); 
> 
>     On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com
>     <mailto:naomi.ceder at gmail.com>> wrote:
> 
>         Ooops! My apologies! I see from looking at the code that new,
>         open and save are not yet implemented, just stubbed out, it
>         appears. 
> 
>         I misunderstood that. Never mind.
> 
>         Naomi
> 
>         On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com
>         <mailto:naomi.ceder at gmail.com>> wrote:
> 
>             Thanks for the reference Carlos. That makes sense...
> 
>             At any rate, when I removed that permission, the warning of
>             course went away. However it still coudn't find my
>             micro:bit, since the port objects have neither a productId
>             nor a vendorId on my system, only a path. When I matched on
>             the path to what I knew to be the right path, I could get a
>             repl working just fine. Which would imply that a different
>             way of finding the right port is needed.
> 
>             I suppose the next thing is to look at the load/save issue.
> 
>             Cheers,
>             Naomi
> 
>             On 6 December 2015 at 16:25, Carlos P.A.
>             <carlos.p.a.87 at gmail.com <mailto:carlos.p.a.87 at gmail.com>>
>             wrote:
> 
>                 Looks like RequestFileSystem might only be supported in
>                 ChromeOS, is that the platform you've been using Nicholas?
> 
>                 https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
> 
>                 On 6 December 2015 at 22:09, Naomi Ceder
>                 <naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>>
>                 wrote:
> 
>                     Sadly I can't get the extension to work on either
>                     OSX or Linux - instead, the extension reports
> 
>                      There were warnings when trying to install this
>                     extension:
> 
>                       * 'fileSystem.requestFileSystem' is not allowed
>                         for specified platform.
> 
> 
>                     So the result for me is that the new, open, and save
>                     functions don't do anything at all, and the repl
>                     says it can't find the microbit. 
> 
>                     I'm not finding any explanations of line, but I've
>                     attached a screen shot of the warning... 
> 
>                     I'm also not seeing any setting for Chrome that
>                     would seem to help.
> 
>                     Cheers,
>                     Naomi
> 
> 
> 
>                     On 6 December 2015 at 15:15, Carlos P.A.
>                     <carlos.p.a.87 at gmail.com
>                     <mailto:carlos.p.a.87 at gmail.com>> wrote:
> 
>                         Excellent work Nicholas!
> 
>                         Will the pluggin also automatically work when
>                         the interface is accessed from the
>                         https://www.microbit.co.uk/create-code python
>                         link? (once it is implemented in the webiste).
> 
>                         As a small suggestion, probably with a low
>                         priority, is that having some visual feedback on
>                         the page that the program is being flashed would
>                         be ideal, even better if there was a tiny
>                         progress bar on the button.
> 
>                         Regards,
>                         Carlos
> 
>                         On 6 December 2015 at 20:34, Nicholas
>                         H.Tollervey <ntoll at ntoll.org
>                         <mailto:ntoll at ntoll.org>> wrote:
> 
>                             Basically, this:
> 
>                             https://www.youtube.com/watch?v=S8MGFVuZrrs
> 
>                             ...is a first draft and the source code is here:
> 
>                             https://github.com/ntoll/python-native-editor
> 
>                             There's no documentation and I'll be working
>                             on it over the coming days
>                             with a view to showing it on Wednesday to a
>                             bunch of teachers.
> 
>                             FYI - working out how to flash the device
>                             took several tortuous days.
>                             Chrome has a USB API that was documented to
>                             appear to be exactly what I
>                             needed (pushing file based data to the
>                             device). I spent far too much
>                             time learning about USB and getting
>                             permission to write to the device to
>                             work.
> 
>                             In the end I gave up when I realised there
>                             was a really easy hack that
>                             was right in front of my nose... just copy
>                             the damn .hex file to the
>                             device via the built-in file-system API.
> 
>                             It worked first time..! :-)
> 
>                             That's several hours of my time I'll never
>                             get back.
> 
>                             Early days. Collaboration welcome!
> 
>                             Best wishes,
> 
>                             Nicholas.
> 
> 
>                             _______________________________________________
>                             Microbit mailing list
>                             Microbit at python.org <mailto:Microbit at python.org>
>                             https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
>                         _______________________________________________
>                         Microbit mailing list
>                         Microbit at python.org <mailto:Microbit at python.org>
>                         https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
>                     -- 
>                     Naomi Ceder
>                     https://plus.google.com/u/0/111396744045017339164/about
> 
>                     _______________________________________________
>                     Microbit mailing list
>                     Microbit at python.org <mailto:Microbit at python.org>
>                     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
>                 _______________________________________________
>                 Microbit mailing list
>                 Microbit at python.org <mailto:Microbit at python.org>
>                 https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
>             -- 
>             Naomi Ceder
>             https://plus.google.com/u/0/111396744045017339164/about
> 
> 
> 
> 
>         -- 
>         Naomi Ceder
>         https://plus.google.com/u/0/111396744045017339164/about
> 
>         _______________________________________________
>         Microbit mailing list
>         Microbit at python.org <mailto:Microbit at python.org>
>         https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
> -- 
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/54ad42ff/attachment.sig>

From carlos.p.a.87 at gmail.com  Mon Dec  7 04:34:25 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Mon, 7 Dec 2015 09:34:25 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <56654D9C.3090401@ntoll.org>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org>
Message-ID: <CAC_p0yAhfCqfm8ULs+fJ0k390Y-EuZR_rBhzBuwN9vygg=iwFQ@mail.gmail.com>

> In an ideal world we'd have just a static .exe for Windows that gave us
> something functionally equivalent to what I've done already. I might
>take a look at some of the Puppy work myself, Dan Pope and Damien did to
> see if this is possible.

Puppy the PHP framework? If we are okay with pivoting tech at this point,
might I suggest Electron using node.js? I've used it to pack web app
applications for desktop (windows, mac, linux and even arm linux) and will
definitely work for this kind of requirements. You can create executables
or have them as a "portable apps", which could then probably be packed into
a single .exe file for windows. The only downside is the application size
might not be all that small, as it packs the chromium embedded engine with
it (so > 50Mbs compressed).

On 7 December 2015 at 09:13, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Folks,
>
> None of this is documented, it's unfinished and is basically a working
> brain dump. Give me some time to write up what I've done..! (I was doing
> this most evening's last week and over the weekend. By Sunday evening I
> was sick of the site of the damn thing - especially after most of the
> time I'd spent on it was wasted on the non-working USB API).
>
> I'll get to it, but in the meantime:
>
> This will be a Chrome App that you download and install from Google's
> "App Store" thingamabob for Chrome Apps. When you download the app
> you'll be walked through the permissions required (that you accept or
> decline). I'm doing my work on Debian Jessie and it worked for me. This
> is a very important user journey, but one that I can't test until we
> have something semi-functional telling us what the permissions need to
> be (currently, storage, serial and filesystem).
>
> I'm using Google's "Chrome Dev Editor" to do this work
> (
> https://chrome.google.com/webstore/detail/chrome-dev-editor-develop/pnoffddplpippgcfjdhbmhkofpnaalpg
> ).
> I suggest you use it too.
>
> Like I said... a very early brain dump.
>
> In an ideal world we'd have just a static .exe for Windows that gave us
> something functionally equivalent to what I've done already. I might
> take a look at some of the Puppy work myself, Dan Pope and Damien did to
> see if this is possible.
>
> Basically, all the amazing work on MicroPython should be easily
> accessible. Teachers have a bad time of it. I want to fix that problem
> and I'm doing so in public so those who want to help can dive in.
>
> N.
>
> On 06/12/15 23:13, Naomi Ceder wrote:
> > Tom, use the entire base directory as the unpacked extension - that
> > worked for me.
> >
> > Naomi
> >
> > On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv
> > <mailto:tom at viner.tv>> wrote:
> >
> >     I'm opening python-native-editor/index.html in Chrome and I don't
> >     see how to get any extension (and there doesn't appear to be
> >     unpacked extension to load in developer
> >     <https://developer.chrome.com/extensions/getstarted#unpacked> mode
> >     either).
> >
> >     I just get:
> >     repl.js:75 Uncaught TypeError: Cannot read property 'sync' of
> undefined
> >
> >     on the line:
> >     hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync);
> >
> >     On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com
> >     <mailto:naomi.ceder at gmail.com>> wrote:
> >
> >         Ooops! My apologies! I see from looking at the code that new,
> >         open and save are not yet implemented, just stubbed out, it
> >         appears.
> >
> >         I misunderstood that. Never mind.
> >
> >         Naomi
> >
> >         On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com
> >         <mailto:naomi.ceder at gmail.com>> wrote:
> >
> >             Thanks for the reference Carlos. That makes sense...
> >
> >             At any rate, when I removed that permission, the warning of
> >             course went away. However it still coudn't find my
> >             micro:bit, since the port objects have neither a productId
> >             nor a vendorId on my system, only a path. When I matched on
> >             the path to what I knew to be the right path, I could get a
> >             repl working just fine. Which would imply that a different
> >             way of finding the right port is needed.
> >
> >             I suppose the next thing is to look at the load/save issue.
> >
> >             Cheers,
> >             Naomi
> >
> >             On 6 December 2015 at 16:25, Carlos P.A.
> >             <carlos.p.a.87 at gmail.com <mailto:carlos.p.a.87 at gmail.com>>
> >             wrote:
> >
> >                 Looks like RequestFileSystem might only be supported in
> >                 ChromeOS, is that the platform you've been using
> Nicholas?
> >
> >
> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
> >
> >                 On 6 December 2015 at 22:09, Naomi Ceder
> >                 <naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>>
> >                 wrote:
> >
> >                     Sadly I can't get the extension to work on either
> >                     OSX or Linux - instead, the extension reports
> >
> >                      There were warnings when trying to install this
> >                     extension:
> >
> >                       * 'fileSystem.requestFileSystem' is not allowed
> >                         for specified platform.
> >
> >
> >                     So the result for me is that the new, open, and save
> >                     functions don't do anything at all, and the repl
> >                     says it can't find the microbit.
> >
> >                     I'm not finding any explanations of line, but I've
> >                     attached a screen shot of the warning...
> >
> >                     I'm also not seeing any setting for Chrome that
> >                     would seem to help.
> >
> >                     Cheers,
> >                     Naomi
> >
> >
> >
> >                     On 6 December 2015 at 15:15, Carlos P.A.
> >                     <carlos.p.a.87 at gmail.com
> >                     <mailto:carlos.p.a.87 at gmail.com>> wrote:
> >
> >                         Excellent work Nicholas!
> >
> >                         Will the pluggin also automatically work when
> >                         the interface is accessed from the
> >                         https://www.microbit.co.uk/create-code python
> >                         link? (once it is implemented in the webiste).
> >
> >                         As a small suggestion, probably with a low
> >                         priority, is that having some visual feedback on
> >                         the page that the program is being flashed would
> >                         be ideal, even better if there was a tiny
> >                         progress bar on the button.
> >
> >                         Regards,
> >                         Carlos
> >
> >                         On 6 December 2015 at 20:34, Nicholas
> >                         H.Tollervey <ntoll at ntoll.org
> >                         <mailto:ntoll at ntoll.org>> wrote:
> >
> >                             Basically, this:
> >
> >                             https://www.youtube.com/watch?v=S8MGFVuZrrs
> >
> >                             ...is a first draft and the source code is
> here:
> >
> >
> https://github.com/ntoll/python-native-editor
> >
> >                             There's no documentation and I'll be working
> >                             on it over the coming days
> >                             with a view to showing it on Wednesday to a
> >                             bunch of teachers.
> >
> >                             FYI - working out how to flash the device
> >                             took several tortuous days.
> >                             Chrome has a USB API that was documented to
> >                             appear to be exactly what I
> >                             needed (pushing file based data to the
> >                             device). I spent far too much
> >                             time learning about USB and getting
> >                             permission to write to the device to
> >                             work.
> >
> >                             In the end I gave up when I realised there
> >                             was a really easy hack that
> >                             was right in front of my nose... just copy
> >                             the damn .hex file to the
> >                             device via the built-in file-system API.
> >
> >                             It worked first time..! :-)
> >
> >                             That's several hours of my time I'll never
> >                             get back.
> >
> >                             Early days. Collaboration welcome!
> >
> >                             Best wishes,
> >
> >                             Nicholas.
> >
> >
> >
>  _______________________________________________
> >                             Microbit mailing list
> >                             Microbit at python.org <mailto:
> Microbit at python.org>
> >
> https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >                         _______________________________________________
> >                         Microbit mailing list
> >                         Microbit at python.org <mailto:Microbit at python.org>
> >
> https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >
> >                     --
> >                     Naomi Ceder
> >
> https://plus.google.com/u/0/111396744045017339164/about
> >
> >                     _______________________________________________
> >                     Microbit mailing list
> >                     Microbit at python.org <mailto:Microbit at python.org>
> >                     https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >                 _______________________________________________
> >                 Microbit mailing list
> >                 Microbit at python.org <mailto:Microbit at python.org>
> >                 https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >
> >             --
> >             Naomi Ceder
> >             https://plus.google.com/u/0/111396744045017339164/about
> >
> >
> >
> >
> >         --
> >         Naomi Ceder
> >         https://plus.google.com/u/0/111396744045017339164/about
> >
> >         _______________________________________________
> >         Microbit mailing list
> >         Microbit at python.org <mailto:Microbit at python.org>
> >         https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >     _______________________________________________
> >     Microbit mailing list
> >     Microbit at python.org <mailto:Microbit at python.org>
> >     https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >
> > --
> > Naomi Ceder
> > https://plus.google.com/u/0/111396744045017339164/about
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/bde5abbe/attachment-0001.html>

From nick.a.sarbicki at gmail.com  Mon Dec  7 04:39:16 2015
From: nick.a.sarbicki at gmail.com (Nick Sarbicki)
Date: Mon, 07 Dec 2015 09:39:16 +0000
Subject: [Microbit-Python] Is Bach Prelude in C the right example for
 the musical API?
In-Reply-To: <56654A87.702@ntoll.org>
References: <CAGuvt93xA5sGOUm3ocVKRKEzo-Njk5Xp+0A9NKyMRbuHKNcajg@mail.gmail.com>
 <56654A87.702@ntoll.org>
Message-ID: <CAGuvt90EuBugqR4KibV+UTpM2caqwi_sQ4e1_6LD8s1HfB3inA@mail.gmail.com>

Sorry tutorial may have been a misleading choice of words.

I was browsing the github and came across the old example.

Going over it in more detail I've found several more coded in.

Out of interest have we got rests programmed into the module?

Nick.

On Mon, Dec 7, 2015 at 9:01 AM Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Hi,
>
> Where are you seeing this tutorial? I designed the music API and I've
> not written a tutorial for it. There's a relatively old music example
> but that can be easily changed.
>
> Totally agree about the music being engaging and appropriate for the
> target year group.
>
> N.
>
> On 06/12/15 21:15, Nick Sarbicki wrote:
> > Sorry if this has already been discussed. I've skimmed the previous
> > threads and haven't found anything on this.
> >
> > I for one love Bach.
> >
> > My 9 year old nephew only knows him from being forced to play Bach
> > pieces during piano lessons.
> >
> > Most other kids I teach at the Dojo I'm fairly sure wouldn't have a clue.
> >
> > Do we think it would be better to have a different song as the main
> > tutorial for the music API? My immediate thought was The Entertainer
> > which most kids are taught at school (they still are right? I'm not just
> > getting old?). But maybe even that is too old-fashioned.
> >
> > If we want to actively address the gender imbalance in programming today
> > we could even put on "Let It Go" (that was a joke, please don't take it
> > seriously).
> >
> > - Nick.
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/c07df631/attachment.html>

From ntoll at ntoll.org  Mon Dec  7 04:40:51 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 09:40:51 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAC_p0yAhfCqfm8ULs+fJ0k390Y-EuZR_rBhzBuwN9vygg=iwFQ@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org>
 <CAC_p0yAhfCqfm8ULs+fJ0k390Y-EuZR_rBhzBuwN9vygg=iwFQ@mail.gmail.com>
Message-ID: <56655423.1070602@ntoll.org>

Hah!

Not Puppy the PHP framework.

Puppy is a Python editor for kids. It's written in Python with QT as the
UI framework.

;-)

N.

On 07/12/15 09:34, Carlos P.A. wrote:
>> In an ideal world we'd have just a static .exe for Windows that gave us
>> something functionally equivalent to what I've done already. I might
>>take a look at some of the Puppy work myself, Dan Pope and Damien did to
>> see if this is possible.
> 
> Puppy the PHP framework? If we are okay with pivoting tech at this
> point, might I suggest Electron using node.js? I've used it to pack web
> app applications for desktop (windows, mac, linux and even arm linux)
> and will definitely work for this kind of requirements. You can create
> executables or have them as a "portable apps", which could then probably
> be packed into a single .exe file for windows. The only downside is the
> application size might not be all that small, as it packs the chromium
> embedded engine with it (so > 50Mbs compressed).
> 
> On 7 December 2015 at 09:13, Nicholas H.Tollervey <ntoll at ntoll.org
> <mailto:ntoll at ntoll.org>> wrote:
> 
>     Folks,
> 
>     None of this is documented, it's unfinished and is basically a working
>     brain dump. Give me some time to write up what I've done..! (I was doing
>     this most evening's last week and over the weekend. By Sunday evening I
>     was sick of the site of the damn thing - especially after most of the
>     time I'd spent on it was wasted on the non-working USB API).
> 
>     I'll get to it, but in the meantime:
> 
>     This will be a Chrome App that you download and install from Google's
>     "App Store" thingamabob for Chrome Apps. When you download the app
>     you'll be walked through the permissions required (that you accept or
>     decline). I'm doing my work on Debian Jessie and it worked for me. This
>     is a very important user journey, but one that I can't test until we
>     have something semi-functional telling us what the permissions need to
>     be (currently, storage, serial and filesystem).
> 
>     I'm using Google's "Chrome Dev Editor" to do this work
>     (https://chrome.google.com/webstore/detail/chrome-dev-editor-develop/pnoffddplpippgcfjdhbmhkofpnaalpg).
>     I suggest you use it too.
> 
>     Like I said... a very early brain dump.
> 
>     In an ideal world we'd have just a static .exe for Windows that gave us
>     something functionally equivalent to what I've done already. I might
>     take a look at some of the Puppy work myself, Dan Pope and Damien did to
>     see if this is possible.
> 
>     Basically, all the amazing work on MicroPython should be easily
>     accessible. Teachers have a bad time of it. I want to fix that problem
>     and I'm doing so in public so those who want to help can dive in.
> 
>     N.
> 
>     On 06/12/15 23:13, Naomi Ceder wrote:
>     > Tom, use the entire base directory as the unpacked extension - that
>     > worked for me.
>     >
>     > Naomi
>     >
>     > On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv <mailto:tom at viner.tv>
>     > <mailto:tom at viner.tv <mailto:tom at viner.tv>>> wrote:
>     >
>     >     I'm opening python-native-editor/index.html in Chrome and I don't
>     >     see how to get any extension (and there doesn't appear to be
>     >     unpacked extension to load in developer
>     >     <https://developer.chrome.com/extensions/getstarted#unpacked> mode
>     >     either).
>     >
>     >     I just get:
>     >     repl.js:75 Uncaught TypeError: Cannot read property 'sync' of undefined
>     >
>     >     on the line:
>     >     hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync);
>     >
>     >     On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>
>     >     <mailto:naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>>> wrote:
>     >
>     >         Ooops! My apologies! I see from looking at the code that new,
>     >         open and save are not yet implemented, just stubbed out, it
>     >         appears.
>     >
>     >         I misunderstood that. Never mind.
>     >
>     >         Naomi
>     >
>     >         On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>
>     >         <mailto:naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>>> wrote:
>     >
>     >             Thanks for the reference Carlos. That makes sense...
>     >
>     >             At any rate, when I removed that permission, the warning of
>     >             course went away. However it still coudn't find my
>     >             micro:bit, since the port objects have neither a productId
>     >             nor a vendorId on my system, only a path. When I matched on
>     >             the path to what I knew to be the right path, I could get a
>     >             repl working just fine. Which would imply that a different
>     >             way of finding the right port is needed.
>     >
>     >             I suppose the next thing is to look at the load/save issue.
>     >
>     >             Cheers,
>     >             Naomi
>     >
>     >             On 6 December 2015 at 16:25, Carlos P.A.
>     >             <carlos.p.a.87 at gmail.com
>     <mailto:carlos.p.a.87 at gmail.com> <mailto:carlos.p.a.87 at gmail.com
>     <mailto:carlos.p.a.87 at gmail.com>>>
>     >             wrote:
>     >
>     >                 Looks like RequestFileSystem might only be supported in
>     >                 ChromeOS, is that the platform you've been using Nicholas?
>     >
>     >                 https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>     >
>     >                 On 6 December 2015 at 22:09, Naomi Ceder
>     >                 <naomi.ceder at gmail.com
>     <mailto:naomi.ceder at gmail.com> <mailto:naomi.ceder at gmail.com
>     <mailto:naomi.ceder at gmail.com>>>
>     >                 wrote:
>     >
>     >                     Sadly I can't get the extension to work on either
>     >                     OSX or Linux - instead, the extension reports
>     >
>     >                      There were warnings when trying to install this
>     >                     extension:
>     >
>     >                       * 'fileSystem.requestFileSystem' is not allowed
>     >                         for specified platform.
>     >
>     >
>     >                     So the result for me is that the new, open, and save
>     >                     functions don't do anything at all, and the repl
>     >                     says it can't find the microbit.
>     >
>     >                     I'm not finding any explanations of line, but I've
>     >                     attached a screen shot of the warning...
>     >
>     >                     I'm also not seeing any setting for Chrome that
>     >                     would seem to help.
>     >
>     >                     Cheers,
>     >                     Naomi
>     >
>     >
>     >
>     >                     On 6 December 2015 at 15:15, Carlos P.A.
>     >                     <carlos.p.a.87 at gmail.com <mailto:carlos.p.a.87 at gmail.com>
>     >                     <mailto:carlos.p.a.87 at gmail.com <mailto:carlos.p.a.87 at gmail.com>>> wrote:
>     >
>     >                         Excellent work Nicholas!
>     >
>     >                         Will the pluggin also automatically work when
>     >                         the interface is accessed from the
>     >                         https://www.microbit.co.uk/create-code python
>     >                         link? (once it is implemented in the webiste).
>     >
>     >                         As a small suggestion, probably with a low
>     >                         priority, is that having some visual feedback on
>     >                         the page that the program is being flashed would
>     >                         be ideal, even better if there was a tiny
>     >                         progress bar on the button.
>     >
>     >                         Regards,
>     >                         Carlos
>     >
>     >                         On 6 December 2015 at 20:34, Nicholas
>     >                         H.Tollervey <ntoll at ntoll.org <mailto:ntoll at ntoll.org>
>     >                         <mailto:ntoll at ntoll.org
>     <mailto:ntoll at ntoll.org>>> wrote:
>     >
>     >                             Basically, this:
>     >
>     >                           
>      https://www.youtube.com/watch?v=S8MGFVuZrrs
>     >
>     >                             ...is a first draft and the source
>     code is here:
>     >
>     >                           
>      https://github.com/ntoll/python-native-editor
>     >
>     >                             There's no documentation and I'll be
>     working
>     >                             on it over the coming days
>     >                             with a view to showing it on Wednesday
>     to a
>     >                             bunch of teachers.
>     >
>     >                             FYI - working out how to flash the device
>     >                             took several tortuous days.
>     >                             Chrome has a USB API that was
>     documented to
>     >                             appear to be exactly what I
>     >                             needed (pushing file based data to the
>     >                             device). I spent far too much
>     >                             time learning about USB and getting
>     >                             permission to write to the device to
>     >                             work.
>     >
>     >                             In the end I gave up when I realised there
>     >                             was a really easy hack that
>     >                             was right in front of my nose... just copy
>     >                             the damn .hex file to the
>     >                             device via the built-in file-system API.
>     >
>     >                             It worked first time..! :-)
>     >
>     >                             That's several hours of my time I'll never
>     >                             get back.
>     >
>     >                             Early days. Collaboration welcome!
>     >
>     >                             Best wishes,
>     >
>     >                             Nicholas.
>     >
>     >
>     >                           
>      _______________________________________________
>     >                             Microbit mailing list
>     >                             Microbit at python.org
>     <mailto:Microbit at python.org> <mailto:Microbit at python.org
>     <mailto:Microbit at python.org>>
>     >                             https://mail.python.org/mailman/listinfo/microbit
>     >
>     >
>     >
>     >                         _______________________________________________
>     >                         Microbit mailing list
>     >                         Microbit at python.org
>     <mailto:Microbit at python.org> <mailto:Microbit at python.org
>     <mailto:Microbit at python.org>>
>     >                         https://mail.python.org/mailman/listinfo/microbit
>     >
>     >
>     >
>     >
>     >                     --
>     >                     Naomi Ceder
>     >                     https://plus.google.com/u/0/111396744045017339164/about
>     >
>     >                     _______________________________________________
>     >                     Microbit mailing list
>     >                     Microbit at python.org
>     <mailto:Microbit at python.org> <mailto:Microbit at python.org
>     <mailto:Microbit at python.org>>
>     >                     https://mail.python.org/mailman/listinfo/microbit
>     >
>     >
>     >
>     >                 _______________________________________________
>     >                 Microbit mailing list
>     >                 Microbit at python.org <mailto:Microbit at python.org>
>     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>     >                 https://mail.python.org/mailman/listinfo/microbit
>     >
>     >
>     >
>     >
>     >             --
>     >             Naomi Ceder
>     >             https://plus.google.com/u/0/111396744045017339164/about
>     >
>     >
>     >
>     >
>     >         --
>     >         Naomi Ceder
>     >         https://plus.google.com/u/0/111396744045017339164/about
>     >
>     >         _______________________________________________
>     >         Microbit mailing list
>     >         Microbit at python.org <mailto:Microbit at python.org>
>     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>     >         https://mail.python.org/mailman/listinfo/microbit
>     >
>     >
>     >
>     >     _______________________________________________
>     >     Microbit mailing list
>     >     Microbit at python.org <mailto:Microbit at python.org>
>     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>     >     https://mail.python.org/mailman/listinfo/microbit
>     >
>     >
>     >
>     >
>     > --
>     > Naomi Ceder
>     > https://plus.google.com/u/0/111396744045017339164/about
>     >
>     >
>     > _______________________________________________
>     > Microbit mailing list
>     > Microbit at python.org <mailto:Microbit at python.org>
>     > https://mail.python.org/mailman/listinfo/microbit
>     >
> 
> 
> 
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/c35fa8f6/attachment.sig>

From ntoll at ntoll.org  Mon Dec  7 04:42:13 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 09:42:13 +0000
Subject: [Microbit-Python] Is Bach Prelude in C the right example for
 the musical API?
In-Reply-To: <CAGuvt90EuBugqR4KibV+UTpM2caqwi_sQ4e1_6LD8s1HfB3inA@mail.gmail.com>
References: <CAGuvt93xA5sGOUm3ocVKRKEzo-Njk5Xp+0A9NKyMRbuHKNcajg@mail.gmail.com>
 <56654A87.702@ntoll.org>
 <CAGuvt90EuBugqR4KibV+UTpM2caqwi_sQ4e1_6LD8s1HfB3inA@mail.gmail.com>
Message-ID: <56655475.6070707@ntoll.org>

Cool...

Yes we have rests. The complete API is described here:

http://microbit-micropython.readthedocs.org/en/latest/music.html

"r" is for rests. It's all very simple. ;-)

N.

On 07/12/15 09:39, Nick Sarbicki wrote:
> Sorry tutorial may have been a misleading choice of words.
> 
> I was browsing the github and came across the old example.
> 
> Going over it in more detail I've found several more coded in.
> 
> Out of interest have we got rests programmed into the module?
> 
> Nick.
> 
> On Mon, Dec 7, 2015 at 9:01 AM Nicholas H.Tollervey <ntoll at ntoll.org
> <mailto:ntoll at ntoll.org>> wrote:
> 
>     Hi,
> 
>     Where are you seeing this tutorial? I designed the music API and I've
>     not written a tutorial for it. There's a relatively old music example
>     but that can be easily changed.
> 
>     Totally agree about the music being engaging and appropriate for the
>     target year group.
> 
>     N.
> 
>     On 06/12/15 21:15, Nick Sarbicki wrote:
>     > Sorry if this has already been discussed. I've skimmed the previous
>     > threads and haven't found anything on this.
>     >
>     > I for one love Bach.
>     >
>     > My 9 year old nephew only knows him from being forced to play Bach
>     > pieces during piano lessons.
>     >
>     > Most other kids I teach at the Dojo I'm fairly sure wouldn't have
>     a clue.
>     >
>     > Do we think it would be better to have a different song as the main
>     > tutorial for the music API? My immediate thought was The Entertainer
>     > which most kids are taught at school (they still are right? I'm
>     not just
>     > getting old?). But maybe even that is too old-fashioned.
>     >
>     > If we want to actively address the gender imbalance in programming
>     today
>     > we could even put on "Let It Go" (that was a joke, please don't
>     take it
>     > seriously).
>     >
>     > - Nick.
>     >
>     >
>     > _______________________________________________
>     > Microbit mailing list
>     > Microbit at python.org <mailto:Microbit at python.org>
>     > https://mail.python.org/mailman/listinfo/microbit
>     >
> 
> 
> 
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/53816fbd/attachment-0001.sig>

From tom at viner.tv  Mon Dec  7 04:53:15 2015
From: tom at viner.tv (Tom Viner)
Date: Mon, 7 Dec 2015 09:53:15 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
Message-ID: <CANBSuyEpw-nvT+-O+3MGN27FLQ8bQXPEyqJ=-TmQobi7r7cXiQ@mail.gmail.com>

Thanks Naomi. Now I have the same warning as you:

There were warnings when trying to install this extension:
    'fileSystem.requestFileSystem' is not allowed for specified platform

I can flash, but the repl doesn't work. My keys get echoed to the chrome
console, but not in the repl window, and nothing back from the microbit.

On 6 December 2015 at 23:13, Naomi Ceder <naomi.ceder at gmail.com> wrote:

> Tom, use the entire base directory as the unpacked extension - that worked
> for me.
>
> Naomi
>
> On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv> wrote:
>
>> I'm opening python-native-editor/index.html in Chrome and I don't see how
>> to get any extension (and there doesn't appear to be unpacked extension to load
>> in developer
>> <https://developer.chrome.com/extensions/getstarted#unpacked> mode
>> either).
>>
>> I just get:
>> repl.js:75 Uncaught TypeError: Cannot read property 'sync' of undefined
>>
>> on the line:
>> hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync);
>>
>> On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>>
>>> Ooops! My apologies! I see from looking at the code that new, open and
>>> save are not yet implemented, just stubbed out, it appears.
>>>
>>> I misunderstood that. Never mind.
>>>
>>> Naomi
>>>
>>> On 6 December 2015 at 16:43, Naomi Ceder <naomi.ceder at gmail.com> wrote:
>>>
>>>> Thanks for the reference Carlos. That makes sense...
>>>>
>>>> At any rate, when I removed that permission, the warning of course went
>>>> away. However it still coudn't find my micro:bit, since the port objects
>>>> have neither a productId nor a vendorId on my system, only a path. When I
>>>> matched on the path to what I knew to be the right path, I could get a repl
>>>> working just fine. Which would imply that a different way of finding the
>>>> right port is needed.
>>>>
>>>> I suppose the next thing is to look at the load/save issue.
>>>>
>>>> Cheers,
>>>> Naomi
>>>>
>>>> On 6 December 2015 at 16:25, Carlos P.A. <carlos.p.a.87 at gmail.com>
>>>> wrote:
>>>>
>>>>> Looks like RequestFileSystem might only be supported in ChromeOS, is
>>>>> that the platform you've been using Nicholas?
>>>>>
>>>>>
>>>>> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>>>>>
>>>>> On 6 December 2015 at 22:09, Naomi Ceder <naomi.ceder at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Sadly I can't get the extension to work on either OSX or Linux -
>>>>>> instead, the extension reports
>>>>>>
>>>>>>  There were warnings when trying to install this extension:
>>>>>>
>>>>>>    - 'fileSystem.requestFileSystem' is not allowed for specified
>>>>>>    platform.
>>>>>>
>>>>>>
>>>>>> So the result for me is that the new, open, and save functions don't
>>>>>> do anything at all, and the repl says it can't find the microbit.
>>>>>>
>>>>>> I'm not finding any explanations of line, but I've attached a screen
>>>>>> shot of the warning...
>>>>>>
>>>>>> I'm also not seeing any setting for Chrome that would seem to help.
>>>>>>
>>>>>> Cheers,
>>>>>> Naomi
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 6 December 2015 at 15:15, Carlos P.A. <carlos.p.a.87 at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Excellent work Nicholas!
>>>>>>>
>>>>>>> Will the pluggin also automatically work when the interface is
>>>>>>> accessed from the https://www.microbit.co.uk/create-code python
>>>>>>> link? (once it is implemented in the webiste).
>>>>>>>
>>>>>>> As a small suggestion, probably with a low priority, is that having
>>>>>>> some visual feedback on the page that the program is being flashed would be
>>>>>>> ideal, even better if there was a tiny progress bar on the button.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Carlos
>>>>>>>
>>>>>>> On 6 December 2015 at 20:34, Nicholas H.Tollervey <ntoll at ntoll.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Basically, this:
>>>>>>>>
>>>>>>>> https://www.youtube.com/watch?v=S8MGFVuZrrs
>>>>>>>>
>>>>>>>> ...is a first draft and the source code is here:
>>>>>>>>
>>>>>>>> https://github.com/ntoll/python-native-editor
>>>>>>>>
>>>>>>>> There's no documentation and I'll be working on it over the coming
>>>>>>>> days
>>>>>>>> with a view to showing it on Wednesday to a bunch of teachers.
>>>>>>>>
>>>>>>>> FYI - working out how to flash the device took several tortuous
>>>>>>>> days.
>>>>>>>> Chrome has a USB API that was documented to appear to be exactly
>>>>>>>> what I
>>>>>>>> needed (pushing file based data to the device). I spent far too much
>>>>>>>> time learning about USB and getting permission to write to the
>>>>>>>> device to
>>>>>>>> work.
>>>>>>>>
>>>>>>>> In the end I gave up when I realised there was a really easy hack
>>>>>>>> that
>>>>>>>> was right in front of my nose... just copy the damn .hex file to the
>>>>>>>> device via the built-in file-system API.
>>>>>>>>
>>>>>>>> It worked first time..! :-)
>>>>>>>>
>>>>>>>> That's several hours of my time I'll never get back.
>>>>>>>>
>>>>>>>> Early days. Collaboration welcome!
>>>>>>>>
>>>>>>>> Best wishes,
>>>>>>>>
>>>>>>>> Nicholas.
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Microbit mailing list
>>>>>>>> Microbit at python.org
>>>>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Microbit mailing list
>>>>>>> Microbit at python.org
>>>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Naomi Ceder
>>>>>> https://plus.google.com/u/0/111396744045017339164/about
>>>>>>
>>>>>> _______________________________________________
>>>>>> Microbit mailing list
>>>>>> Microbit at python.org
>>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Microbit mailing list
>>>>> Microbit at python.org
>>>>> https://mail.python.org/mailman/listinfo/microbit
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Naomi Ceder
>>>> https://plus.google.com/u/0/111396744045017339164/about
>>>>
>>>
>>>
>>>
>>> --
>>> Naomi Ceder
>>> https://plus.google.com/u/0/111396744045017339164/about
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
>
> --
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/d4a5705f/attachment.html>

From ntoll at ntoll.org  Mon Dec  7 04:55:37 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 09:55:37 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <CANBSuyEpw-nvT+-O+3MGN27FLQ8bQXPEyqJ=-TmQobi7r7cXiQ@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <CANBSuyEpw-nvT+-O+3MGN27FLQ8bQXPEyqJ=-TmQobi7r7cXiQ@mail.gmail.com>
Message-ID: <56655799.1000106@ntoll.org>

Tom,

Are you in the correct group for permission to use serial connectivity
via USB?

N.

On 07/12/15 09:53, Tom Viner wrote:
> Thanks Naomi. Now I have the same warning as you:
> 
> There were warnings when trying to install this extension:
>     'fileSystem.requestFileSystem' is not allowed for specified platform
> 
> I can flash, but the repl doesn't work. My keys get echoed to the chrome
> console, but not in the repl window, and nothing back from the microbit.
> 
> On 6 December 2015 at 23:13, Naomi Ceder <naomi.ceder at gmail.com
> <mailto:naomi.ceder at gmail.com>> wrote:
> 
>     Tom, use the entire base directory as the unpacked extension - that
>     worked for me.
> 
>     Naomi
> 
>     On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv
>     <mailto:tom at viner.tv>> wrote:
> 
>         I'm opening python-native-editor/index.html in Chrome and I
>         don't see how to get any extension (and there doesn't appear to
>         be unpacked extension to load in developer
>         <https://developer.chrome.com/extensions/getstarted#unpacked>
>         mode either).
> 
>         I just get:
>         repl.js:75 Uncaught TypeError: Cannot read property 'sync' of
>         undefined
> 
>         on the line:
>         hterm.defaultStorage = new lib.Storage.Chrome(chrome.storage.sync); 
> 
>         On 6 December 2015 at 22:53, Naomi Ceder <naomi.ceder at gmail.com
>         <mailto:naomi.ceder at gmail.com>> wrote:
> 
>             Ooops! My apologies! I see from looking at the code that
>             new, open and save are not yet implemented, just stubbed
>             out, it appears. 
> 
>             I misunderstood that. Never mind.
> 
>             Naomi
> 
>             On 6 December 2015 at 16:43, Naomi Ceder
>             <naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>> wrote:
> 
>                 Thanks for the reference Carlos. That makes sense...
> 
>                 At any rate, when I removed that permission, the warning
>                 of course went away. However it still coudn't find my
>                 micro:bit, since the port objects have neither a
>                 productId nor a vendorId on my system, only a path. When
>                 I matched on the path to what I knew to be the right
>                 path, I could get a repl working just fine. Which would
>                 imply that a different way of finding the right port is
>                 needed.
> 
>                 I suppose the next thing is to look at the load/save issue.
> 
>                 Cheers,
>                 Naomi
> 
>                 On 6 December 2015 at 16:25, Carlos P.A.
>                 <carlos.p.a.87 at gmail.com
>                 <mailto:carlos.p.a.87 at gmail.com>> wrote:
> 
>                     Looks like RequestFileSystem might only be supported
>                     in ChromeOS, is that the platform you've been using
>                     Nicholas?
> 
>                     https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
> 
>                     On 6 December 2015 at 22:09, Naomi Ceder
>                     <naomi.ceder at gmail.com
>                     <mailto:naomi.ceder at gmail.com>> wrote:
> 
>                         Sadly I can't get the extension to work on
>                         either OSX or Linux - instead, the extension reports
> 
>                          There were warnings when trying to install this
>                         extension:
> 
>                           * 'fileSystem.requestFileSystem' is not
>                             allowed for specified platform.
> 
> 
>                         So the result for me is that the new, open, and
>                         save functions don't do anything at all, and the
>                         repl says it can't find the microbit. 
> 
>                         I'm not finding any explanations of line, but
>                         I've attached a screen shot of the warning... 
> 
>                         I'm also not seeing any setting for Chrome that
>                         would seem to help.
> 
>                         Cheers,
>                         Naomi
> 
> 
> 
>                         On 6 December 2015 at 15:15, Carlos P.A.
>                         <carlos.p.a.87 at gmail.com
>                         <mailto:carlos.p.a.87 at gmail.com>> wrote:
> 
>                             Excellent work Nicholas!
> 
>                             Will the pluggin also automatically work
>                             when the interface is accessed from the
>                             https://www.microbit.co.uk/create-code
>                             python link? (once it is implemented in the
>                             webiste).
> 
>                             As a small suggestion, probably with a low
>                             priority, is that having some visual
>                             feedback on the page that the program is
>                             being flashed would be ideal, even better if
>                             there was a tiny progress bar on the button.
> 
>                             Regards,
>                             Carlos
> 
>                             On 6 December 2015 at 20:34, Nicholas
>                             H.Tollervey <ntoll at ntoll.org
>                             <mailto:ntoll at ntoll.org>> wrote:
> 
>                                 Basically, this:
> 
>                                 https://www.youtube.com/watch?v=S8MGFVuZrrs
> 
>                                 ...is a first draft and the source code
>                                 is here:
> 
>                                 https://github.com/ntoll/python-native-editor
> 
>                                 There's no documentation and I'll be
>                                 working on it over the coming days
>                                 with a view to showing it on Wednesday
>                                 to a bunch of teachers.
> 
>                                 FYI - working out how to flash the
>                                 device took several tortuous days.
>                                 Chrome has a USB API that was documented
>                                 to appear to be exactly what I
>                                 needed (pushing file based data to the
>                                 device). I spent far too much
>                                 time learning about USB and getting
>                                 permission to write to the device to
>                                 work.
> 
>                                 In the end I gave up when I realised
>                                 there was a really easy hack that
>                                 was right in front of my nose... just
>                                 copy the damn .hex file to the
>                                 device via the built-in file-system API.
> 
>                                 It worked first time..! :-)
> 
>                                 That's several hours of my time I'll
>                                 never get back.
> 
>                                 Early days. Collaboration welcome!
> 
>                                 Best wishes,
> 
>                                 Nicholas.
> 
> 
>                                 _______________________________________________
>                                 Microbit mailing list
>                                 Microbit at python.org
>                                 <mailto:Microbit at python.org>
>                                 https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
>                             _______________________________________________
>                             Microbit mailing list
>                             Microbit at python.org <mailto:Microbit at python.org>
>                             https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
>                         -- 
>                         Naomi Ceder
>                         https://plus.google.com/u/0/111396744045017339164/about
> 
>                         _______________________________________________
>                         Microbit mailing list
>                         Microbit at python.org <mailto:Microbit at python.org>
>                         https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
>                     _______________________________________________
>                     Microbit mailing list
>                     Microbit at python.org <mailto:Microbit at python.org>
>                     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
>                 -- 
>                 Naomi Ceder
>                 https://plus.google.com/u/0/111396744045017339164/about
> 
> 
> 
> 
>             -- 
>             Naomi Ceder
>             https://plus.google.com/u/0/111396744045017339164/about
> 
>             _______________________________________________
>             Microbit mailing list
>             Microbit at python.org <mailto:Microbit at python.org>
>             https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
>         _______________________________________________
>         Microbit mailing list
>         Microbit at python.org <mailto:Microbit at python.org>
>         https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
>     -- 
>     Naomi Ceder
>     https://plus.google.com/u/0/111396744045017339164/about
> 
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/55366aba/attachment-0001.sig>

From mail at timgolden.me.uk  Mon Dec  7 05:04:30 2015
From: mail at timgolden.me.uk (Tim Golden)
Date: Mon, 7 Dec 2015 10:04:30 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <56654D9C.3090401@ntoll.org>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org>
Message-ID: <566559AE.5080208@timgolden.me.uk>

On 07/12/2015 09:13, Nicholas H.Tollervey wrote:
> This will be a Chrome App that you download and install from Google's
> "App Store" thingamabob for Chrome Apps. When you download the app
> you'll be walked through the permissions required (that you accept or
> decline). I'm doing my work on Debian Jessie and it worked for me. This
> is a very important user journey, but one that I can't test until we
> have something semi-functional telling us what the permissions need to
> be (currently, storage, serial and filesystem).

I'm only following this at a distance but... Raspberry Pi? I know it's
now running Jessie, but can it handle Chrome / Chromium? Looking a
little tricky if I'm reading things aright:

https://medium.com/@icebob/jessie-on-raspberry-pi-2-with-docker-and-chromium-c43b8d80e7e1#.9g5xnqtju

(I'm not clear whether RPi is to be considered a primary target platform
for the Python Microbit work or not).

TJG

From ntoll at ntoll.org  Mon Dec  7 05:06:39 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 10:06:39 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <566559AE.5080208@timgolden.me.uk>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org> <566559AE.5080208@timgolden.me.uk>
Message-ID: <56655A2F.3080801@ntoll.org>

On 07/12/15 10:04, Tim Golden wrote:
> On 07/12/2015 09:13, Nicholas H.Tollervey wrote:
>> This will be a Chrome App that you download and install from Google's
>> "App Store" thingamabob for Chrome Apps. When you download the app
>> you'll be walked through the permissions required (that you accept or
>> decline). I'm doing my work on Debian Jessie and it worked for me. This
>> is a very important user journey, but one that I can't test until we
>> have something semi-functional telling us what the permissions need to
>> be (currently, storage, serial and filesystem).
> 
> I'm only following this at a distance but... Raspberry Pi? I know it's
> now running Jessie, but can it handle Chrome / Chromium? Looking a
> little tricky if I'm reading things aright:
> 
> https://medium.com/@icebob/jessie-on-raspberry-pi-2-with-docker-and-chromium-c43b8d80e7e1#.9g5xnqtju
> 
> (I'm not clear whether RPi is to be considered a primary target platform
> for the Python Microbit work or not).
> 
> TJG
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


I've been chatting with Ben N. about RPi support. Once we're happy,
they're happy to include command line packages for creating a hex and
flashing into Raspbian. Users can use whatever editor they like then...

WRT REPL... they already have picocom as a package for that sort of thing.

N.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/21b6212c/attachment.sig>

From mail at timgolden.me.uk  Mon Dec  7 05:11:28 2015
From: mail at timgolden.me.uk (Tim Golden)
Date: Mon, 7 Dec 2015 10:11:28 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <56655A2F.3080801@ntoll.org>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org> <566559AE.5080208@timgolden.me.uk>
 <56655A2F.3080801@ntoll.org>
Message-ID: <56655B50.3070906@timgolden.me.uk>

On 07/12/2015 10:06, Nicholas H.Tollervey wrote:
> I've been chatting with Ben N. about RPi support. Once we're happy,
> they're happy to include command line packages for creating a hex and
> flashing into Raspbian. Users can use whatever editor they like then...
> 
> WRT REPL... they already have picocom as a package for that sort of thing.

Thanks

TJG

From carlos.p.a.87 at gmail.com  Mon Dec  7 07:33:17 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Mon, 7 Dec 2015 12:33:17 +0000
Subject: [Microbit-Python] A native editor
In-Reply-To: <56655423.1070602@ntoll.org>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org>
 <CAC_p0yAhfCqfm8ULs+fJ0k390Y-EuZR_rBhzBuwN9vygg=iwFQ@mail.gmail.com>
 <56655423.1070602@ntoll.org>
Message-ID: <CAC_p0yBSw0xcrJQO1Ytpp+9kQDhMtrHCtCVrCF7WBtG7vXNqUA@mail.gmail.com>

If anybody was wondering about Puppy as I was:
https://github.com/lordmauve/puppy
Looks promising, if it works well I don't see why it couldn't be packed as
a stand alone application without dependencies, could probably be used in
the raspberry pi as well.

On 7 December 2015 at 09:40, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Hah!
>
> Not Puppy the PHP framework.
>
> Puppy is a Python editor for kids. It's written in Python with QT as the
> UI framework.
>
> ;-)
>
> N.
>
> On 07/12/15 09:34, Carlos P.A. wrote:
> >> In an ideal world we'd have just a static .exe for Windows that gave us
> >> something functionally equivalent to what I've done already. I might
> >>take a look at some of the Puppy work myself, Dan Pope and Damien did to
> >> see if this is possible.
> >
> > Puppy the PHP framework? If we are okay with pivoting tech at this
> > point, might I suggest Electron using node.js? I've used it to pack web
> > app applications for desktop (windows, mac, linux and even arm linux)
> > and will definitely work for this kind of requirements. You can create
> > executables or have them as a "portable apps", which could then probably
> > be packed into a single .exe file for windows. The only downside is the
> > application size might not be all that small, as it packs the chromium
> > embedded engine with it (so > 50Mbs compressed).
> >
> > On 7 December 2015 at 09:13, Nicholas H.Tollervey <ntoll at ntoll.org
> > <mailto:ntoll at ntoll.org>> wrote:
> >
> >     Folks,
> >
> >     None of this is documented, it's unfinished and is basically a
> working
> >     brain dump. Give me some time to write up what I've done..! (I was
> doing
> >     this most evening's last week and over the weekend. By Sunday
> evening I
> >     was sick of the site of the damn thing - especially after most of the
> >     time I'd spent on it was wasted on the non-working USB API).
> >
> >     I'll get to it, but in the meantime:
> >
> >     This will be a Chrome App that you download and install from Google's
> >     "App Store" thingamabob for Chrome Apps. When you download the app
> >     you'll be walked through the permissions required (that you accept or
> >     decline). I'm doing my work on Debian Jessie and it worked for me.
> This
> >     is a very important user journey, but one that I can't test until we
> >     have something semi-functional telling us what the permissions need
> to
> >     be (currently, storage, serial and filesystem).
> >
> >     I'm using Google's "Chrome Dev Editor" to do this work
> >     (
> https://chrome.google.com/webstore/detail/chrome-dev-editor-develop/pnoffddplpippgcfjdhbmhkofpnaalpg
> ).
> >     I suggest you use it too.
> >
> >     Like I said... a very early brain dump.
> >
> >     In an ideal world we'd have just a static .exe for Windows that gave
> us
> >     something functionally equivalent to what I've done already. I might
> >     take a look at some of the Puppy work myself, Dan Pope and Damien
> did to
> >     see if this is possible.
> >
> >     Basically, all the amazing work on MicroPython should be easily
> >     accessible. Teachers have a bad time of it. I want to fix that
> problem
> >     and I'm doing so in public so those who want to help can dive in.
> >
> >     N.
> >
> >     On 06/12/15 23:13, Naomi Ceder wrote:
> >     > Tom, use the entire base directory as the unpacked extension - that
> >     > worked for me.
> >     >
> >     > Naomi
> >     >
> >     > On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv <mailto:
> tom at viner.tv>
> >     > <mailto:tom at viner.tv <mailto:tom at viner.tv>>> wrote:
> >     >
> >     >     I'm opening python-native-editor/index.html in Chrome and I
> don't
> >     >     see how to get any extension (and there doesn't appear to be
> >     >     unpacked extension to load in developer
> >     >     <https://developer.chrome.com/extensions/getstarted#unpacked>
> mode
> >     >     either).
> >     >
> >     >     I just get:
> >     >     repl.js:75 Uncaught TypeError: Cannot read property 'sync' of
> undefined
> >     >
> >     >     on the line:
> >     >     hterm.defaultStorage = new
> lib.Storage.Chrome(chrome.storage.sync);
> >     >
> >     >     On 6 December 2015 at 22:53, Naomi Ceder <
> naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>
> >     >     <mailto:naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>>>
> wrote:
> >     >
> >     >         Ooops! My apologies! I see from looking at the code that
> new,
> >     >         open and save are not yet implemented, just stubbed out, it
> >     >         appears.
> >     >
> >     >         I misunderstood that. Never mind.
> >     >
> >     >         Naomi
> >     >
> >     >         On 6 December 2015 at 16:43, Naomi Ceder <
> naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>
> >     >         <mailto:naomi.ceder at gmail.com <mailto:
> naomi.ceder at gmail.com>>> wrote:
> >     >
> >     >             Thanks for the reference Carlos. That makes sense...
> >     >
> >     >             At any rate, when I removed that permission, the
> warning of
> >     >             course went away. However it still coudn't find my
> >     >             micro:bit, since the port objects have neither a
> productId
> >     >             nor a vendorId on my system, only a path. When I
> matched on
> >     >             the path to what I knew to be the right path, I could
> get a
> >     >             repl working just fine. Which would imply that a
> different
> >     >             way of finding the right port is needed.
> >     >
> >     >             I suppose the next thing is to look at the load/save
> issue.
> >     >
> >     >             Cheers,
> >     >             Naomi
> >     >
> >     >             On 6 December 2015 at 16:25, Carlos P.A.
> >     >             <carlos.p.a.87 at gmail.com
> >     <mailto:carlos.p.a.87 at gmail.com> <mailto:carlos.p.a.87 at gmail.com
> >     <mailto:carlos.p.a.87 at gmail.com>>>
> >     >             wrote:
> >     >
> >     >                 Looks like RequestFileSystem might only be
> supported in
> >     >                 ChromeOS, is that the platform you've been using
> Nicholas?
> >     >
> >     >
> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
> >     >
> >     >                 On 6 December 2015 at 22:09, Naomi Ceder
> >     >                 <naomi.ceder at gmail.com
> >     <mailto:naomi.ceder at gmail.com> <mailto:naomi.ceder at gmail.com
> >     <mailto:naomi.ceder at gmail.com>>>
> >     >                 wrote:
> >     >
> >     >                     Sadly I can't get the extension to work on
> either
> >     >                     OSX or Linux - instead, the extension reports
> >     >
> >     >                      There were warnings when trying to install
> this
> >     >                     extension:
> >     >
> >     >                       * 'fileSystem.requestFileSystem' is not
> allowed
> >     >                         for specified platform.
> >     >
> >     >
> >     >                     So the result for me is that the new, open,
> and save
> >     >                     functions don't do anything at all, and the
> repl
> >     >                     says it can't find the microbit.
> >     >
> >     >                     I'm not finding any explanations of line, but
> I've
> >     >                     attached a screen shot of the warning...
> >     >
> >     >                     I'm also not seeing any setting for Chrome that
> >     >                     would seem to help.
> >     >
> >     >                     Cheers,
> >     >                     Naomi
> >     >
> >     >
> >     >
> >     >                     On 6 December 2015 at 15:15, Carlos P.A.
> >     >                     <carlos.p.a.87 at gmail.com <mailto:
> carlos.p.a.87 at gmail.com>
> >     >                     <mailto:carlos.p.a.87 at gmail.com <mailto:
> carlos.p.a.87 at gmail.com>>> wrote:
> >     >
> >     >                         Excellent work Nicholas!
> >     >
> >     >                         Will the pluggin also automatically work
> when
> >     >                         the interface is accessed from the
> >     >                         https://www.microbit.co.uk/create-code
> python
> >     >                         link? (once it is implemented in the
> webiste).
> >     >
> >     >                         As a small suggestion, probably with a low
> >     >                         priority, is that having some visual
> feedback on
> >     >                         the page that the program is being flashed
> would
> >     >                         be ideal, even better if there was a tiny
> >     >                         progress bar on the button.
> >     >
> >     >                         Regards,
> >     >                         Carlos
> >     >
> >     >                         On 6 December 2015 at 20:34, Nicholas
> >     >                         H.Tollervey <ntoll at ntoll.org <mailto:
> ntoll at ntoll.org>
> >     >                         <mailto:ntoll at ntoll.org
> >     <mailto:ntoll at ntoll.org>>> wrote:
> >     >
> >     >                             Basically, this:
> >     >
> >     >
> >      https://www.youtube.com/watch?v=S8MGFVuZrrs
> >     >
> >     >                             ...is a first draft and the source
> >     code is here:
> >     >
> >     >
> >      https://github.com/ntoll/python-native-editor
> >     >
> >     >                             There's no documentation and I'll be
> >     working
> >     >                             on it over the coming days
> >     >                             with a view to showing it on Wednesday
> >     to a
> >     >                             bunch of teachers.
> >     >
> >     >                             FYI - working out how to flash the
> device
> >     >                             took several tortuous days.
> >     >                             Chrome has a USB API that was
> >     documented to
> >     >                             appear to be exactly what I
> >     >                             needed (pushing file based data to the
> >     >                             device). I spent far too much
> >     >                             time learning about USB and getting
> >     >                             permission to write to the device to
> >     >                             work.
> >     >
> >     >                             In the end I gave up when I realised
> there
> >     >                             was a really easy hack that
> >     >                             was right in front of my nose... just
> copy
> >     >                             the damn .hex file to the
> >     >                             device via the built-in file-system
> API.
> >     >
> >     >                             It worked first time..! :-)
> >     >
> >     >                             That's several hours of my time I'll
> never
> >     >                             get back.
> >     >
> >     >                             Early days. Collaboration welcome!
> >     >
> >     >                             Best wishes,
> >     >
> >     >                             Nicholas.
> >     >
> >     >
> >     >
> >      _______________________________________________
> >     >                             Microbit mailing list
> >     >                             Microbit at python.org
> >     <mailto:Microbit at python.org> <mailto:Microbit at python.org
> >     <mailto:Microbit at python.org>>
> >     >
> https://mail.python.org/mailman/listinfo/microbit
> >     >
> >     >
> >     >
> >     >
>  _______________________________________________
> >     >                         Microbit mailing list
> >     >                         Microbit at python.org
> >     <mailto:Microbit at python.org> <mailto:Microbit at python.org
> >     <mailto:Microbit at python.org>>
> >     >
> https://mail.python.org/mailman/listinfo/microbit
> >     >
> >     >
> >     >
> >     >
> >     >                     --
> >     >                     Naomi Ceder
> >     >
> https://plus.google.com/u/0/111396744045017339164/about
> >     >
> >     >                     _______________________________________________
> >     >                     Microbit mailing list
> >     >                     Microbit at python.org
> >     <mailto:Microbit at python.org> <mailto:Microbit at python.org
> >     <mailto:Microbit at python.org>>
> >     >
> https://mail.python.org/mailman/listinfo/microbit
> >     >
> >     >
> >     >
> >     >                 _______________________________________________
> >     >                 Microbit mailing list
> >     >                 Microbit at python.org <mailto:Microbit at python.org>
> >     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
> >     >                 https://mail.python.org/mailman/listinfo/microbit
> >     >
> >     >
> >     >
> >     >
> >     >             --
> >     >             Naomi Ceder
> >     >
> https://plus.google.com/u/0/111396744045017339164/about
> >     >
> >     >
> >     >
> >     >
> >     >         --
> >     >         Naomi Ceder
> >     >         https://plus.google.com/u/0/111396744045017339164/about
> >     >
> >     >         _______________________________________________
> >     >         Microbit mailing list
> >     >         Microbit at python.org <mailto:Microbit at python.org>
> >     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
> >     >         https://mail.python.org/mailman/listinfo/microbit
> >     >
> >     >
> >     >
> >     >     _______________________________________________
> >     >     Microbit mailing list
> >     >     Microbit at python.org <mailto:Microbit at python.org>
> >     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
> >     >     https://mail.python.org/mailman/listinfo/microbit
> >     >
> >     >
> >     >
> >     >
> >     > --
> >     > Naomi Ceder
> >     > https://plus.google.com/u/0/111396744045017339164/about
> >     >
> >     >
> >     > _______________________________________________
> >     > Microbit mailing list
> >     > Microbit at python.org <mailto:Microbit at python.org>
> >     > https://mail.python.org/mailman/listinfo/microbit
> >     >
> >
> >
> >
> >     _______________________________________________
> >     Microbit mailing list
> >     Microbit at python.org <mailto:Microbit at python.org>
> >     https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/1cb5c6ea/attachment-0001.html>

From naomi.ceder at gmail.com  Mon Dec  7 12:08:50 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Mon, 7 Dec 2015 11:08:50 -0600
Subject: [Microbit-Python] A native editor
In-Reply-To: <CAC_p0yBSw0xcrJQO1Ytpp+9kQDhMtrHCtCVrCF7WBtG7vXNqUA@mail.gmail.com>
References: <56649BDF.9030002@ntoll.org>
 <CAC_p0yBg06yYANJQBsaVo84PS==ge+P+kvq4Zjv+_P1V65x+5w@mail.gmail.com>
 <CAKvj0qR=LgeV633aEfzO4kogvRPuFbTJkLmB0jPLgv-zTuY80g@mail.gmail.com>
 <CAC_p0yBsXfKQZA2eFFP_vUMCSOCyv-SQz7R0QDv0p-pWPe4PLg@mail.gmail.com>
 <CAKvj0qT3Vq-A9W0avYLzn92p3az=4B2CrzmauOFMuWTt8Y2w9A@mail.gmail.com>
 <CAKvj0qQPgZrZquuyU8tS7kB+zrF5VT7BK2UqExp93Y8=BUqadg@mail.gmail.com>
 <CANBSuyGi+3WQBUV_h3zOD=hUZScg0R3DD9qm3rt017Tkj4JmBQ@mail.gmail.com>
 <CAKvj0qQHJHjb6k1FQK8w9e0gdeBbNisWrnpvEpujm6v49Mq_iA@mail.gmail.com>
 <56654D9C.3090401@ntoll.org>
 <CAC_p0yAhfCqfm8ULs+fJ0k390Y-EuZR_rBhzBuwN9vygg=iwFQ@mail.gmail.com>
 <56655423.1070602@ntoll.org>
 <CAC_p0yBSw0xcrJQO1Ytpp+9kQDhMtrHCtCVrCF7WBtG7vXNqUA@mail.gmail.com>
Message-ID: <CAKvj0qRXtDV84DSO3aWdrPLpjz2Jb00=vnq0rpMpVwb8MyGE7g@mail.gmail.com>

As a point of information, it seems that Chrome and the Chromium browser
behave differently. On Debian Jessie, using Chrome the , "requestFileSystem"
is not supported and the warning appears. Using Chromium, however, there is
no warning on that permission.

If that specific permission is needed it looks like there might be trouble
with the vast majority of us who hate freedom and use the non-free Chrome.
But there still must be a way to save a file locally.

Naomi

On 7 December 2015 at 06:33, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:

> If anybody was wondering about Puppy as I was:
> https://github.com/lordmauve/puppy
> Looks promising, if it works well I don't see why it couldn't be packed as
> a stand alone application without dependencies, could probably be used in
> the raspberry pi as well.
>
> On 7 December 2015 at 09:40, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
>
>> Hah!
>>
>> Not Puppy the PHP framework.
>>
>> Puppy is a Python editor for kids. It's written in Python with QT as the
>> UI framework.
>>
>> ;-)
>>
>> N.
>>
>> On 07/12/15 09:34, Carlos P.A. wrote:
>> >> In an ideal world we'd have just a static .exe for Windows that gave us
>> >> something functionally equivalent to what I've done already. I might
>> >>take a look at some of the Puppy work myself, Dan Pope and Damien did to
>> >> see if this is possible.
>> >
>> > Puppy the PHP framework? If we are okay with pivoting tech at this
>> > point, might I suggest Electron using node.js? I've used it to pack web
>> > app applications for desktop (windows, mac, linux and even arm linux)
>> > and will definitely work for this kind of requirements. You can create
>> > executables or have them as a "portable apps", which could then probably
>> > be packed into a single .exe file for windows. The only downside is the
>> > application size might not be all that small, as it packs the chromium
>> > embedded engine with it (so > 50Mbs compressed).
>> >
>> > On 7 December 2015 at 09:13, Nicholas H.Tollervey <ntoll at ntoll.org
>> > <mailto:ntoll at ntoll.org>> wrote:
>> >
>> >     Folks,
>> >
>> >     None of this is documented, it's unfinished and is basically a
>> working
>> >     brain dump. Give me some time to write up what I've done..! (I was
>> doing
>> >     this most evening's last week and over the weekend. By Sunday
>> evening I
>> >     was sick of the site of the damn thing - especially after most of
>> the
>> >     time I'd spent on it was wasted on the non-working USB API).
>> >
>> >     I'll get to it, but in the meantime:
>> >
>> >     This will be a Chrome App that you download and install from
>> Google's
>> >     "App Store" thingamabob for Chrome Apps. When you download the app
>> >     you'll be walked through the permissions required (that you accept
>> or
>> >     decline). I'm doing my work on Debian Jessie and it worked for me.
>> This
>> >     is a very important user journey, but one that I can't test until we
>> >     have something semi-functional telling us what the permissions need
>> to
>> >     be (currently, storage, serial and filesystem).
>> >
>> >     I'm using Google's "Chrome Dev Editor" to do this work
>> >     (
>> https://chrome.google.com/webstore/detail/chrome-dev-editor-develop/pnoffddplpippgcfjdhbmhkofpnaalpg
>> ).
>> >     I suggest you use it too.
>> >
>> >     Like I said... a very early brain dump.
>> >
>> >     In an ideal world we'd have just a static .exe for Windows that
>> gave us
>> >     something functionally equivalent to what I've done already. I might
>> >     take a look at some of the Puppy work myself, Dan Pope and Damien
>> did to
>> >     see if this is possible.
>> >
>> >     Basically, all the amazing work on MicroPython should be easily
>> >     accessible. Teachers have a bad time of it. I want to fix that
>> problem
>> >     and I'm doing so in public so those who want to help can dive in.
>> >
>> >     N.
>> >
>> >     On 06/12/15 23:13, Naomi Ceder wrote:
>> >     > Tom, use the entire base directory as the unpacked extension -
>> that
>> >     > worked for me.
>> >     >
>> >     > Naomi
>> >     >
>> >     > On 6 December 2015 at 17:11, Tom Viner <tom at viner.tv <mailto:
>> tom at viner.tv>
>> >     > <mailto:tom at viner.tv <mailto:tom at viner.tv>>> wrote:
>> >     >
>> >     >     I'm opening python-native-editor/index.html in Chrome and I
>> don't
>> >     >     see how to get any extension (and there doesn't appear to be
>> >     >     unpacked extension to load in developer
>> >     >     <https://developer.chrome.com/extensions/getstarted#unpacked>
>> mode
>> >     >     either).
>> >     >
>> >     >     I just get:
>> >     >     repl.js:75 Uncaught TypeError: Cannot read property 'sync' of
>> undefined
>> >     >
>> >     >     on the line:
>> >     >     hterm.defaultStorage = new
>> lib.Storage.Chrome(chrome.storage.sync);
>> >     >
>> >     >     On 6 December 2015 at 22:53, Naomi Ceder <
>> naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>
>> >     >     <mailto:naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>>>
>> wrote:
>> >     >
>> >     >         Ooops! My apologies! I see from looking at the code that
>> new,
>> >     >         open and save are not yet implemented, just stubbed out,
>> it
>> >     >         appears.
>> >     >
>> >     >         I misunderstood that. Never mind.
>> >     >
>> >     >         Naomi
>> >     >
>> >     >         On 6 December 2015 at 16:43, Naomi Ceder <
>> naomi.ceder at gmail.com <mailto:naomi.ceder at gmail.com>
>> >     >         <mailto:naomi.ceder at gmail.com <mailto:
>> naomi.ceder at gmail.com>>> wrote:
>> >     >
>> >     >             Thanks for the reference Carlos. That makes sense...
>> >     >
>> >     >             At any rate, when I removed that permission, the
>> warning of
>> >     >             course went away. However it still coudn't find my
>> >     >             micro:bit, since the port objects have neither a
>> productId
>> >     >             nor a vendorId on my system, only a path. When I
>> matched on
>> >     >             the path to what I knew to be the right path, I could
>> get a
>> >     >             repl working just fine. Which would imply that a
>> different
>> >     >             way of finding the right port is needed.
>> >     >
>> >     >             I suppose the next thing is to look at the load/save
>> issue.
>> >     >
>> >     >             Cheers,
>> >     >             Naomi
>> >     >
>> >     >             On 6 December 2015 at 16:25, Carlos P.A.
>> >     >             <carlos.p.a.87 at gmail.com
>> >     <mailto:carlos.p.a.87 at gmail.com> <mailto:carlos.p.a.87 at gmail.com
>> >     <mailto:carlos.p.a.87 at gmail.com>>>
>> >     >             wrote:
>> >     >
>> >     >                 Looks like RequestFileSystem might only be
>> supported in
>> >     >                 ChromeOS, is that the platform you've been using
>> Nicholas?
>> >     >
>> >     >
>> https://groups.google.com/a/chromium.org/forum/m/#!msg/apps-dev/LEne7qedZrc/7ZEY0uwfDgAJ
>> >     >
>> >     >                 On 6 December 2015 at 22:09, Naomi Ceder
>> >     >                 <naomi.ceder at gmail.com
>> >     <mailto:naomi.ceder at gmail.com> <mailto:naomi.ceder at gmail.com
>> >     <mailto:naomi.ceder at gmail.com>>>
>> >     >                 wrote:
>> >     >
>> >     >                     Sadly I can't get the extension to work on
>> either
>> >     >                     OSX or Linux - instead, the extension reports
>> >     >
>> >     >                      There were warnings when trying to install
>> this
>> >     >                     extension:
>> >     >
>> >     >                       * 'fileSystem.requestFileSystem' is not
>> allowed
>> >     >                         for specified platform.
>> >     >
>> >     >
>> >     >                     So the result for me is that the new, open,
>> and save
>> >     >                     functions don't do anything at all, and the
>> repl
>> >     >                     says it can't find the microbit.
>> >     >
>> >     >                     I'm not finding any explanations of line, but
>> I've
>> >     >                     attached a screen shot of the warning...
>> >     >
>> >     >                     I'm also not seeing any setting for Chrome
>> that
>> >     >                     would seem to help.
>> >     >
>> >     >                     Cheers,
>> >     >                     Naomi
>> >     >
>> >     >
>> >     >
>> >     >                     On 6 December 2015 at 15:15, Carlos P.A.
>> >     >                     <carlos.p.a.87 at gmail.com <mailto:
>> carlos.p.a.87 at gmail.com>
>> >     >                     <mailto:carlos.p.a.87 at gmail.com <mailto:
>> carlos.p.a.87 at gmail.com>>> wrote:
>> >     >
>> >     >                         Excellent work Nicholas!
>> >     >
>> >     >                         Will the pluggin also automatically work
>> when
>> >     >                         the interface is accessed from the
>> >     >                         https://www.microbit.co.uk/create-code
>> python
>> >     >                         link? (once it is implemented in the
>> webiste).
>> >     >
>> >     >                         As a small suggestion, probably with a low
>> >     >                         priority, is that having some visual
>> feedback on
>> >     >                         the page that the program is being
>> flashed would
>> >     >                         be ideal, even better if there was a tiny
>> >     >                         progress bar on the button.
>> >     >
>> >     >                         Regards,
>> >     >                         Carlos
>> >     >
>> >     >                         On 6 December 2015 at 20:34, Nicholas
>> >     >                         H.Tollervey <ntoll at ntoll.org <mailto:
>> ntoll at ntoll.org>
>> >     >                         <mailto:ntoll at ntoll.org
>> >     <mailto:ntoll at ntoll.org>>> wrote:
>> >     >
>> >     >                             Basically, this:
>> >     >
>> >     >
>> >      https://www.youtube.com/watch?v=S8MGFVuZrrs
>> >     >
>> >     >                             ...is a first draft and the source
>> >     code is here:
>> >     >
>> >     >
>> >      https://github.com/ntoll/python-native-editor
>> >     >
>> >     >                             There's no documentation and I'll be
>> >     working
>> >     >                             on it over the coming days
>> >     >                             with a view to showing it on Wednesday
>> >     to a
>> >     >                             bunch of teachers.
>> >     >
>> >     >                             FYI - working out how to flash the
>> device
>> >     >                             took several tortuous days.
>> >     >                             Chrome has a USB API that was
>> >     documented to
>> >     >                             appear to be exactly what I
>> >     >                             needed (pushing file based data to the
>> >     >                             device). I spent far too much
>> >     >                             time learning about USB and getting
>> >     >                             permission to write to the device to
>> >     >                             work.
>> >     >
>> >     >                             In the end I gave up when I realised
>> there
>> >     >                             was a really easy hack that
>> >     >                             was right in front of my nose... just
>> copy
>> >     >                             the damn .hex file to the
>> >     >                             device via the built-in file-system
>> API.
>> >     >
>> >     >                             It worked first time..! :-)
>> >     >
>> >     >                             That's several hours of my time I'll
>> never
>> >     >                             get back.
>> >     >
>> >     >                             Early days. Collaboration welcome!
>> >     >
>> >     >                             Best wishes,
>> >     >
>> >     >                             Nicholas.
>> >     >
>> >     >
>> >     >
>> >      _______________________________________________
>> >     >                             Microbit mailing list
>> >     >                             Microbit at python.org
>> >     <mailto:Microbit at python.org> <mailto:Microbit at python.org
>> >     <mailto:Microbit at python.org>>
>> >     >
>> https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >     >
>> >     >
>> >     >
>>  _______________________________________________
>> >     >                         Microbit mailing list
>> >     >                         Microbit at python.org
>> >     <mailto:Microbit at python.org> <mailto:Microbit at python.org
>> >     <mailto:Microbit at python.org>>
>> >     >
>> https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >     >
>> >     >
>> >     >
>> >     >                     --
>> >     >                     Naomi Ceder
>> >     >
>> https://plus.google.com/u/0/111396744045017339164/about
>> >     >
>> >     >
>>  _______________________________________________
>> >     >                     Microbit mailing list
>> >     >                     Microbit at python.org
>> >     <mailto:Microbit at python.org> <mailto:Microbit at python.org
>> >     <mailto:Microbit at python.org>>
>> >     >
>> https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >     >
>> >     >
>> >     >                 _______________________________________________
>> >     >                 Microbit mailing list
>> >     >                 Microbit at python.org <mailto:Microbit at python.org>
>> >     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>> >     >                 https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >     >
>> >     >
>> >     >
>> >     >             --
>> >     >             Naomi Ceder
>> >     >
>> https://plus.google.com/u/0/111396744045017339164/about
>> >     >
>> >     >
>> >     >
>> >     >
>> >     >         --
>> >     >         Naomi Ceder
>> >     >         https://plus.google.com/u/0/111396744045017339164/about
>> >     >
>> >     >         _______________________________________________
>> >     >         Microbit mailing list
>> >     >         Microbit at python.org <mailto:Microbit at python.org>
>> >     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>> >     >         https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >     >
>> >     >
>> >     >     _______________________________________________
>> >     >     Microbit mailing list
>> >     >     Microbit at python.org <mailto:Microbit at python.org>
>> >     <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>> >     >     https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >     >
>> >     >
>> >     >
>> >     > --
>> >     > Naomi Ceder
>> >     > https://plus.google.com/u/0/111396744045017339164/about
>> >     >
>> >     >
>> >     > _______________________________________________
>> >     > Microbit mailing list
>> >     > Microbit at python.org <mailto:Microbit at python.org>
>> >     > https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >
>> >
>> >
>> >     _______________________________________________
>> >     Microbit mailing list
>> >     Microbit at python.org <mailto:Microbit at python.org>
>> >     https://mail.python.org/mailman/listinfo/microbit
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Microbit mailing list
>> > Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/d87c9627/attachment-0001.html>

From ntoll at ntoll.org  Mon Dec  7 18:37:15 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Mon, 7 Dec 2015 23:37:15 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
Message-ID: <5666182B.9050809@ntoll.org>

The result of this evening's hacking... :-)

https://www.youtube.com/watch?v=I17t-AapgQo

I think I prefer this to the Chrome based solution for the following
reasons:

* QT5 is mature.
* This code can be packaged into a static single .exe file user's can
just drop onto their filesystem.
* It's actually written in Python..!
* It's cross platform Windows, OS X and Linux without the need for
external dependencies (like Chrome / Chromium).
* Finally, it should work quite well on a RPi.

Based upon Dan Pope's Puppy editor but gutted to create an MVP.

Look and feel based upon Steve Hawkes designs. I'm completely knackered
now so will tidy up the code in the morning, document it and push to
GitHub so you can all dive in and help.

As always, comments, constructive critique and ideas are most welcome..!

Best wishes,

Nicholas.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/43223308/attachment.sig>

From carlos.p.a.87 at gmail.com  Mon Dec  7 18:52:20 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Mon, 7 Dec 2015 23:52:20 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <5666182B.9050809@ntoll.org>
References: <5666182B.9050809@ntoll.org>
Message-ID: <CAC_p0yBmD0UDisQuF2Hji68-QEbN8nbLg8WXFtrge8v4Cbhnzw@mail.gmail.com>

+1 on preferring this compared to the chrome plugin, for all the reasons
listed. I also like the idea of having a simple editor that the users could
hack as well.

The only inconvenience will be having to maintain two versions of the
"simple python editor", one for the website (assuming that is still going
to be launched), and then this one. If this was a huge deal, I guess the qt
webkit web view could be used, but I'm not so sure if the ACE editor will
work on that, and it will also significantly increase the size of the
packed exe (although not as much as something like electron or cefpython).



On 7 December 2015 at 23:37, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> The result of this evening's hacking... :-)
>
> https://www.youtube.com/watch?v=I17t-AapgQo
>
> I think I prefer this to the Chrome based solution for the following
> reasons:
>
> * QT5 is mature.
> * This code can be packaged into a static single .exe file user's can
> just drop onto their filesystem.
> * It's actually written in Python..!
> * It's cross platform Windows, OS X and Linux without the need for
> external dependencies (like Chrome / Chromium).
> * Finally, it should work quite well on a RPi.
>
> Based upon Dan Pope's Puppy editor but gutted to create an MVP.
>
> Look and feel based upon Steve Hawkes designs. I'm completely knackered
> now so will tidy up the code in the morning, document it and push to
> GitHub so you can all dive in and help.
>
> As always, comments, constructive critique and ideas are most welcome..!
>
> Best wishes,
>
> Nicholas.
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151207/10c796da/attachment.html>

From ntoll at ntoll.org  Tue Dec  8 03:19:18 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 8 Dec 2015 08:19:18 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <5666182B.9050809@ntoll.org>
References: <5666182B.9050809@ntoll.org>
Message-ID: <56669286.8020800@ntoll.org>

Source code, along with open issues can be found here:

https://github.com/ntoll/mu

Happy hacking!

:-)

N.


On 07/12/15 23:37, Nicholas H.Tollervey wrote:
> The result of this evening's hacking... :-)
> 
> https://www.youtube.com/watch?v=I17t-AapgQo
> 
> I think I prefer this to the Chrome based solution for the following
> reasons:
> 
> * QT5 is mature.
> * This code can be packaged into a static single .exe file user's can
> just drop onto their filesystem.
> * It's actually written in Python..!
> * It's cross platform Windows, OS X and Linux without the need for
> external dependencies (like Chrome / Chromium).
> * Finally, it should work quite well on a RPi.
> 
> Based upon Dan Pope's Puppy editor but gutted to create an MVP.
> 
> Look and feel based upon Steve Hawkes designs. I'm completely knackered
> now so will tidy up the code in the morning, document it and push to
> GitHub so you can all dive in and help.
> 
> As always, comments, constructive critique and ideas are most welcome..!
> 
> Best wishes,
> 
> Nicholas.
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/b6aec300/attachment.sig>

From peter.inglesby at gmail.com  Tue Dec  8 15:20:59 2015
From: peter.inglesby at gmail.com (Peter Inglesby)
Date: Tue, 8 Dec 2015 20:20:59 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <56669286.8020800@ntoll.org>
References: <5666182B.9050809@ntoll.org>
	<56669286.8020800@ntoll.org>
Message-ID: <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>

This looks great, but unfortunately I don't have a postgraduate diploma in
installing PyQT.  In particular, having managed to install PyQT, I can now
import PyQt5 and things like PyQt5.QtCore, but I can't import PyQt5.Qsci.

Nicholas: is Qsci a separate dependency of the project?  (According to this
<http://eli.thegreenplace.net/2011/04/01/sample-using-qscintilla-with-pyqt>,
it "comes packaged with PyQt", but that might be out of date.)

Anybody else: have you managed to get this to work on OSX?

On 8 December 2015 at 08:19, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Source code, along with open issues can be found here:
>
> https://github.com/ntoll/mu
>
> Happy hacking!
>
> :-)
>
> N.
>
>
> On 07/12/15 23:37, Nicholas H.Tollervey wrote:
> > The result of this evening's hacking... :-)
> >
> > https://www.youtube.com/watch?v=I17t-AapgQo
> >
> > I think I prefer this to the Chrome based solution for the following
> > reasons:
> >
> > * QT5 is mature.
> > * This code can be packaged into a static single .exe file user's can
> > just drop onto their filesystem.
> > * It's actually written in Python..!
> > * It's cross platform Windows, OS X and Linux without the need for
> > external dependencies (like Chrome / Chromium).
> > * Finally, it should work quite well on a RPi.
> >
> > Based upon Dan Pope's Puppy editor but gutted to create an MVP.
> >
> > Look and feel based upon Steve Hawkes designs. I'm completely knackered
> > now so will tidy up the code in the morning, document it and push to
> > GitHub so you can all dive in and help.
> >
> > As always, comments, constructive critique and ideas are most welcome..!
> >
> > Best wishes,
> >
> > Nicholas.
> >
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/8aec09fa/attachment.html>

From ntoll at ntoll.org  Tue Dec  8 16:11:49 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 8 Dec 2015 21:11:49 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
Message-ID: <56674795.4080108@ntoll.org>

Hi Peter,

Just got home from London. Did you follow the instructions here..?

http://pyqt.sourceforge.net/Docs/PyQt5/installation.html

It appears to say that the installer needs some sort of flag to be
passed in order for Qsci to be installed.

Hope this helps,

N.

On 08/12/15 20:20, Peter Inglesby wrote:
> This looks great, but unfortunately I don't have a postgraduate diploma
> in installing PyQT.  In particular, having managed to install PyQT, I
> can now import PyQt5 and things like PyQt5.QtCore, but I can't import
> PyQt5.Qsci.
> 
> Nicholas: is Qsci a separate dependency of the project?  (According to
> this
> <http://eli.thegreenplace.net/2011/04/01/sample-using-qscintilla-with-pyqt>,
> it "comes packaged with PyQt", but that might be out of date.)
> 
> Anybody else: have you managed to get this to work on OSX?
> 
> On 8 December 2015 at 08:19, Nicholas H.Tollervey <ntoll at ntoll.org
> <mailto:ntoll at ntoll.org>> wrote:
> 
>     Source code, along with open issues can be found here:
> 
>     https://github.com/ntoll/mu
> 
>     Happy hacking!
> 
>     :-)
> 
>     N.
> 
> 
>     On 07/12/15 23:37, Nicholas H.Tollervey wrote:
>     > The result of this evening's hacking... :-)
>     >
>     > https://www.youtube.com/watch?v=I17t-AapgQo
>     >
>     > I think I prefer this to the Chrome based solution for the following
>     > reasons:
>     >
>     > * QT5 is mature.
>     > * This code can be packaged into a static single .exe file user's can
>     > just drop onto their filesystem.
>     > * It's actually written in Python..!
>     > * It's cross platform Windows, OS X and Linux without the need for
>     > external dependencies (like Chrome / Chromium).
>     > * Finally, it should work quite well on a RPi.
>     >
>     > Based upon Dan Pope's Puppy editor but gutted to create an MVP.
>     >
>     > Look and feel based upon Steve Hawkes designs. I'm completely
>     knackered
>     > now so will tidy up the code in the morning, document it and push to
>     > GitHub so you can all dive in and help.
>     >
>     > As always, comments, constructive critique and ideas are most
>     welcome..!
>     >
>     > Best wishes,
>     >
>     > Nicholas.
>     >
>     >
>     >
>     > _______________________________________________
>     > Microbit mailing list
>     > Microbit at python.org <mailto:Microbit at python.org>
>     > https://mail.python.org/mailman/listinfo/microbit
>     >
> 
> 
> 
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/05ff2c79/attachment.sig>

From carlos.p.a.87 at gmail.com  Tue Dec  8 16:16:56 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Tue, 8 Dec 2015 21:16:56 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <56674795.4080108@ntoll.org>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
Message-ID: <CAC_p0yBKXuf6MC=V6vJMWnXRSL5XMO+heG210bXqruXTu9MLJA@mail.gmail.com>

Hi Nicholas,

I'm in the process to get a virtual env set up for pyinstaller testing,
however looks like PyQt5 does not play nice with virtual envs. Any chance
it will work with PyQt4 if manage to get that in an env?


On 8 December 2015 at 21:11, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Hi Peter,
>
> Just got home from London. Did you follow the instructions here..?
>
> http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
>
> It appears to say that the installer needs some sort of flag to be
> passed in order for Qsci to be installed.
>
> Hope this helps,
>
> N.
>
> On 08/12/15 20:20, Peter Inglesby wrote:
> > This looks great, but unfortunately I don't have a postgraduate diploma
> > in installing PyQT.  In particular, having managed to install PyQT, I
> > can now import PyQt5 and things like PyQt5.QtCore, but I can't import
> > PyQt5.Qsci.
> >
> > Nicholas: is Qsci a separate dependency of the project?  (According to
> > this
> > <
> http://eli.thegreenplace.net/2011/04/01/sample-using-qscintilla-with-pyqt
> >,
> > it "comes packaged with PyQt", but that might be out of date.)
> >
> > Anybody else: have you managed to get this to work on OSX?
> >
> > On 8 December 2015 at 08:19, Nicholas H.Tollervey <ntoll at ntoll.org
> > <mailto:ntoll at ntoll.org>> wrote:
> >
> >     Source code, along with open issues can be found here:
> >
> >     https://github.com/ntoll/mu
> >
> >     Happy hacking!
> >
> >     :-)
> >
> >     N.
> >
> >
> >     On 07/12/15 23:37, Nicholas H.Tollervey wrote:
> >     > The result of this evening's hacking... :-)
> >     >
> >     > https://www.youtube.com/watch?v=I17t-AapgQo
> >     >
> >     > I think I prefer this to the Chrome based solution for the
> following
> >     > reasons:
> >     >
> >     > * QT5 is mature.
> >     > * This code can be packaged into a static single .exe file user's
> can
> >     > just drop onto their filesystem.
> >     > * It's actually written in Python..!
> >     > * It's cross platform Windows, OS X and Linux without the need for
> >     > external dependencies (like Chrome / Chromium).
> >     > * Finally, it should work quite well on a RPi.
> >     >
> >     > Based upon Dan Pope's Puppy editor but gutted to create an MVP.
> >     >
> >     > Look and feel based upon Steve Hawkes designs. I'm completely
> >     knackered
> >     > now so will tidy up the code in the morning, document it and push
> to
> >     > GitHub so you can all dive in and help.
> >     >
> >     > As always, comments, constructive critique and ideas are most
> >     welcome..!
> >     >
> >     > Best wishes,
> >     >
> >     > Nicholas.
> >     >
> >     >
> >     >
> >     > _______________________________________________
> >     > Microbit mailing list
> >     > Microbit at python.org <mailto:Microbit at python.org>
> >     > https://mail.python.org/mailman/listinfo/microbit
> >     >
> >
> >
> >
> >     _______________________________________________
> >     Microbit mailing list
> >     Microbit at python.org <mailto:Microbit at python.org>
> >     https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/de9accfb/attachment-0001.html>

From carlos.p.a.87 at gmail.com  Tue Dec  8 16:31:11 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Tue, 8 Dec 2015 21:31:11 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <CAC_p0yBKXuf6MC=V6vJMWnXRSL5XMO+heG210bXqruXTu9MLJA@mail.gmail.com>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
 <CAC_p0yBKXuf6MC=V6vJMWnXRSL5XMO+heG210bXqruXTu9MLJA@mail.gmail.com>
Message-ID: <CAC_p0yCueigd4ims1wsuPeFmuAakkEQBzMZnszUF_hxTbFsGmw@mail.gmail.com>

Looks like the answer is no, they are not compatible and the app would need
to be ported.

On 8 December 2015 at 21:16, Carlos P.A. <carlos.p.a.87 at gmail.com> wrote:

> Hi Nicholas,
>
> I'm in the process to get a virtual env set up for pyinstaller testing,
> however looks like PyQt5 does not play nice with virtual envs. Any chance
> it will work with PyQt4 if manage to get that in an env?
>
>
> On 8 December 2015 at 21:11, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
>
>> Hi Peter,
>>
>> Just got home from London. Did you follow the instructions here..?
>>
>> http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
>>
>> It appears to say that the installer needs some sort of flag to be
>> passed in order for Qsci to be installed.
>>
>> Hope this helps,
>>
>> N.
>>
>> On 08/12/15 20:20, Peter Inglesby wrote:
>> > This looks great, but unfortunately I don't have a postgraduate diploma
>> > in installing PyQT.  In particular, having managed to install PyQT, I
>> > can now import PyQt5 and things like PyQt5.QtCore, but I can't import
>> > PyQt5.Qsci.
>> >
>> > Nicholas: is Qsci a separate dependency of the project?  (According to
>> > this
>> > <
>> http://eli.thegreenplace.net/2011/04/01/sample-using-qscintilla-with-pyqt
>> >,
>> > it "comes packaged with PyQt", but that might be out of date.)
>> >
>> > Anybody else: have you managed to get this to work on OSX?
>> >
>> > On 8 December 2015 at 08:19, Nicholas H.Tollervey <ntoll at ntoll.org
>> > <mailto:ntoll at ntoll.org>> wrote:
>> >
>> >     Source code, along with open issues can be found here:
>> >
>> >     https://github.com/ntoll/mu
>> >
>> >     Happy hacking!
>> >
>> >     :-)
>> >
>> >     N.
>> >
>> >
>> >     On 07/12/15 23:37, Nicholas H.Tollervey wrote:
>> >     > The result of this evening's hacking... :-)
>> >     >
>> >     > https://www.youtube.com/watch?v=I17t-AapgQo
>> >     >
>> >     > I think I prefer this to the Chrome based solution for the
>> following
>> >     > reasons:
>> >     >
>> >     > * QT5 is mature.
>> >     > * This code can be packaged into a static single .exe file user's
>> can
>> >     > just drop onto their filesystem.
>> >     > * It's actually written in Python..!
>> >     > * It's cross platform Windows, OS X and Linux without the need for
>> >     > external dependencies (like Chrome / Chromium).
>> >     > * Finally, it should work quite well on a RPi.
>> >     >
>> >     > Based upon Dan Pope's Puppy editor but gutted to create an MVP.
>> >     >
>> >     > Look and feel based upon Steve Hawkes designs. I'm completely
>> >     knackered
>> >     > now so will tidy up the code in the morning, document it and push
>> to
>> >     > GitHub so you can all dive in and help.
>> >     >
>> >     > As always, comments, constructive critique and ideas are most
>> >     welcome..!
>> >     >
>> >     > Best wishes,
>> >     >
>> >     > Nicholas.
>> >     >
>> >     >
>> >     >
>> >     > _______________________________________________
>> >     > Microbit mailing list
>> >     > Microbit at python.org <mailto:Microbit at python.org>
>> >     > https://mail.python.org/mailman/listinfo/microbit
>> >     >
>> >
>> >
>> >
>> >     _______________________________________________
>> >     Microbit mailing list
>> >     Microbit at python.org <mailto:Microbit at python.org>
>> >     https://mail.python.org/mailman/listinfo/microbit
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Microbit mailing list
>> > Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/15801679/attachment.html>

From peter.inglesby at gmail.com  Tue Dec  8 16:34:16 2015
From: peter.inglesby at gmail.com (Peter Inglesby)
Date: Tue, 8 Dec 2015 21:34:16 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <56674795.4080108@ntoll.org>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
Message-ID: <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>

>
> Just got home from London. Did you follow the instructions here..?
>
> http://pyqt.sourceforge.net/Docs/PyQt5/installation.html


No I didn't, because that page is not linked to (as far as I could see)
from anywhere on https://riverbankcomputing.com/software/pyqt/, and nor is
it in the first page of Google results for "install pyqt osx" (although I
see it *is* the top hit for "install pyqt"...).

It does look promising though -- thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/f95d36e9/attachment.html>

From ntoll at ntoll.org  Tue Dec  8 16:42:40 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 8 Dec 2015 21:42:40 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <CAC_p0yCueigd4ims1wsuPeFmuAakkEQBzMZnszUF_hxTbFsGmw@mail.gmail.com>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
 <CAC_p0yBKXuf6MC=V6vJMWnXRSL5XMO+heG210bXqruXTu9MLJA@mail.gmail.com>
 <CAC_p0yCueigd4ims1wsuPeFmuAakkEQBzMZnszUF_hxTbFsGmw@mail.gmail.com>
Message-ID: <56674ED0.8020201@ntoll.org>

Would rather stick with Qt5 given it's the latest iteration unless
there's a game changing blocker.

N.

On 08/12/15 21:31, Carlos P.A. wrote:
> Looks like the answer is no, they are not compatible and the app would
> need to be ported.
> 
> On 8 December 2015 at 21:16, Carlos P.A. <carlos.p.a.87 at gmail.com
> <mailto:carlos.p.a.87 at gmail.com>> wrote:
> 
>     Hi Nicholas,
> 
>     I'm in the process to get a virtual env set up for pyinstaller
>     testing, however looks like PyQt5 does not play nice with virtual
>     envs. Any chance it will work with PyQt4 if manage to get that in an
>     env?
> 
> 
>     On 8 December 2015 at 21:11, Nicholas H.Tollervey <ntoll at ntoll.org
>     <mailto:ntoll at ntoll.org>> wrote:
> 
>         Hi Peter,
> 
>         Just got home from London. Did you follow the instructions here..?
> 
>         http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
> 
>         It appears to say that the installer needs some sort of flag to be
>         passed in order for Qsci to be installed.
> 
>         Hope this helps,
> 
>         N.
> 
>         On 08/12/15 20:20, Peter Inglesby wrote:
>         > This looks great, but unfortunately I don't have a postgraduate diploma
>         > in installing PyQT.  In particular, having managed to install PyQT, I
>         > can now import PyQt5 and things like PyQt5.QtCore, but I can't import
>         > PyQt5.Qsci.
>         >
>         > Nicholas: is Qsci a separate dependency of the project?  (According to
>         > this
>         >
>         <http://eli.thegreenplace.net/2011/04/01/sample-using-qscintilla-with-pyqt>,
>         > it "comes packaged with PyQt", but that might be out of date.)
>         >
>         > Anybody else: have you managed to get this to work on OSX?
>         >
>         > On 8 December 2015 at 08:19, Nicholas H.Tollervey <ntoll at ntoll.org <mailto:ntoll at ntoll.org>
>         > <mailto:ntoll at ntoll.org <mailto:ntoll at ntoll.org>>> wrote:
>         >
>         >     Source code, along with open issues can be found here:
>         >
>         >     https://github.com/ntoll/mu
>         >
>         >     Happy hacking!
>         >
>         >     :-)
>         >
>         >     N.
>         >
>         >
>         >     On 07/12/15 23:37, Nicholas H.Tollervey wrote:
>         >     > The result of this evening's hacking... :-)
>         >     >
>         >     > https://www.youtube.com/watch?v=I17t-AapgQo
>         >     >
>         >     > I think I prefer this to the Chrome based solution for
>         the following
>         >     > reasons:
>         >     >
>         >     > * QT5 is mature.
>         >     > * This code can be packaged into a static single .exe
>         file user's can
>         >     > just drop onto their filesystem.
>         >     > * It's actually written in Python..!
>         >     > * It's cross platform Windows, OS X and Linux without
>         the need for
>         >     > external dependencies (like Chrome / Chromium).
>         >     > * Finally, it should work quite well on a RPi.
>         >     >
>         >     > Based upon Dan Pope's Puppy editor but gutted to create
>         an MVP.
>         >     >
>         >     > Look and feel based upon Steve Hawkes designs. I'm
>         completely
>         >     knackered
>         >     > now so will tidy up the code in the morning, document it
>         and push to
>         >     > GitHub so you can all dive in and help.
>         >     >
>         >     > As always, comments, constructive critique and ideas are
>         most
>         >     welcome..!
>         >     >
>         >     > Best wishes,
>         >     >
>         >     > Nicholas.
>         >     >
>         >     >
>         >     >
>         >     > _______________________________________________
>         >     > Microbit mailing list
>         >     > Microbit at python.org <mailto:Microbit at python.org>
>         <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>         >     > https://mail.python.org/mailman/listinfo/microbit
>         >     >
>         >
>         >
>         >
>         >     _______________________________________________
>         >     Microbit mailing list
>         >     Microbit at python.org <mailto:Microbit at python.org>
>         <mailto:Microbit at python.org <mailto:Microbit at python.org>>
>         >     https://mail.python.org/mailman/listinfo/microbit
>         >
>         >
>         >
>         >
>         > _______________________________________________
>         > Microbit mailing list
>         > Microbit at python.org <mailto:Microbit at python.org>
>         > https://mail.python.org/mailman/listinfo/microbit
>         >
> 
> 
> 
>         _______________________________________________
>         Microbit mailing list
>         Microbit at python.org <mailto:Microbit at python.org>
>         https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/a609c441/attachment-0001.sig>

From ntoll at ntoll.org  Tue Dec  8 16:42:58 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 8 Dec 2015 21:42:58 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
 <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>
Message-ID: <56674EE2.6000605@ntoll.org>

On 08/12/15 21:34, Peter Inglesby wrote:
>     Just got home from London. Did you follow the instructions here..?
> 
>     http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
> 
> 
> No I didn't, because that page is not linked to (as far as I could see)
> from anywhere on https://riverbankcomputing.com/software/pyqt/, and nor
> is it in the first page of Google results for "install pyqt osx"
> (although I see it /is/ the top hit for "install pyqt"...).
> 
> It does look promising though -- thanks!
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 

Let me know how you get on..!

N.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151208/75e42c1f/attachment.sig>

From peter.inglesby at gmail.com  Wed Dec  9 09:21:55 2015
From: peter.inglesby at gmail.com (Peter Inglesby)
Date: Wed, 9 Dec 2015 14:21:55 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
 <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>
Message-ID: <CAENJrP=PcoYEqOZN91veACM=uGC6de83WJ7zx7629YWa4tBvAg@mail.gmail.com>

I've finally got my system into a state where it can run mu.  I had to go
through a bit of a song and dance to get QScintilla installed, but I've
written up the steps at
https://github.com/Homebrew/homebrew/issues/37591#issuecomment-163251145,
and I hope to produce a homebrew package so that it becomes a matter of
running "brew install qscintilla".

Hope this is helpful to somebody!

On 8 December 2015 at 21:34, Peter Inglesby <peter.inglesby at gmail.com>
wrote:

> Just got home from London. Did you follow the instructions here..?
>>
>> http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
>
>
> No I didn't, because that page is not linked to (as far as I could see)
> from anywhere on https://riverbankcomputing.com/software/pyqt/, and nor
> is it in the first page of Google results for "install pyqt osx" (although
> I see it *is* the top hit for "install pyqt"...).
>
> It does look promising though -- thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151209/5f8bd026/attachment.html>

From ntoll at ntoll.org  Wed Dec  9 09:25:42 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Wed, 9 Dec 2015 14:25:42 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <CAENJrP=PcoYEqOZN91veACM=uGC6de83WJ7zx7629YWa4tBvAg@mail.gmail.com>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
 <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>
 <CAENJrP=PcoYEqOZN91veACM=uGC6de83WJ7zx7629YWa4tBvAg@mail.gmail.com>
Message-ID: <566839E6.8000202@ntoll.org>

Great work Peter computering the computerer. ;-)

N.

On 09/12/15 14:21, Peter Inglesby wrote:
> I've finally got my system into a state where it can run mu.  I had to
> go through a bit of a song and dance to get QScintilla installed, but
> I've written up the steps
> at https://github.com/Homebrew/homebrew/issues/37591#issuecomment-163251145,
> and I hope to produce a homebrew package so that it becomes a matter of
> running "brew install qscintilla".
> 
> Hope this is helpful to somebody!
> 
> On 8 December 2015 at 21:34, Peter Inglesby <peter.inglesby at gmail.com
> <mailto:peter.inglesby at gmail.com>> wrote:
> 
>         Just got home from London. Did you follow the instructions here..?
> 
>         http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
> 
> 
>     No I didn't, because that page is not linked to (as far as I could
>     see) from anywhere on https://riverbankcomputing.com/software/pyqt/,
>     and nor is it in the first page of Google results for "install pyqt
>     osx" (although I see it /is/ the top hit for "install pyqt"...).
> 
>     It does look promising though -- thanks!
> 
> 
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151209/69e35380/attachment.sig>

From carlos.p.a.87 at gmail.com  Wed Dec  9 15:17:35 2015
From: carlos.p.a.87 at gmail.com (Carlos P.A.)
Date: Wed, 9 Dec 2015 20:17:35 +0000
Subject: [Microbit-Python] Another native solution... this time with QT
In-Reply-To: <566839E6.8000202@ntoll.org>
References: <5666182B.9050809@ntoll.org> <56669286.8020800@ntoll.org>
 <CAENJrPkkiGoDUz0jJGNOKk-+M5WTzZsfA9ERWG7CUe3h76Ob9w@mail.gmail.com>
 <56674795.4080108@ntoll.org>
 <CAENJrPnO1iXzANYK=GN25BkYzbcwP-oWaaxyNjQGVs+FC_T5pQ@mail.gmail.com>
 <CAENJrP=PcoYEqOZN91veACM=uGC6de83WJ7zx7629YWa4tBvAg@mail.gmail.com>
 <566839E6.8000202@ntoll.org>
Message-ID: <CAC_p0yADmCBcqWRu9b9CyRi-71QdSO7LtTV1vZYPrCuNit7yzA@mail.gmail.com>

I've got a very rough windows executable with the current state of Mu, if
any body else could help me test it on different Windows versions that'd be
quite helpful. Try to download the one with the latest time-stamp from the
link below, but if I do break something, the latest one at the moment of
writing that should be working is mu-2015-12-09_20_12_01.exe
<https://s3-us-west-2.amazonaws.com/ardublockly-builds/microbit/windows/mu-2015-12-09_20_12_01.exe>
.

http://ardublockly-builds.s3-website-us-west-2.amazonaws.com/index.html?prefix=microbit/windows/

On 9 December 2015 at 14:25, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Great work Peter computering the computerer. ;-)
>
> N.
>
> On 09/12/15 14:21, Peter Inglesby wrote:
> > I've finally got my system into a state where it can run mu.  I had to
> > go through a bit of a song and dance to get QScintilla installed, but
> > I've written up the steps
> > at
> https://github.com/Homebrew/homebrew/issues/37591#issuecomment-163251145,
> > and I hope to produce a homebrew package so that it becomes a matter of
> > running "brew install qscintilla".
> >
> > Hope this is helpful to somebody!
> >
> > On 8 December 2015 at 21:34, Peter Inglesby <peter.inglesby at gmail.com
> > <mailto:peter.inglesby at gmail.com>> wrote:
> >
> >         Just got home from London. Did you follow the instructions
> here..?
> >
> >         http://pyqt.sourceforge.net/Docs/PyQt5/installation.html
> >
> >
> >     No I didn't, because that page is not linked to (as far as I could
> >     see) from anywhere on https://riverbankcomputing.com/software/pyqt/,
> >     and nor is it in the first page of Google results for "install pyqt
> >     osx" (although I see it /is/ the top hit for "install pyqt"...).
> >
> >     It does look promising though -- thanks!
> >
> >
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151209/258544bd/attachment.html>

From tanya at tickel.net  Fri Dec 11 13:22:01 2015
From: tanya at tickel.net (Tanya Schlusser)
Date: Fri, 11 Dec 2015 12:22:01 -0600
Subject: [Microbit-Python] Jupyter kernel for the micropython repl
Message-ID: <CA+bo0=RGHR7NKKQUttoyfEggD=w3gQxE+dv7SC9qfJ6q-YJ6+w@mail.gmail.com>

Naomi's second talk finally pulled me into your listserv :-)
The micro::bit is pretty great and it's awesome that Python is involved.


I'm interested in helping but am new to this ecosystem, and so want to test
my current awareness after reading the listserv archives:

1. the goal for a Jupyter kernel would just be to modify / wrap the
microrepl client (https://github.com/ntoll/microrepl)

2. there is not yet a simulator (even a command line one?) for the microbit
library

3. the micro editor mu (https://github.com/ntoll/mu) should be used instead
of the python-native-editor (https://github.com/ntoll/python-native-editor)

4. The TouchDevelop PythonEditor (
https://github.com/bbcmicrobit/PythonEditor) is unrelated and I wouldn't
need to look at it

5. Nobody else is currently working on this (a Jupyter kernal with
microrepl) with whom I should collaborate


Thanks friends!

Best,
Tanya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151211/e6cb9c64/attachment.html>

From damien.p.george at gmail.com  Fri Dec 11 16:01:32 2015
From: damien.p.george at gmail.com (Damien George)
Date: Fri, 11 Dec 2015 21:01:32 +0000
Subject: [Microbit-Python] Jupyter kernel for the micropython repl
In-Reply-To: <CA+bo0=RGHR7NKKQUttoyfEggD=w3gQxE+dv7SC9qfJ6q-YJ6+w@mail.gmail.com>
References: <CA+bo0=RGHR7NKKQUttoyfEggD=w3gQxE+dv7SC9qfJ6q-YJ6+w@mail.gmail.com>
Message-ID: <CANw+MznvBjzWO3SsoyHqQVJdOjGTcQVeE8DGoyPSmhkiJ8FcxQ@mail.gmail.com>

Hi Tanya,

I think it's pretty much "yes" to all your 5 questions/points.  But
I'll clarify 2 of them:

1. I don't think you'll even need microrepl.  I think just connecting
to the correct serial port using pyserial would be enough.

3. I don't think you need to use any of the existing editors.  Doesn't
IPython provide this?

This (getting Jupyter running with MicroPython) is something that has
been on my todo list for a long time now, but at a low priority (and
hence I've not done anything on it).  So I'd be very interested to see
how you make progress.  Please shout if you need anything!

Cheers,
Damien.


On Fri, Dec 11, 2015 at 6:22 PM, Tanya Schlusser <tanya at tickel.net> wrote:
> Naomi's second talk finally pulled me into your listserv :-)
> The micro::bit is pretty great and it's awesome that Python is involved.
>
>
> I'm interested in helping but am new to this ecosystem, and so want to test
> my current awareness after reading the listserv archives:
>
> 1. the goal for a Jupyter kernel would just be to modify / wrap the
> microrepl client (https://github.com/ntoll/microrepl)
>
> 2. there is not yet a simulator (even a command line one?) for the microbit
> library
>
> 3. the micro editor mu (https://github.com/ntoll/mu) should be used instead
> of the python-native-editor (https://github.com/ntoll/python-native-editor)
>
> 4. The TouchDevelop PythonEditor
> (https://github.com/bbcmicrobit/PythonEditor) is unrelated and I wouldn't
> need to look at it
>
> 5. Nobody else is currently working on this (a Jupyter kernal with
> microrepl) with whom I should collaborate
>
>
> Thanks friends!
>
> Best,
> Tanya
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From damien.p.george at gmail.com  Fri Dec 11 16:40:57 2015
From: damien.p.george at gmail.com (Damien George)
Date: Fri, 11 Dec 2015 21:40:57 +0000
Subject: [Microbit-Python] Battery connector and battery holder
In-Reply-To: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>
References: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>
Message-ID: <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>

Hi Tom,

I hope this reply is not too late!  I looked at the options for the
battery pack and the one with 2x AA would be perfect:
https://www.kitronik.co.uk/2268-2x-aa-battery-box-with-switch-and-connector.html
.  That would give you about 3v for the microbit which is what it
needs.  It can run from between 1.8v and 3.6v, so you definitely don't
want more than 2x AA's.

Cheers,
Damien.


On Sun, Dec 6, 2015 at 1:09 AM, Tom Viner <tom at viner.tv> wrote:
> Hi all,
>
> I've found the edge connector breakout board and the motor driver board but
> I'm not sure exactly which to buy as a battery pack.
>
> Something that can run for a while would be good, but blowing up the board
> (as happened to poor Mahiri) should be avoided!
>
> If one of these does the job, I can order my boards and battery connector in
> one go from Kitronik.
>
> Incidentally Kitronik have a load of great micro:bit resources on their
> site.
>
> Cheers,
> Tom
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From tanya at tickel.net  Fri Dec 11 16:41:52 2015
From: tanya at tickel.net (Tanya Schlusser)
Date: Fri, 11 Dec 2015 15:41:52 -0600
Subject: [Microbit-Python] Jupyter kernel for the micropython repl
Message-ID: <CA+bo0=T62A79DF6Usc+6v3VM20u09m5=grNNeWT2ESMDrEstZw@mail.gmail.com>

This might exist already -- (well mostly)
https://github.com/TDAbboud/mpkernel

Here's where it was announced:
http://forum.micropython.org/viewtopic.php?t=979


Best,
Tanya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151211/4d019cd7/attachment.html>

From david at thinkingbinaries.com  Fri Dec 11 17:38:09 2015
From: david at thinkingbinaries.com (David Whale)
Date: Fri, 11 Dec 2015 22:38:09 +0000
Subject: [Microbit-Python] Battery connector and battery holder
In-Reply-To: <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>
References: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>
 <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>
Message-ID: <CABeH_SsAJ5iJ_Ly5Ok4FN=8XJex1TPOU2FQ+O6MqrtbAp15QZA@mail.gmail.com>

I recall that there is a regulator on board on one of the ARM chips. I'm
not sure what that regulator is specified to, but USB in particular powers
from 5V, so I doubt the upper limit is specified as 3.6V. I have a
recollection that powering from the 3V pad misses one diode drop so might
have different maximum voltage ratings to elsewhere in the circuit.

As the schematics are not in the public domain yet, unless we can get Jonny
from ARM to confirm minimum/maximum voltage ratings, the best we can do is
infer these from the data sheets from standard parts, and any experimental
evidence. I have a recollection that Michael Sparks has had it running
safely for ages from a higher voltage, which suggests that the on-chip
regulator is actually a wider voltage range than you suggest.

Wikipedia for example suggests that USB max voltage is 5.25V, so there must
be some on board regulation to bring this down to the maximum voltage of
the various cores on the board.

Signal5 V DC <https://en.wikipedia.org/wiki/Direct_current>Max. voltage

   - 5.00?0.25 V (pre-3.0)
   - 5.00+0.25
   ?0.55 V (USB 3.0)
   - 20.00 V (USB-PD)



https://en.wikipedia.org/wiki/USB

I'm wondering if we could get some specific advice from Jonny at ARM here,
to stop us guessing at this stuff? It's only two numbers (min voltage and
max voltage), but they would be really useful to know definitively.

David


___________________________________________________________
David Whale, B.Sc (Hons), MIET
*Software Engineer and IET Schools Liaison Officer, Essex*

email:  dwhale at theiet.org
twitter: @whaleygeek
blog:  blog.whaleygeek.co.uk

Co-author of global bestselling book "Adventures in Minecraft"
<http://amzn.to/ZGfxZG> - lets get kids coding!
Now in English, Spanish, Chinese and Russian.


On 11 December 2015 at 21:40, Damien George <damien.p.george at gmail.com>
wrote:

> Hi Tom,
>
> I hope this reply is not too late!  I looked at the options for the
> battery pack and the one with 2x AA would be perfect:
>
> https://www.kitronik.co.uk/2268-2x-aa-battery-box-with-switch-and-connector.html
> .  That would give you about 3v for the microbit which is what it
> needs.  It can run from between 1.8v and 3.6v, so you definitely don't
> want more than 2x AA's.
>
> Cheers,
> Damien.
>
>
> On Sun, Dec 6, 2015 at 1:09 AM, Tom Viner <tom at viner.tv> wrote:
> > Hi all,
> >
> > I've found the edge connector breakout board and the motor driver board
> but
> > I'm not sure exactly which to buy as a battery pack.
> >
> > Something that can run for a while would be good, but blowing up the
> board
> > (as happened to poor Mahiri) should be avoided!
> >
> > If one of these does the job, I can order my boards and battery
> connector in
> > one go from Kitronik.
> >
> > Incidentally Kitronik have a load of great micro:bit resources on their
> > site.
> >
> > Cheers,
> > Tom
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151211/33c323cf/attachment-0001.html>

From damien.p.george at gmail.com  Fri Dec 11 17:53:33 2015
From: damien.p.george at gmail.com (Damien George)
Date: Fri, 11 Dec 2015 22:53:33 +0000
Subject: [Microbit-Python] Battery connector and battery holder
In-Reply-To: <CABeH_SsAJ5iJ_Ly5Ok4FN=8XJex1TPOU2FQ+O6MqrtbAp15QZA@mail.gmail.com>
References: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>
 <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>
 <CABeH_SsAJ5iJ_Ly5Ok4FN=8XJex1TPOU2FQ+O6MqrtbAp15QZA@mail.gmail.com>
Message-ID: <CANw+MzniBpLS7taqMrF1FdRXYmwVbro26=UE3Ra5Kxt_LyEg8Q@mail.gmail.com>

The KL26Z has a special built-in USB voltage regulator that takes USB VBUS
in and produces 3.3v out.

But yes, it depends on how this is connected internally.  Jonny will need
to tell us what the min/max input is for the battery connector, but I'd say
that 3v, 2x AA batteries, is a very safe bet :)

On Fri, Dec 11, 2015 at 10:38 PM, David Whale <david at thinkingbinaries.com>
wrote:

> I recall that there is a regulator on board on one of the ARM chips. I'm
> not sure what that regulator is specified to, but USB in particular powers
> from 5V, so I doubt the upper limit is specified as 3.6V. I have a
> recollection that powering from the 3V pad misses one diode drop so might
> have different maximum voltage ratings to elsewhere in the circuit.
>
> As the schematics are not in the public domain yet, unless we can get
> Jonny from ARM to confirm minimum/maximum voltage ratings, the best we can
> do is infer these from the data sheets from standard parts, and any
> experimental evidence. I have a recollection that Michael Sparks has had it
> running safely for ages from a higher voltage, which suggests that the
> on-chip regulator is actually a wider voltage range than you suggest.
>
> Wikipedia for example suggests that USB max voltage is 5.25V, so there
> must be some on board regulation to bring this down to the maximum voltage
> of the various cores on the board.
>
> Signal5 V DC <https://en.wikipedia.org/wiki/Direct_current>Max. voltage
>
>    - 5.00?0.25 V (pre-3.0)
>    - 5.00+0.25
>    ?0.55 V (USB 3.0)
>    - 20.00 V (USB-PD)
>
>
>
> https://en.wikipedia.org/wiki/USB
>
> I'm wondering if we could get some specific advice from Jonny at ARM here,
> to stop us guessing at this stuff? It's only two numbers (min voltage and
> max voltage), but they would be really useful to know definitively.
>
> David
>
>
> ___________________________________________________________
> David Whale, B.Sc (Hons), MIET
> *Software Engineer and IET Schools Liaison Officer, Essex*
>
> email:  dwhale at theiet.org
> twitter: @whaleygeek
> blog:  blog.whaleygeek.co.uk
>
> Co-author of global bestselling book "Adventures in Minecraft"
> <http://amzn.to/ZGfxZG> - lets get kids coding!
> Now in English, Spanish, Chinese and Russian.
>
>
> On 11 December 2015 at 21:40, Damien George <damien.p.george at gmail.com>
> wrote:
>
>> Hi Tom,
>>
>> I hope this reply is not too late!  I looked at the options for the
>> battery pack and the one with 2x AA would be perfect:
>>
>> https://www.kitronik.co.uk/2268-2x-aa-battery-box-with-switch-and-connector.html
>> .  That would give you about 3v for the microbit which is what it
>> needs.  It can run from between 1.8v and 3.6v, so you definitely don't
>> want more than 2x AA's.
>>
>> Cheers,
>> Damien.
>>
>>
>> On Sun, Dec 6, 2015 at 1:09 AM, Tom Viner <tom at viner.tv> wrote:
>> > Hi all,
>> >
>> > I've found the edge connector breakout board and the motor driver board
>> but
>> > I'm not sure exactly which to buy as a battery pack.
>> >
>> > Something that can run for a while would be good, but blowing up the
>> board
>> > (as happened to poor Mahiri) should be avoided!
>> >
>> > If one of these does the job, I can order my boards and battery
>> connector in
>> > one go from Kitronik.
>> >
>> > Incidentally Kitronik have a load of great micro:bit resources on their
>> > site.
>> >
>> > Cheers,
>> > Tom
>> >
>> >
>> > _______________________________________________
>> > Microbit mailing list
>> > Microbit at python.org
>> > https://mail.python.org/mailman/listinfo/microbit
>> >
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151211/27ef7829/attachment.html>

From tom at viner.tv  Fri Dec 11 18:37:07 2015
From: tom at viner.tv (Tom Viner)
Date: Fri, 11 Dec 2015 23:37:07 +0000
Subject: [Microbit-Python] Battery connector and battery holder
In-Reply-To: <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>
References: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>
 <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>
Message-ID: <CANBSuyEEqZ+KLN7dCmb8wYnQK4+XXdLZ9zMaEoYYJXD9qeBJjQ@mail.gmail.com>

On 11 December 2015 at 21:40, Damien George <damien.p.george at gmail.com>
wrote:

> I hope this reply is not too late!  I looked at the options for the
> battery pack and the one with 2x AA would be perfect:
>
> https://www.kitronik.co.uk/2268-2x-aa-battery-box-with-switch-and-connector.html
>

I ordered one of those, but they've then clarified via the first Q&A on
that page that it's not actually going to fit the micro:bit. At least I'll
have something to hold a pair of AAs in place.

I'll let the person concerned speak for themselves, but I have had word
from certain roboteer that he's powering the micro:bit via the 3V and GND
pins, skipping the need for USB / battery connector all together! Any views
on that approach? We weren't sure if it was "correct" but does seem to work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151211/66335b10/attachment.html>

From david at thinkingbinaries.com  Fri Dec 11 19:13:57 2015
From: david at thinkingbinaries.com (David Whale)
Date: Sat, 12 Dec 2015 00:13:57 +0000
Subject: [Microbit-Python] Battery connector and battery holder
In-Reply-To: <CANBSuyEEqZ+KLN7dCmb8wYnQK4+XXdLZ9zMaEoYYJXD9qeBJjQ@mail.gmail.com>
References: <CANBSuyHS+548LCmxVjATQJDCe5ro=iTKttwzc=PU-x5M57h45w@mail.gmail.com>
 <CANw+Mz=X_yb9b+pg_JXyAjM4+2OdUtTJWd1knMPmaBsuNiFdFA@mail.gmail.com>
 <CANBSuyEEqZ+KLN7dCmb8wYnQK4+XXdLZ9zMaEoYYJXD9qeBJjQ@mail.gmail.com>
Message-ID: <CABeH_StmmQ7a705FtB3LctRU9Dd6_3=eE51KuaOviXQhtTpUBg@mail.gmail.com>

You can power from the 3V and 0V ring pads directly, that's how Spencer
powers his foosball table and the Whack A Mole game, and also that's how
the kitronik motor controller powers the micro:bit.

I recall a conversation months ago where someone said there is one less
diode drop via that route, so you need to be sure to not over voltage it.
The cores are specified up to 3.6V on the 3V3_IF supply, so two AA's should
be fine.

David


___________________________________________________________
David Whale, B.Sc (Hons), MIET
*Software Engineer and IET Schools Liaison Officer, Essex*

email:  dwhale at theiet.org
twitter: @whaleygeek
blog:  blog.whaleygeek.co.uk

Co-author of global bestselling book "Adventures in Minecraft"
<http://amzn.to/ZGfxZG> - lets get kids coding!
Now in English, Spanish, Chinese and Russian.


On 11 December 2015 at 23:37, Tom Viner <tom at viner.tv> wrote:

>
> On 11 December 2015 at 21:40, Damien George <damien.p.george at gmail.com>
> wrote:
>
>> I hope this reply is not too late!  I looked at the options for the
>> battery pack and the one with 2x AA would be perfect:
>>
>> https://www.kitronik.co.uk/2268-2x-aa-battery-box-with-switch-and-connector.html
>>
>
> I ordered one of those, but they've then clarified via the first Q&A on
> that page that it's not actually going to fit the micro:bit. At least I'll
> have something to hold a pair of AAs in place.
>
> I'll let the person concerned speak for themselves, but I have had word
> from certain roboteer that he's powering the micro:bit via the 3V and GND
> pins, skipping the need for USB / battery connector all together! Any views
> on that approach? We weren't sure if it was "correct" but does seem to work.
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151212/1ab0b8f5/attachment-0001.html>

From naomi.ceder at gmail.com  Fri Dec 11 22:37:43 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Fri, 11 Dec 2015 21:37:43 -0600
Subject: [Microbit-Python] Repl not echoing back
Message-ID: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>

Hi everyone,

I'm having a very weird issue with Mary the micro:bit.

It had been working fine... until I was about to demo before the Chicago
Python group (ChiPy) last night.

Then suddenly the repl wouldn't work. That is, I could apparently connect,
I could type commands in, the LED on the microbit would flash as normal,
but nothing was echoed back. I could put scripts on the flash and the would
run normally, but after trying 3 different terminal programs (all of which
had worked before), still no joy.

Tonight I've been experimenting more and I can confirm that the commands
I'm entering do get to the microbit and are executed as normal. Even
arrowing up and tab completion are working normally, but nothing gets sent
back to my screen.

I've mainly kept the comm settings at what worked well before 115200, N-8-1
and I might add that I've used 2 or 3 different versions of the firmware
with the same reaction, two different USB cables, a lot of swearing, and
I'm sort of at wit's end.

Has anyone else encountered this? Is there something obvious that I'm
missing? Or something mysterious that I need to know? Or is it just a wonky
micro:bit. I honestly didn't do a thing to it from when it worked fine
until when it didn't, and it strikes me as a bit odd that it will do
everything as before, EXCEPT echo the characters back to the terminal.

Halp?

Thanks,
Naomi


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151211/aa2882a5/attachment.html>

From microbit at sheep.art.pl  Sat Dec 12 03:52:08 2015
From: microbit at sheep.art.pl (Radomir Dopieralski)
Date: Sat, 12 Dec 2015 09:52:08 +0100
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
Message-ID: <20151212095208.6dea9e90@ghostwheel>

Hi,

I'm not sure what could the problem be, but for a full picture, can you
also try it on a different computer, to make sure it's not something in
your configuration?

On Fri, 11 Dec 2015 21:37:43 -0600
Naomi Ceder <naomi.ceder at gmail.com> wrote:

> Hi everyone,
> 
> I'm having a very weird issue with Mary the micro:bit.
> 
> It had been working fine... until I was about to demo before the
> Chicago Python group (ChiPy) last night.
> 
> Then suddenly the repl wouldn't work. That is, I could apparently
> connect, I could type commands in, the LED on the microbit would
> flash as normal, but nothing was echoed back. I could put scripts on
> the flash and the would run normally, but after trying 3 different
> terminal programs (all of which had worked before), still no joy.
> 
> Tonight I've been experimenting more and I can confirm that the
> commands I'm entering do get to the microbit and are executed as
> normal. Even arrowing up and tab completion are working normally, but
> nothing gets sent back to my screen.
> 
> I've mainly kept the comm settings at what worked well before 115200,
> N-8-1 and I might add that I've used 2 or 3 different versions of the
> firmware with the same reaction, two different USB cables, a lot of
> swearing, and I'm sort of at wit's end.
> 
> Has anyone else encountered this? Is there something obvious that I'm
> missing? Or something mysterious that I need to know? Or is it just a
> wonky micro:bit. I honestly didn't do a thing to it from when it
> worked fine until when it didn't, and it strikes me as a bit odd that
> it will do everything as before, EXCEPT echo the characters back to
> the terminal.
> 
> Halp?
> 
> Thanks,
> Naomi
> 
> 



-- 
Radomir Dopieralski

-- 
Radomir Dopieralski

From ntoll at ntoll.org  Sat Dec 12 05:12:49 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Sat, 12 Dec 2015 10:12:49 +0000
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
Message-ID: <566BF321.1020800@ntoll.org>

Hi Naomi,

I'm guessing you've done the obvious things like try connecting with a
different USB-serial client (using picocom instead of urepl for example)..?

Have you connected it to a different computer..?

Trying to eliminate different variables to close in on the problem is
hard and frustrating. :-/

If you're using my urepl, has the code changed..?

Let us know how you get on.

N.

On 12/12/15 03:37, Naomi Ceder wrote:
> Hi everyone, 
> 
> I'm having a very weird issue with Mary the micro:bit.
> 
> It had been working fine... until I was about to demo before the Chicago
> Python group (ChiPy) last night.
> 
> Then suddenly the repl wouldn't work. That is, I could apparently
> connect, I could type commands in, the LED on the microbit would flash
> as normal, but nothing was echoed back. I could put scripts on the flash
> and the would run normally, but after trying 3 different terminal
> programs (all of which had worked before), still no joy. 
> 
> Tonight I've been experimenting more and I can confirm that the commands
> I'm entering do get to the microbit and are executed as normal. Even
> arrowing up and tab completion are working normally, but nothing gets
> sent back to my screen.
> 
> I've mainly kept the comm settings at what worked well before 115200,
> N-8-1 and I might add that I've used 2 or 3 different versions of the
> firmware with the same reaction, two different USB cables, a lot of
> swearing, and I'm sort of at wit's end. 
> 
> Has anyone else encountered this? Is there something obvious that I'm
> missing? Or something mysterious that I need to know? Or is it just a
> wonky micro:bit. I honestly didn't do a thing to it from when it worked
> fine until when it didn't, and it strikes me as a bit odd that it will
> do everything as before, EXCEPT echo the characters back to the terminal. 
> 
> Halp?
> 
> Thanks, 
> Naomi
> 
> 
> -- 
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151212/eacb9150/attachment.sig>

From damien.p.george at gmail.com  Sat Dec 12 11:16:40 2015
From: damien.p.george at gmail.com (Damien George)
Date: Sat, 12 Dec 2015 16:16:40 +0000
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <566BF321.1020800@ntoll.org>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566BF321.1020800@ntoll.org>
Message-ID: <CANw+Mz=gLMaFs3VdAsf3qNZ2HBANw3P939rVsm_qsHyeR-dwyg@mail.gmail.com>

If characters are going to the microbit, but not coming back, then it
could be an issue internally on the board with the UART TX pin/track
on the nRF.  Or maybe the Freescale support chip has a problem.

The only thing I can suggest is to reflash the Freescale support chip,
but I don't know if the firmware for that is available to the
public...

I think this is an issue that Jonny (from ARM) would be interested to
hear about.


On Sat, Dec 12, 2015 at 10:12 AM, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
> Hi Naomi,
>
> I'm guessing you've done the obvious things like try connecting with a
> different USB-serial client (using picocom instead of urepl for example)..?
>
> Have you connected it to a different computer..?
>
> Trying to eliminate different variables to close in on the problem is
> hard and frustrating. :-/
>
> If you're using my urepl, has the code changed..?
>
> Let us know how you get on.
>
> N.
>
> On 12/12/15 03:37, Naomi Ceder wrote:
>> Hi everyone,
>>
>> I'm having a very weird issue with Mary the micro:bit.
>>
>> It had been working fine... until I was about to demo before the Chicago
>> Python group (ChiPy) last night.
>>
>> Then suddenly the repl wouldn't work. That is, I could apparently
>> connect, I could type commands in, the LED on the microbit would flash
>> as normal, but nothing was echoed back. I could put scripts on the flash
>> and the would run normally, but after trying 3 different terminal
>> programs (all of which had worked before), still no joy.
>>
>> Tonight I've been experimenting more and I can confirm that the commands
>> I'm entering do get to the microbit and are executed as normal. Even
>> arrowing up and tab completion are working normally, but nothing gets
>> sent back to my screen.
>>
>> I've mainly kept the comm settings at what worked well before 115200,
>> N-8-1 and I might add that I've used 2 or 3 different versions of the
>> firmware with the same reaction, two different USB cables, a lot of
>> swearing, and I'm sort of at wit's end.
>>
>> Has anyone else encountered this? Is there something obvious that I'm
>> missing? Or something mysterious that I need to know? Or is it just a
>> wonky micro:bit. I honestly didn't do a thing to it from when it worked
>> fine until when it didn't, and it strikes me as a bit odd that it will
>> do everything as before, EXCEPT echo the characters back to the terminal.
>>
>> Halp?
>>
>> Thanks,
>> Naomi
>>
>>
>> --
>> Naomi Ceder
>> https://plus.google.com/u/0/111396744045017339164/about
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From tom at viner.tv  Sat Dec 12 15:54:53 2015
From: tom at viner.tv (Tom Viner)
Date: Sat, 12 Dec 2015 20:54:53 +0000
Subject: [Microbit-Python] Where to document hardware pitfalls and
 instructions?
Message-ID: <CANBSuyG+HOtYsy83eMRfC7uvd=uacyrMLgtrssw4Uy=zGVJBWg@mail.gmail.com>

Hi all,

It's great to see the microbit-micropython docs
<https://microbit-micropython.readthedocs.org/en/latest/> expanding with
help for the software side of things. I think we need somewhere to also
document some hardware matters. Essential facts like:

- collated example robots, tutorials
- lessons learnt:
-- e.g. how the battery connector works *
- links to compatible hardware for sale
- links to formal datasheets as they're published

* as noted by Radomir via Angus' Monifa post
<https://microworldtour.github.io/microbit/monifa.html>:

> when it comes to connecting the battery, "Plus is on the lower pin, and
> minus on the higher (outermost) pin of the PCB."


Obviously this wouldn't be Python specific, but it's certainly going to be
helpful for those of us attempting to make robots without baking our
boards! (RIP Mahiri <https://microworldtour.github.io/microbit/mahiri.html>)

Collating our hardware experience from this mailing list and the
microworldtour blogs into one place would be a great open-source-style
contribution for others to jump off from.

Possible locations for this info:
- a hardware section in the microbit-micropython docs
- a hardware lessons page on the microworldtour site
- something new

I'd lean toward adding a new page to the microworldtour site, at least
until it grows into a corpus substantial enough to be it's own thing (if
that were to ever happen).

What do people think? I'm happy to kick off the content, and review
contributions.

Cheers,
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151212/236df4b8/attachment.html>

From naomi.ceder at gmail.com  Sat Dec 12 16:30:59 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sat, 12 Dec 2015 15:30:59 -0600
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <CANw+Mz=gLMaFs3VdAsf3qNZ2HBANw3P939rVsm_qsHyeR-dwyg@mail.gmail.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566BF321.1020800@ntoll.org>
 <CANw+Mz=gLMaFs3VdAsf3qNZ2HBANw3P939rVsm_qsHyeR-dwyg@mail.gmail.com>
Message-ID: <CAKvj0qQF_v2LRzSrhXa_+z6dj2jUKB4vXLF+0eSirukDmqnfFw@mail.gmail.com>

So to be clear I've tried this with the following:

2 computers - a Macbook Pro and a chromebook
2 USB cables - both known to have worked with other devices and with the
micro:bit in the past week
4 terminal programs -  screen, minicom, Beagle Term (a chrome terminal
app), and Nicholas' chrome plug-in editor, all at N-8-1, 115200 (I've also
experimented with various other settings, and as expected they don't seem
to work)
3 different firmware files - one I compiled, which was working the day
before, one downloaded directly from Damien's link in an earlier message,
and the one distributed with Nicholas' Chrome editor.
And yes, I've rebooted the computers, yes, I've reset the micro:bit, left
it without power overnight, etc.

*In every single case, I get the exact same result* - it's clear that the
keystrokes are getting in - I can enter things and see what I enter, and I
can scroll stuff, play music, etc. Also tab completion and the up arrow key
appear to work (I can't see the results but if I complete the commands and
hit enter I do get the right result. Also the LED on the micro:bit flickers
on each keystroke, just as it did when it was working correctly.

However, other that what I enter from the keyboard, nothing is sent back to
be shown on my screen.

So yes, I've come to the conclusion that it has to be something on the
device, and Damien's suggestion of something with the UART certainly makes
sense to me. As far as I can see with a jeweler's loupe, there are a couple
of tiny scratches on the device that expose the surface of a trace, but
none of the traces is broken or shorted to another.

I'm not sure if Johnny from ARM is on this list. If he is, I'd love to hear
from him and would try anything he might suggest. If he isn't and someone
could connect me with him, that would be ace.

Cheers,
Naomi



On 12 December 2015 at 10:16, Damien George <damien.p.george at gmail.com>
wrote:

> If characters are going to the microbit, but not coming back, then it
> could be an issue internally on the board with the UART TX pin/track
> on the nRF.  Or maybe the Freescale support chip has a problem.
>
> The only thing I can suggest is to reflash the Freescale support chip,
> but I don't know if the firmware for that is available to the
> public...
>
> I think this is an issue that Jonny (from ARM) would be interested to
> hear about.
>
>
> On Sat, Dec 12, 2015 at 10:12 AM, Nicholas H.Tollervey <ntoll at ntoll.org>
> wrote:
> > Hi Naomi,
> >
> > I'm guessing you've done the obvious things like try connecting with a
> > different USB-serial client (using picocom instead of urepl for
> example)..?
> >
> > Have you connected it to a different computer..?
> >
> > Trying to eliminate different variables to close in on the problem is
> > hard and frustrating. :-/
> >
> > If you're using my urepl, has the code changed..?
> >
> > Let us know how you get on.
> >
> > N.
> >
> > On 12/12/15 03:37, Naomi Ceder wrote:
> >> Hi everyone,
> >>
> >> I'm having a very weird issue with Mary the micro:bit.
> >>
> >> It had been working fine... until I was about to demo before the Chicago
> >> Python group (ChiPy) last night.
> >>
> >> Then suddenly the repl wouldn't work. That is, I could apparently
> >> connect, I could type commands in, the LED on the microbit would flash
> >> as normal, but nothing was echoed back. I could put scripts on the flash
> >> and the would run normally, but after trying 3 different terminal
> >> programs (all of which had worked before), still no joy.
> >>
> >> Tonight I've been experimenting more and I can confirm that the commands
> >> I'm entering do get to the microbit and are executed as normal. Even
> >> arrowing up and tab completion are working normally, but nothing gets
> >> sent back to my screen.
> >>
> >> I've mainly kept the comm settings at what worked well before 115200,
> >> N-8-1 and I might add that I've used 2 or 3 different versions of the
> >> firmware with the same reaction, two different USB cables, a lot of
> >> swearing, and I'm sort of at wit's end.
> >>
> >> Has anyone else encountered this? Is there something obvious that I'm
> >> missing? Or something mysterious that I need to know? Or is it just a
> >> wonky micro:bit. I honestly didn't do a thing to it from when it worked
> >> fine until when it didn't, and it strikes me as a bit odd that it will
> >> do everything as before, EXCEPT echo the characters back to the
> terminal.
> >>
> >> Halp?
> >>
> >> Thanks,
> >> Naomi
> >>
> >>
> >> --
> >> Naomi Ceder
> >> https://plus.google.com/u/0/111396744045017339164/about
> >>
> >>
> >> _______________________________________________
> >> Microbit mailing list
> >> Microbit at python.org
> >> https://mail.python.org/mailman/listinfo/microbit
> >>
> >
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>



-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151212/8378de29/attachment.html>

From willingc at willingconsulting.com  Sat Dec 12 18:27:26 2015
From: willingc at willingconsulting.com (Carol Willing)
Date: Sat, 12 Dec 2015 15:27:26 -0800
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
Message-ID: <566CAD5E.6000205@willingconsulting.com>

Hi Naomi,

Perhaps a shot in the dark, did you try picocom?  picocom /dev/ttyACM0 
-b 115200  Replacing with the correct port. I've used with the Mac Pro. 
I'm still running Yosemite. Are you on El Capitan?

You could try getting rid of any cruft of old USB /dev/tty files.


Damien, Does the microbit have a hard reset by pulling a GPIO pin low?


> Naomi Ceder <mailto:naomi.ceder at gmail.com>
> December 11, 2015 at 7:37 PM
> Hi everyone,
>
> I'm having a very weird issue with Mary the micro:bit.
>
> It had been working fine... until I was about to demo before the 
> Chicago Python group (ChiPy) last night.
>
> Then suddenly the repl wouldn't work. That is, I could apparently 
> connect, I could type commands in, the LED on the microbit would flash 
> as normal, but nothing was echoed back. I could put scripts on the 
> flash and the would run normally, but after trying 3 different 
> terminal programs (all of which had worked before), still no joy.
>
> Tonight I've been experimenting more and I can confirm that the 
> commands I'm entering do get to the microbit and are executed as 
> normal. Even arrowing up and tab completion are working normally, but 
> nothing gets sent back to my screen.
>
> I've mainly kept the comm settings at what worked well before 115200, 
> N-8-1 and I might add that I've used 2 or 3 different versions of the 
> firmware with the same reaction, two different USB cables, a lot of 
> swearing, and I'm sort of at wit's end.
>
> Has anyone else encountered this? Is there something obvious that I'm 
> missing? Or something mysterious that I need to know? Or is it just a 
> wonky micro:bit. I honestly didn't do a thing to it from when it 
> worked fine until when it didn't, and it strikes me as a bit odd that 
> it will do everything as before, EXCEPT echo the characters back to 
> the terminal.
>
> Halp?
>
> Thanks,
> Naomi
>
>
> -- 
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit

-- 
Sent from Postbox 
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151212/489b8d69/attachment-0001.html>

From naomi.ceder at gmail.com  Sat Dec 12 20:33:32 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sat, 12 Dec 2015 19:33:32 -0600
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <566CAD5E.6000205@willingconsulting.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
Message-ID: <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>

Hi Carol,

I just tried picocom with exactly the same results - I'm still on yosemite,
but getting the same behaviour on 5 terminal programs and two different
OS's I'm going to say the issue is the device at this point.

Cheers,
Naomi


On 12 December 2015 at 17:27, Carol Willing <willingc at willingconsulting.com>
wrote:

> Hi Naomi,
>
> Perhaps a shot in the dark, did you try picocom?  picocom /dev/ttyACM0 -b
> 115200  Replacing with the correct port. I've used with the Mac Pro. I'm
> still running Yosemite. Are you on El Capitan?
>
> You could try getting rid of any cruft of old USB /dev/tty files.
>
>
> Damien, Does the microbit have a hard reset by pulling a GPIO pin low?
>
>
> Naomi Ceder <naomi.ceder at gmail.com>
> December 11, 2015 at 7:37 PM
> Hi everyone,
>
> I'm having a very weird issue with Mary the micro:bit.
>
> It had been working fine... until I was about to demo before the Chicago
> Python group (ChiPy) last night.
>
> Then suddenly the repl wouldn't work. That is, I could apparently connect,
> I could type commands in, the LED on the microbit would flash as normal,
> but nothing was echoed back. I could put scripts on the flash and the would
> run normally, but after trying 3 different terminal programs (all of which
> had worked before), still no joy.
>
> Tonight I've been experimenting more and I can confirm that the commands
> I'm entering do get to the microbit and are executed as normal. Even
> arrowing up and tab completion are working normally, but nothing gets sent
> back to my screen.
>
> I've mainly kept the comm settings at what worked well before 115200,
> N-8-1 and I might add that I've used 2 or 3 different versions of the
> firmware with the same reaction, two different USB cables, a lot of
> swearing, and I'm sort of at wit's end.
>
> Has anyone else encountered this? Is there something obvious that I'm
> missing? Or something mysterious that I need to know? Or is it just a wonky
> micro:bit. I honestly didn't do a thing to it from when it worked fine
> until when it didn't, and it strikes me as a bit odd that it will do
> everything as before, EXCEPT echo the characters back to the terminal.
>
> Halp?
>
> Thanks,
> Naomi
>
>
> --
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
> --
> Sent from Postbox
> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151212/ff9e4ae4/attachment.html>

From ntoll at ntoll.org  Sun Dec 13 04:23:44 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Sun, 13 Dec 2015 09:23:44 +0000
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
 <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
Message-ID: <566D3920.70700@ntoll.org>

Folks,

Poor old Mary micro:bit... my (wife) Mary is going to be heartbroken
that her namesake has a bad case of the collywobbles.

Here's what I suggest:

* We "retire" Mary - can you post her back to me and I'll make sure it
gets to Jonny at ARM who'll be interested in such hardware failures?

* We "promote" one of the new boards heading in your direction to the
world tour. Given this is a US based series of events I propose we name
the new micro:bit in honour of the FLOTUS: "Michelle micro:bit". :-P

* Naomi, can you write up how Mary got "sick" and ping me a PR for the
website? I'll add a note to explain the appearance of Michelle and then
we can let the tour continue.

Sound like a plan?

N.

On 13/12/15 01:33, Naomi Ceder wrote:
> Hi Carol,
> 
> I just tried picocom with exactly the same results - I'm still on
> yosemite, but getting the same behaviour on 5 terminal programs and two
> different OS's I'm going to say the issue is the device at this point.
> 
> Cheers,
> Naomi
> 
> 
> On 12 December 2015 at 17:27, Carol Willing
> <willingc at willingconsulting.com <mailto:willingc at willingconsulting.com>>
> wrote:
> 
>     Hi Naomi,
> 
>     Perhaps a shot in the dark, did you try picocom?  picocom
>     /dev/ttyACM0 -b 115200  Replacing with the correct port. I've used
>     with the Mac Pro. I'm still running Yosemite. Are you on El Capitan?
> 
>     You could try getting rid of any cruft of old USB /dev/tty files.
> 
> 
>     Damien, Does the microbit have a hard reset by pulling a GPIO pin low?
> 
> 
>>     Naomi Ceder <mailto:naomi.ceder at gmail.com>
>>     December 11, 2015 at 7:37 PM
>>     Hi everyone, 
>>
>>     I'm having a very weird issue with Mary the micro:bit.
>>
>>     It had been working fine... until I was about to demo before the
>>     Chicago Python group (ChiPy) last night.
>>
>>     Then suddenly the repl wouldn't work. That is, I could apparently
>>     connect, I could type commands in, the LED on the microbit would
>>     flash as normal, but nothing was echoed back. I could put scripts
>>     on the flash and the would run normally, but after trying 3
>>     different terminal programs (all of which had worked before),
>>     still no joy. 
>>
>>     Tonight I've been experimenting more and I can confirm that the
>>     commands I'm entering do get to the microbit and are executed as
>>     normal. Even arrowing up and tab completion are working normally,
>>     but nothing gets sent back to my screen.
>>
>>     I've mainly kept the comm settings at what worked well before
>>     115200, N-8-1 and I might add that I've used 2 or 3 different
>>     versions of the firmware with the same reaction, two different USB
>>     cables, a lot of swearing, and I'm sort of at wit's end. 
>>
>>     Has anyone else encountered this? Is there something obvious that
>>     I'm missing? Or something mysterious that I need to know? Or is it
>>     just a wonky micro:bit. I honestly didn't do a thing to it from
>>     when it worked fine until when it didn't, and it strikes me as a
>>     bit odd that it will do everything as before, EXCEPT echo the
>>     characters back to the terminal. 
>>
>>     Halp?
>>
>>     Thanks, 
>>     Naomi
>>
>>
>>     -- 
>>     Naomi Ceder
>>     https://plus.google.com/u/0/111396744045017339164/about
>>     _______________________________________________
>>     Microbit mailing list
>>     Microbit at python.org <mailto:Microbit at python.org>
>>     https://mail.python.org/mailman/listinfo/microbit
> 
>     -- 
>     Sent from Postbox
>     <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
> 
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
> 
> 
> 
> 
> -- 
> Naomi Ceder
> https://plus.google.com/u/0/111396744045017339164/about
> 
> 
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151213/dcadacf4/attachment.sig>

From mschafer at wireframe.biz  Sun Dec 13 05:13:25 2015
From: mschafer at wireframe.biz (Mark Schafer)
Date: Sun, 13 Dec 2015 23:13:25 +1300
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <566D3920.70700@ntoll.org>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
 <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
 <566D3920.70700@ntoll.org>
Message-ID: <566D44C5.9020705@wireframe.biz>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151213/1ee10cba/attachment-0001.html>

From naomi.ceder at gmail.com  Sun Dec 13 09:59:24 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sun, 13 Dec 2015 08:59:24 -0600
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <566D44C5.9020705@wireframe.biz>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
 <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
 <566D3920.70700@ntoll.org> <566D44C5.9020705@wireframe.biz>
Message-ID: <CAKvj0qQyqy0Bfge7PYWFtr+axnGUS+ib5=SoH9pyRS+Ag-TDtg@mail.gmail.com>

As I mentioned in an earlier post I've flashed 3 different hex files
already, one directly downloaded from Damien's site.
On Dec 13, 2015 4:20 AM, "Mark Schafer" <mschafer at wireframe.biz> wrote:

> Or someone could send you a hex file and you could try reflashing it by
> dropping it onto the folder and see if that works ?
>
> On 12/13/2015 10:23 PM, Nicholas H.Tollervey wrote:
>
> Folks,
>
> Poor old Mary micro:bit... my (wife) Mary is going to be heartbroken
> that her namesake has a bad case of the collywobbles.
>
> Here's what I suggest:
>
> * We "retire" Mary - can you post her back to me and I'll make sure it
> gets to Jonny at ARM who'll be interested in such hardware failures?
>
> * We "promote" one of the new boards heading in your direction to the
> world tour. Given this is a US based series of events I propose we name
> the new micro:bit in honour of the FLOTUS: "Michelle micro:bit". :-P
>
> * Naomi, can you write up how Mary got "sick" and ping me a PR for the
> website? I'll add a note to explain the appearance of Michelle and then
> we can let the tour continue.
>
> Sound like a plan?
>
> N.
>
> On 13/12/15 01:33, Naomi Ceder wrote:
>
> Hi Carol,
>
> I just tried picocom with exactly the same results - I'm still on
> yosemite, but getting the same behaviour on 5 terminal programs and two
> different OS's I'm going to say the issue is the device at this point.
>
> Cheers,
> Naomi
>
>
> On 12 December 2015 at 17:27, Carol Willing
> <willingc at willingconsulting.com <mailto:willingc at willingconsulting.com> <willingc at willingconsulting.com>>
> wrote:
>
>     Hi Naomi,
>
>     Perhaps a shot in the dark, did you try picocom?  picocom
>     /dev/ttyACM0 -b 115200  Replacing with the correct port. I've used
>     with the Mac Pro. I'm still running Yosemite. Are you on El Capitan?
>
>     You could try getting rid of any cruft of old USB /dev/tty files.
>
>
>     Damien, Does the microbit have a hard reset by pulling a GPIO pin low?
>
>
>
>     Naomi Ceder <mailto:naomi.ceder at gmail.com> <naomi.ceder at gmail.com>
>     December 11, 2015 at 7:37 PM
>     Hi everyone,
>
>     I'm having a very weird issue with Mary the micro:bit.
>
>     It had been working fine... until I was about to demo before the
>     Chicago Python group (ChiPy) last night.
>
>     Then suddenly the repl wouldn't work. That is, I could apparently
>     connect, I could type commands in, the LED on the microbit would
>     flash as normal, but nothing was echoed back. I could put scripts
>     on the flash and the would run normally, but after trying 3
>     different terminal programs (all of which had worked before),
>     still no joy.
>
>     Tonight I've been experimenting more and I can confirm that the
>     commands I'm entering do get to the microbit and are executed as
>     normal. Even arrowing up and tab completion are working normally,
>     but nothing gets sent back to my screen.
>
>     I've mainly kept the comm settings at what worked well before
>     115200, N-8-1 and I might add that I've used 2 or 3 different
>     versions of the firmware with the same reaction, two different USB
>     cables, a lot of swearing, and I'm sort of at wit's end.
>
>     Has anyone else encountered this? Is there something obvious that
>     I'm missing? Or something mysterious that I need to know? Or is it
>     just a wonky micro:bit. I honestly didn't do a thing to it from
>     when it worked fine until when it didn't, and it strikes me as a
>     bit odd that it will do everything as before, EXCEPT echo the
>     characters back to the terminal.
>
>     Halp?
>
>     Thanks,
>     Naomi
>
>
>     --
>     Naomi Ceder
>     https://plus.google.com/u/0/111396744045017339164/about
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org> <Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
>
>
>     --
>     Sent from Postbox
>     <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach> <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
>
>     _______________________________________________
>     Microbit mailing list
>     Microbit at python.org <mailto:Microbit at python.org> <Microbit at python.org>
>     https://mail.python.org/mailman/listinfo/microbit
>
>
>
>
> --
> Naomi Cederhttps://plus.google.com/u/0/111396744045017339164/about
>
>
> _______________________________________________
> Microbit mailing listMicrobit at python.orghttps://mail.python.org/mailman/listinfo/microbit
>
>
>
>
> _______________________________________________
> Microbit mailing listMicrobit at python.orghttps://mail.python.org/mailman/listinfo/microbit
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7294 / Virus Database: 4483/11165 - Release Date: 12/12/15
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151213/c3546ea6/attachment.html>

From naomi.ceder at gmail.com  Sun Dec 13 18:42:32 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Sun, 13 Dec 2015 17:42:32 -0600
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <566D3920.70700@ntoll.org>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
 <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
 <566D3920.70700@ntoll.org>
Message-ID: <CAKvj0qQPPXDfUsVaBd19804aZx3zuusQHVdSS9=fGaO4HB++mQ@mail.gmail.com>

Yep, those suggestions make sense. I particularly like the Michelle idea.
:-)

Since Mary is functioning in all other respects I'll keep her here for
hacking until the others safely arrive.

Cheers,
Naomi

On 13 December 2015 at 03:23, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:

> Folks,
>
> Poor old Mary micro:bit... my (wife) Mary is going to be heartbroken
> that her namesake has a bad case of the collywobbles.
>
> Here's what I suggest:
>
> * We "retire" Mary - can you post her back to me and I'll make sure it
> gets to Jonny at ARM who'll be interested in such hardware failures?
>
> * We "promote" one of the new boards heading in your direction to the
> world tour. Given this is a US based series of events I propose we name
> the new micro:bit in honour of the FLOTUS: "Michelle micro:bit". :-P
>
> * Naomi, can you write up how Mary got "sick" and ping me a PR for the
> website? I'll add a note to explain the appearance of Michelle and then
> we can let the tour continue.
>
> Sound like a plan?
>
> N.
>
> On 13/12/15 01:33, Naomi Ceder wrote:
> > Hi Carol,
> >
> > I just tried picocom with exactly the same results - I'm still on
> > yosemite, but getting the same behaviour on 5 terminal programs and two
> > different OS's I'm going to say the issue is the device at this point.
> >
> > Cheers,
> > Naomi
> >
> >
> > On 12 December 2015 at 17:27, Carol Willing
> > <willingc at willingconsulting.com <mailto:willingc at willingconsulting.com>>
> > wrote:
> >
> >     Hi Naomi,
> >
> >     Perhaps a shot in the dark, did you try picocom?  picocom
> >     /dev/ttyACM0 -b 115200  Replacing with the correct port. I've used
> >     with the Mac Pro. I'm still running Yosemite. Are you on El Capitan?
> >
> >     You could try getting rid of any cruft of old USB /dev/tty files.
> >
> >
> >     Damien, Does the microbit have a hard reset by pulling a GPIO pin
> low?
> >
> >
> >>     Naomi Ceder <mailto:naomi.ceder at gmail.com>
> >>     December 11, 2015 at 7:37 PM
> >>     Hi everyone,
> >>
> >>     I'm having a very weird issue with Mary the micro:bit.
> >>
> >>     It had been working fine... until I was about to demo before the
> >>     Chicago Python group (ChiPy) last night.
> >>
> >>     Then suddenly the repl wouldn't work. That is, I could apparently
> >>     connect, I could type commands in, the LED on the microbit would
> >>     flash as normal, but nothing was echoed back. I could put scripts
> >>     on the flash and the would run normally, but after trying 3
> >>     different terminal programs (all of which had worked before),
> >>     still no joy.
> >>
> >>     Tonight I've been experimenting more and I can confirm that the
> >>     commands I'm entering do get to the microbit and are executed as
> >>     normal. Even arrowing up and tab completion are working normally,
> >>     but nothing gets sent back to my screen.
> >>
> >>     I've mainly kept the comm settings at what worked well before
> >>     115200, N-8-1 and I might add that I've used 2 or 3 different
> >>     versions of the firmware with the same reaction, two different USB
> >>     cables, a lot of swearing, and I'm sort of at wit's end.
> >>
> >>     Has anyone else encountered this? Is there something obvious that
> >>     I'm missing? Or something mysterious that I need to know? Or is it
> >>     just a wonky micro:bit. I honestly didn't do a thing to it from
> >>     when it worked fine until when it didn't, and it strikes me as a
> >>     bit odd that it will do everything as before, EXCEPT echo the
> >>     characters back to the terminal.
> >>
> >>     Halp?
> >>
> >>     Thanks,
> >>     Naomi
> >>
> >>
> >>     --
> >>     Naomi Ceder
> >>     https://plus.google.com/u/0/111396744045017339164/about
> >>     _______________________________________________
> >>     Microbit mailing list
> >>     Microbit at python.org <mailto:Microbit at python.org>
> >>     https://mail.python.org/mailman/listinfo/microbit
> >
> >     --
> >     Sent from Postbox
> >     <
> https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
> >
> >
> >     _______________________________________________
> >     Microbit mailing list
> >     Microbit at python.org <mailto:Microbit at python.org>
> >     https://mail.python.org/mailman/listinfo/microbit
> >
> >
> >
> >
> > --
> > Naomi Ceder
> > https://plus.google.com/u/0/111396744045017339164/about
> >
> >
> > _______________________________________________
> > Microbit mailing list
> > Microbit at python.org
> > https://mail.python.org/mailman/listinfo/microbit
> >
>
>
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>


-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151213/84a555c0/attachment.html>

From damien.p.george at gmail.com  Sun Dec 20 19:41:36 2015
From: damien.p.george at gmail.com (Damien George)
Date: Mon, 21 Dec 2015 00:41:36 +0000
Subject: [Microbit-Python] Where to document hardware pitfalls and
 instructions?
In-Reply-To: <CANBSuyG+HOtYsy83eMRfC7uvd=uacyrMLgtrssw4Uy=zGVJBWg@mail.gmail.com>
References: <CANBSuyG+HOtYsy83eMRfC7uvd=uacyrMLgtrssw4Uy=zGVJBWg@mail.gmail.com>
Message-ID: <CANw+Mz=APYg84DyNPoThp0m+Dn_kWTH1PVGP9-1Mbzi0BuMLrw@mail.gmail.com>

Hi Tom,

This is definitely something that should be shared among all users of
the microbit (Python, TD, JS, etc).  We could start writing up
something, but ultimately it should be put somewhere on
microbit.co.uk.

Cheers,
Damien.


On Sat, Dec 12, 2015 at 8:54 PM, Tom Viner <tom at viner.tv> wrote:
> Hi all,
>
> It's great to see the microbit-micropython docs expanding with help for the
> software side of things. I think we need somewhere to also document some
> hardware matters. Essential facts like:
>
> - collated example robots, tutorials
> - lessons learnt:
> -- e.g. how the battery connector works *
> - links to compatible hardware for sale
> - links to formal datasheets as they're published
>
> * as noted by Radomir via Angus' Monifa post:
>>
>> when it comes to connecting the battery, "Plus is on the lower pin, and
>> minus on the higher (outermost) pin of the PCB."
>
>
> Obviously this wouldn't be Python specific, but it's certainly going to be
> helpful for those of us attempting to make robots without baking our boards!
> (RIP Mahiri)
>
> Collating our hardware experience from this mailing list and the
> microworldtour blogs into one place would be a great open-source-style
> contribution for others to jump off from.
>
> Possible locations for this info:
> - a hardware section in the microbit-micropython docs
> - a hardware lessons page on the microworldtour site
> - something new
>
> I'd lean toward adding a new page to the microworldtour site, at least until
> it grows into a corpus substantial enough to be it's own thing (if that were
> to ever happen).
>
> What do people think? I'm happy to kick off the content, and review
> contributions.
>
> Cheers,
> Tom
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>

From harry.percival at gmail.com  Sun Dec 27 09:13:50 2015
From: harry.percival at gmail.com (Harry Percival)
Date: Sun, 27 Dec 2015 14:13:50 +0000
Subject: [Microbit-Python] Notes from "developers meet teachers" session
Message-ID: <CACFvh9_yZVx2Sif6nX=+=0roHH256o6E_i2m4_V5vWOgSwoA6A@mail.gmail.com>

Hi gang,

Y'all may know Nick ran a session with Computing At School to introduce
teachers to Python developers.  Here are the notes I took while working
with the teacher I met:


## possible confusion from no. of arguments to method that looks like a
function

>>> microbit.display.set_pixel(2,3)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: function takes 4 positional arguments but 3 were given

--> error msg confusing, 2 or 3 or 4 arguments?


## some things that are different from normal Python

- random function is not like python one!  grr

- perhaps more confusingly, sleep uses different units from time.sleep. arg!

(neither of these are dealbreakers, just maybe something to warn ppl about?)



## workflow of save + flashing, the editor

download / save / remember to rename is annoying.  but we found a shortcut
- you can save directly to the flash drive.

re: editor, we found ourselves wanting a shortcut key for save/download

re editor, we wanted to save the file out of the editor.  maybe having a
button for that is too much, but we did struggle to copy + paste into
notepad cos it had linux line endings.

## other misc

x,y pixels starting at top left is not like standard x,y in maths... but,
ok.

re microrepl readme:  teacher asks, what is a virtualenv?


Sorry these are in rough form, hope they might spark some ideas or just
provide some useful background knowledge for ppl.

Hope you're all having a great christmas!

HP


-- 
------------------------------
Harry J.W. Percival
------------------------------
Twitter: @hjwp
Mobile:  +44 (0) 78877 02511
Skype:         harry.percival
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151227/ef80407b/attachment.html>

From tom at viner.tv  Sun Dec 27 13:13:18 2015
From: tom at viner.tv (Tom Viner)
Date: Sun, 27 Dec 2015 18:13:18 +0000
Subject: [Microbit-Python] Notes from "developers meet teachers" session
In-Reply-To: <CACFvh9_yZVx2Sif6nX=+=0roHH256o6E_i2m4_V5vWOgSwoA6A@mail.gmail.com>
References: <CACFvh9_yZVx2Sif6nX=+=0roHH256o6E_i2m4_V5vWOgSwoA6A@mail.gmail.com>
Message-ID: <CANBSuyFQw4E7Kny5qVX5-Se0b9fv7vvy3HiBqzJ8GYu1Fg4BsQ@mail.gmail.com>

On 27 December 2015 at 14:13, Harry Percival <harry.percival at gmail.com>
wrote:

> ## workflow of save + flashing, the editor
>
> download / save / remember to rename is annoying.  but we found a shortcut
> - you can save directly to the flash drive.
>
> re: editor, we found ourselves wanting a shortcut key for save/download
>
> re editor, we wanted to save the file out of the editor.  maybe having a
> button for that is too much, but we did struggle to copy + paste into
> notepad cos it had linux line endings.
>

Which editor are you using Harry? Why did you have to rename the hex file?

If you're using upyed <https://github.com/ntoll/upyed>, then you can use
the upy*flash*ed <https://pypi.python.org/pypi/upyflashed> utility to
insta-copy the hex to the mounted micro:bit for you.

There's also the pyboard.py script
<https://github.com/bbcmicrobit/micropython/blob/master/tools/pyboard.py#L36>
that
can copy over your python script and compile it direct on the micro:bit.
Although you'll hit a MemoryError for "non-small" scripts.

Finally, there's mu <https://github.com/ntoll/mu> which is still in
development.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151227/f85dc6cb/attachment.html>

From david at thinkingbinaries.com  Sun Dec 27 16:01:16 2015
From: david at thinkingbinaries.com (David Whale)
Date: Sun, 27 Dec 2015 21:01:16 +0000
Subject: [Microbit-Python] Notes from "developers meet teachers" session
In-Reply-To: <CACFvh9_yZVx2Sif6nX=+=0roHH256o6E_i2m4_V5vWOgSwoA6A@mail.gmail.com>
References: <CACFvh9_yZVx2Sif6nX=+=0roHH256o6E_i2m4_V5vWOgSwoA6A@mail.gmail.com>
Message-ID: <CABeH_Sv7p_Qw-hFg5Q=J4N8d7Y-ycRrzW3-T5tSmC1sorp2_Ag@mail.gmail.com>

Some of this is browser specific, if you are using the in-browser
experience, and Touch Develop and Blocks an Code Kingdoms suffer the same
fate.

Safari on Mac does not have a way (apparently) of naming the saved file,
from a file downloaded via a javascript application - it always calls it
'Unknown'. The hex and the SAVE'd (serialised code) file both get called
Unknown, which is doubly confusing.

At an event a couple of weeks ago where 1000 kids attended, we tried the
Chrome method of defaulting the save location to the micro:bit, but it was
confusing for two reasons

1) There was no download progress inside Chrome, and if you didn't think to
look at the flashing LED on the *back* of the micro:bit, you had no way to
know the download was in progress or indeed had finished. This caused the
children to press the download again, and two concurrent downloads
happened, which confuses the micro:bit and makes matters worse.

2) If you save directly to the micro:bit drive, you don't now have a local
copy of your program (e.g. to store on a USB memory stick), and to save it,
you then have to download it again to a different location (by which time
you might have accidentally edited the program and got something different
saved to what was working). We saw this a number of times when children
wanted to take a copy of their program onto a USB memory stick. The default
download location was then a pain, because you had to find a way to change
it to save it on the USB memory stick.

In the end, we re-configured the computers to just save in the 'default
downloads folder'.

Also note, the instructions on the screen of the other editors say 'drag
the downloaded .hex file onto your micro:bit' - so this further confused
users.

You might also like to know that the TD and blocks have an 'import code'
feature, so that if you get your .hex and your saved code files mixed up,
you can still import from the .hex file - presumably they serialise the AST
inside the .hex file at the cost of a small amount of flash space on the
real micro:bit, so that the code is always retrievable. Does the python
support this (seems like a good idea given that the script is already
embedded inside the .hex file anyway).

David.


___________________________________________________________
David Whale, B.Sc (Hons), MIET
*Software Engineer and IET Schools Liaison Officer, Essex*

email:  dwhale at theiet.org
twitter: @whaleygeek
blog:  blog.whaleygeek.co.uk

Co-author of global bestselling book "Adventures in Minecraft"
<http://amzn.to/ZGfxZG> - lets get kids coding!
Now in English, Spanish, Chinese and Russian.


On 27 December 2015 at 14:13, Harry Percival <harry.percival at gmail.com>
wrote:

> Hi gang,
>
> Y'all may know Nick ran a session with Computing At School to introduce
> teachers to Python developers.  Here are the notes I took while working
> with the teacher I met:
>
>
> ## possible confusion from no. of arguments to method that looks like a
> function
>
> >>> microbit.display.set_pixel(2,3)
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> TypeError: function takes 4 positional arguments but 3 were given
>
> --> error msg confusing, 2 or 3 or 4 arguments?
>
>
> ## some things that are different from normal Python
>
> - random function is not like python one!  grr
>
> - perhaps more confusingly, sleep uses different units from time.sleep.
> arg!
>
> (neither of these are dealbreakers, just maybe something to warn ppl
> about?)
>
>
>
> ## workflow of save + flashing, the editor
>
> download / save / remember to rename is annoying.  but we found a shortcut
> - you can save directly to the flash drive.
>
> re: editor, we found ourselves wanting a shortcut key for save/download
>
> re editor, we wanted to save the file out of the editor.  maybe having a
> button for that is too much, but we did struggle to copy + paste into
> notepad cos it had linux line endings.
>
> ## other misc
>
> x,y pixels starting at top left is not like standard x,y in maths... but,
> ok.
>
> re microrepl readme:  teacher asks, what is a virtualenv?
>
>
> Sorry these are in rough form, hope they might spark some ideas or just
> provide some useful background knowledge for ppl.
>
> Hope you're all having a great christmas!
>
> HP
>
>
> --
> ------------------------------
> Harry J.W. Percival
> ------------------------------
> Twitter: @hjwp
> Mobile:  +44 (0) 78877 02511
> Skype:         harry.percival
>
> _______________________________________________
> Microbit mailing list
> Microbit at python.org
> https://mail.python.org/mailman/listinfo/microbit
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151227/f23bae11/attachment.html>

From mal at egenix.com  Tue Dec 29 07:22:12 2015
From: mal at egenix.com (M.-A. Lemburg)
Date: Tue, 29 Dec 2015 13:22:12 +0100
Subject: [Microbit-Python] Starting up with the Microbit
Message-ID: <56827AF4.2000300@egenix.com>

Hello everyone,

I received a microbit from Angus just before Christmas and
would like to start playing with it this week:

http://microworldtour.github.io/microbit/monifa.html

Unfortunately, I'm a bit lost how to start, since the information
about basic things like how to connect and power up the device
seems to be well hidden somewhere on the net ;-)

The board has pins saying "3V" and "GND" and there's
a battery connector on it as well (but without indication
of which pin is + and which is ground (*)). Would it be enough to
connect a power supply to the pins or do I need to
find a plug for the battery connector ?

Also: I've seen a serial console being used to drive the
REPL, but there don't appear to be serial con pins on the
device. Is the USB port used for this ? The README seems to
imply this ("Upon reset you will have a REPL on the USB CDC
serial port").

Lastly: For flashing the device, is it possible to mount
the flash drive using the USB port or do I need to send the
image over the serial port ?

Lots of question and I assume that most of these are FAQs :-)

I will probably drive to an electronics shop to get some
cables and perhaps a battery pack today.

(*) It may be useful to add some text to the board to
help kids and teachers with this.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Dec 29 2015)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/


From ntoll at ntoll.org  Tue Dec 29 08:12:07 2015
From: ntoll at ntoll.org (Nicholas H.Tollervey)
Date: Tue, 29 Dec 2015 13:12:07 +0000
Subject: [Microbit-Python] Starting up with the Microbit
In-Reply-To: <56827AF4.2000300@egenix.com>
References: <56827AF4.2000300@egenix.com>
Message-ID: <568286A7.9050902@ntoll.org>

Hi Marc-Andre,

To flash Python scripts onto the device try uflash
(http://uflash.readthedocs.org/en/latest/) from the command line.

To connect to the REPL, try this:

picocom /dev/ttyACM0 -b 115200

...or microrepl:

https://github.com/ntoll/microrepl

There will be a native editor available soon that should "just work"
(tm) - once it'd finished (that's my "Christmas holiday fun project" for
this year...).

Documentation for the microbit API is here:

http://microbit-micropython.readthedocs.org/en/latest/

;-)

N.

On 29/12/15 12:22, M.-A. Lemburg wrote:
> Hello everyone,
> 
> I received a microbit from Angus just before Christmas and
> would like to start playing with it this week:
> 
> http://microworldtour.github.io/microbit/monifa.html
> 
> Unfortunately, I'm a bit lost how to start, since the information
> about basic things like how to connect and power up the device
> seems to be well hidden somewhere on the net ;-)
> 
> The board has pins saying "3V" and "GND" and there's
> a battery connector on it as well (but without indication
> of which pin is + and which is ground (*)). Would it be enough to
> connect a power supply to the pins or do I need to
> find a plug for the battery connector ?
> 
> Also: I've seen a serial console being used to drive the
> REPL, but there don't appear to be serial con pins on the
> device. Is the USB port used for this ? The README seems to
> imply this ("Upon reset you will have a REPL on the USB CDC
> serial port").
> 
> Lastly: For flashing the device, is it possible to mount
> the flash drive using the USB port or do I need to send the
> image over the serial port ?
> 
> Lots of question and I assume that most of these are FAQs :-)
> 
> I will probably drive to an electronics shop to get some
> cables and perhaps a battery pack today.
> 
> (*) It may be useful to add some text to the board to
> help kids and teachers with this.
> 
> Thanks,
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/microbit/attachments/20151229/4dd1fef9/attachment.sig>

From mal at egenix.com  Wed Dec 30 17:21:41 2015
From: mal at egenix.com (M.-A. Lemburg)
Date: Wed, 30 Dec 2015 23:21:41 +0100
Subject: [Microbit-Python] Starting up with the Microbit
In-Reply-To: <568286A7.9050902@ntoll.org>
References: <56827AF4.2000300@egenix.com> <568286A7.9050902@ntoll.org>
Message-ID: <568458F5.9090308@egenix.com>

On 29.12.2015 14:12, Nicholas H.Tollervey wrote:
> Hi Marc-Andre,
> 
> To flash Python scripts onto the device try uflash
> (http://uflash.readthedocs.org/en/latest/) from the command line.
> 
> To connect to the REPL, try this:
> 
> picocom /dev/ttyACM0 -b 115200
> 
> ...or microrepl:
> 
> https://github.com/ntoll/microrepl
> 
> There will be a native editor available soon that should "just work"
> (tm) - once it'd finished (that's my "Christmas holiday fun project" for
> this year...).
> 
> Documentation for the microbit API is here:
> 
> http://microbit-micropython.readthedocs.org/en/latest/
> 
> ;-)

Thanks, I had already found the micropython docs, but
nothing on how to get the board up and running.

Turns out that simply plugging in the USB connector does
the trick (life can be simple ;-)). I also learned that
powering up the device via the pins GND and 3V does not
appear to work.

On Windows, this allows accessing the flash drive and
after you install the serial driver for mbed:

https://developer.mbed.org/handbook/Windows-serial-configuration

it's also possible to access the serial console and REPL
using Tera Term:

https://www.microbit.co.uk/td/serial-library

Now, another FAQ: How can I run a Python script which I
copy to the flash drive ?

The os module doesn't appear to be available in MicroPython,
import doesn't look on the flash drive (it seems), sys.path
is not available either.

Looking at tools/pyboard.py, this sends the raw data over the wire
and your blog post suggests that Python scripts are only
automatically run when embedded into the firmware hex file:

http://ntoll.org/article/story-micropython-on-microbit

e.g. using your uflash tool.

Would it be possible to have MicroPython automatically
detect a main.py file in the flash memory and run
this when the board is reset ?

BTW: While researching into how this could be done I found
DAPLink (which handles the USB connection on the board) and
from there the nRF51822-mKIT, which appears to have *very*
similar hardware details to the microbit:

https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/
https://www.mbed.com/en/development/hardware/boards/nordic/nrf51822/

The SDK is open source (Apache), so perhaps there are some
things to learn from it. E.g. that board uses pyOCD for development,
flashing and debugging:

https://github.com/NordicSemiconductor/pyOCD

which uses Python USB/HID interfaces for connecting. Perhaps
this allows for a more reliable way of connecting to the board
than relying on mounting and finding the flash drive ?!

Here's the code they use for the interfacing:

https://github.com/NordicSemiconductor/pyOCD/tree/master/pyOCD/interface

Back to the above question: Perhaps we could ask Sam Grove
who implemented the DAPLink feature for some hints as how
to make this work ?!

https://developer.mbed.org/handbook/cmsis-dap-interface-firmware
https://ch.linkedin.com/in/samgrove


> N.
> 
> On 29/12/15 12:22, M.-A. Lemburg wrote:
>> Hello everyone,
>>
>> I received a microbit from Angus just before Christmas and
>> would like to start playing with it this week:
>>
>> http://microworldtour.github.io/microbit/monifa.html
>>
>> Unfortunately, I'm a bit lost how to start, since the information
>> about basic things like how to connect and power up the device
>> seems to be well hidden somewhere on the net ;-)
>>
>> The board has pins saying "3V" and "GND" and there's
>> a battery connector on it as well (but without indication
>> of which pin is + and which is ground (*)). Would it be enough to
>> connect a power supply to the pins or do I need to
>> find a plug for the battery connector ?
>>
>> Also: I've seen a serial console being used to drive the
>> REPL, but there don't appear to be serial con pins on the
>> device. Is the USB port used for this ? The README seems to
>> imply this ("Upon reset you will have a REPL on the USB CDC
>> serial port").
>>
>> Lastly: For flashing the device, is it possible to mount
>> the flash drive using the USB port or do I need to send the
>> image over the serial port ?
>>
>> Lots of question and I assume that most of these are FAQs :-)
>>
>> I will probably drive to an electronics shop to get some
>> cables and perhaps a battery pack today.
>>
>> (*) It may be useful to add some text to the board to
>> help kids and teachers with this.
>>
>> Thanks,


-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Dec 30 2015)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/


From mal at egenix.com  Wed Dec 30 17:34:52 2015
From: mal at egenix.com (M.-A. Lemburg)
Date: Wed, 30 Dec 2015 23:34:52 +0100
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <CAKvj0qQPPXDfUsVaBd19804aZx3zuusQHVdSS9=fGaO4HB++mQ@mail.gmail.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
 <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
 <566D3920.70700@ntoll.org>
 <CAKvj0qQPPXDfUsVaBd19804aZx3zuusQHVdSS9=fGaO4HB++mQ@mail.gmail.com>
Message-ID: <56845C0C.3060300@egenix.com>

Hi Naomi,

even though this all sounds very much like a hardware
problem, you might want to try reflashing the DAPLink
firmware which implements the serial console USB connections:

https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/

Cheers,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Dec 30 2015)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/


On 14.12.2015 00:42, Naomi Ceder wrote:
> Yep, those suggestions make sense. I particularly like the Michelle idea.
> :-)
> 
> Since Mary is functioning in all other respects I'll keep her here for
> hacking until the others safely arrive.
> 
> Cheers,
> Naomi
> 
> On 13 December 2015 at 03:23, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
> 
>> Folks,
>>
>> Poor old Mary micro:bit... my (wife) Mary is going to be heartbroken
>> that her namesake has a bad case of the collywobbles.
>>
>> Here's what I suggest:
>>
>> * We "retire" Mary - can you post her back to me and I'll make sure it
>> gets to Jonny at ARM who'll be interested in such hardware failures?
>>
>> * We "promote" one of the new boards heading in your direction to the
>> world tour. Given this is a US based series of events I propose we name
>> the new micro:bit in honour of the FLOTUS: "Michelle micro:bit". :-P
>>
>> * Naomi, can you write up how Mary got "sick" and ping me a PR for the
>> website? I'll add a note to explain the appearance of Michelle and then
>> we can let the tour continue.
>>
>> Sound like a plan?
>>
>> N.
>>
>> On 13/12/15 01:33, Naomi Ceder wrote:
>>> Hi Carol,
>>>
>>> I just tried picocom with exactly the same results - I'm still on
>>> yosemite, but getting the same behaviour on 5 terminal programs and two
>>> different OS's I'm going to say the issue is the device at this point.
>>>
>>> Cheers,
>>> Naomi
>>>
>>>
>>> On 12 December 2015 at 17:27, Carol Willing
>>> <willingc at willingconsulting.com <mailto:willingc at willingconsulting.com>>
>>> wrote:
>>>
>>>     Hi Naomi,
>>>
>>>     Perhaps a shot in the dark, did you try picocom?  picocom
>>>     /dev/ttyACM0 -b 115200  Replacing with the correct port. I've used
>>>     with the Mac Pro. I'm still running Yosemite. Are you on El Capitan?
>>>
>>>     You could try getting rid of any cruft of old USB /dev/tty files.
>>>
>>>
>>>     Damien, Does the microbit have a hard reset by pulling a GPIO pin
>> low?
>>>
>>>
>>>>     Naomi Ceder <mailto:naomi.ceder at gmail.com>
>>>>     December 11, 2015 at 7:37 PM
>>>>     Hi everyone,
>>>>
>>>>     I'm having a very weird issue with Mary the micro:bit.
>>>>
>>>>     It had been working fine... until I was about to demo before the
>>>>     Chicago Python group (ChiPy) last night.
>>>>
>>>>     Then suddenly the repl wouldn't work. That is, I could apparently
>>>>     connect, I could type commands in, the LED on the microbit would
>>>>     flash as normal, but nothing was echoed back. I could put scripts
>>>>     on the flash and the would run normally, but after trying 3
>>>>     different terminal programs (all of which had worked before),
>>>>     still no joy.
>>>>
>>>>     Tonight I've been experimenting more and I can confirm that the
>>>>     commands I'm entering do get to the microbit and are executed as
>>>>     normal. Even arrowing up and tab completion are working normally,
>>>>     but nothing gets sent back to my screen.
>>>>
>>>>     I've mainly kept the comm settings at what worked well before
>>>>     115200, N-8-1 and I might add that I've used 2 or 3 different
>>>>     versions of the firmware with the same reaction, two different USB
>>>>     cables, a lot of swearing, and I'm sort of at wit's end.
>>>>
>>>>     Has anyone else encountered this? Is there something obvious that
>>>>     I'm missing? Or something mysterious that I need to know? Or is it
>>>>     just a wonky micro:bit. I honestly didn't do a thing to it from
>>>>     when it worked fine until when it didn't, and it strikes me as a
>>>>     bit odd that it will do everything as before, EXCEPT echo the
>>>>     characters back to the terminal.
>>>>
>>>>     Halp?
>>>>
>>>>     Thanks,
>>>>     Naomi
>>>>
>>>>
>>>>     --
>>>>     Naomi Ceder
>>>>     https://plus.google.com/u/0/111396744045017339164/about
>>>>     _______________________________________________
>>>>     Microbit mailing list
>>>>     Microbit at python.org <mailto:Microbit at python.org>
>>>>     https://mail.python.org/mailman/listinfo/microbit
>>>
>>>     --
>>>     Sent from Postbox
>>>     <
>> https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
>>>
>>>
>>>     _______________________________________________
>>>     Microbit mailing list
>>>     Microbit at python.org <mailto:Microbit at python.org>
>>>     https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>>
>>>
>>> --
>>> Naomi Ceder
>>> https://plus.google.com/u/0/111396744045017339164/about
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
> 
> 

From naomi.ceder at gmail.com  Wed Dec 30 17:40:35 2015
From: naomi.ceder at gmail.com (Naomi Ceder)
Date: Wed, 30 Dec 2015 16:40:35 -0600
Subject: [Microbit-Python] Repl not echoing back
In-Reply-To: <56845C0C.3060300@egenix.com>
References: <CAKvj0qTkKg+SLWqs0LF3qGrccR8e-VkH2HhJMUcSjJpXo+3bug@mail.gmail.com>
 <566CAD5E.6000205@willingconsulting.com>
 <CAKvj0qQxQbEuU-Ov0XeGvU7Fpp-cVAn7W-prwpbo8bR=tW557g@mail.gmail.com>
 <566D3920.70700@ntoll.org>
 <CAKvj0qQPPXDfUsVaBd19804aZx3zuusQHVdSS9=fGaO4HB++mQ@mail.gmail.com>
 <56845C0C.3060300@egenix.com>
Message-ID: <CAKvj0qRX-sc2bqrAM6W--2nYF+xhNbfu+6G9E0_TJ-jTE3Vedw@mail.gmail.com>

Hi Marc,

That board (and another with some issues) is already in the hands of people
with microscopes who will be better able to figure out what's going on. But
if I still had it, I would definitely try your suggestion. For a while I
suspected physical damage to the board was the cause, but I never could
find that.

Cheers,
Naomi

On 30 December 2015 at 16:34, M.-A. Lemburg <mal at egenix.com> wrote:

> Hi Naomi,
>
> even though this all sounds very much like a hardware
> problem, you might want to try reflashing the DAPLink
> firmware which implements the serial console USB connections:
>
>
> https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/
>
> Cheers,
> --
> Marc-Andre Lemburg
> eGenix.com
>
> Professional Python Services directly from the Experts (#1, Dec 30 2015)
> >>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
> >>> Python Database Interfaces ...           http://products.egenix.com/
> >>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
> ________________________________________________________________________
>
> ::: We implement business ideas - efficiently in both time and costs :::
>
>    eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
>     D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
>            Registered at Amtsgericht Duesseldorf: HRB 46611
>                http://www.egenix.com/company/contact/
>                       http://www.malemburg.com/
>
>
> On 14.12.2015 00:42, Naomi Ceder wrote:
> > Yep, those suggestions make sense. I particularly like the Michelle idea.
> > :-)
> >
> > Since Mary is functioning in all other respects I'll keep her here for
> > hacking until the others safely arrive.
> >
> > Cheers,
> > Naomi
> >
> > On 13 December 2015 at 03:23, Nicholas H.Tollervey <ntoll at ntoll.org>
> wrote:
> >
> >> Folks,
> >>
> >> Poor old Mary micro:bit... my (wife) Mary is going to be heartbroken
> >> that her namesake has a bad case of the collywobbles.
> >>
> >> Here's what I suggest:
> >>
> >> * We "retire" Mary - can you post her back to me and I'll make sure it
> >> gets to Jonny at ARM who'll be interested in such hardware failures?
> >>
> >> * We "promote" one of the new boards heading in your direction to the
> >> world tour. Given this is a US based series of events I propose we name
> >> the new micro:bit in honour of the FLOTUS: "Michelle micro:bit". :-P
> >>
> >> * Naomi, can you write up how Mary got "sick" and ping me a PR for the
> >> website? I'll add a note to explain the appearance of Michelle and then
> >> we can let the tour continue.
> >>
> >> Sound like a plan?
> >>
> >> N.
> >>
> >> On 13/12/15 01:33, Naomi Ceder wrote:
> >>> Hi Carol,
> >>>
> >>> I just tried picocom with exactly the same results - I'm still on
> >>> yosemite, but getting the same behaviour on 5 terminal programs and two
> >>> different OS's I'm going to say the issue is the device at this point.
> >>>
> >>> Cheers,
> >>> Naomi
> >>>
> >>>
> >>> On 12 December 2015 at 17:27, Carol Willing
> >>> <willingc at willingconsulting.com <mailto:willingc at
> willingconsulting.com>>
> >>> wrote:
> >>>
> >>>     Hi Naomi,
> >>>
> >>>     Perhaps a shot in the dark, did you try picocom?  picocom
> >>>     /dev/ttyACM0 -b 115200  Replacing with the correct port. I've used
> >>>     with the Mac Pro. I'm still running Yosemite. Are you on El
> Capitan?
> >>>
> >>>     You could try getting rid of any cruft of old USB /dev/tty files.
> >>>
> >>>
> >>>     Damien, Does the microbit have a hard reset by pulling a GPIO pin
> >> low?
> >>>
> >>>
> >>>>     Naomi Ceder <mailto:naomi.ceder at gmail.com>
> >>>>     December 11, 2015 at 7:37 PM
> >>>>     Hi everyone,
> >>>>
> >>>>     I'm having a very weird issue with Mary the micro:bit.
> >>>>
> >>>>     It had been working fine... until I was about to demo before the
> >>>>     Chicago Python group (ChiPy) last night.
> >>>>
> >>>>     Then suddenly the repl wouldn't work. That is, I could apparently
> >>>>     connect, I could type commands in, the LED on the microbit would
> >>>>     flash as normal, but nothing was echoed back. I could put scripts
> >>>>     on the flash and the would run normally, but after trying 3
> >>>>     different terminal programs (all of which had worked before),
> >>>>     still no joy.
> >>>>
> >>>>     Tonight I've been experimenting more and I can confirm that the
> >>>>     commands I'm entering do get to the microbit and are executed as
> >>>>     normal. Even arrowing up and tab completion are working normally,
> >>>>     but nothing gets sent back to my screen.
> >>>>
> >>>>     I've mainly kept the comm settings at what worked well before
> >>>>     115200, N-8-1 and I might add that I've used 2 or 3 different
> >>>>     versions of the firmware with the same reaction, two different USB
> >>>>     cables, a lot of swearing, and I'm sort of at wit's end.
> >>>>
> >>>>     Has anyone else encountered this? Is there something obvious that
> >>>>     I'm missing? Or something mysterious that I need to know? Or is it
> >>>>     just a wonky micro:bit. I honestly didn't do a thing to it from
> >>>>     when it worked fine until when it didn't, and it strikes me as a
> >>>>     bit odd that it will do everything as before, EXCEPT echo the
> >>>>     characters back to the terminal.
> >>>>
> >>>>     Halp?
> >>>>
> >>>>     Thanks,
> >>>>     Naomi
> >>>>
> >>>>
> >>>>     --
> >>>>     Naomi Ceder
> >>>>     https://plus.google.com/u/0/111396744045017339164/about
> >>>>     _______________________________________________
> >>>>     Microbit mailing list
> >>>>     Microbit at python.org <mailto:Microbit at python.org>
> >>>>     https://mail.python.org/mailman/listinfo/microbit
> >>>
> >>>     --
> >>>     Sent from Postbox
> >>>     <
> >>
> https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
> >>>
> >>>
> >>>     _______________________________________________
> >>>     Microbit mailing list
> >>>     Microbit at python.org <mailto:Microbit at python.org>
> >>>     https://mail.python.org/mailman/listinfo/microbit
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Naomi Ceder
> >>> https://plus.google.com/u/0/111396744045017339164/about
> >>>
> >>>
> >>> _______________________________________________
> >>> Microbit mailing list
> >>> Microbit at python.org
> >>> https://mail.python.org/mailman/listinfo/microbit
> >>>
> >>
> >>
> >>
> >> _______________________________________________
> >> Microbit mailing list
> >> Microbit at python.org
> >> https://mail.python.org/mailman/listinfo/microbit
> >>
> >>
> >
> >
>



-- 
Naomi Ceder
https://plus.google.com/u/0/111396744045017339164/about
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/microbit/attachments/20151230/5ab75190/attachment-0001.html>