This is a read-only archive of the old Scratch 1.x Forums.
Try searching the current Scratch discussion forums.

#1 2008-09-07 20:16:26

cbas
Scratcher
Registered: 2008-09-01
Posts: 5

Working online

My project http://scratch.mit.edu/projects/cbas/260450  (1.3) doesn't work online. I used the new features. (The result is the same for IE and FF)

I think that a project with complicated and many instructions doesn't work online.

In another project I had to remove many costumes to get run it online:
http://scratch.mit.edu/projects/cbas/255626

The only way to discover the errors is to place the projects online right at the beginning, as soon as possible and not at the end of development, to find the bug as soon as possible. Now it is boring to remove features projects ... to discover the bugs or to mending the project.

Last edited by cbas (2008-09-07 20:20:37)

Offline

 

#2 2008-09-07 20:32:33

demosthenes
Retired Community Moderator
Registered: 2008-02-19
Posts: 1000+

Re: Working online

I'm no expert but I don't think that scratch 1.3 is compatible with the java applet yet. I hope the scratch team gets around to working on that soon.


I've taken a long hiatus, but I still visit sometimes. Give me some time to answer any messages you post on my projects!

Offline

 

#3 2008-09-08 22:45:29

MasterOfMac
Scratcher
Registered: 2008-02-01
Posts: 62

Re: Working online

It should be working. A lot of other's had 1.3 web upload glitches, but I'm pretty sure the Java version has started working.


*sarcasm*

Offline

 

#4 2008-09-09 01:48:17

vikaros
Scratcher
Registered: 2007-06-04
Posts: 100

Re: Working online

We have uploaded a new version of the Applet to provide better 1.3 support.  Still please keep letting the team know about any problems you encounter.  What is especially helpful is like cbas says, post a project online early during development to check that new additions work, and then make more changes, and keep going back and forth.  This is how programming in many types of languages happens.  It helps to identify what specific changes caused a problem. 

This is also important for fixing the Applet, since we can only make improvements when we can reproduce a problem someone else is having.  So if you have a problem, try to describe what you did/changed when it happened.

Offline

 

Board footer