I think that Scratch should implement support for the raspberry pi pico, as it would increase accessibility as it is already cheap to buy so making it easier to code would make it even better.

If you're talking about using Scratch to code a Raspberry Pi Pico, then I support. This would make it easier to code a Raspberry Pi Pico and will allow kids who only know Scratch and not any other programming language to make a whole range of cool projects.

Just to verify, are you talking about that?

yes, Yes I am .
Glad you share my opinion.

what would this add?

cookieclickerer33 wrote:

what would this add?

The ability to use Scratch to code a Raspbery Pi Pico.

bump

cookieclickerer33 wrote:

what would this add?

It would add blocks in that you could use to control and read the gpio pins

I suggest that they allow all the capabilities to be used (such as SPI, I2C & etc). That would really give Scratch power.

o97doge wrote:

I suggest that they allow all the capabilities to be used (such as SPI, I2C & etc). That would really give Scratch power.

I think the point of Srcath is to be easy for beginners to use, if they somehow got a Pico for their class/present (etc.) then it might be somehow confusing.

Though not many people use physical extensions because it might be a bit fiddly to use them,

TL;DR This might be somewhat awesome to people who are experienced with external devices but not for 8 year olds.

Edit: they didn't add I2C with the micro:bit on Srcath.

The Raspberry Pi Pico is an unusual case… It isn't powerful enough to run Scratch itself, but it is far more powerful than anything that can be programmed with Scratch or Scratch derivatives, including the EV3, Arduino, Micro:bit, and MakeBot. This means that the Pico is far beyond the normal limits of what Scratch is capable of.

However, if the awkwardness of this can be worked around, I think this would be a really cool suggestion to implement.

bump and support. i have a pi pico, and this would open up insane new opportunities for having custom keyboard inputs, i2c displays and controllers, and even potentially using a jtag to debug a scratch project (altho thats a bit unlikely tbf, but would be insanely cool). i can think of so many ways this can be innovatively, since (barring the prexisting pi extension, which you cannot share any projects made with it) there's no real gpio that scratch can use. the only ones that somewhat work are makey-makey, which limits you to simple buttons instead of keys, and microbit, which has only 3 inputs. plus, neither of those have any outputs, so they really can't beat the pico.

BIPES supports the Pico using Block programming (similar to Scratch). It may not be exactly what you are looking for since it is centered around physical computing, but could be a step in the right direction. Take a look at https://bipes.net.br/pico/ui/ Make sure to select the Raspberry Pi Pico (or any of the RP2040 boards). Additionally, CoderDojoTC has several labs centered around using BIPES and various components. https://www.coderdojotc.org/bipes/

Since I'm always looking for more things to add to BIPES, please feel free to offer suggestions.

Thanks,

should scratch have its own, headless, pico fork? remember that the pico is a rudimentary and low power (both of which i refer to as “by scratch's standards”) device

Banana

bump

This would be awesome. If they implemented some of the tools in the Raspberry Pi OS version of Scratch such as control of GPIO, it would give a lot more control to Scratch. Also, the ability to connect via SPI or I2C to a display would be nice. Support for potentiometers could be convenient, and separate threads would be extremely powerful, since the pico can run scripts much faster that the 30fps limit of Scratch. This would allow for physical computing projects and high speed calculations, especially with the new pico 2 and pico 2W. I'm surprised that GarboMuffin hasn't added this to Turbowarp.

Why not just learn python???????

Da_BFBM_show wrote:

Why not just learn python???????

I agree, but a Pico can still do faster computations per second than Scratch on it's own, so it could be used as a graphics card.

MatthiasMouse99 wrote:

Da_BFBM_show wrote:

Why not just learn python???????

I agree, but a Pico can still do faster computations per second than Scratch on it's own, so it could be used as a graphics card.

Ummm, no it can't? The pico is literally the slowest of the pis

Da_BFBM_show wrote:

Why not just learn python???????

Yeah, why do bike practice wheels exist? Just learn how to drive a rocket?

scratchcode1_2_3 wrote:

(#18)

MatthiasMouse99 wrote:

Da_BFBM_show wrote:

Why not just learn python???????

I agree, but a Pico can still do faster computations per second than Scratch on it's own, so it could be used as a graphics card.

Ummm, no it can't? The pico is literally the slowest of the pis

But that doesn't mean it isn't faster than Scratch lol Scratch is slow as hecc

kkidslogin wrote:

(#19)

scratchcode1_2_3 wrote:

(#18)

MatthiasMouse99 wrote:

Da_BFBM_show wrote:

Why not just learn python???????

I agree, but a Pico can still do faster computations per second than Scratch on it's own, so it could be used as a graphics card.

Ummm, no it can't? The pico is literally the slowest of the pis

But that doesn't mean it isn't faster than Scratch lol Scratch is slow as hecc

Scratch is actually really fast on my end. It depends more on hardware. If you run Scratch on a potato blackberry, it is garbage. If you run it on a nasa super computer, it's blazingly fast. A pico isn't powerful enough to run scratch itself. The clockspeed is the exact same as that of a Nintendo DSi. It's a great console, it unfortunately has terrible graphics if you compare it to modern day things. (that doesn't mean it's bad I've been playing it since 3 yrs old)