Welcome to the temporary discussion page of Sapphire os in OS Wars 25!
As said this is temporary, while we find better solutions

Information

We already have planned some stuff, so to not add unnecessary clutter imma clarify some stuff:

• - We already have the base and idea for the programming language including names
  - We already have some sort of an idea for our rendering engine
  

The programming language is what the os will be built on for the most part. It'l be c++-like

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

leader here. if you have the blue disco app, tell me or @ItsGraphax plz

Also Info: I'm gonna remove smaller projects thta act as a toolbox or small demos. Let's keep the studio cleaned up and make it only for “bigger/important” updates and parts

vaibhavchandra wrote:

leader here. if you have the blue disco app, tell me or @ItsGraphax plz

can we communicate in flgma?

vaibhavchandra wrote:

leader here. if you have the blue disco app, tell me or @ItsGraphax plz

Can u pls add me to the studio?

yo like we should fix the studio banner so it's not like stretched

So who will set up the fig file? I mean for the UI and everything. We also should get to know each other a bit (sounds stupid but could be helpful), so we know our strengths and weaknesses

24_Jupiter wrote:

So who will set up the fig file? I mean for the UI and everything. We also should get to know each other a bit (sounds stupid but could be helpful), so we know our strengths and weaknesses

We already have the fig file. Idk drop your username and v will add you

Also imma introduce myself:
Name: Graphax
Interests: Coding (Scratch, Python, Lua), Modding (Balatro) and what my interest is atm lol
Country/Continent and Languages: Swiss / English, German and a bit Spanish and French
More about me: I like coding stuff, specially if it involves making workarounds or doing something that wasn't intended. I find that fun. Atm I also train a bit pixel art for my semi-popular Balatro mod
Idk probably copy this as a preset and introduce yourselves!

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

ItsGraphax wrote:

24_Jupiter wrote:

So who will set up the fig file? I mean for the UI and everything. We also should get to know each other a bit (sounds stupid but could be helpful), so we know our strengths and weaknesses

We already have the fig file. Idk drop your username and v will add you

Also imma introduce myself:
Name: Graphax
Interests: Coding (Scratch, Python, Lua), Modding (Balatro) and what my interest is atm lol
Country/Continent and Languages: Swiss / English, German and a bit Spanish and French
More about me: I like coding stuff, specially if it involves making workarounds or doing something that wasn't intended. I find that fun. Atm I also train a bit pixel art for my semi-popular Balatro mod
Idk probably copy this as a preset and introduce yourselves!

My username on fig is the same as it is here on scratch: @24_Jupiter

Name: Jupiter
Interests: Designing, sports, aviation.
Country/Continent and Languages: Asian - English, German (pretty ok at), Malayalam (Indian Language), and Spanish (a bit).
More About Me: 5 years of experience on Scratch; 3 years of coding and 2 years of designing.

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

24_Jupiter wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

You guys are completly wrong, using pen would make the project run faster smoother and would make the json file smaller, and also, a big project like sapphire would be recommended to be used on turbowarp anyways! so all we have to do it just to use turbowarp's high-quality pen thing!

Name: TechNerd
Interests: Coding (Scratch, Python, HTML), computer hardware, and Jellyfin
Country/Continent and Languages: English and USA
More about me: I've been coding since i was 10, but really started getting better around 2 years ago. I've recently been investing in learning python (with flask) and HTML (CSS and JS included)

coolmetal_ wrote:

24_Jupiter wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

You guys are completly wrong, using pen would make the project run faster smoother and would make the json file smaller, and also, a big project like sapphire would be recommended to be used on turbowarp anyways! so all we have to do it just to use turbowarp's high-quality pen thing!

the turbowarp high pen can never get as high quality as a regular svg. while the project would run slightly faster, the amount of time it takes to clone things takes longer meaning stages where there are a lot of new clone could take up to a second to render even if done in the fastest possible way. also there is less control over individual clones when stamped. If done correctly you can easily keep the json file small by using a good cloning system which would also minimise lag in the projects. Making the project versatile between scratch and turbowarp i feel would be good, but if we are talking turbowarp i feel lag and load time should not even be in a list of problems.

Imperial_Purple wrote:

coolmetal_ wrote:

24_Jupiter wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

You guys are completly wrong, using pen would make the project run faster smoother and would make the json file smaller, and also, a big project like sapphire would be recommended to be used on turbowarp anyways! so all we have to do it just to use turbowarp's high-quality pen thing!

the turbowarp high pen can never get as high quality as a regular svg. while the project would run slightly faster, the amount of time it takes to clone things takes longer meaning stages where there are a lot of new clone could take up to a second to render even if done in the fastest possible way. also there is less control over individual clones when stamped. If done correctly you can easily keep the json file small by using a good cloning system which would also minimise lag in the projects. Making the project versatile between scratch and turbowarp i feel would be good, but if we are talking turbowarp i feel lag and load time should not even be in a list of problems.

Clones have a special amount in scratch and while we still can use turbowarp's infinite clone, we would not be able to make an actual resizable window. and also, using stamp is actually a LOT faster than clones because of the fact that it doesn't make a temporary sprite-like object

coolmetal_ wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

24_Jupiter wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

You guys are completly wrong, using pen would make the project run faster smoother and would make the json file smaller, and also, a big project like sapphire would be recommended to be used on turbowarp anyways! so all we have to do it just to use turbowarp's high-quality pen thing!

the turbowarp high pen can never get as high quality as a regular svg. while the project would run slightly faster, the amount of time it takes to clone things takes longer meaning stages where there are a lot of new clone could take up to a second to render even if done in the fastest possible way. also there is less control over individual clones when stamped. If done correctly you can easily keep the json file small by using a good cloning system which would also minimise lag in the projects. Making the project versatile between scratch and turbowarp i feel would be good, but if we are talking turbowarp i feel lag and load time should not even be in a list of problems.

Clones have a special amount in scratch and while we still can use turbowarp's infinite clone, we would not be able to make an actual resizable window. and also, using stamp is actually a LOT faster than clones because of the fact that it doesn't make a temporary sprite-like object

wow this is getting long. anyway in answer to your statements:

1. Yes, turbowarp has an infinite clones setting that scratch doesn't however I don't see any situation where we would actually want to have over 300 clones on the screen, as if we add up all the assets needed on the screen at any one time it would most likely cap out at 20 or 30.

2. resiseable windows have never been used in an scratch os and they would prove both difficult and limiting if we decided to use them, not to mention if we stamped our windows, a resizeable window would either stretch or crop and wouldn't work properly.

3. stamping relies on a cloner “stamper” sprite. this sprite needs to be changed to whatever costume is needed then stamped. this stamping process converts the svg into a png then places that on the screen. this process takes roughly the same to slightly longer than cloning, (if done correctly), as the way scratch converts svg to png isn't optomised perfectly, not to mention that stamping cannot be unlayerd or altered after being stamped so interactive buttons aren't an option, unless you refresh the entire screen between every frame, in which case you need to do the stamping process many times every single frame.

if you have any more things that you would like me to clear up I don't mind just tell me

Imperial_Purple wrote:

coolmetal_ wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

24_Jupiter wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

You guys are completly wrong, using pen would make the project run faster smoother and would make the json file smaller, and also, a big project like sapphire would be recommended to be used on turbowarp anyways! so all we have to do it just to use turbowarp's high-quality pen thing!

the turbowarp high pen can never get as high quality as a regular svg. while the project would run slightly faster, the amount of time it takes to clone things takes longer meaning stages where there are a lot of new clone could take up to a second to render even if done in the fastest possible way. also there is less control over individual clones when stamped. If done correctly you can easily keep the json file small by using a good cloning system which would also minimise lag in the projects. Making the project versatile between scratch and turbowarp i feel would be good, but if we are talking turbowarp i feel lag and load time should not even be in a list of problems.

Clones have a special amount in scratch and while we still can use turbowarp's infinite clone, we would not be able to make an actual resizable window. and also, using stamp is actually a LOT faster than clones because of the fact that it doesn't make a temporary sprite-like object

wow this is getting long. anyway in answer to your statements:

1. Yes, turbowarp has an infinite clones setting that scratch doesn't however I don't see any situation where we would actually want to have over 300 clones on the screen, as if we add up all the assets needed on the screen at any one time it would most likely cap out at 20 or 30.

2. resiseable windows have never been used in an scratch os and they would prove both difficult and limiting if we decided to use them, not to mention if we stamped our windows, a resizeable window would either stretch or crop and wouldn't work properly.

3. stamping relies on a cloner “stamper” sprite. this sprite needs to be changed to whatever costume is needed then stamped. this stamping process converts the svg into a png then places that on the screen. this process takes roughly the same to slightly longer than cloning, (if done correctly), as the way scratch converts svg to png isn't optomised perfectly, not to mention that stamping cannot be unlayerd or altered after being stamped so interactive buttons aren't an option, unless you refresh the entire screen between every frame, in which case you need to do the stamping process many times every single frame.

if you have any more things that you would like me to clear up I don't mind just tell me

https://scratch.mit.edu/projects/1219573154/ < How's this? Glass windows

RedSweaterGuy wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

24_Jupiter wrote:

Imperial_Purple wrote:

coolmetal_ wrote:

What if we try stamping to render windows?
like the window size is 100*100 we can fille it with 4 50*50 rectangles

I don't think relying on pen would be a good idea because of pixelation, and also stamping means we would need a single cloner which would make render time slower

Agreed, plus way too complicated imo especially if the project will be big. Stamping can sometimes have * quality to it cuz of it converting the costume into a png/pixelized version. So yeah I def think there should be no heavy use of pen.

You guys are completly wrong, using pen would make the project run faster smoother and would make the json file smaller, and also, a big project like sapphire would be recommended to be used on turbowarp anyways! so all we have to do it just to use turbowarp's high-quality pen thing!

the turbowarp high pen can never get as high quality as a regular svg. while the project would run slightly faster, the amount of time it takes to clone things takes longer meaning stages where there are a lot of new clone could take up to a second to render even if done in the fastest possible way. also there is less control over individual clones when stamped. If done correctly you can easily keep the json file small by using a good cloning system which would also minimise lag in the projects. Making the project versatile between scratch and turbowarp i feel would be good, but if we are talking turbowarp i feel lag and load time should not even be in a list of problems.

Clones have a special amount in scratch and while we still can use turbowarp's infinite clone, we would not be able to make an actual resizable window. and also, using stamp is actually a LOT faster than clones because of the fact that it doesn't make a temporary sprite-like object

wow this is getting long. anyway in answer to your statements:

1. Yes, turbowarp has an infinite clones setting that scratch doesn't however I don't see any situation where we would actually want to have over 300 clones on the screen, as if we add up all the assets needed on the screen at any one time it would most likely cap out at 20 or 30.

2. resiseable windows have never been used in an scratch os and they would prove both difficult and limiting if we decided to use them, not to mention if we stamped our windows, a resizeable window would either stretch or crop and wouldn't work properly.

3. stamping relies on a cloner “stamper” sprite. this sprite needs to be changed to whatever costume is needed then stamped. this stamping process converts the svg into a png then places that on the screen. this process takes roughly the same to slightly longer than cloning, (if done correctly), as the way scratch converts svg to png isn't optomised perfectly, not to mention that stamping cannot be unlayerd or altered after being stamped so interactive buttons aren't an option, unless you refresh the entire screen between every frame, in which case you need to do the stamping process many times every single frame.

if you have any more things that you would like me to clear up I don't mind just tell me

https://scratch.mit.edu/projects/1219573154/ < How's this? Glass windows

it still uses the pen extension