Scratch

logiblocs · 2012-09-28 15:10:38

I came up with an idea for 'tests' (scratch projects to be run through itchy to test whether an idea works). See github for details.

Currently both tests 'fail'. I am running fedora 17 with gnome shell. I will try it out tomorrow on mint with cinnamon and my Arch Linux box.

For testing purposes mint is ubuntu.

bobbybee · 2012-09-28 15:54:26

@Math
Still a prob

pwiter · 2012-09-28 18:21:08

Hmm...
Endian.h is also not available on Windows.

I went on Windows to compile the exe.

bobbybee · 2012-09-28 19:42:53

@pwiter
Modify the if to include windows, guess.

pwiter · 2012-09-28 19:52:25

C++ uses "|" for "or" right?

pwiter · 2012-09-28 19:58:36

@bobbybee
But "/usr/include/machine/endian.h" isn't on windows.

I heard that boost has endian like stuff?

bobbybee · 2012-09-28 20:46:21

If you like at my scratchio.h, I put a copy of endian.h in the header. Just use that wink

amcerbu · 2012-09-28 21:39:45

@pwitter: || for Boolean OR, | for bitwise OR.

Last edited by amcerbu (2012-09-28 21:39:58)

pwiter · 2012-09-28 21:49:17

@amcerbu
Thx, I was just making sure that was it in C++.

@bobbybee
I did that, but it's giving errors for htobe32 and htobe64.

Darn, I keep pressing ; for .

Last edited by pwiter (2012-09-28 21:50:43)

MathWizz · 2012-09-28 23:38:08

Ok... Really? All of the issues? You may as well point out that scripts don't work and I should fix them. Be patient, I am still working on the sprites and stuff. Also, the reason sprites don't render is that they images cannot be decoded yet.

Last edited by MathWizz (2012-09-28 23:42:48)

logiblocs · 2012-09-29 13:39:45

I just made some new branches where the packaging will go eventually. Arch linux packaging is complete and I am going to start work on the rpm.

bobbybee · 2012-09-30 06:21:42

I know how to package -apps through make.

amcerbu · 2012-10-01 01:09:34

@All - Can we consider doing some organization of the graphics code? I think it would be a good idea to abstract the messy SDL stuff to within a series of graphics classes (I noticed there's a good deal in main() ), or something like that, because it could come in very handy down the road for us to change graphics-specific stuff without altering program logic.

Last edited by amcerbu (2012-10-01 01:11:44)

MathWizz · 2012-10-01 01:25:25

@amcerbu - Yes, but later. When we get into the more graphics intensive editor stuff, we can do this, but at the moment let's concentrate on the project player.

bobbybee · 2012-10-01 15:59:54

Wait...can we do a sub-division of itchy++, the Itchy Emulator. Basically, it would emulate Scratch's VM (sounds odd). Itchy++ would use the library form of the Itchy Emulator for playing projects.

TRocket · 2012-10-01 16:02:43

bobbybee wrote:
Wait...can we do a sub-division of itchy++, the Itchy Emulator. Basically, it would emulate Scratch's VM (sounds odd). Itchy++ would use the library form of the Itchy Emulator for playing projects.

i was thinking the same sort of thing with my IPPX idea it would be written for Itchy Bytecode and Itchy++ would convert the scratch project and compile it...

bobbybee · 2012-10-01 16:03:51

Exactly. It would be particularly good because the Scratch file format requires a module in itself to parse, so if we wrote a module to convert to bytecode, we wouldn't be forced to mash all the code together.

bobbybee · 2012-10-01 16:06:28

By the way, having written a small Scratch 2.0 player myself, I could write the sb2 to bytecode module. Then we have a universal code (plus if we want to read other sorts of projects, maybe even Itchy code itself, we can have a universal method of doing stuff).

TRocket · 2012-10-01 16:16:50

bobbybee wrote:
By the way, having written a small Scratch 2.0 player myself, I could write the sb2 to bytecode module. Then we have a universal code (plus if we want to read other sorts of projects, maybe even Itchy code itself, we can have a universal method of doing stuff).

sounds good to me, we need to decide on a format for Itchy Byte code... and document it properly!

bobbybee · 2012-10-01 16:35:43

I'm quite good at designing file formats and writing specs for them, consider it done.

MathWizz · 2012-10-01 17:14:08

TRocket wrote:
bobbybee wrote:
By the way, having written a small Scratch 2.0 player myself, I could write the sb2 to bytecode module. Then we have a universal code (plus if we want to read other sorts of projects, maybe even Itchy code itself, we can have a universal method of doing stuff).
sounds good to me, we need to decide on a format for Itchy Byte code... and document it properly!

We don't need to write a THIRD format for saving files. -.-

amcerbu · 2012-10-01 17:17:41

Yeah, I think we did talk about writing a special Itchy++ file format earlier, and decided against it.

On a completely unrelated note: do you think we could build a feature that would "convert" a Scratch project into a .cpp file? Of course, that file would have to be compiled manually (unless we could somehow include some open-source compiler, which, I actually realized, could be done), but I think it would be cool to be able to create executables.

Last edited by amcerbu (2012-10-01 17:18:56)

pwiter · 2012-10-01 17:26:13

I can't find cairo for Windows...

bobbybee · 2012-10-01 17:58:25

amcerbu wrote:
Yeah, I think we did talk about writing a special Itchy++ file format earlier, and decided against it.

On a completely unrelated note: do you think we could build a feature that would "convert" a Scratch project into a .cpp file? Of course, that file would have to be compiled manually (unless we could somehow include some open-source compiler, which, I actually realized, could be done), but I think it would be cool to be able to create executables.

I think an Itchy++ format would simplify things, not complexify them. Since we're dealing with 2.0 and 1.4 files, we need a universal way to do things between them, e.g. the Itchy format.

nXIII · 2012-10-01 18:26:01

bobbybee wrote:
I think an Itchy++ format would simplify things, not complexify them. Since we're dealing with 2.0 and 1.4 files, we need a universal way to do things between them, e.g. the Itchy format.

It's worth noting that your format would accomplish a different goal (viz. execution) from the Scratch 1.x and 2.0 file formats (which are designed for storage).

Scratch

archived forums

#201 2012-09-28 15:10:38

Re: Itchy++ - a Scratch C++ Port

#202 2012-09-28 15:54:26

Re: Itchy++ - a Scratch C++ Port

#203 2012-09-28 18:21:08

Re: Itchy++ - a Scratch C++ Port

#204 2012-09-28 19:42:53

Re: Itchy++ - a Scratch C++ Port

#205 2012-09-28 19:52:25

Re: Itchy++ - a Scratch C++ Port

#206 2012-09-28 19:58:36

Re: Itchy++ - a Scratch C++ Port

#207 2012-09-28 20:46:21

Re: Itchy++ - a Scratch C++ Port

#208 2012-09-28 21:39:45

Re: Itchy++ - a Scratch C++ Port

#209 2012-09-28 21:49:17

Re: Itchy++ - a Scratch C++ Port

#210 2012-09-28 23:38:08

Re: Itchy++ - a Scratch C++ Port

#211 2012-09-29 13:39:45

Re: Itchy++ - a Scratch C++ Port

#212 2012-09-30 06:21:42

Re: Itchy++ - a Scratch C++ Port

#213 2012-10-01 01:09:34

Re: Itchy++ - a Scratch C++ Port

#214 2012-10-01 01:25:25

Re: Itchy++ - a Scratch C++ Port

#215 2012-10-01 15:59:54

Re: Itchy++ - a Scratch C++ Port

#216 2012-10-01 16:02:43

Re: Itchy++ - a Scratch C++ Port

bobbybee wrote:

#217 2012-10-01 16:03:51

Re: Itchy++ - a Scratch C++ Port

#218 2012-10-01 16:06:28

Re: Itchy++ - a Scratch C++ Port

#219 2012-10-01 16:16:50

Re: Itchy++ - a Scratch C++ Port

bobbybee wrote:

#220 2012-10-01 16:35:43

Re: Itchy++ - a Scratch C++ Port

#221 2012-10-01 17:14:08

Re: Itchy++ - a Scratch C++ Port

TRocket wrote:

bobbybee wrote:

#222 2012-10-01 17:17:41

Re: Itchy++ - a Scratch C++ Port

#223 2012-10-01 17:26:13

Re: Itchy++ - a Scratch C++ Port

#224 2012-10-01 17:58:25

Re: Itchy++ - a Scratch C++ Port

amcerbu wrote:

#225 2012-10-01 18:26:01

Re: Itchy++ - a Scratch C++ Port

bobbybee wrote:

Board footer