You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Jesse Kuhnert <jk...@gmail.com> on 2008/06/06 19:49:38 UTC
Re: T5 JSONObject issues
We ran across a similar issue in T4 and opted to use a LinkedHashMap
internally there in order to get deterministic ordering of the entries
without any real performance hits.
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5 JSONObject issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
Tell me about it!
On Fri, Jun 6, 2008 at 11:24 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> Sure sure, was "just sayin.."..that we made a couple improvements to
> it. (though I question the string literal stuff now)
>
> javascript can be a real finicky bitch sometimes eh? ;)
>
> On Fri, Jun 6, 2008 at 2:00 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>> We can hold that issue in reserve, but I'm looking at changing the
>> order of evaluation on the client side to not care as much, which I
>> think is more in line with the prevalent philosophy of JavaScript and
>> Prototype.
>>
>> On Fri, Jun 6, 2008 at 10:49 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
>>> We ran across a similar issue in T4 and opted to use a LinkedHashMap
>>> internally there in order to get deterministic ordering of the entries
>>> without any real performance hits.
>>>
>>> --
>>> Jesse Kuhnert
>>> Tapestry / OGNL / Dojo team member/developer
>>>
>>> Open source based consulting work centered around
>>> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5 JSONObject issues
Posted by Jesse Kuhnert <jk...@gmail.com>.
Sure sure, was "just sayin.."..that we made a couple improvements to
it. (though I question the string literal stuff now)
javascript can be a real finicky bitch sometimes eh? ;)
On Fri, Jun 6, 2008 at 2:00 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> We can hold that issue in reserve, but I'm looking at changing the
> order of evaluation on the client side to not care as much, which I
> think is more in line with the prevalent philosophy of JavaScript and
> Prototype.
>
> On Fri, Jun 6, 2008 at 10:49 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
>> We ran across a similar issue in T4 and opted to use a LinkedHashMap
>> internally there in order to get deterministic ordering of the entries
>> without any real performance hits.
>>
>> --
>> Jesse Kuhnert
>> Tapestry / OGNL / Dojo team member/developer
>>
>> Open source based consulting work centered around
>> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5 JSONObject issues
Posted by Howard Lewis Ship <hl...@gmail.com>.
We can hold that issue in reserve, but I'm looking at changing the
order of evaluation on the client side to not care as much, which I
think is more in line with the prevalent philosophy of JavaScript and
Prototype.
On Fri, Jun 6, 2008 at 10:49 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> We ran across a similar issue in T4 and opted to use a LinkedHashMap
> internally there in order to get deterministic ordering of the entries
> without any real performance hits.
>
> --
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org