flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Left Right <olegsivo...@gmail.com>
Subject Re: Flex and names spaces in MXML
Date Sat, 17 Mar 2012 18:54:27 GMT
Well, it currently does: you have to use some Flex-framework-related
namespace to compile things that have nothing to do with the framework. If
compiler will suddenly acquire additional special knowledge of framework
classes (unfortunately, it already has quite a bit), it will create
coupling of any non-framework code with the framework - this is spoiling
the non-framework code.

The talk about what namespace to use for components developed at Apache
Flex is in the different thread though :) I see how it may be confusing,
because the word "namespace" is used extensively both here and there.

What I'm being against here is expressed simply:

Compiler should not be aware of the framework code.
MXML should not be aware of the framework code.

The problem:

The compiler and MXML are already aware of the framework code, and it
creates undesirable effects. Possible solution: create a very small subset
of AS3 code that helps MXML with the final goal to remove all such code,
when MXML code generation is revised. Of course, not to add dependencies
and of course not to make cosmetic changes to MXML, because it requires a
more fundamental fix, which may or may not make cosmetic fixes possible.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message