No need to force it to 5.0, there are enough great features already :)
I still have to go through tapestry.js code completely to enumerate
used functions.
Then tests to cover the usages. And learn more tapestry internals :)
Davor Hrg
On Sat, Feb 23, 2008 at 6:30 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> This sounds great, though I've been thinking that JavaScript agnostics
> should come in 5.1. I also like the ideas about having a mechanism to
> automatically combine and minimize all the library JavaScript for a
> page into a single request.
>
> I really want to get things stable now. My personal target is a
> release, or at least a release candidate, by April 1st. In addition,
> I'm going to need a chunk of March to prepare examples for my upcoming
> speaking engagements.
>
>
>
> On Sat, Feb 23, 2008 at 9:12 AM, Davor Hrg <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I've been writing a document do gather thoughts on what tapestry
> > javascript should look like(server and js side).
> >
> > Even prototype is no longer a small library, 145 KB takes time to load
> > even from cache,
> > and parsing 150 KB javascript file takes about 150 ms for firefox2 on
> > 2 GHz machine.
> > (Firefox3 seems to be a lot faster)
> >
> > Another thing is, that prototype's way of writing things is not easy
> > to extract dependencies.
> >
> > for example
> > someFunc.bindAsEventListener(this);
> >
> > after all it is called prototype for it's approach.
> >
> > then, the fix for prototype .visible is not done way -i'd like it
> > $$(".t-invisible").each(function(element)
> > {
> > element.hide();
> > element.removeClassName("t-invisible");
> > });
> >
> > the problem is that prototype is not using getComputedStyle
> > which is different for different browsers but can be easily ported.
> >
> > I would not like to argue much on which library is the best,
> > but the approach where tapestry.js uses more neutral style would make
> > abstracting the library support easy:
> >
> > this is more dojo-like and easier to replace
> >
> > Tapestry.bindAsEventListener(elem, "onclick", callbackFunc)
> > Tapestry.bindAsEventListener(elem, "onclick", scopeObj, callbackFunc)
> >
> > or making function that checks visibility:
> > Tapestry.visible(element)
> >
> >
> >
> > I would much like to try put together the js abstraction for the first
> release,
> > and having three implementations:
> > minimal (prototype based, hand made)
> > scriptaculous
> > dojo
> >
> > would be a great thing to have.
> >
> >
> > I'll look into running existing selenium tests that concern javascript
> parts,
> > and try to make new ones before changing tapestry.js
> >
> >
> > Davor Hrg
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
