GP1 wrote:
al-x wrote:
GP1 wrote:
OK, your in.I don't think we need a fullscreen button... I can update the graphics a bunch though and if you guys don't mind can we remove the gradient header? I find it annoying..
Sure. Do what ever you want, we can just roll back to it anytime. And we need a fullscreen button, because we are doing an HTML5 version of the current Scratch 2.0 viewer. And the current Scratch viewer has a full screen button.
okay but can you point me to where the header is made?
Offline
GP1 wrote:
al-x wrote:
GP1 wrote:
OK, your in.I don't think we need a fullscreen button... I can update the graphics a bunch though and if you guys don't mind can we remove the gradient header? I find it annoying..
Sure. Do what ever you want, we can just roll back to it anytime. And we need a fullscreen button, because we are doing an HTML5 version of the current Scratch 2.0 viewer. And the current Scratch viewer has a full screen button.
Btw, the Scratch 2.0 viewer is very different from the current jsScratch.
Offline
al-x wrote:
GP1 wrote:
al-x wrote:
I don't think we need a fullscreen button... I can update the graphics a bunch though and if you guys don't mind can we remove the gradient header? I find it annoying..Sure. Do what ever you want, we can just roll back to it anytime. And we need a fullscreen button, because we are doing an HTML5 version of the current Scratch 2.0 viewer. And the current Scratch viewer has a full screen button.
okay but can you point me to where the header is made?
Its in player.css, thats where all the style is.
Offline
pwiter wrote:
GP1 wrote:
al-x wrote:
I don't think we need a fullscreen button... I can update the graphics a bunch though and if you guys don't mind can we remove the gradient header? I find it annoying..Sure. Do what ever you want, we can just roll back to it anytime. And we need a fullscreen button, because we are doing an HTML5 version of the current Scratch 2.0 viewer. And the current Scratch viewer has a full screen button.
Btw, the Scratch 2.0 viewer is very different from the current jsScratch.
I know. Simple style can make it look like the Scratch 2.0 viewer. (we probably don't need the turbo-mode button. Scratch 2.0 doesn't have that. What do you think about that?)
Offline
GitHub pages was created for the main Go Everywhere repo. It is at http://goeverywhere.github.com/Go-Everywhere/.
Offline
pwiter wrote:
Anyone know of a good free host that we should use for Go Everywhere? If you don't I can use my raspberry pi(but might go down).
We can use 000webhost. Its pretty reliable. Its the most reliable one I've seen so far.
Offline
ATTENTION!!!!!
When working on Go Everywhere, DO NOT WORK IN THE GH-PAGES DIRECTORY! Work only in the master. When you think that what is in the master directory, then merge the master into gh-pages. This ensures that everybody is 1) working on the same code (and not old code) 2) there is a stable version of Go Everywhere before it gets released to prime time.
However, you can, at anytime, merge the two, if you feel the time is right. JsScratch needs to run on a server, so I recommend XAMPP (if you are on Windows. Mac and Linux have it built in, you just need to activate it).
Offline
GP1 wrote:
ATTENTION!!!!!
When working on Go Everywhere, DO NOT WORK IN THE GH-PAGES DIRECTORY! Work only in the master. When you think that what is in the master directory, then merge the master into gh-pages. This ensures that everybody is 1) working on the same code (and not old code) 2) there is a stable version of Go Everywhere before it gets released to prime time.
However, you can, at anytime, merge the two, if you feel the time is right. JsScratch needs to run on a server, so I recommend XAMPP (if you are on Windows. Mac and Linux have it built in, you just need to activate it).
Ok, I'll make sure I do that. I just worked in gh-pages without knowing that I should work in master. Anyways when we set the server up we don't need the gh-pages.
Offline
GP1 wrote:
pwiter wrote:
Anyone know of a good free host that we should use for Go Everywhere? If you don't I can use my raspberry pi(but might go down).
We can use 000webhost. Its pretty reliable. Its the most reliable one I've seen so far.
Sure, it's just that I need to create a new email to use it, because I have to wait 24 hours with my email(created an account that had the wrong domain).
Offline
pwiter wrote:
GP1 wrote:
ATTENTION!!!!!
When working on Go Everywhere, DO NOT WORK IN THE GH-PAGES DIRECTORY! Work only in the master. When you think that what is in the master directory, then merge the master into gh-pages. This ensures that everybody is 1) working on the same code (and not old code) 2) there is a stable version of Go Everywhere before it gets released to prime time.
However, you can, at anytime, merge the two, if you feel the time is right. JsScratch needs to run on a server, so I recommend XAMPP (if you are on Windows. Mac and Linux have it built in, you just need to activate it).Ok, I'll make sure I do that. I just worked in gh-pages without knowing that I should work in master. Anyways when we set the server up we don't need the gh-pages.
I just meant in the Go Everywhere repo. JsScratch I don't care so much. I'm going to delete the master off of it. The main Go Everywhere one I will delete gh-pages and create a new branch that we merge when it is ready for prime.
Offline
GP1 wrote:
pwiter wrote:
GP1 wrote:
ATTENTION!!!!!
When working on Go Everywhere, DO NOT WORK IN THE GH-PAGES DIRECTORY! Work only in the master. When you think that what is in the master directory, then merge the master into gh-pages. This ensures that everybody is 1) working on the same code (and not old code) 2) there is a stable version of Go Everywhere before it gets released to prime time.
However, you can, at anytime, merge the two, if you feel the time is right. JsScratch needs to run on a server, so I recommend XAMPP (if you are on Windows. Mac and Linux have it built in, you just need to activate it).Ok, I'll make sure I do that. I just worked in gh-pages without knowing that I should work in master. Anyways when we set the server up we don't need the gh-pages.
I just meant in the Go Everywhere repo. JsScratch I don't care so much. I'm going to delete the master off of it. The main Go Everywhere one I will delete gh-pages and create a new branch that we merge when it is ready for prime.
Oh, that makes sense.
Anyways, I'm just going to register on 000webhost with a new email for now. That way we can have some stuff getting worked on. It might be some time till I get the GitHub OAuth thing worked out, but at least I can start working on it.
Offline
al-x wrote:
pwiter wrote:
al-x wrote:
I took the header away, the turbo buttons, and added better graphics I just have to upload it to github
You mean push
yeah
Awesome!! Can't wait to see it! Push it as soon as you can.
Last edited by GP1 (2012-12-30 23:41:39)
Offline
pwiter wrote:
Ugh... Php is being annoying. I'm just gonna ditch this OAuth thing until later. Gonna go sleep now. It's 12:13 am.
Good idea. Don't get too engaged in this, it shouldn't take over your sleep cycle.
Offline
al-x wrote:
GP1 wrote:
al-x wrote:
yeahAwesome!! Can't wait to see it! Push it as soon as you can.
okay I did
OMG! That looks awesome! But shouldn't we put a border around the canvas element so the player does not know that the green flag is not part of the stage? Scratch 2.0s viewer has a very light blue for a header, maybe we could do the same, but with orange instead if blue. Or something like that. I sorta like the header, come to think of it.
Offline
GP1 wrote:
al-x wrote:
GP1 wrote:
Awesome!! Can't wait to see it! Push it as soon as you can.okay I did
OMG! That looks awesome! But shouldn't we put a border around the canvas element so the player does not know that the green flag is not part of the stage? Scratch 2.0s viewer has a very light blue for a header, maybe we could do the same, but with orange instead if blue. Or something like that. I sorta like the header, come to think of it.
I don't see it for some reason.
Offline
GP1 wrote:
pwiter wrote:
Ugh... Php is being annoying. I'm just gonna ditch this OAuth thing until later. Gonna go sleep now. It's 12:13 am.
Good idea. Don't get too engaged in this, it shouldn't take over your sleep cycle.
My sleep cycle is already messed up from the Ludum Dare.
Offline
pwiter wrote:
GP1 wrote:
pwiter wrote:
Ugh... Php is being annoying. I'm just gonna ditch this OAuth thing until later. Gonna go sleep now. It's 12:13 am.
Good idea. Don't get too engaged in this, it shouldn't take over your sleep cycle.
My sleep cycle is already messed up from the Ludum Dare.
Oh. That's cool. Anyway, if you need help with the PHP code, I might be able to help. I'm really good at PHP. Not so much on OAuth 2.0, though...
Offline
pwiter wrote:
GP1 wrote:
al-x wrote:
okay I didOMG! That looks awesome! But shouldn't we put a border around the canvas element so the player does not know that the green flag is not part of the stage? Scratch 2.0s viewer has a very light blue for a header, maybe we could do the same, but with orange instead if blue. Or something like that. I sorta like the header, come to think of it.
I don't see it for some reason.
Like, the viewer is the same as before? Well, you could try clearing your cache, that would work.
Offline
GP1 wrote:
al-x wrote:
GP1 wrote:
Awesome!! Can't wait to see it! Push it as soon as you can.okay I did
OMG! That looks awesome! But shouldn't we put a border around the canvas element so the player does not know that the green flag is not part of the stage? Scratch 2.0s viewer has a very light blue for a header, maybe we could do the same, but with orange instead if blue. Or something like that. I sorta like the header, come to think of it.
the green flag is still in the header just the header is white... so it is part of the stage in a way
Offline