Bump

Bump

chexbox wrote:

Chrome Apps, too?

Yes, but Google is discontinuing Chrome apps. You can still browse to the site though.

jmonster5 wrote:

chexbox wrote:

Chrome Apps, too?

Yes, but Google is discontinuing Chrome apps. You can still browse to the site though.

Woah I didn't know

jmonster5 wrote:

chexbox wrote:

Chrome Apps, too?

Yes, but Google is discontinuing Chrome apps. You can still browse to the site though.

I think he means Chrome Apps for Chrome OS which aren't being killed off.

Support, that's sad that you can't really make your own games on consoles because they are always protected and they hate games that you did not give any money to it

LLDeluxe wrote:

Support, that's sad that you can't really make your own games on consoles because they are always protected and they hate games that you did not give any money to it

Please stop using the
“Support, that's sad that X…” - It's what you said on my post.

Bump

Bump

Bump

Support. This could be cool to see

Bump

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.

myeducate wrote:

jmonster5 wrote:

chexbox wrote:

Chrome Apps, too?

Yes, but Google is discontinuing Chrome apps. You can still browse to the site though.

I think he means Chrome Apps for Chrome OS which aren't being killed off.

Oh cool, I didn't realize that it wouldn't affect Chrome OS. Looked it up and it makes sense anyway.

Bump

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

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.

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?

Bump

Bump