874
edits
Labs/Jetpack/Reboot FAQ: Difference between revisions
added another question
(added another question) |
(added another question) |
||
| Line 72: | Line 72: | ||
Right now we need a better solution for this. One super lightweight solution is to just use a wiki page with a simple format that <tt>cfx</tt> can automatically retrieve and parse. Narwhal uses github for everything and a <tt>catalog.json</tt> file to index packages. We could potentially use bitbucket... Or if bitbucket/github have a developer API and some concept of "tagging" projects, we might be able to e.g. just define the available packages as all projects tagged with <tt>#cfx-package</tt> or something. | Right now we need a better solution for this. One super lightweight solution is to just use a wiki page with a simple format that <tt>cfx</tt> can automatically retrieve and parse. Narwhal uses github for everything and a <tt>catalog.json</tt> file to index packages. We could potentially use bitbucket... Or if bitbucket/github have a developer API and some concept of "tagging" projects, we might be able to e.g. just define the available packages as all projects tagged with <tt>#cfx-package</tt> or something. | ||
'''Why doesn't the Jetpack reboot just use narwhal and tusk?''' | |||
Narwhal is an awesome project, but it's just moving too fast right now for us to use it as a dependency. cfx is similar enough to narwhal/tusk that we might eventually be able to move over to it, and substitute out current Python code for JS. | |||