[Prev] Thread [Next]  |  [Prev] Date [Next]

[Caja] Re: Fixes uses of cajita's taming API and improves primFreeze speed. erights Fri Jun 26 00:00:28 2009

Still looking at your first issue below -- the disabling of some taming
methods by cajita-debugmode -- in light of new issue 1058. This first
issue is not yet addressed. All the rest are ready for judgment. Thanks.
File src/com/google/caja/cajita-debugmode.js (right):
Line 355: 'grantEnum', noop,
Looking at this disabling again in light of issue 1058.
File src/com/google/caja/demos/calendar/demo-cajoled.html (right):
Line 152: ___.ctor(StringInterpolation, Object, 'StringInterpolation');
On 2009/05/20 20:09:27, BenL wrote:
NiceNeighbour doesn't explain what optSuper and optName are for.

File src/com/google/caja/demos/lolcat-search/search.html (right):
Line 66: ___.grantRead(___.sharedImports, 'StringInterpolation');
On 2009/05/20 20:09:27, BenL wrote:
Why not ___.grantFunc and eliminate ___.frozenFunc above?

Line 492: "___.grantFunc(testImports, 'assertEquals');" +
On 2009/05/20 20:09:27, BenL wrote:
Are both the frozenFunc and grantFunc calls needed? NiceNeighbour
suggests not.

File tests/com/google/caja/parser/quasiliteral/taming_test.html (right):
Line 88: ___.handleGeneric(MyRootNamespace.SubSpace, 'attenuated',
function (f) {
On 2009/05/20 20:09:27, BenL wrote:
I'm not sure I like the name ... shouldn't this (and friends) be

The naming style used by these taming functions is to use *Func only for
marking things as simple-functions, which are first class in Cajita. All
the others functions for taming methods assume that the function
involved is exophoric, and so shouldn't be accessible from Cajita.
Perhaps handleGenericMethod would be clearer? I think I'll leave this