Hi,
I know we can minimize the library, but I saw some mention that part of the
library is for the compiler. Would it be possible to remove that part?
Thanks
Fred

The compiler stuff is attached to the end.  You can simply chop it  
off.  Furthermore, the flapjax library is wrapped in a "module" that  
makes a portion of the Flapjax functions private.  The code to export  
public functions is lengthy.

I've attached a version of the library that removes the wrapper and  
the compiler functions.  It shaves about 10K off the uncompressed  
library.

Arjun

flapjax-no-compiler.js 60K Download

On Nov 3, 2009, at 23:40 , Fred Janon wrote:

I saw in the OOPSLA paper that Flapjax takes a page from Prototype for
some of its DOM and Javascript helpers.  I was wondering why not just
place a dependency on Prototype instead of copying the functionality?

- John

I usually use jQuery with Flapjax and I don't think Flapjax should be tied
to any specific Javascript framework.
I agree that Flapjax Dom manipulation is sometimes lacking compared to
Prototype or jQuery, and regret having to download both Flapjax and another
framework, when Flapjax largely supersedes the event management and Ajax
parts of these frameworks.
But Arjun no-compiler flapjax release + a minimal JS framework (say
Sizzle.js) is the ticket for flexibility and a smaller size

T25

I think the trick is to split Flapjax into three pieces:

1. core FRP
2. Reactive DOM
3. Additional stuff

We'll distribute 1+2+3 as "Flapjax."  1+2 is still useful,  
particularly in combination with prototype/jQuery.  Just 1 alone is  
slightly useless, but separating it from 2 gives us the option of  
writing a DOM layer that uses jQuery / Prototype for better browser  
interoperability.

Arjun