Re: Apache Flex Namespace URI

Hi, > Why do you think it won't allow for multiple sets of components? Couldn't > we just use different namespaces and URLs for each set? We don't have to use different namespaces for each set of components just different package names. Separate sub projects in the SDK can share the same name sp

Re: Apache Flex Namespace URI

Hi, > I'd suggest http://flex.apache.org/ns (meaning "namespaces") as a > prefix for namespace URLs - things like http://flex.apache.org/spark > might collide with Flex website content. Unless there are any better ideas I think this is a winner and I'll change what I've submitted to this. We ca

Re: Apache Flex Namespace URI

> From: "Bertrand Delacretaz" > > If you want those namespace URLs to eventually point to documents they > should be under http://flex.apache.org which will belong to this > project once graduated. > > I'd suggest http://flex.apache.org/ns (meaning "namespaces") as a > prefix for namespace URLs -

Re: Apache Flex Namespace URI

On Fri, Mar 16, 2012 at 5:02 AM, Justin Mclean wrote: > ...So far I think we mostly agree that having real URLs is nice but have no > idea what those URL should be... > ...The one I've currently committed is http://www.apache.org/flex ... Note that the Flex project cannot own that URL - that be

Re: Apache Flex Namespace URI

On Friday, March 16, 2012, Tink wrote: > If we use this URL as the namespace > > http://www.apache.org/flex > > when we have a new component set, what new URL would you then use? > > We should start out with this in mind, so something like > > http://www.apache.org/flex/COMPONENT_SET_NAME > > to e

Re: Apache Flex Namespace URI

If we use this URL as the namespace http://www.apache.org/flex when we have a new component set, what new URL would you then use? We should start out with this in mind, so something like http://www.apache.org/flex/COMPONENT_SET_NAME to enable use to add sets in the future. As or current comp

Re: Apache Flex Namespace URI

> > This really won't allow for multiple sets of components under Apache >> moving forward. >> > Why do you think it won't allow for multiple sets of components? Couldn't we just use different namespaces and URLs for each set? Maybe I'm not understanding something correctly. Also, I think it'd b

Re: Apache Flex Namespace URI

On 16 Mar 2012, at 04:02, Justin Mclean wrote: Hi, So far I think we mostly agree that having real URLs is nice but have no idea what those URL should be. Are spilt if we should have a small or large number of new namespaces. The one I've currently committed is http://www.apache.org/flex (

Re: Apache Flex Namespace URI

Hi, So far I think we mostly agree that having real URLs is nice but have no idea what those URL should be. Are spilt if we should have a small or large number of new namespaces. The one I've currently committed is http://www.apache.org/flex (look in flex-config.template.xml and/or flex-confi

Re: Apache Flex Namespace URI

On 3/14/2012 12:36 PM, Omar Gonzalez wrote: On Wednesday, March 14, 2012, Jeffry Houser > wrote: > On 3/14/2012 5:39 AM, Justin Mclean wrote: >> >> Hi, >> >>> I don't know about Flex but in many cases changing namespace URIs is >>> problematic >> >> They have no

Re: Apache Flex Namespace URI

On Wednesday, March 14, 2012, Jeffry Houser wrote: > On 3/14/2012 5:39 AM, Justin Mclean wrote: >> >> Hi, >> >>> I don't know about Flex but in many cases changing namespace URIs is >>> problematic >> >> They have no effect on ActionScript code (ie 99% of the SDK). It would effect MXML code > >

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 8:39 AM, Jeffry Houser wrote: > It doesn't matter if it's a valid URL. The current namespace URL aren't. > In my experience most namespace URLs aren't. None may be valid now, but in the future we may find the need to link to a document or scheme. I would prefer that fr

Re: Apache Flex Namespace URI

Hi, > It doesn't matter if it's a valid URL. The current namespace URL aren't. In > my experience most namespace URLs aren't. Sure they don't have to be and it's not essential in any way. Just think it would be nice if new name spaces were valid URLs then each application would contain a (val

Re: Apache Flex Namespace URI

On 3/14/2012 8:32 AM, Bertrand Delacretaz wrote: On Wed, Mar 14, 2012 at 1:27 PM, Jeffry Houser wrote: ... I'm all for following the 'Adobe" convention and using something like this: http://www.apache.org/flex/mxml ... Which will never be a valid URL, as Apache Flex won't own that URL space.

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 1:27 PM, Jeffry Houser wrote: > ... I'm all for following the 'Adobe" convention and using something like > this: > > http://www.apache.org/flex/mxml >... Which will never be a valid URL, as Apache Flex won't own that URL space. Don't you think http://flex.apache.org/ns

Re: Apache Flex Namespace URI

On 3/14/2012 5:39 AM, Justin Mclean wrote: Hi, I don't know about Flex but in many cases changing namespace URIs is problematic They have no effect on ActionScript code (ie 99% of the SDK). It would effect MXML code Which is 99% of the code people write. Changing namespaces will cause mor

Re: Apache Flex Namespace URI

Yeah course. I thought Justin was implying they should be working URLs, which would be nice, but they are not. Tink Omar Gonzalez wrote: >On Wednesday, March 14, 2012, Tink wrote: >> We need to support separate names spaces for spark, mx and fx though. >> >> Tink >> >> > >org.apache.flex.spar

Re: Apache Flex Namespace URI

Hi, > We need to support separate names spaces for spark, mx and fx though. I'm not proposing we change the existing name spaces. Do you mean packages in new names spaces? Thanks, Justin

Re: Apache Flex Namespace URI

On Wednesday, March 14, 2012, Tink wrote: > We need to support separate names spaces for spark, mx and fx though. > > Tink > > org.apache.flex.spark... org.apache.flex.mx... org.apache.flex.fx... That doesn't work? -omar

Re: Apache Flex Namespace URI

We need to support separate names spaces for spark, mx and fx though. Tink Justin Mclean wrote: >Hi, > >> I don't know about Flex but in many cases changing namespace URIs is >> problematic >They have no effect on ActionScript code (ie 99% of the SDK). It would effect >MXML code (but only fi

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 10:39 AM, Justin Mclean wrote: > ...It would be easy enough to have an incubating URI and another URI when we > graduate. > They could even point to the same manifest file (basically a list of classes > for that namespace) ah ok, cool then. -Bertrand

Re: Apache Flex Namespace URI

Hi, > I don't know about Flex but in many cases changing namespace URIs is > problematic They have no effect on ActionScript code (ie 99% of the SDK). It would effect MXML code (but only files using the new name space) if a URI was changed. As far as I'm aware anyway there may be a something I

Re: Apache Flex Namespace URI

On Wed, Mar 14, 2012 at 10:18 AM, Justin Mclean wrote: > ...Rather than using "http://www.apache.org/flex"; should we use > "http://incubator.apache.org/flex/"; > as the namespace URI and change to "http://flex.apache.org";  (which I assume > would be the correct URL) > when we graduate?  Having