il.com [mailto:carlos.rov...@gmail.com] De la part de
> Carlos Rovira
> Envoyé : mercredi 22 janvier 2014 16:39
> À : dev@flex.apache.org
> Objet : Re: namespace for experimental components
>
> If components are promoted to top level library,people will need to update
> their
urice
-Message d'origine-
De : carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] De la part de
Carlos Rovira
Envoyé : mercredi 22 janvier 2014 16:39
À : dev@flex.apache.org
Objet : Re: namespace for experimental components
If components are promoted to top level library,people w
4 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 component
s.rov...@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 n
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:
But "spark.components.*" are the spark default package
