flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: namespace for experimental components
Date Wed, 22 Jan 2014 15:39:03 GMT
If components are promoted to top level library,people will need to update
their code to update namespaces

Do you think it could be a problem?


2014/1/22 Maurice Amsellem <maurice.amsellem@systar.com>

> Actually, experimental component have their own namespace:
> http://flex.apache.org/experimental/ns , with no predefined prefix (no
> design.xml file)
>
> But this is not documented very well , if at all.
>
> Maurice
>
> -----Message d'origine-----
> De : carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] De la part
> de Carlos Rovira
> Envoyé : mercredi 22 janvier 2014 15:04
> À : dev@flex.apache.org
> Objet : namespace for experimental components
>
> Hi,
>
> maybe this was discussed at some time, but I'd want to know what's the
> general thinking about experimental library namespace.
>
> Since new experimental components are based on Spark arquitecture, I'd
> expect they use the spark prefix (i.e: <s:Accordion, <s:ColorPicker,
> <s:MaskedTextInput,...and so on.
>
> But instead they are instanced using the package where they live:
>
> xmlns:components="spark.components.*"
>
> and
>
> <components:MaskedTextInput />
>
> But "spark.components.*" are the spark default package
>
> What do you think about it? I'd expect to get
>
> xmlns:s="library://ns.adobe.com/flex/spark"
>
> and
>
> <s:MaskedTextInput />
>
> What do you think about it?
>
>
> --
> --
> Carlos Rovira
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

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