GP1 wrote:

tatefly wrote:

Alright the website is looking okay but there are still major changes that need to be made but don't worry it's almost done

Sweet! I just added block palettes and templates to the List editor, so I'm feeling pretty good right now. (one step closer at a time…)

Nice! I was just testing out the editor and throwing away blocks and moving them feels pretty fluid except for hat blocks. For some reason when I go to throw them away they appear under the header not above like with regular blocks. It's not the most important bug probably but just wanted to let you know

tatefly wrote:

GP1 wrote:

tatefly wrote:

Alright the website is looking okay but there are still major changes that need to be made but don't worry it's almost done

Sweet! I just added block palettes and templates to the List editor, so I'm feeling pretty good right now. (one step closer at a time…)

Nice! I was just testing out the editor and throwing away blocks and moving them feels pretty fluid except for hat blocks. For some reason when I go to throw them away they appear under the header not above like with regular blocks. It's not the most important bug probably but just wanted to let you know

I think I fixed that in one of the pushes I made yesterday. When hat blocks are dragged, the zIndex is changed to 1000 so it appears on top of everything else, while before it wasn't. It was something I noticed as I dragged the define-hat block around, as it was appearing under some blocks.

GP1 wrote:

tatefly wrote:

GP1 wrote:

tatefly wrote:

Alright the website is looking okay but there are still major changes that need to be made but don't worry it's almost done

Sweet! I just added block palettes and templates to the List editor, so I'm feeling pretty good right now. (one step closer at a time…)

Nice! I was just testing out the editor and throwing away blocks and moving them feels pretty fluid except for hat blocks. For some reason when I go to throw them away they appear under the header not above like with regular blocks. It's not the most important bug probably but just wanted to let you know

I think I fixed that in one of the pushes I made yesterday. When hat blocks are dragged, the zIndex is changed to 1000 so it appears on top of everything else, while before it wasn't. It was something I noticed as I dragged the define-hat block around, as it was appearing under some blocks.

I just tried using the hat blocks on my phone and the hat blocks are still appearing under the toolbar

tatefly wrote:

GP1 wrote:

tatefly wrote:

GP1 wrote:

tatefly wrote:

Alright the website is looking okay but there are still major changes that need to be made but don't worry it's almost done

Sweet! I just added block palettes and templates to the List editor, so I'm feeling pretty good right now. (one step closer at a time…)

Nice! I was just testing out the editor and throwing away blocks and moving them feels pretty fluid except for hat blocks. For some reason when I go to throw them away they appear under the header not above like with regular blocks. It's not the most important bug probably but just wanted to let you know

I think I fixed that in one of the pushes I made yesterday. When hat blocks are dragged, the zIndex is changed to 1000 so it appears on top of everything else, while before it wasn't. It was something I noticed as I dragged the define-hat block around, as it was appearing under some blocks.

I just tried using the hat blocks on my phone and the hat blocks are still appearing under the toolbar

That's because I haven't pushed to Heroku yet XD
I'll probably do it when I finish the checklist I'm working on in Trello, probably on Saturday.
*hint. The post with green text saying “Site updated. Timestamp: *********” is when I push to Heroku. So you know *

GP1 wrote:

tatefly wrote:

GP1 wrote:

tatefly wrote:

GP1 wrote:

tatefly wrote:

Alright the website is looking okay but there are still major changes that need to be made but don't worry it's almost done

Sweet! I just added block palettes and templates to the List editor, so I'm feeling pretty good right now. (one step closer at a time…)

Nice! I was just testing out the editor and throwing away blocks and moving them feels pretty fluid except for hat blocks. For some reason when I go to throw them away they appear under the header not above like with regular blocks. It's not the most important bug probably but just wanted to let you know

I think I fixed that in one of the pushes I made yesterday. When hat blocks are dragged, the zIndex is changed to 1000 so it appears on top of everything else, while before it wasn't. It was something I noticed as I dragged the define-hat block around, as it was appearing under some blocks.

I just tried using the hat blocks on my phone and the hat blocks are still appearing under the toolbar

That's because I haven't pushed to Heroku yet XD
I'll probably do it when I finish the checklist I'm working on in Trello, probably on Saturday.
*hint. The post with green text saying “Site updated. Timestamp: *********” is when I push to Heroku. So you know *

Ohhhh okay sorry. I guess I'm unclear on some topics thanks for the info!

GP1 wrote:

Site Update. Timestamp: 1399086181 (UTC).

AAhhhhhh something went wrong in the push. Right now Heroku says that there are no stylesheets, sub-directories, etc. I will look into this and fix it ASAP.

GP1 wrote:

GP1 wrote:

Site Update. Timestamp: 1399086181 (UTC).

AAhhhhhh something went wrong in the push. Right now Heroku says that there are no stylesheets, sub-directories, etc. I will look into this and fix it ASAP.

Just emailed comp500 to see if he can help with Heroku, when he gets a chance. Oh well. I guess the next thing to work on is making the Editor work with node-webkit

Running on your local PC (in development mode)

For Windows/Linux users:
1) Download the latest binaries of node-webkit (or the source code, if you want to build it yourself) (https://github.com/rogerwang/node-webkit).
2) Go to the Go Everywhere repo, and either download the ZIP of the repo, or clone it to your computer.
3) Run the base Go-Everywhere folder (should contain “package.json”) through node-webkit.
4) Enjoy!

For Mac OSX users:
1) Go to the Go Everywhere repo, and either download the ZIP of the repo, or clone it to your computer.
2) Open the Go-Everywhere folder in the Finder, and double-click “OSX.app”
3) Enjoy!
4) To open the .ge extension in GE (you can make one by renaming “project.sb2” to “project.ge”), right-click on the .ge project file and select “Open With>>Other…”. Browse to “OSX.app”, enable “All Applications”, and select OSX.app. You can now double click the .ge file with GE!

Running on mobile device (in development mode)
**Android users - Use “Chrome for Android” for best results**
**iOS users - Use “Safari Mobile” (default Safari) for best results**

1) Make sure that you can run GE on your computer via node-webkit application (http://scratch.mit.edu/discuss/post/314220/). Also make sure that you have the latest version of the GE repo on your PC.
2) Go ahead and open the desktop version of GE (using node-webkit!!). This will open the GE List editor and start the GE local server. MAKE SURE TO KEEP THE GE PROGRAM ON YOUR COMPUTER RUNNING!! The local server depends on it. If your computer asks about the GE editor needing through your firewall, let it through!
3) Visit http://localhost:6564/create/editor/images/loading.gif. If you see the “loading” GIF, then your local server is working! If not, try seeing if port 6564 is being used on your computer, and free it.
4) Find and record the local IP of your computer. On Mac OSX and Ubuntu Linux, this can be found in the network preferences/settings. On Windows, this can be found by opening Command Prompt and entering “ipconfig”, and record the IP address from the Ethernet device you are using to connect to your router. Search the internet if you are having trouble with this step.
5) Make sure that your computer running the GE local server and your mobile device are running on the same network, and go to this site on your mobile device (change {localip} to the local IP of your GE local server computer):

http://{localip}:6564/create/editor/list/?project=../1.ge

6) If you see the GE List editor on your device, congratulations! If not, try retracing your steps to see if you made any mistakes along the way.

Wait, has it been so long that I've actually lost the credit for the name?

GP1 wrote:

This was ONLY tested on an Android platform. Other platforms may not have functionality yet, but iOS should work the same if using “Chrome for iOS”
**for best results, try getting Google Chrome on your mobile device**

Just so you know, Chrome for iOS is just Safari with a slower javascript engine, skinned to look like Chrome, so Go Everywhere would run best in Safari.

whizzer wrote:

Wait, has it been so long that I've actually lost the credit for the name?

I was never told this…. :0

djdolphin wrote:

GP1 wrote:

This was ONLY tested on an Android platform. Other platforms may not have functionality yet, but iOS should work the same if using “Chrome for iOS”
**for best results, try getting Google Chrome on your mobile device**

Just so you know, Chrome for iOS is just Safari with a slower javascript engine, skinned to look like Chrome, so Go Everywhere would run best in Safari.

Huh… that makes sense. The only reason why said to use Chrome was because I hadn't tested any other browsers (lazy me!). Thanks for the info, I'll update the post.

GP1 wrote:

whizzer wrote:

Wait, has it been so long that I've actually lost the credit for the name?

I was never told this…. :0

It was originally called “Scratch Everywhere” but the Scratch Team, obviously, said we couldn't use the name “Scratch”. This was the REALLY REALLY REALLY early days of GE. There were, like, only two pages on the forum topic! A request for new name submissions was given and my idea of “Go Everywhere” was chosen. Ask jvvg for the archive if you don't believe me.

whizzer wrote:

GP1 wrote:

whizzer wrote:

Wait, has it been so long that I've actually lost the credit for the name?

I was never told this…. :0

It was originally called “Scratch Everywhere” but the Scratch Team, obviously, said we couldn't use the name “Scratch”. This was the REALLY REALLY REALLY early days of GE. There were, like, only two pages on the forum topic! A request for new name submissions was given and my idea of “Go Everywhere” was chosen. Ask jvvg for the archive if you don't believe me.

Don't worry, I believe you. I'll put your name in the main post.

GP1 wrote:

whizzer wrote:

GP1 wrote:

whizzer wrote:

Wait, has it been so long that I've actually lost the credit for the name?

I was never told this…. :0

It was originally called “Scratch Everywhere” but the Scratch Team, obviously, said we couldn't use the name “Scratch”. This was the REALLY REALLY REALLY early days of GE. There were, like, only two pages on the forum topic! A request for new name submissions was given and my idea of “Go Everywhere” was chosen. Ask jvvg for the archive if you don't believe me.

Don't worry, I believe you. I'll put your name in the main post.

Dankeschön!

3) Run the base Go-Everywhere folder (should contain “package.json”) through node-webkit.

How the heck am I supposed to do that?

goldfish678 wrote:

3) Run the base Go-Everywhere folder (should contain “package.json”) through node-webkit.

How the heck am I supposed to do that?

Depends on which platform you are running. Let's take Windows, for example. Open up node-webkit (it should look like a web browser). In the URL you need to put the path of the Go-Everywhere folder. For example, if you cloned the Go-Everywhere folder into your Documents, the path would look like:

C:\Users\GP1\Documents\Go-Everywhere

Windows has a nice little shift-secret you can do to help. Browse to the Go-Everywhere folder (the root of the repo), and while holding down “shift”, right-click the folder. In the context menu, there should be an extra option, “Copy as Path”. Go back to node-webkit and paste it in the URL bar, and hit enter (while in focus of the URL bar, to load the local path). If you did it right, the Editor SHOULD load up a blank project.

Sorry for me being inactive. I don't know when I'll get time to work on this again, since I started 2 huge (somewhat never ending) projects.

GP1 wrote:

goldfish678 wrote:

3) Run the base Go-Everywhere folder (should contain “package.json”) through node-webkit.

How the heck am I supposed to do that?

Depends on which platform you are running. Let's take Windows, for example. Open up node-webkit (it should look like a web browser). In the URL you need to put the path of the Go-Everywhere folder. For example, if you cloned the Go-Everywhere folder into your Documents, the path would look like:

C:\Users\GP1\Documents\Go-Everywhere

Windows has a nice little shift-secret you can do to help. Browse to the Go-Everywhere folder (the root of the repo), and while holding down “shift”, right-click the folder. In the context menu, there should be an extra option, “Copy as Path”. Go back to node-webkit and paste it in the URL bar, and hit enter (while in focus of the URL bar, to load the local path). If you did it right, the Editor SHOULD load up a blank project.

Luckily, I have Windows! THANKS!