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

Stable CloudOS JS Library #3

Open
alexkolson opened this issue Feb 13, 2014 · 3 comments
Open

Stable CloudOS JS Library #3

alexkolson opened this issue Feb 13, 2014 · 3 comments

Comments

@alexkolson
Copy link
Member

We need to stop making custom mods for each PCAA app we do to CloudOS.js, and instead put the custom mods in the PCAA app themselves. If we want CloudOS.js to be a usable, attractive bridge into CloudOS from javascript, we have to make it a stable, well-documented, semantically versioned codebase.

@JessieAMorris
Copy link
Member

You guys came out with a 1.0.0, so has this now been done?

@windley
Copy link
Member

windley commented Jul 3, 2014

That’s what I’m working on.

I’m putting a release version on Amazon S3 and we’ll link to that in apps that need the JS (could use CloudFront if things get too slow).

I want to get CloudOS.js out of each app’s js directory.

--phil--

On Jul 3, 2014, at 2:23 PM, Jessie A. Morris notifications@github.com wrote:

You guys came out with a 1.0.0, so has this now been done?


Reply to this email directly or view it on GitHub.

@windley
Copy link
Member

windley commented Jul 3, 2014

Here: https://s3.amazonaws.com/CloudOS_assets/js/CloudOS-1.0.0.js

--phil--

On Jul 3, 2014, at 2:24 PM, Phillip J. Windley Ph.D. phil@windley.org wrote:

That’s what I’m working on.

I’m putting a release version on Amazon S3 and we’ll link to that in apps that need the JS (could use CloudFront if things get too slow).

I want to get CloudOS.js out of each app’s js directory.

--phil--

On Jul 3, 2014, at 2:23 PM, Jessie A. Morris notifications@github.com wrote:

You guys came out with a 1.0.0, so has this now been done?


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants