MinecraftM153 wrote:

-MASSIVE SNIP-

Okay, let's get back on topic.

MrMeowington wrote:

MinecraftM153 wrote:

-MASSIVE SNIP-

Okay, let's get back on topic.

Yes, let's.

I did the math, and there are only ~3 weeks left before Scratch 3.0 comes out (unless something's changed).

There's not much development time left before it's released officially.

DoatRedding wrote:

So, I know Scratch 3.0 works for Lego Mindstorms EV3, But does it also work for Mindstorms' older version, the NXT?

MabonBaladevaKain wrote:

Will we be able to save our Scratch project files as .apk files and sign them easily to make apps for Google Play and/or other app stores?

Please say yes. It is the only feature that really needs to be added. The rest are not important.

If not then I will have to spend most of my time on something other than Scratch or find some way to turn Scratch projects into .apk
and I have no clue how to do that at all. Most likely I will end up having to learn an entirely different interface and/or text syntax of
some other game creation tool and/or coding language that I don't have time to spend upon. Everything that I have found so far that
codes directly to .apk has way more cumbersome of interfaces compared to Scratch or needs several large bloatware programs to
be installed before they are capable of converting code to .apk and that does not even guarantee that it will work correctly.

It needs to be a standalone native .apk because I tried turning Scratch projects into hybrid apps and that did not work out so well.
The game would not always work and it required the internet while playing the game and it took way too long loading if it did work.
And that was for a really simple little game that just moved a spotlight around the screen. So it has to be native android .apk.

MabonBaladevaKain wrote:

Will we be able to save our Scratch project files as .apk files and sign them easily to make apps for Google Play and/or other app stores?

Please say yes. It is the only feature that really needs to be added. The rest are not important.

If not then I will have to spend most of my time on something other than Scratch or find some way to turn Scratch projects into .apk
and I have no clue how to do that at all. Most likely I will end up having to learn an entirely different interface and/or text syntax of
some other game creation tool and/or coding language that I don't have time to spend upon. Everything that I have found so far that
codes directly to .apk has way more cumbersome of interfaces compared to Scratch or needs several large bloatware programs to
be installed before they are capable of converting code to .apk and that does not even guarantee that it will work correctly.

It needs to be a standalone native .apk because I tried turning Scratch projects into hybrid apps and that did not work out so well.
The game would not always work and it required the internet while playing the game and it took way too long loading if it did work.
And that was for a really simple little game that just moved a spotlight around the screen. So it has to be native android .apk.

MabonBaladevaKain wrote:

Turning Scratch into an app is NOT what I am asking.
I simply want to know if I will be able to save my work in Scratch 3.0 (the code I create with it) as a standalone android file.

I'm certain that it can be done. I just don't know how to do it. Even full websites can be played offline without the internet,
so why would a project + the player to play it be any different? … Surely it is not that difficult of a thing to do for the people
at MIT who are in charge of having created Scratch.

Btw, If you just want to make things with Scratch on your mobile device, they already have that.
It's called Scratch Xbot and you can get it for free off the Google Play store, but I reiterate that this is NOT what I am asking.
I want to create a project on Scratch 3.0, save the project file along with just the player to play it (no editor) as a .apk file that can
be signed to allow for possible sale on app stores such as Google Play.

I want to use Scratch 3.0 as a launching platform to create apps until I learn how to code something like Java.

Even if it had a Java code option in Scratch 3.0 where it shows what the Scratch blocks would be in Java code would be useful,
because even though I would still need to download lots of things, at least I could have a starting point by copy/pasting the code
over into a normal programming interface like Android Studio and then perform whatever tweaks are needed there.

I have heard that it is notoriously slow to test programs for Android and Scratch would be a great prototyping tool if it had at least
one of these features. Surely you can see the benefit of having Scratch projects associated with a real coding language.
It would then be powerful enough to help those who want to program learn how to code in a real accredited programming language.

0037318 wrote:

Websites are viewed offline using html files, which is a collection of html and javascript. The nature of scratch conflicts with the nature of java. In scratch, variables do not have types. You can set it to anything. If you try to do an operation on a string, a default number will be returned. In Java, all values would have to be stored as a string, and if you wanted to do an operation on something, it would create an unexpected result because you are doing operations on a string, and not an integer. If you stored all values as an integer, you would not be able to store strings into the variables. Many scratch projects rely on the ability to use strings AND numbers synonymously, and Java simply can't do that. If you want to use scratch to build an android app, I would recommend using app inventor at http://ai2.appinventor.mit.edu/ which allows you to code apps using blocks and then test them through their app.

infinitytec wrote:

Let's get back on topic OK?

MabonBaladevaKain wrote:

Will we be able to save our Scratch project files as .apk files and sign them easily to make apps for Google Play and/or other app stores?

Please say yes. It is the only feature that really needs to be added. The rest are not important.

I want to create a project on Scratch 3.0, save the project file along with just the player to play it (no editor) as a .apk file that can
be signed to allow for possible sale on app stores such as Google Play.

Even if it had a Java code option in Scratch 3.0 where it shows what the Scratch blocks would be in Java code would be useful […]

Oh, and I am also wondering, when Scratch 2.0 becomes Scratch 3.0, will the Instructions and the Notes and Credits for our games
be transferred over to Scratch 3.0 or do we need to copy them to a text file in order to keep them?

Well does anyone know of a Scratch to Java converter that will take the .sb2 file and display it in Java? … Even if it left the variables as text equivalents of the block versions, at least then I could go back through and edit those to be of the Java syntax.

Scratch needs a way to teach actual programming anyway or else it really is just a toy after all. Right now there is no real correlation other than it being a form of logic to build something with, but so are Lego blocks and those too are just toys.

MabonBaladevaKain wrote:

infinitytec wrote:

Let's get back on topic OK?

Everything I have mentioned is relevant and related to Scratch 3.0 technical discussion. I have never left topic.
None of you have answered even a single question other than to antagonize and troll me.
Just because my wording happens to be a little long, that does not make it any less relevant.

Can you at least then please tell me, Once they move the Scratch 2.0 projects to Scratch 3.0, will all of
the projects' Descriptions / Notes and Credits be copied over too? Or do we have to save all that stuff ourselves
if we wish to keep them? ….

_nix wrote:

MabonBaladevaKain wrote:

Will we be able to save our Scratch project files as .apk files and sign them easily to make apps for Google Play and/or other app stores?

Please say yes. It is the only feature that really needs to be added. The rest are not important.

This isn't a feature the Scratch Team is working on, as far as I know (and I more or less keep track of pretty much all their open source repositories and public discussion). While maybe it's not out of scope of Scratch 3.0 as a programming tool, it makes sense that the Scratch Team seems not to have prioritized the idea at all – their target audience is people who are learning programming, not developing and publishing/selling apps. While there are people like you who want to be able to release projects as easily-distributed binaries (APKs, EXEs, you name it), that just isn't everyone.

I can't recall if the ST has said anything about SB3 -> EXE. They may have said they're considering it (but do not quote me on that), but I doubt it's something they'd be working on right now, seeing as there's so much else they had to finish before release and there hasn't been any mention of converting Scratch projects to EXEs inside 3.0 FAQ, official ST announcements, etc. (I'm saying -> exe instead of exe/apk because I just cannot remember APK files / android export having been mentioned anywhere before your posts here.)

MabonBaladevaKain wrote:

Will Scratch 3.0 have a text editor that displays the code that the puzzle blocks already create?

MabonBaladevaKain wrote:

Thank you _nix. That answered all my questions fairly well. …] I just meant…

MabonBaladevaKain wrote:

Now for precision of being on-topic's sake and my sheer curiosity, I ask one last question:
Will Scratch 3.0 have a text editor that displays the code that the puzzle blocks already create?

{
  op: "when green flag clicked",
  children: [
    {op: "move steps", inputs: [10]},
    {
      op: "if then", inputs: [
        {op: "=", inputs: [{op: "days since 2000"}, 10000]}}
      ], children: [
        {op: "play sound", inputs: ["Bing!"]}
      ]
    }
  ]
}