Holder_Of_Life wrote:

StorageOS wrote:

!! Another Big Update !!

Starting with StorageOS v1.23.6, along with the new API is the change of variables. OS variables (volume, saved files, etc.) are stored in list-memory, rather than actual variables. OS-dependent variables (app variables, clone IDs, etc.) will use variables though.

Any questions or concerns, go to @StorageOS's profile and ask there.

Thank you, any sorry for any inconveniences.

EDIT: Update on the API: If there was some sort of error (bad input, etc.), the result is “Error”, or if StorageOS senses the API trying to hurt the OS in some way (make it crash, etc.), it will return “Fatal Error” and will produce an error screen.

I assume now impact on designers?

StorageOS wrote:

Holder_Of_Life wrote:

StorageOS wrote:

!! Another Big Update !!

Starting with StorageOS v1.23.6, along with the new API is the change of variables. OS variables (volume, saved files, etc.) are stored in list-memory, rather than actual variables. OS-dependent variables (app variables, clone IDs, etc.) will use variables though.

Any questions or concerns, go to @StorageOS's profile and ask there.

Thank you, any sorry for any inconveniences.

EDIT: Update on the API: If there was some sort of error (bad input, etc.), the result is “Error”, or if StorageOS senses the API trying to hurt the OS in some way (make it crash, etc.), it will return “Fatal Error” and will produce an error screen.

I assume now impact on designers?

Again, not hugely.

CyberOverload wrote:

StorageOS wrote:

!! Another Big Update !!

Starting with StorageOS v1.23.6, along with the new API is the change of variables. OS variables (volume, saved files, etc.) are stored in list-memory, rather than actual variables. OS-dependent variables (app variables, clone IDs, etc.) will use variables though.

Any questions or concerns, go to @StorageOS's profile and ask there.

Thank you, any sorry for any inconveniences.

EDIT: Update on the API: If there was some sort of error (bad input, etc.), the result is “Error”, or if StorageOS senses the API trying to hurt the OS in some way (make it crash, etc.), it will return “Fatal Error” and will produce an error screen.

Genius. Would have never thought of using lists as variables. Maybe I should start doing that. (In other projects)

Thanks. I got the idea from someone (I forget who it was though), and thought it would be a good idea to do that to save storage space and make the code clearer.

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

MRVR_studios wrote:

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

Wait until someone decides to use the Python script for importing and exporting data to create an assistant that runs off ChatGPT

MRVR_studios wrote:

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

Wait until someone decides to use the Python script for importing and exporting data to create an assistant that runs off ChatGPT

Warrobot10 wrote:

Username / nickname: Warrobot10
Job: Head tester or tester.
Have you read and agree to the rules stated? Yes!
Activity: 7/10
Experience: 8/10
Why do you want this job? I have all ways wanted to to help out on a OS, and I think I can gain more experience helping here!
How will you help? I will test out new features and give feedback!
Other: n/a

Warrobot10 wrote:

Thanks!

hxckerdoge wrote:

MRVR_studios wrote:

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

Wait until someone decides to use the Python script for importing and exporting data to create an assistant that runs off ChatGPT

ChatGPT can be really risky because you can ask for it anything and some things could be inappropriate

CyberOverload wrote:

hxckerdoge wrote:

MRVR_studios wrote:

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

Wait until someone decides to use the Python script for importing and exporting data to create an assistant that runs off ChatGPT

ChatGPT can be really risky because you can ask for it anything and some things could be inappropriate

I think Scratch bans A.i generated projects and profiles run by A.i.

MyScratchedAccount wrote:

Username / nickname: MyScratchedaccount
Job: co owner and coder
Have you read and agree to the rules stated? yes
Activity: x/10: 7
Experience: x/10: 10
Why do you want this job? I like coding
How will you help? I will help be a co owner and make code
Other: I AM REAPPLYING BECUASE I WAS HAVING A WIKI EDITING BREAK AND I FERGOT TO TELL

cs2722201 wrote:

Username / nickname: cs2722201
Job: coder and tester
Have you read and agree to the rules stated? yes
Activity: x/10 5
Experience: x/10 5
Why do you want this job? I wanted to help make a os for a long time.
How will you help? by coding and testing
Other:

YC72909 wrote:

MyScratchedAccount wrote:

Username / nickname: MyScratchedaccount
Job: co owner and coder
Have you read and agree to the rules stated? yes
Activity: x/10: 7
Experience: x/10: 10
Why do you want this job? I like coding
How will you help? I will help be a co owner and make code
Other: I AM REAPPLYING BECUASE I WAS HAVING A WIKI EDITING BREAK AND I FERGOT TO TELL

Sorry, we already have a new co-owner and head coder, it's not under my authority to accept/decline you. I'll ask the owner.

YC72909,
co-owner, head coder

MRVR_studios wrote:

TheTeacherOfLogos wrote:

StorageOS wrote:

Quick update:
StorageOS will include its own programming language, so you will be able to use that to make API calls as well. More updates on that later. Also, the introduction of the API for apps will be changed starting with StorageOS v1.23.6. The studio can be found here.

An entire language, api integrations, off-platform development? I feel like this is getting to the point where we run into the limitations of scratch.

Wait until someone decides to use the Python script for importing and exporting data to create an assistant that runs off ChatGPT