search

chrivers / pyjaco

Python to JavaScript translator
http://pyjaco.org
MIT License
140 stars 18 forks source link

py-builtins.js should be minified #5

Open dusty-phillips opened 12 years ago

dusty-phillips commented 12 years ago

When generate_library.py is run, the rulting py-builtins.js is a very large file. It would be ideal if generate_library could accept an option to run the output through a javascript minifier of some sort.

For long-term compatibility, this file should also be versioned (probably the same version as pyjaco itself).

Perhaps a little early for this suggestion, but distributing py-builtins.js over a CDN would also make it easier to promote and demo the project.

Neppord commented 12 years ago

-1 Den 28 dec 2011 01.19 skrev "Dusty Phillips" < reply@reply.github.com

:

When generate_library.py is run, the rulting py-builtins.js is a very large file. It would be ideal if generate_library could accept an option to run the output through a javascript minifier of some sort.

For long-term compatibility, this file should also be versioned (probably the same version as pyjaco itself).

Perhaps a little early for this suggestion, but distributing py-builtins.js over a CDN would also make it easier to promote and demo the project.

Reply to this email directly or view it on GitHub: https://github.com/chrivers/pyjaco/issues/5

dusty-phillips commented 12 years ago

Bringing the CDN discussion here from my blog ( http://archlinux.me/dusty/2011/12/27/pyjaco-and-jquery/ )

At this point, I don't think we need a formal CDN with load and geographic balancing. The key is to have the file uploaded somewhere so that documentation and blog entries can be written with sample code that "just works" without instructing the user to build and install the library. If you want to pop it up at something like http://pyjaco.org/jslib/py-builtins-1.0.0.js that would probably be sufficient for the time being.

I'm sure that you'll know in advance if the file is going to need a more scalable CDN, but at that point, the major CDNs would likely already have it hosted. If not, Amazon S3 might be a good option.

chrivers commented 12 years ago

I could make sub-domain, statis.pyjaco.org that redirects to a light-weight static web-server. The main site is actually hosted on a WSGI server to handle the AJAX live-compilation demo, and the latency and server load would not be a good match for static hosting.

Having it on static.pyjaco.org also means we can later redirect this sub-domain to a real CDN when we need to. I think this is a fine way to begin.

However, we need to agree on a more controlled release process. Right now the pyjaco/debian folder contains a debian package that we use internally (for pyjaco.org, among other projects), and I believe the debian/changelog file should conform to our general releases.

I'll continue this on the mailing list.

chrivers commented 12 years ago

The existing pypi release number is 1.0.0, so we'll start somewhere around there. I'll re-raise this issue on the mailing list.