bump

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Good idea. This could work because since Nintendo already has something like it (Labo) this isn't too far fetched!

Bump

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Good idea. This could work because since Nintendo already has something like it (Labo) this isn't too far fetched!

I think Scratch should have people download it via the Eshop

How the UI on it works: It looks like the scratch's UI

App name: Scratch Web App Viewer

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Good idea. This could work because since Nintendo already has something like it (Labo) this isn't too far fetched!

I think Scratch should have people download it via the Eshop

How the UI on it works: It looks like the scratch's UI

App name: Scratch Web App Viewer

Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Good idea. This could work because since Nintendo already has something like it (Labo) this isn't too far fetched!

I think Scratch should have people download it via the Eshop

How the UI on it works: It looks like the scratch's UI

App name: Scratch Web App Viewer

Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

How would that work? Nintendo wouldn't accept a educational programming app

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Good idea. This could work because since Nintendo already has something like it (Labo) this isn't too far fetched!

I think Scratch should have people download it via the Eshop

How the UI on it works: It looks like the scratch's UI

App name: Scratch Web App Viewer

Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

How would that work? Nintendo wouldn't accept a educational programming app

yes, they would(ahem labo ahem)

myeducate wrote:

GamesGuyTV wrote:

jmonster5 wrote:

~snip~
Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

How would that work? Nintendo wouldn't accept a educational programming app

yes, they would(ahem labo ahem)

Um, I’m pettty sure that labo was made by Nintendo, so why wouldn’t they accept their own application? In terms of of Scratch, would they accept an external educational programming app?

ACE009 wrote:

myeducate wrote:

GamesGuyTV wrote:

~snip~
Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

How would that work? Nintendo wouldn't accept a educational programming app

yes, they would(ahem labo ahem)

Um, I’m pettty sure that labo was made by Nintendo, so why wouldn’t they accept their own application? In terms of of Scratch, would they accept an external educational programming app?

I'm not sure

myeducate wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Good idea. This could work because since Nintendo already has something like it (Labo) this isn't too far fetched!

I think Scratch should have people download it via the Eshop

How the UI on it works: It looks like the scratch's UI

App name: Scratch Web App Viewer

Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

How would that work? Nintendo wouldn't accept a educational programming app

yes, they would(ahem labo ahem)

Oh ok lets make that able to view and make projects

Nintendo Switch joy-cons can work on PC-Macs. (They are Bluetooth)

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Can you also add Wii remote support? I mean by it doesn’t support Wii but it supports Wii remotes

GamesGuyTV wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Can you also add Wii remote support? I mean by it doesn’t support Wii but it supports Wii remotes

Probably not, as the Wiimote isn't treated as a regular gamepad, because it doesn't use the standard gamepad API stuff. It could be technically done but it would be kind of unnecessary and a waste of time. It would be kinda cool though.

GamesGuyTV wrote:

ACE009 wrote:

myeducate wrote:

GamesGuyTV wrote:

~snip~
Without the web browser, the Eshop is the only distribution option on the Switch. It would probably be just called Scratch, as just making the application for the Switch just for existing projects would be kind of wasteful. If it were to be released as an native application, it should be able to make projects too!

How would that work? Nintendo wouldn't accept a educational programming app

yes, they would(ahem labo ahem)

Um, I’m pettty sure that labo was made by Nintendo, so why wouldn’t they accept their own application? In terms of of Scratch, would they accept an external educational programming app?

I'm not sure
Honestly I'm not sure if it would be allowed even though Nintendo did something similar themselves. Anyway the idea for actually making an app for a console has kinda been rejected before but now it's a little easier. It is pretty unlikely that they would actually try to get an app considering Nintendo's strict security policy, but it's possible!

jmonster5 wrote:

GamesGuyTV wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

jmonster5 wrote:

GamesGuyTV wrote:

Bump

Alright fine, with you bumping this (thanks for your support) I guess I will start actually discussing controller support. Let's start off with buttons. The buttons on a controller should be easy to implement except that button shapes and layouts can differ between manufactures. For example, the Xbox controller has the letters A, B, X and Y going in a counter-clockwise order, while Nintendo's Joy-Cons have A and B switched, and Sony's DualShock controllers don't even have letters, they have shapes! This complicates putting this in blocks, but one way they could kind of solve this is to put both letters and shapes on one block for each key, then adding a block that says what type of controller the user has plugged in, so for example the Scratch project can show the right controls in the menu. The next problem is the analog thumbsticks. For those who don't know, the thumbsticks on a controller actually report their position data which can make movement more precise, but it overcomplicates things for beginners. To solve this problem, there should be two blocks. One that just does basic up, down, right and left, and one that does the more precise analog position data for advanced users. The same things goes for the triggers on the top of the controller, which are also analog. One for basic pressed or not pressed, and one for advanced analog data. The D-Pad and shoulder buttons on the controller should be really easy, but then you get to the three buttons left, which are for the Xbox One for example Xbox, Menu, and Guide I think. These three buttons vary widely between consoles and manufactures, so they might just be renamed to generic ones like Home, Back, and Start.
If you made it this far, then congratulations! This should show how hard it is to pull off adding controller support, but since I mentioned fixes to each problem, it should be possible. I really hope this gets read by a Scratch Team member because it might be useful for them to already have some problems and their solutions already solved.

Actually, Nintendo Switch doesn t have a browser yet!!! So how would it work if we were also going to do for the Switch

We would just have to wait for Nintendo for add a browser to the Switch. Since there is ways to unofficially get a browser running on the switch, and besides you can use the joy cons on computer and Android we should at least have support for Joy Cons, but it should be easy to add anyway.

Maybe Scratch can make a app for the Switch to let you run those things?

Can you also add Wii remote support? I mean by it doesn’t support Wii but it supports Wii remotes

Probably not, as the Wiimote isn't treated as a regular gamepad, because it doesn't use the standard gamepad API stuff. It could be technically done but it would be kind of unnecessary and a waste of time. It would be kinda cool though.

Well Wii remotes could be used in driving and sports games like in Wii Sports and Mario Kart Wii

Bring up his thread

Bump

the problem with this is that scratch projects have a fixed aspect ratio (4:3 i think, which they probably won't change in 3.0). trying to interact with an application in a 4:3 aspect ratio on your 1:2 phone won't work very well. also interface design usually has to be tailored to individual platforms - you would want to design a desktop app, a mobile app, and a console app very differently because people interact with them differently. i don't think a one-size-fits-all solution would work here.

otoh scratch will most likely have an embeddable player so that you can embed your projects in any html web page - just like it has now.

xn--cr8h wrote:

the problem with this is that scratch projects have a fixed aspect ratio (4:3 i think, which they probably won't change in 3.0). trying to interact with an application in a 4:3 aspect ratio on your 1:2 phone won't work very well. also interface design usually has to be tailored to individual platforms - you would want to design a desktop app, a mobile app, and a console app very differently because people interact with them differently. i don't think a one-size-fits-all solution would work here.

otoh scratch will most likely have an embeddable player so that you can embed your projects in any html web page - just like it has now.

I have already seen some of the issues with 4:3 in my testing on mobile! They did say at the start of the 3.0 project that they would consider moving to 16:9 but considering how far we already are it probably won't happen with the initial release at least, as you already mentioned. I also get your concerns about UI scaling between devices, so in that case I would have a block that detects what kind of device it is running on.

Bring up his post