Download Snap Source link

jmoenig / Snap

a visual programming language inspired by Scratch

http://snap.berkeley.edu

GNU Affero General Public License v3.0

1.51k stars 745 forks source link

Download Snap Source link #347

Closed cycomachead closed 5 years ago

cycomachead commented 10 years ago

Depending on what we do (re #346) we could change the zip file URL to point to the most recent version on github. All we need to do is use this: https://github.com/jmoenig/Snap--Build-Your-Own-Blocks/archive/master.zip It will always be updated. :)

jmoenig commented 10 years ago

Sure. Thing is, I often don't update the s.b.e. distro right away with every commit. Sometimes, in between releases the github repo actually hosts something buggy (as when I'm pulling a pull-request with bugs in it, before I fix them). Maybe Github new-ish "release" feature addresses this issue, I haven't checked into this, though, as it's apparently not a standard git feature (Bitbucket doesn't seem to have it).

xtitter commented 10 years ago

I think we can come up with a better workflow that will even make Jens' life easier. A few pieces:

use git branches to manage production verses development versions, like most projects.
use a snap.b.e commit hook to automagically pull from the production branch when its updated
have a build script (called by the commit hook) that does the file renaming and, perhaps, modification to the contents (of snap.html). We can keep the default format working as a webapp for those that want to stay buildless (on githubpages, for instance)

Would you be open to using git branches, Jens? It would involve more git fu on your part, unfortunately, but we'd be using the tools as they were intended to be used.

Michael, are you up for some server-side writing?

cycomachead commented 10 years ago

Agreed. We should get this working for all BJC stuff. As part of a process we could also work on other best practices like minifying code and removing comments which would dramatically reduce the size of loading snap.

Jens, GitHub's releases feature uses tags, which are a standard Git feature and then expands upon it.

jmoenig commented 10 years ago

I'd love to chat about these things ("best practices", minifying, git-branches) in person sometimes. I'll be around in SF in the week before Easter (mid April). Anybody around there then? Otherwise we could also Skype at some time, now that I'm on better bandwidth...

cycomachead commented 10 years ago

Yep, we should all be here then! :) (Berkeley's Spring break is in 2 weeks so most of us Pluswill be gone then). A meeting in person sounds like a great idea!

Michael Ball http://www.michaelballphoto.com Photos & iPhone Apps

On Tue, Mar 11, 2014 at 2:48 PM, Jens Mönig notifications@github.comwrote:

I'd love to chat about these things ("best practices", minifying, git-branches) in person sometimes. I'll be around in SF in the week before Easter (mid April). Anybody around there then? Otherwise we could also Skype at some time, now that I'm on better bandwidth...

— Reply to this email directly or view it on GitHubhttps://github.com/jmoenig/Snap--Build-Your-Own-Blocks/issues/347#issuecomment-37352945 .

marwahaha commented 10 years ago

@jmoenig Would you like this? I may be able to help.

hotsphink commented 8 years ago

Sorry for the +1 comment, but I just started looking at snap and quickly found the "Download Source" link in the UI, which was good, but then it unpacked a bunch of OSX-specific junk files, which made it look pretty half-baked. My immediate thought was "why isn't this on github or somewhere?" It took me some time to discover that it is on github. Cloning the github repo makes far more sense for my usage than downloading a zip file snapshot. From the point of view of a potential contributor, the current setup feels a little sketchy. I would recommend at the least getting rid of the osx droppings and making README.md and/or readme.txt point to the github page.

cycomachead commented 5 years ago

Closing since this now points to the latest GitHub release.

brianharvey commented 5 years ago

The repo has a .gitignore that includes .DS_Store; what is the "OSX-specific junk" in the repo?

marwahaha commented 5 years ago

I'd guess that removing .DS_Store from the .gitignore would increase the chance of someone checking-in "OSX-specific junk"....

jmoenig commented 5 years ago

I think he was talking not about the github repo but about the zip file we used to have. When you make a zip file on a Mac it does not play well on Windows computers, and often creates some folders and files that look like OSX junk when you unpack it. I think it was just that and that @hotsphink was probably even right about it...