Scratch

nXIII wrote:

I'm probably going to use the minimal category buttons on the block dialog as well.

Umm.  Please let's don't have development forks.  Just one GUI, please, and if you're going to propose changes, you have to start by explaining why your proposal is better for a beginning user, i.e., one who has not already memorized how the category names correspond to colors, or does not even realize that there is more than one block palette.

Not meaning to rain on your parade, but we have a deadline in about two weeks, and load/save still needs work, and nobody should be working on GUI issues just now.

Thanks!

bharvey wrote:

nXIII wrote:

I'm probably going to use the minimal category buttons on the block dialog as well.

Umm.  Please let's don't have development forks.  Just one GUI, please, and if you're going to propose changes, you have to start by explaining why your proposal is better for a beginning user, i.e., one who has not already memorized how the category names correspond to colors, or does not even realize that there is more than one block palette.

Consistency. It's confusing to have one part of the GUI look one way and another part of the GUI that does the same thing look different. A beginning user who has become familiar with the minimal tabs and sees this new interface would probably think it did something else.

Not meaning to rain on your parade, but we have a deadline in about two weeks, and load/save still needs work, and nobody should be working on GUI issues just now.

Well, there haven't really been any reporter bugs on this thread or the mailing list, so I don't have much to work on for the actual serialization (although, if anyone has found a bug, please report it! It makes my job easier  ). I am working on the BYOB project importer, but that's not really vital to demoing or safely saving projects.

When is BYOB 4 scheduled to come out? (If there is a date)

scimonster wrote:

I got a failure code. 0x80040111. Whatever that means.

In the error popup, or from your browser? (and, if so, what browser?)

Jutros wrote:

But if I close the browser and restart it, the project is gone.
Is this an oversight or is it working as intended?

It's working as best it can.  Javascript doesn't get to write real files on your computer; it uses "local storage" -- not exactly cookies, but the same principle.  So, yeah, you have to whitelist Snap!.

bharvey wrote:

o, yeah, you have to whitelist Snap!.

Thank you. I guess I'll have to wait for the downloadable version then.

In addition, I foresee problems with computers at schools, which are highly protected and eradicate any changes made to them outside of personal folders on shutdown.

-- Jutros

scimonster wrote:

nXIII wrote:

scimonster wrote:

I got a failure code. 0x80040111. Whatever that means.

In the error popup, or from your browser? (and, if so, what browser?)

In an error popup in your Snap!. Also, all the UI elements were out of place.
I think I was using Aurora at the time. It's Firefox 12 alpha. The browser may be connected anyways. 

Okay, it should be fixed now. There was something wrong with texture drawing.

funelephant wrote:

When is BYOB 4 scheduled to come out? (If there is a date)

It sort of already came out-- it's called Snap now. 

Jutros wrote:

Thank you. I guess I'll have to wait for the downloadable version then.

In addition, I foresee problems with computers at schools, which are highly protected and eradicate any changes made to them outside of personal folders on shutdown.

Hmm, we may have to rethink this issue.  We've been excited about a browser-based version because another problem with school computers is that the paranoid IT people won't let teachers install BYOB (because it doesn't come from Microsoft or Apple). Snap! doesn't require a download, which solves that problem, but as of now I don't know a solution that allows saving projects without one of allowing local storage, enabling Java, downloading software, or installing an upload server somewhere.

bharvey wrote:

Jutros wrote:

Thank you. I guess I'll have to wait for the downloadable version then.

In addition, I foresee problems with computers at schools, which are highly protected and eradicate any changes made to them outside of personal folders on shutdown.

Hmm, we may have to rethink this issue.  We've been excited about a browser-based version because another problem with school computers is that the paranoid IT people won't let teachers install BYOB (because it doesn't come from Microsoft or Apple). Snap! doesn't require a download, which solves that problem, but as of now I don't know a solution that allows saving projects without one of allowing local storage, enabling Java, downloading software, or installing an upload server somewhere.

Let's see... PHP has file read/write. How about creating a real save on the user's hard drive (as a .xml or maybe .snap), which means it could also be shared. Would that do better?

bharvey wrote:

scimonster wrote:

Let's see... PHP has file read/write. How about creating a real save on the user's hard drive (as a .xml or maybe .snap), which means it could also be shared. Would that do better?

That would be great, but PHP runs on a server, not on a client, right?

I guess the official right thing is to make the user click "save page as..." in the browser's menu, which we've been trying to avoid because it's a non-morphic mechanism.

Well, there's actually a (very hack-y) way to save a file with exclusively js, although it uses the 'download' attribute of the 'a' element, which I believe only Chrome supports; also, there is no way to replace an existing file or change the filename unless the user changes his/her preferences.

Last edited by nXIII (2012-02-12 13:37:14)

bharvey wrote:

scimonster wrote:

Let's see... PHP has file read/write. How about creating a real save on the user's hard drive (as a .xml or maybe .snap), which means it could also be shared. Would that do better?

That would be great, but PHP runs on a server, not on a client, right?

I guess the official right thing is to make the user click "save page as..." in the browser's menu, which we've been trying to avoid because it's a non-morphic mechanism.

AJAX+JS+PHP. Send a request to the server with the code, and then the PHP file does the downloading.