Scratch

nXIII wrote:

Sorry to intervene, but this is the Panther development thread and none of the recent conversations have anything to do with Panther for a while.

Sorry.

johnnydean1 wrote:

3001 comments on this thread!

Correction: 3002

henley wrote:

MathWizz wrote:

johnnydean1 wrote:

3001 comments on this thread!

Correction: 3002

No, 3004. Because you were 3003, and now I am writing.

ANYWAY

You can save this pointless conversation for the miscellaneous forums. I am sick of people developing this kind of conversation in the Panther Development Thread. The Panther Development Thread is for the development of Panther. Not randomness, spam, and pointlessness.

Please let a mod deal with this if it is out of hand.

johnnydean1 wrote:

Hows block shareing??

S.E.P. - Someone Else's Problem

If you care to know what I'M doing, I am working on a minimizeable and draggable block palette, as well as a resizeable stage! (it uses interpolation instead of physical size differences, but I have to fix positioning, etc.)

johnnydean1 wrote:

Very cool, I would love the block pallete.

It is cool, though a bit glitchy at the moment. Iv tried it out, really is helpful.

nXIII wrote:

johnnydean1 wrote:

Hows block shareing??

S.E.P. - Someone Else's Problem

If you care to know what I'M doing, I am working on a minimizeable and draggable block palette, as well as a resizeable stage! (it uses interpolation instead of physical size differences, but I have to fix positioning, etc.)

If you get that that to work, they might actually want to use that.

Unless it's already been done.

nXIII wrote:

cds56 wrote:

nXIII wrote:

S.E.P. - Someone Else's Problem

If you care to know what I'M doing, I am working on a minimizeable and draggable block palette, as well as a resizeable stage! (it uses interpolation instead of physical size differences, but I have to fix positioning, etc.)

If you get that that to work, they might actually want to use that.

Unless it's already been done.

... actually want to use it?

whoaaaaaaaaaaah my comment is ultra-vague.

The scratch team may believe that a resizeable stage is a good idea.


how are you going to interpolate the stage then?

Is it going to be based on, like percentages of the screen size instead of pixels?

*ignore my previous comment*

nXIII wrote:

cds56 wrote:

nXIII wrote:

... actually want to use it?

whoaaaaaaaaaaah my comment is ultra-vague.

The scratch team may believe that a resizeable stage is a good idea.


how are you going to interpolate the stage then?

Is it going to be based on, like percentages of the screen size instead of pixels?

*ignore my previous comment*

Well, I am basically making the stage first draw itself as though it was a 480x360 stage, then scale the result to fit its current size. I am just having problems with the whole drawing offscreen thingy.

Does anyone know if some Morph's fullCopy copies submorphs? Or is it deepCopy?

Why not try both?

bharvey wrote:

nXIII wrote:

Well, I am basically making the stage first draw itself as though it was a 480x360 stage, then scale the result to fit its current size.

A couple of suggestions:

1. Be careful about scaling text.  You don't want to render the text and then scale the pixels; you want to compute what the scaled font size should be and then rasterize at that size to begin with.

2. You might consider first drawing onto a very big stage, like say 480,000 by 360,000, and then scaling down to the desired size, so you don't get jaggies scaling up.  Or are you using color-shifting to anti-alias?

Hm... well, 480,000x360,000 would most likely crash the Squeak VM, but I see what you mean... right now I am drawing it on the natural size, then scaling it to the current size; here is a (very large, I'm not putting it inline) picture of the stage at 960x720: (it snaps to 2x, 1.5x, 1x, .5x, and .25x) <link>

nXIII wrote:

bharvey wrote:

nXIII wrote:

Well, I am basically making the stage first draw itself as though it was a 480x360 stage, then scale the result to fit its current size.

A couple of suggestions:

1. Be careful about scaling text.  You don't want to render the text and then scale the pixels; you want to compute what the scaled font size should be and then rasterize at that size to begin with.

2. You might consider first drawing onto a very big stage, like say 480,000 by 360,000, and then scaling down to the desired size, so you don't get jaggies scaling up.  Or are you using color-shifting to anti-alias?

Hm... well, 480,000x360,000 would most likely crash the Squeak VM, but I see what you mean... right now I am drawing it on the natural size, then scaling it to the current size; here is a (very large, I'm not putting it inline) picture of the stage at 960x720: (it snaps to 2x, 1.5x, 1x, .5x, and .25x) <link>

Whats it looks like at .25?

I can add more blocks, when I see that youve implemented it in Panther.

sparks wrote:

johnnydean1 wrote:

I can add more blocks, when I see that youve implemented it in Panther.

Well I get your meaning, but I'm not technically implementing it in Panther, I'm making a project with scratch 1.0 that uses a few custom blocks and the URL blocks to read an online collection of blocks and present them into the project.

and then you can make it make them into blocks in the project!

So when are you doing it.