Re: Whiteboard Code Namespaces

2012-01-17 Thread Omar Gonzalez
I think I'll just stick with "org.apache.flex...", we'll have to support legacy with Flex SDK so it doesn't make sense to change the "spark.components..." etc namespaces. Plus like someone said, its the whiteboard area. -omar

Re: Whiteboard Code Namespaces

2012-01-16 Thread Martin Heidegger
On 17/01/2012 09:34, Omar Gonzalez wrote: Before I started on the StringValidator I committed to my whiteboard I sat and stared at the screen for a few minutes trying to decide which namespace to use. Ultimately I went with "org.apache.flex.validators" because I did not want to confuse people by

Re: Whiteboard Code Namespaces

2012-01-16 Thread Greg Reddin
I really think it doesn't matter at all. The code is not released and will be moved to a more appropriate place before it gets released. At that time it will probably be more obvious what the namespace should be. Sent from my mobile device. On Jan 16, 2012, at 6:34 PM, Omar Gonzalez wrote: >

Whiteboard Code Namespaces

2012-01-16 Thread Omar Gonzalez
Before I started on the StringValidator I committed to my whiteboard I sat and stared at the screen for a few minutes trying to decide which namespace to use. Ultimately I went with "org.apache.flex.validators" because I did not want to confuse people by using "spark.validators". However, I still