My plan is to have it "just work" by just having it be a normal attribute and writing a presentation type for CSSDeclaration. I'll call for help if that doesn't pan out.
On Aug 31, 2010, at 16:31, Henry Minsky <[email protected]> wrote: > If you run into any twisty passages in the compiler - > debug control path, > I'l be happy to > do some of the plumbing if you want. > > On Tue, Aug 31, 2010 at 9:26 AM, P T Withington <[email protected]> wrote: > I'm working on > > LPP-9311 flash halts in backtrace mode but not in debug mode when dealing > with deeply nested views > > and one piece of the puzzle (I think) is to ensure that the debugger's notion > of maximum stack depth is within the underlying runtime's limit. In the case > of SWF, we have a canvas property `scriptlimits` that lets you specify the > maximum recursion and timeout values for the player. (See LPP-6132 > debug.backtraceStack.maxDepth attribute should be copied form scriptlimits > recursion depth). > > To do this, I plan to pass a debugger `preferences` object through the > console window (as embodied by the <debug> tag). Since I'm in there, I > figure I might as well surface this in the tag, so you will be able to say > things like: > > <debug ... preferences="print-length: 256, print-depth:32, > show-internal-properties: true" /> > > My thought is to compile the preferences as a CSS properties list and use the > normal CSS mapping of hyphens to camel case, e.g.: > > camel-case -> camelCase > > to translate CSS properties to debugger attributes. > > Comments? > > > > -- > Henry Minsky > Software Architect > [email protected] > >
