YC72909 wrote:

StorageOS wrote:

-snip-

btw there is no last item of list anymore so:

(item (length of (list :: list)) of [list v] :: list)

StorageOS wrote:

YC72909 wrote:

StorageOS wrote:

-snip-

btw there is no last item of list anymore so:

(item (length of (list :: list)) of [list v] :: list)

Holder_Of_Life wrote:

YC72909 wrote:

StorageOS wrote:

!! API Documentation !!

API messages (broadcasts) can be sent for each of these:

broadcast [os.home v] // return to home screen
broadcast [app.open.* v] // open the specified app
broadcast [app.camera v] // access the camera app
broadcast [os.name v] // access the username of the signed-in user (e.x. (username))
broadcast [os.uname v] // access the OS username
broadcast [os.version v] // OS version as semicolon-separated string

and will be received in the ‘API RESULT’ list.

Example:

when I receive [app.open.pen v] // when opening the pen app
broadcast [os.uname v] and wait // get OS username
set [username v] to (item [last] of [API RESULT v]) // new results get appended to the end, get the newest result
forever
  say (join [Hello, ] (join (username::variable) [!]))
  if <mouse down> then
    pen down
  else
    pen up
  end
  go to [mouse pointer v]
  if <key [space v] pressed> then
    broadcast [os.home v]
    stop [this script v]
  end
end

btw there is no last item of list anymore so:

(item (length of (list :: list)) of [list v] :: list)[/quote]

I so confused

lol ya gotta know coding…

YC72909 wrote:

Holder_Of_Life wrote:

YC72909 wrote:

StorageOS wrote:

!! API Documentation !!

API messages (broadcasts) can be sent for each of these:

broadcast [os.home v] // return to home screen
broadcast [app.open.* v] // open the specified app
broadcast [app.camera v] // access the camera app
broadcast [os.name v] // access the username of the signed-in user (e.x. (username))
broadcast [os.uname v] // access the OS username
broadcast [os.version v] // OS version as semicolon-separated string

and will be received in the ‘API RESULT’ list.

Example:

when I receive [app.open.pen v] // when opening the pen app
broadcast [os.uname v] and wait // get OS username
set [username v] to (item [last] of [API RESULT v]) // new results get appended to the end, get the newest result
forever
  say (join [Hello, ] (join (username::variable) [!]))
  if <mouse down> then
    pen down
  else
    pen up
  end
  go to [mouse pointer v]
  if <key [space v] pressed> then
    broadcast [os.home v]
    stop [this script v]
  end
end

btw there is no last item of list anymore so:

(item (length of (list :: list)) of [list v] :: list)[/quote]

I so confused

lol ya gotta know coding…

Ik I am just don't think we'll when I see that NY brain starts spinning around in a hundred directions

YC72909 wrote:

Holder_Of_Life wrote:

YC72909 wrote:

StorageOS wrote:

!! API Documentation !!

API messages (broadcasts) can be sent for each of these:

broadcast [os.home v] // return to home screen
broadcast [app.open.* v] // open the specified app
broadcast [app.camera v] // access the camera app
broadcast [os.name v] // access the username of the signed-in user (e.x. (username))
broadcast [os.uname v] // access the OS username
broadcast [os.version v] // OS version as semicolon-separated string

and will be received in the ‘API RESULT’ list.

Example:

when I receive [app.open.pen v] // when opening the pen app
broadcast [os.uname v] and wait // get OS username
set [username v] to (item [last] of [API RESULT v]) // new results get appended to the end, get the newest result
forever
  say (join [Hello, ] (join (username::variable) [!]))
  if <mouse down> then
    pen down
  else
    pen up
  end
  go to [mouse pointer v]
  if <key [space v] pressed> then
    broadcast [os.home v]
    stop [this script v]
  end
end

btw there is no last item of list anymore so:

(item (length of (list :: list)) of [list v] :: list)[/quote]

I so confused

lol ya gotta know coding…

Ik I am just don't think we'll when I see that NY brain starts spinning around in a hundred directions

banana3333333333 wrote:

Username / nickname: banana3333333333/snowie
Job: Co-owner
Have you read and agree to the rules stated? Yes
Activity: 5/10
Experience: 9/10

I love making OSes. Operating systems have always fascinated me. I also have some pretty good leadership schools, and coding skills. Since I was 5, and first on Scratch, I've been coding a lot.

I will help by managing the project, and helping out with the hard parts while coding.

Other: I'm pretty good at vector art, graphic design, and music creation.

banana3333333333 wrote:

Username / nickname: banana3333333333/snowie
Job: Co-owner
Have you read and agree to the rules stated? Yes
Activity: 5/10
Experience: 9/10

I love making OSes. Operating systems have always fascinated me. I also have some pretty good leadership schools, and coding skills. Since I was 5, and first on Scratch, I've been coding a lot.

I will help by managing the project, and helping out with the hard parts while coding.

Other: I'm pretty good at vector art, graphic design, and music creation.

YC72909 wrote:

banana3333333333 wrote:

Username / nickname: banana3333333333/snowie
Job: Co-owner
Have you read and agree to the rules stated? Yes
Activity: 5/10
Experience: 9/10

I love making OSes. Operating systems have always fascinated me. I also have some pretty good leadership schools, and coding skills. Since I was 5, and first on Scratch, I've been coding a lot.

I will help by managing the project, and helping out with the hard parts while coding.

Other: I'm pretty good at vector art, graphic design, and music creation.

Hello, the front page just hasn't been updated, but I'm the co-owner. Would you like another job position in this OS collaboration?

banana3333333333 wrote:

YC72909 wrote:

banana3333333333 wrote:

Username / nickname: banana3333333333/snowie
Job: Co-owner
Have you read and agree to the rules stated? Yes
Activity: 5/10
Experience: 9/10

I love making OSes. Operating systems have always fascinated me. I also have some pretty good leadership schools, and coding skills. Since I was 5, and first on Scratch, I've been coding a lot.

I will help by managing the project, and helping out with the hard parts while coding.

Other: I'm pretty good at vector art, graphic design, and music creation.

Hello, the front page just hasn't been updated, but I'm the co-owner. Would you like another job position in this OS collaboration?

is just a coder ok?

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.

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.

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.

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?

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)

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)