Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to ZPM #1

Merged
merged 18 commits into from
Mar 6, 2014
Merged

Updates to ZPM #1

merged 18 commits into from
Mar 6, 2014

Conversation

zefhemel
Copy link

@zefhemel zefhemel commented Mar 5, 2014

Ok this is kind of a big PR with many unrelated commits which will go away once you merge zed/master into your TheKiteEathingTree/zpm branch. The commits that are relevant to see what I did here:

  1. zedapp@f169d09
  2. zedapp@49f25d4

Basically I implemented what I mentioned in zedapp#90:

  • Configs now have a packages key, whenever you add stuff to this, the URI in question (more on URIs later) will be installed and once installed, will be loaded.
  • URIs can either be full URLs, or of the form gh:username/repo:branch, or gh:username/repo (master is implicit), bb:username/repo or bb:username/repo:branch which would all be expanded to their HTTPS equivalents

Things that I changed along the way:

  • Extensions are now called packages (and live under /packages)
  • package.json no longer need a configFile key (config.json is assumed), this is for practical reasons, but it also has the advantage of requiring less options in package.json
  • package.json no longer requires an id key, since "pathified" versions of the URIs are used (colons are replaced with a slash).

As a demo, I moved out the spell checker into its own package: https://github.com/zedapp/spellchecker you can install it either the interactive way, or by adding "gh:zedapp/spellchecker" to your packages key in user.json, watch zed::log for messages.

I've also tested it by putting a (previously) not installed package in /zedconfig.json and it successfully installs the package and loads it only in that project and not others.

What do you think?

allie-wake-up and others added 18 commits February 21, 2014 01:25
…ite and delete configfs files. Created api to download files. Added a handler that fires once after configuration loads.
…stall extension command to installed extensions page. Changed how updating works to try to make it less likely that an extension breaks during a failed update. If you're in the configuration project when installing, updating or uninstalling an extension the filelist now reloads
Conflicts:
	app/config/api/zed/config_fs.js
	app/config/api/zed/http.js
	app/config/api/zed/project.js
	app/js/sandbox.js
@zefhemel
Copy link
Author

zefhemel commented Mar 5, 2014

Btw, it may look like I rewrote everything, this is no the case ;) I did switch over the plugins to CommonJS style (removed AMD junk), which is the diff is a bit skewed.

@allie-wake-up allie-wake-up merged commit 9698b6e into allie-wake-up:zpm Mar 6, 2014
@allie-wake-up
Copy link
Owner

Awesome, this works great! Very excited about this...it's so cool.

allie-wake-up pushed a commit that referenced this pull request Apr 11, 2014
Updating to the latest master
allie-wake-up pushed a commit that referenced this pull request Jan 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants