Nexus_HQ wrote:

DotDash wrote:

GreenDog3 wrote:

I think MIT should ask Nintendo if they can make Scratch for the 3DS and let you download it for free on the Nintendo eShop.

Sorry, but any DS device will not be able to handle the power of Scratch.

No, I've fiddled with my 3DS a few times and I managed to get Scratch 1.4 on it.

Can you tell me the instructions. I've had a look and can't find a Squeak VM for the 3DS. Without this, running an actual version of Scratch 1.4 would be impossible.

No. Nintendo would not allow this, even if it was optimized to allow it, because it'd hurt their profits. People would just remake their Mario games and other stuff like that in Scratch, and then the title would drop dead in the water.

bybb wrote:

Nexus_HQ wrote:

DotDash wrote:

GreenDog3 wrote:

I think MIT should ask Nintendo if they can make Scratch for the 3DS and let you download it for free on the Nintendo eShop.

Sorry, but any DS device will not be able to handle the power of Scratch.

No, I've fiddled with my 3DS a few times and I managed to get Scratch 1.4 on it.

Can you tell me the instructions. I've had a look and can't find a Squeak VM for the 3DS. Without this, running an actual version of Scratch 1.4 would be impossible.

Hmm, it's too difficult to explain at first, but i could post a Youtube video once I can solve a few problems.

braxbroscratcher wrote:

No. Nintendo would not allow this, even if it was optimized to allow it, because it'd hurt their profits. People would just remake their Mario games and other stuff like that in Scratch, and then the title would drop dead in the water.

Is there any reason why you're targeting Mario games?
(I'm a big fan of Mario, by the way)

PERCE-NEIGE wrote:

Nintendo is a commercial system, for Nintendo to accept Scratch, it must bring money to Nintendo, and learning plus-value for Scratch.

Some way it good and it not,
Some block and feature might of be limited just to make it stable and some block won't work,
Like Roblox on Xbox One, you will have limited project to try. Sure add feature project for 3DS but still won't be enough to make it a good experience.

Sorry but No support…

I am attempting to make this on github. If you know C (what we'll be programming in) then please apply at the link in my sig.

No support. You should have at least some type of device, other than a $169 3DS. And like others said, it would be nearly impossible. 3DS isn't popular, they would have to learn a new programming language, the screen would be too small, the controls wouldn't work, Nintendo wouldn't accept it (probably), the 3DS wouldn't have the power to load Scratch, and loading a project would take forever.

TheAdriCoolManDude wrote:

the 3DS wouldn't have the power to load Scratch

May I ask where everyone is getting this idea? The 3DS isn't a super under-powered device, the New 3DS has 256MB RAM, 4 cores @ 804MHz, up to 2TB storage (mSD card)

TheAdriCoolManDude wrote:

the 3DS isn't popular

I don't really think so.

TheAdriCoolManDude wrote:

they would have to learn a new programming language, the screen would be too small, the controls wouldn't work

1. No they wouldn't? Do you think that devices can only use one programming language?
2. And?
3. How?

TheAdriCoolManDude wrote:

the 3DS wouldn't have the power to load Scratch, and loading a project would take forever.

If the 3DS wouldn't be able to run Scratch then it wouldn't be able to play Mario 3D Land, Minecraft or have an internet browser which it can do all 3 things.

dude341 wrote:

TheAdriCoolManDude wrote:

the 3DS isn't popular

TheAdriCoolManDude wrote:

they would have to learn a new programming language, the screen would be too small, the controls wouldn't work

1. No they wouldn't? Do you think that devices can only use one programming language?
2. And?
3. How?

1. Yes they would, Nintendo only allow official 3DS development in C++, no electron based application would ever work due to the 64MB of RAM available to normal applications
2. The resolution is terrible, in combination with the small screen it would make it very hard to do anything in Scratch.
3. If the 3DS application was native, this wouldn't be a problem, however the 3DS browser does not allow controls to be used to control websites.

Also, the browser just can't load most websites. And TLS 1.2 isn't supported on the 3DS at all.Users would need CFW to access any site or resource loaded over TLS 1.2

bybb wrote:

1. Yes they would, Nintendo only allow official 3DS development in C++, no electron based application would ever work due to the 64MB of RAM available to normal applications
2. The resolution is terrible, in combination with the small screen it would make it very hard to do anything in Scratch.
3. If the 3DS application was native, this wouldn't be a problem, however the 3DS browser does not allow controls to be used to control websites.

1. They do? Strange… still not a limitation of the hardware though.
2. It would just have to run at 240p. The screen could scroll with the mouse pointer.
3. I don't understand, I never said anything about the 3DS browser?

Keep in mind I'm thinking of either Scratch 1.4 or a port of Scratch 3.0 that isn't HTML/Javascript based.

dude341 wrote:

bybb wrote:

1. Yes they would, Nintendo only allow official 3DS development in C++, no electron based application would ever work due to the 64MB of RAM available to normal applications
2. The resolution is terrible, in combination with the small screen it would make it very hard to do anything in Scratch.
3. If the 3DS application was native, this wouldn't be a problem, however the 3DS browser does not allow controls to be used to control websites.

1. They do? Strange… still not a limitation of the hardware though.
2. It would just have to run at 240p. The screen could scroll with the mouse pointer.
3. I don't understand, I never said anything about the 3DS browser?

Keep in mind I'm thinking of either Scratch 1.4 or a port of Scratch 3.0 that isn't HTML/Javascript based.

There are a lot of hardware limitations you'd have to work around.
For one, you'd most likely have to run the application in extended memory mode, since projects on Scratch can be up to 50MB, with normal applications only being allotted 64MB of RAM, leaving 14MB for the rest of the player / editor. Also, the 3DS' wifi is super slow, with the highest speeds I've seen being 256KBps (2Mbps) (it's rumoured overclocking using CFW can get faster speeds). The 3DS bottom screen is 320 x 240 and the top screen is 800x240 (2 x 400 x 240 in 3D mode). Text is very hard to read.

bybb wrote:

There are a lot of hardware limitations you'd have to work around.
For one, you'd most likely have to run the application in extended memory mode{…}

In homebrew (I think, correct me if I've confused data), it runs in extended memory (EM) mode if the game you run it from is an EM game. With Luma3ds, all you do is run it from an EM game via rosalina. For non-CFW consoles, exploits like mhxxhax could be used (though CFW costs up to… $2 these days).

bybb wrote:

Also, the 3DS' wifi is super slow, with the highest speeds I've seen being 256kbps (2mbps){…}

I've used FTP clients and had speeds of ~300kbps (no overclocking). Whether this is to do with homebrew or not, I don't know, but even so, a homebrew app would be faster than 256kbps. Wait, hang on why do we even need internet?

bybb wrote:

The 3DS bottom screen is 330 x 240 and the top screen is 800x240 (2 x 400 x 240 in 3D mode). Text is very hard to read.

There is so much I could say about this point. First, 320 x 240 is fine for…well…everything you do on your 3DS. If it is too much of a problem, you wouldn't play on it, and if you didn't play on it, you wouldn't be affected either way. Same for the top screen. Also, if text were hard to read, I wouldn't be able to exactly quote you WITHOUT using the quote button.

I'd also like to say that this is the person who said they'd test scratch3ds (see sig) when it got to a testable state. Thanks for your encouragement.

Shaymin524 wrote:

-snip-

This is mainly because AFAIK official 3DS development through Nintendo is much less user friendly than homebrew development. Since the Scratch Team would have to do it officially, they'd have to have a full dev team working on it rather than a few dedicated developers.

bybb wrote:

Shaymin524 wrote:

-snip-

This is mainly because AFAK official 3DS development through Nintendo is much less user friendly than homebrew development. Since the Scratch Team would have to do it officially, they'd have to have a full dev team working on it rather than a few dedicated developers.

Sorry, what's the problem here? All you've said is that homebrew is easier than official development, and that the Scratch Team would have to do it with all of their devs, which they don't, twice.

Also, I 3DS-quoted you without the quote button again.

Shaymin524 wrote:

bybb wrote:

Shaymin524 wrote:

-snip-

This is mainly because AFAK official 3DS development through Nintendo is much less user friendly than homebrew development. Since the Scratch Team would have to do it officially, they'd have to have a full dev team working on it rather than a few dedicated developers.

Sorry, what's the problem here? All you've said is that homebrew is easier than official development, and that the Scratch Team would have to do it with all of their devs, which they don't, twice.

Also, I 3DS-quoted you without the quote button again.

Because homebrew is a legal grey-area and would not be supported by the Scratch Team. If they make Scratch for the 3DS, it would be through Nintendo's official developer portal

bybb wrote:

Shaymin524 wrote:

bybb wrote:

Shaymin524 wrote:

-snip-

This is mainly because AFAK official 3DS development through Nintendo is much less user friendly than homebrew development. Since the Scratch Team would have to do it officially, they'd have to have a full dev team working on it rather than a few dedicated developers.

Sorry, what's the problem here? All you've said is that homebrew is easier than official development, and that the Scratch Team would have to do it with all of their devs, which they don't, twice.

Also, I 3DS-quoted you without the quote button again.

Because homebrew is a legal grey-area and would not be supported by the Scratch Team. If they make Scratch for the 3DS, it would be through Nintendo's official developer portal

Both Homebrew and CFW ARE legal in many countries and there is no reason why it has to be the Scratch Team. Even if it were the ST, you don't know that they wouldn't accept using homebrew. If you want, I'll ask @paddle2see.

Shaymin524 wrote:

bybb wrote:

Shaymin524 wrote:

-snip-

-snip-

Because homebrew is a legal grey-area and would not be supported by the Scratch Team. If they make Scratch for the 3DS, it would be through Nintendo's official developer portal

Both Homebrew and CFW ARE legal in many countries and there is no reason why it has to be the Scratch Team. Even if it were the ST, you don't know that they wouldn't accept using homebrew. If you want, I'll ask @paddle2see.

Paddle2see doesn't know what homebrew is, and hasn't replied to the post explaining what it is.

No support, my 3DS XL cannot even handle online Super Smash Bros. battles, so I do not believe this will work. Even my computer (specs listed in my signature) lags sometimes on Scratch.

finnb4513 wrote:

No support, my 3DS XL cannot even handle online Super Smash Bros. battles, so I do not believe this will work. Even my computer (specs listed in my signature) lags sometimes on Scratch.

1) It doesn't have to be online at all.
2) Using Firefox and Windows 10 myself, I can say that with my 8 GB of memory and 2 GHz of CPU (which is slightly above average, if not normal) Scratch only lags if I have a memory/graphics intensive game open in the background. Scratch 3.0 will use less CPU / GPU / Memory.