Combining amber files into a single minified file

Hi Sebantian,

Thanks for replying.

Yes I did try the "concat all deploy files" approach, but for some reason that I couldn't dig into easily the system wouldn't start (got lots of "stack exceeded" errors). That was with the released amber version sans requirejs. So I just switched to the master branch and tried my luck with requirejs and it worked! With requirejs, I no longer needed to bother about loading files in the right dependency order, which I felt was the problem when I did the concat. Anyway, good times ahead indeed!

Btw I popped by your airflowing site and you say you pretty much developed the whole thing yourself (2k+ classes and 26k+ methods?!) and you use amber and pharo. Impressive! I've now landed on the same combo for my work which is like a wiki/shareboard for indian classical music notation and recordings. Do you have some kind of writeup or pointers on your current amber-pharo workflow and such tips? I'm somewhat new to both environments, but I do feel a nice impedance match with my brain, so am quite excited about this combo. Also, Helios is coming along nicely with great support for a keyboard centric workflow.

Best,

-Kumar

On Tuesday, November 5, 2013 9:27:00 PM UTC+5:30, Sebastian Sastre wrote:

hey Sri,

I only combine for deploy (not development) so the IDE isn't there.

But yeah.. lately I was thinking that it might be appealing to have a dev combined for the stuff you need to develop on the server itself (social media apps for instance)

Anyway, when I combine I just:

1. take all the .deploy files and concatenate them in a new file named source.js

2. uglifyjs source.js into all1.js (where 1 is your next version name)

3. publish

Doing that from a simple bash script is comfortable enough for me

Looking forward for the next amber version with require, sounds exciting

On Nov 5, 2013, at 10:45 AM, Srikumar Subramanian <[hidden email]> wrote:

Hi all,

I'm new to Amber and am quite excited to explore it in conjunction with Pharo.

Regarding deployment, it is good to have a single minified file like "amber_deploy.min.js"

to save space and number of http requests. This has been discussed here before, but 

I can't seem to get a clear solution from those threads. 

Given that amber is now using requirejs, I thought this ought to be easy and tried it myself. 

Here is the build result and instructions based on what worked for me -

https://github.com/srikumarks/amber-combined

The amber_helios.html and amber_devel.html can both be opened in a browser

and used. I haven't sorted out the webdav problem yet. It'll be nice to have a grunt

task or something to make these deployable files at any time during webdav-based

development. (I'm new to grunt as well, so lots to catch up here).

-Kumar

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.

To unsubscribe from this group and stop receiving emails from it, send an email to amber-lang+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.