> But to me, the advantages of abstracting
implementations with Interfaces outweighs the effort to “fake” namespaces
in the JS side.
This is essentially a namespace anyway. The interface is the namespace, if
you make the framework interface centric, then casting to the concrete type
is the public
OK. So I’ll just use public for now and put @private in the ASDocs. We’ll
figure it all out later.
On Nov 12, 2015, at 7:10 PM, Alex Harui wrote:
>
>
> On 11/12/15, 8:52 AM, "Harbs" wrote:
>
>> Here’s where I am (and why I’m asking):
>>
>> I figured out how to use Document and Element as t
On 11/12/15, 8:52 AM, "Harbs" wrote:
>Here’s where I am (and why I’m asking):
>
>I figured out how to use Document and Element as the underlying structure
>for JS XML. But to use them correctly, I need to manipulate the internal
>structure of one XML object from another.
>
>One example: in Acti
Here’s where I am (and why I’m asking):
I figured out how to use Document and Element as the underlying structure for
JS XML. But to use them correctly, I need to manipulate the internal structure
of one XML object from another.
One example: in ActionScript XML you can call appendChild to move
On 11/12/15, 3:16 AM, "Harbs" wrote:
>While working on XML, I have a situation where I’d like to use an
>internal namespace for some functions (like mx_internal and tlf_internal
>scattered around the classic Flex SDK). I do not see internal used in
>FlexJS. Was this a conscious decision, or not
