Still, I bet t5conduit would be easier, and with less code / featues. Who says that WRO4j works correctly at all times? As a t5conduit user, it work great, works great with tapestry and I haven't had a single bug with it.
On Nov 1, 2012, at 3:08 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > Not extactly NIH ... I will be letting WRO4J do all the heavy lifting. > The remainder doesn't amount to much. > > On Thu, Nov 1, 2012 at 12:05 PM, Lenny Primak <lpri...@aceinnovative.com> > wrote: >> Do I detect a bit of NIH going on here? Please let me be mistaken. >> >> On Nov 1, 2012, at 3:04 PM, Jochen Frey <joc...@jochenfrey.com> wrote: >> >>> Amen! >>> >>> On Nov 1, 2012, at 12:00 PM, Howard Lewis Ship <hls...@gmail.com> wrote: >>> >>>> We've also had a number of cases of committers coming on, dumping code >>>> (without tests or documentation), and disappearing. That causes a lot >>>> of havoc. I'd prefer to have fewer features, better supported, than a >>>> large ecosystem of broken and abandoned code. >>>> >>>> On Thu, Nov 1, 2012 at 11:59 AM, Howard Lewis Ship <hls...@gmail.com> >>>> wrote: >>>>> It's not always as simple as that. >>>>> >>>>> First, there is licensing; I can't just take a library; it has to be >>>>> properly granted to the ASF. >>>>> >>>>> Second, I'm hesitant to take on code "from the wild"; ultimately, the >>>>> T5 committers (primarily myself) end up taking on the responsibility >>>>> for the code; t5conduit does not even include tests. >>>>> >>>>> Further, more changes are likely needed as I've been changing some >>>>> APIs so that (specifically) it is possible to determine what >>>>> extensions map to JavaScript. So the code as is may not compile >>>>> against 5.4 since one key interface needed a new method. >>>>> >>>>> On Thu, Nov 1, 2012 at 11:54 AM, Lenny Primak <lpri...@aceinnovative.com> >>>>> wrote: >>>>>> Please consider t5conduit for inclusion into Tapestry. >>>>>> It already supports CoffeeScript and LessCSS >>>>>> No need to reinvent the wheel here. >>>>>> >>>>>> On Nov 1, 2012, at 2:20 PM, Howard Lewis Ship <hls...@gmail.com> wrote: >>>>>> >>>>>>> The conversion from CoffeeScript to JavaScript occurs on the server. >>>>>>> >>>>>>> The generated JavaScript is quite straight-forward for most cases. >>>>>>> >>>>>>> CoffeeScript is more concise than JavaScript; it includes a couple of >>>>>>> higher-order features, such as really smart loops, and smarter >>>>>>> handling of function parameters; providing defaults, and handling >>>>>>> extra arguments nicely. >>>>>>> >>>>>>> The -> and => syntax for defining functions is close to ideal for the >>>>>>> web, where you constantly introduce new functions. >>>>>>> >>>>>>> Each module is automatically packaged up inside a hygienic function. >>>>>>> All variables are declared before being used. CoffeeScript supports >>>>>>> variable interpolation inside strings. >>>>>>> >>>>>>> However, if you want to replace a module (by contributing an override >>>>>>> to the ModuleManager service), you can write that module is JavaScript >>>>>>> or CoffeeScript. >>>>>>> >>>>>>> In fact, I haven't actually added support for CoffeeScript to the >>>>>>> project; that will be a suggested add-on module that hasn't been >>>>>>> written. Currently, the build is responsible for compiling >>>>>>> CoffeeScript into JavaScript; what's getting packaged inside >>>>>>> tapestry-core.jar is JavaScript. >>>>>>> >>>>>>> In the future, there will be a module that will detect the ".coffee" >>>>>>> file extension, and convert that to JavaScript as needed, at runtime. >>>>>>> >>>>>>> Ive used CoffeeScript extensively over the last six months; I like it, >>>>>>> I like how my code looks, I think the code is easier to follow and >>>>>>> mantain. Brendan Eich thinks so too ... he's adapting idea from >>>>>>> CoffeeScript (and from Python, and elsewhere) into the next-generation >>>>>>> version of JavaScript. >>>>>>> >>>>>>> On Thu, Nov 1, 2012 at 11:10 AM, Thiago H de Paula Figueiredo >>>>>>> <thiag...@gmail.com> wrote: >>>>>>>> On Thu, 01 Nov 2012 16:02:21 -0200, Paul Stanton <p...@mapshed.com.au> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> ok, our usage of the term 'monkey-patch' is where the >>>>>>>>> misunderstanding is. >>>>>>>>> I mean, patch. not monkey-patch, in your definition. >>>>>>>> >>>>>>>> >>>>>>>> That's why I always told my students: use the right words, the right >>>>>>>> names, >>>>>>>> the right terminologies all the times, because otherwise people won't >>>>>>>> understand you. :) >>>>>>>> >>>>>>>> Monkey-patching in JavaScript and other dynamic-typed languages has a >>>>>>>> very >>>>>>>> specific definition: changing some function by overriding it through >>>>>>>> code in >>>>>>>> runtime. The source code is *not* changed. Patching, in the source code >>>>>>>> sense, is something completely different, because it doesn't occur in >>>>>>>> runtime, being done on the source itself. What you're doing is >>>>>>>> patching, but >>>>>>>> not monkey-patching at all. >>>>>>>> >>>>>>>> According to Wikipedia: http://en.wikipedia.org/wiki/Monkey_patch: >>>>>>>> >>>>>>>> A monkey patch is a way to extend or modify the run-time code of >>>>>>>> dynamic >>>>>>>> languages without altering the original source code. This process has >>>>>>>> also >>>>>>>> been termed duck punching.[1] >>>>>>>> >>>>>>>> Regarding the gains of using CoffeeScript: I've never used it, so I >>>>>>>> cannot >>>>>>>> answer that. >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thiago H. de Paula Figueiredo >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>>>>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Howard M. Lewis Ship >>>>>>> >>>>>>> Creator of Apache Tapestry >>>>>>> >>>>>>> The source for Tapestry training, mentoring and support. Contact me to >>>>>>> learn how I can get you up and productive in Tapestry fast! >>>>>>> >>>>>>> (971) 678-5210 >>>>>>> http://howardlewisship.com >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>>>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>>>>> >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Howard M. Lewis Ship >>>>> >>>>> Creator of Apache Tapestry >>>>> >>>>> The source for Tapestry training, mentoring and support. Contact me to >>>>> learn how I can get you up and productive in Tapestry fast! >>>>> >>>>> (971) 678-5210 >>>>> http://howardlewisship.com >>>> >>>> >>>> >>>> -- >>>> Howard M. Lewis Ship >>>> >>>> Creator of Apache Tapestry >>>> >>>> The source for Tapestry training, mentoring and support. Contact me to >>>> learn how I can get you up and productive in Tapestry fast! >>>> >>>> (971) 678-5210 >>>> http://howardlewisship.com >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>> >>> >>> --- >>> joc...@jochenfrey.com >>> +1.415.366.0450 >>> @jochen_frey >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
