You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Tink <fl...@tink.ws> on 2012/03/16 10:14:48 UTC
MobileAlert - quetwo
I immediately noticed when looking at this is that it extends
SkinnablePopUpContainer.
In my mind an Alert isn't a container. You do not create one and then
put contents in it, and therefore you get unnecessary overhead with
the container, and from outside the API will look like you can add
elements to it.
I would suggest we add a SkinnablePopUpComponent, then and Alert can
be added on top of that. Then do we need a MobileAlert and Alert, or
can we not just have a different skin for the 2 versions?
Tink
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 (look
> in flex-config.template.xml and/or flex-config.xml) so until we come
> up with something better that what it will be.
>
> Thanks,
> Justin
>
Re: MobileAlert - quetwo
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
Alex,
I'm hoping for something more generic than that. Only one of the 6 or so
of the mobile apps I've published were able to utilize the
View/ViewApplication/TabbedViewApplication construct. This should be able
to be used from any Mobile project.
-Nick
On Fri, Mar 16, 2012 at 11:45 AM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 3/16/12 5:09 AM, "Nicholas Kwiatkowski" <ni...@spoon.as> wrote:
>
> > My only thought on having two versions (a MobileAlert and an Alert) is
> that
> > the MobileAlert would cut out some functionality in order to be a bit
> > quicker (for example, not launching via the PopUpManager, because we
> really
> > wouldn't use any of that functionality other than the ability to display
> > the component).
> I agree. I would think a MobileAlert would push itself as a view.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: MobileAlert - quetwo
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
I'll play around with it and see what I can come up with. I do know that
my testing suite did NOT like your PopUpExample.mxml being in there :)
(this is a library on my side, which caused all sorts of errors).
-Nick
On Fri, Mar 16, 2012 at 6:43 PM, Tink <fl...@tink.ws> wrote:
> Done.
>
> I've also added an example application, and example component that extends
> SkinnablePopUpComponent that requires a single button skin part, that when
> clicked closes the popup, and obviously a skin for it (it just contains a
> button).
>
> One thing I couldn't do was add the modal styles in
> SkinnablePopUpComponent. You'll see there in the file, but commented out as
> when I uncomment them i get the following error:
>
> Declaration of style 'modalTransparencyDuration' conflicts with previous
> declaration in /Users/tinktink/Documents/**tink/libraries/apache
> flex/whiteboard/quetwo/**MobileAlert/src/org/apache/**spark/components/**
> supportClasses/**SkinnablePopUpComponent.as.
>
> Yet without them you can't specify these as inline styles on the component
> (see they are commented out in the example application).
>
> Anyone shed any light on the problem here?
>
> Tink
>
>
>
> On 16 Mar 2012, at 21:50, Nicholas Kwiatkowski wrote:
>
> Do it. I'm working on getting the iOS skin to look proper, which should
>> stay out of the way of that work.
>>
>> -Nick
>>
>> On Fri, Mar 16, 2012 at 4:14 PM, Tink <fl...@tink.ws> wrote:
>>
>> On 16 Mar 2012, at 19:27, Jonathan Campos wrote:
>>>
>>> On Fri, Mar 16, 2012 at 1:40 PM, Tink <fl...@tink.ws> wrote:
>>>
>>>>
>>>> These 2 things are what PopUpManager takes care of for you. If you don't
>>>>
>>>>> use PopUpManager it will still get included, as it's instantiated in
>>>>> SystemManager.
>>>>>
>>>>>
>>>>
>>>> I too have created a variety of popups and alerts for mobile for my
>>>> projects. I would prefer that we stick with using the popupmanager as it
>>>> is
>>>> the way most people are used to working with the framework.
>>>>
>>>> Also I would prefer to have a modal ability as with tablet applications
>>>> modal is still very important.
>>>>
>>>> --
>>>> Jonathan Campos
>>>>
>>>>
>>> Spark moved away from the direct use of the PopUpManager, with
>>> SkinnablePopUpContainer, which used it internally.
>>> I think if we added a SkinnablePopUpComponent (which would be really
>>> useful anyway as most popups I have had to make, generally don't need to
>>> be
>>> containers), it would then be ideal to extend for an Alert.
>>>
>>> One thing I would like to see implemented in the new
>>> SkinnablePopUpContainer, and added to the PopUpSkinnableContainer, is the
>>> ability to center the popup, and keep it centered. They should also
>>> contain
>>> the metadata for the modal styles so they can be set inline.
>>>
>>> Quite happy to throw one of these together and add it to Nick's
>>> whiteboard
>>> space, and then he can take a look whether he wants to use it for his
>>> Alert.
>>>
>>> Tink
>>>
>>>
>
Re: MobileAlert - quetwo
Posted by Tink <fl...@tink.ws>.
Done.
I've also added an example application, and example component that
extends SkinnablePopUpComponent that requires a single button skin
part, that when clicked closes the popup, and obviously a skin for it
(it just contains a button).
One thing I couldn't do was add the modal styles in
SkinnablePopUpComponent. You'll see there in the file, but commented
out as when I uncomment them i get the following error:
Declaration of style 'modalTransparencyDuration' conflicts with
previous declaration in /Users/tinktink/Documents/tink/libraries/
apache flex/whiteboard/quetwo/MobileAlert/src/org/apache/spark/
components/supportClasses/SkinnablePopUpComponent.as.
Yet without them you can't specify these as inline styles on the
component (see they are commented out in the example application).
Anyone shed any light on the problem here?
Tink
On 16 Mar 2012, at 21:50, Nicholas Kwiatkowski wrote:
> Do it. I'm working on getting the iOS skin to look proper, which
> should
> stay out of the way of that work.
>
> -Nick
>
> On Fri, Mar 16, 2012 at 4:14 PM, Tink <fl...@tink.ws> wrote:
>
>> On 16 Mar 2012, at 19:27, Jonathan Campos wrote:
>>
>> On Fri, Mar 16, 2012 at 1:40 PM, Tink <fl...@tink.ws> wrote:
>>>
>>> These 2 things are what PopUpManager takes care of for you. If you
>>> don't
>>>> use PopUpManager it will still get included, as it's
>>>> instantiated in
>>>> SystemManager.
>>>>
>>>
>>>
>>> I too have created a variety of popups and alerts for mobile for my
>>> projects. I would prefer that we stick with using the popupmanager
>>> as it
>>> is
>>> the way most people are used to working with the framework.
>>>
>>> Also I would prefer to have a modal ability as with tablet
>>> applications
>>> modal is still very important.
>>>
>>> --
>>> Jonathan Campos
>>>
>>
>> Spark moved away from the direct use of the PopUpManager, with
>> SkinnablePopUpContainer, which used it internally.
>> I think if we added a SkinnablePopUpComponent (which would be really
>> useful anyway as most popups I have had to make, generally don't
>> need to be
>> containers), it would then be ideal to extend for an Alert.
>>
>> One thing I would like to see implemented in the new
>> SkinnablePopUpContainer, and added to the PopUpSkinnableContainer,
>> is the
>> ability to center the popup, and keep it centered. They should also
>> contain
>> the metadata for the modal styles so they can be set inline.
>>
>> Quite happy to throw one of these together and add it to Nick's
>> whiteboard
>> space, and then he can take a look whether he wants to use it for
>> his Alert.
>>
>> Tink
>>
Re: MobileAlert - quetwo
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
Do it. I'm working on getting the iOS skin to look proper, which should
stay out of the way of that work.
-Nick
On Fri, Mar 16, 2012 at 4:14 PM, Tink <fl...@tink.ws> wrote:
> On 16 Mar 2012, at 19:27, Jonathan Campos wrote:
>
> On Fri, Mar 16, 2012 at 1:40 PM, Tink <fl...@tink.ws> wrote:
>>
>> These 2 things are what PopUpManager takes care of for you. If you don't
>>> use PopUpManager it will still get included, as it's instantiated in
>>> SystemManager.
>>>
>>
>>
>> I too have created a variety of popups and alerts for mobile for my
>> projects. I would prefer that we stick with using the popupmanager as it
>> is
>> the way most people are used to working with the framework.
>>
>> Also I would prefer to have a modal ability as with tablet applications
>> modal is still very important.
>>
>> --
>> Jonathan Campos
>>
>
> Spark moved away from the direct use of the PopUpManager, with
> SkinnablePopUpContainer, which used it internally.
> I think if we added a SkinnablePopUpComponent (which would be really
> useful anyway as most popups I have had to make, generally don't need to be
> containers), it would then be ideal to extend for an Alert.
>
> One thing I would like to see implemented in the new
> SkinnablePopUpContainer, and added to the PopUpSkinnableContainer, is the
> ability to center the popup, and keep it centered. They should also contain
> the metadata for the modal styles so they can be set inline.
>
> Quite happy to throw one of these together and add it to Nick's whiteboard
> space, and then he can take a look whether he wants to use it for his Alert.
>
> Tink
>
Re: MobileAlert - quetwo
Posted by Jonathan Campos <jo...@gmail.com>.
On Fri, Mar 16, 2012 at 3:27 PM, Tink <fl...@tink.ws> wrote:
> You mean relative positioning to another component, or providing a series
> of absolute x and y positions?
Exactly. I have solutions already for the issue also. Just raising a flag.
--
Jonathan Campos
Re: MobileAlert - quetwo
Posted by Tink <fl...@tink.ws>.
On 16 Mar 2012, at 20:20, Jonathan Campos wrote:
> On Fri, Mar 16, 2012 at 3:14 PM, Tink <fl...@tink.ws> wrote:
>
>> One thing I would like to see implemented in the new
>> SkinnablePopUpContainer, and added to the PopUpSkinnableContainer,
>> is the
>> ability to center the popup, and keep it centered. They should also
>> contain
>> the metadata for the modal styles so they can be set inline.
>
>
> My one problem with the SkinnablePopups is they use a function called
> updatePosition (or something like that) to position themselves. This
> seems
> okay, but what if you want to be able to give 1 popup multiple
> places to
> popup (based on user input). To solve this I've long since extended
> the
> SkinnablePopups to include additional parameters similar to the
> callout's
> functionality. Then the updatePosition (or whatever) function uses
> those
> parameters to position itself.
>
> I'd probably push to add a few positioning parameters to the
> SkinnablePopups.
>
> --
> Jonathan Campos
You mean relative positioning to another component, or providing a
series of absolute x and y positions?
If you mean positioning relative to components, I have a layout
(layouts should position stuff) for positioning popups relative to
other components, that supports the same positioning s a Callout (the
code in Callout is pretty bad, layout all over the shop), and it also
supports the ability to control the positioning of a pointer as well.
It's a little strange how it works as you use the layout in the popup
skin, and it actually positiongs the content and the arrow, not the
component or the skin itself. I dig it out and provide an example.
Tink
Re: MobileAlert - quetwo
Posted by Jonathan Campos <jo...@gmail.com>.
On Fri, Mar 16, 2012 at 3:14 PM, Tink <fl...@tink.ws> wrote:
> One thing I would like to see implemented in the new
> SkinnablePopUpContainer, and added to the PopUpSkinnableContainer, is the
> ability to center the popup, and keep it centered. They should also contain
> the metadata for the modal styles so they can be set inline.
My one problem with the SkinnablePopups is they use a function called
updatePosition (or something like that) to position themselves. This seems
okay, but what if you want to be able to give 1 popup multiple places to
popup (based on user input). To solve this I've long since extended the
SkinnablePopups to include additional parameters similar to the callout's
functionality. Then the updatePosition (or whatever) function uses those
parameters to position itself.
I'd probably push to add a few positioning parameters to the
SkinnablePopups.
--
Jonathan Campos
Re: MobileAlert - quetwo
Posted by Tink <fl...@tink.ws>.
On 16 Mar 2012, at 19:27, Jonathan Campos wrote:
> On Fri, Mar 16, 2012 at 1:40 PM, Tink <fl...@tink.ws> wrote:
>
>> These 2 things are what PopUpManager takes care of for you. If you
>> don't
>> use PopUpManager it will still get included, as it's instantiated in
>> SystemManager.
>
>
> I too have created a variety of popups and alerts for mobile for my
> projects. I would prefer that we stick with using the popupmanager
> as it is
> the way most people are used to working with the framework.
>
> Also I would prefer to have a modal ability as with tablet
> applications
> modal is still very important.
>
> --
> Jonathan Campos
Spark moved away from the direct use of the PopUpManager, with
SkinnablePopUpContainer, which used it internally.
I think if we added a SkinnablePopUpComponent (which would be really
useful anyway as most popups I have had to make, generally don't need
to be containers), it would then be ideal to extend for an Alert.
One thing I would like to see implemented in the new
SkinnablePopUpContainer, and added to the PopUpSkinnableContainer, is
the ability to center the popup, and keep it centered. They should
also contain the metadata for the modal styles so they can be set
inline.
Quite happy to throw one of these together and add it to Nick's
whiteboard space, and then he can take a look whether he wants to use
it for his Alert.
Tink
Re: MobileAlert - quetwo
Posted by Jonathan Campos <jo...@gmail.com>.
On Fri, Mar 16, 2012 at 1:40 PM, Tink <fl...@tink.ws> wrote:
> These 2 things are what PopUpManager takes care of for you. If you don't
> use PopUpManager it will still get included, as it's instantiated in
> SystemManager.
I too have created a variety of popups and alerts for mobile for my
projects. I would prefer that we stick with using the popupmanager as it is
the way most people are used to working with the framework.
Also I would prefer to have a modal ability as with tablet applications
modal is still very important.
--
Jonathan Campos
Re: MobileAlert - quetwo
Posted by Tink <fl...@tink.ws>.
Modal shouldn't disable other components (i.e. it shouldn't set
enabled to false on the components as it will then change their skin
state) it just places a mouse blocker above all content but below your
popup, you'd want this on mobile though i would have thought. You'd
also want to make sure the Alert appear above all other content.
These 2 things are what PopUpManager takes care of for you. If you
don't use PopUpManager it will still get included, as it's
instantiated in SystemManager.
Tink
On 16 Mar 2012, at 14:20, Nicholas Kwiatkowski wrote:
> Modal, in my mind would should disable everything that is not within
> that
> component. Do you understand it to be something else?
>
> -Nick
>
> On Fri, Mar 16, 2012 at 9:40 AM, Tink <fl...@tink.ws> wrote:
>
>> Mobile wouldn't use modal, and need to make sure its sitting on top
>> of any
>> other content?
>>
>>
>> On 16 Mar 2012, at 12:09, Nicholas Kwiatkowski wrote:
>>
>> I wouldn't mind switching it over to a SkinablePopUpComponent.
>> I'll set
>>> that as a goal.
>>>
>>> My only thought on having two versions (a MobileAlert and an
>>> Alert) is
>>> that
>>> the MobileAlert would cut out some functionality in order to be a
>>> bit
>>> quicker (for example, not launching via the PopUpManager, because we
>>> really
>>> wouldn't use any of that functionality other than the ability to
>>> display
>>> the component). I also have the ability to switch skins based on
>>> the OS
>>> automatically to make it look more native, which would be harder
>>> if they
>>> were all one.
>>>
>>> -Nick
>>>
>>> On Fri, Mar 16, 2012 at 5:14 AM, Tink <fl...@tink.ws> wrote:
>>>
>>> I immediately noticed when looking at this is that it extends
>>>> SkinnablePopUpContainer.
>>>>
>>>> In my mind an Alert isn't a container. You do not create one and
>>>> then put
>>>> contents in it, and therefore you get unnecessary overhead with the
>>>> container, and from outside the API will look like you can add
>>>> elements
>>>> to
>>>> it.
>>>>
>>>> I would suggest we add a SkinnablePopUpComponent, then and Alert
>>>> can be
>>>> added on top of that. Then do we need a MobileAlert and Alert, or
>>>> can we
>>>> not just have a different skin for the 2 versions?
>>>>
>>>> Tink
>>>>
>>>>
>>>> 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
>>>>> (look in
>>>>> flex-config.template.xml and/or flex-config.xml) so until we
>>>>> come up
>>>>> with
>>>>> something better that what it will be.
>>>>>
>>>>> Thanks,
>>>>> Justin
>>>>>
>>>>>
>>>>>
>>>>
>>
Re: MobileAlert - quetwo
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
Modal, in my mind would should disable everything that is not within that
component. Do you understand it to be something else?
-Nick
On Fri, Mar 16, 2012 at 9:40 AM, Tink <fl...@tink.ws> wrote:
> Mobile wouldn't use modal, and need to make sure its sitting on top of any
> other content?
>
>
> On 16 Mar 2012, at 12:09, Nicholas Kwiatkowski wrote:
>
> I wouldn't mind switching it over to a SkinablePopUpComponent. I'll set
>> that as a goal.
>>
>> My only thought on having two versions (a MobileAlert and an Alert) is
>> that
>> the MobileAlert would cut out some functionality in order to be a bit
>> quicker (for example, not launching via the PopUpManager, because we
>> really
>> wouldn't use any of that functionality other than the ability to display
>> the component). I also have the ability to switch skins based on the OS
>> automatically to make it look more native, which would be harder if they
>> were all one.
>>
>> -Nick
>>
>> On Fri, Mar 16, 2012 at 5:14 AM, Tink <fl...@tink.ws> wrote:
>>
>> I immediately noticed when looking at this is that it extends
>>> SkinnablePopUpContainer.
>>>
>>> In my mind an Alert isn't a container. You do not create one and then put
>>> contents in it, and therefore you get unnecessary overhead with the
>>> container, and from outside the API will look like you can add elements
>>> to
>>> it.
>>>
>>> I would suggest we add a SkinnablePopUpComponent, then and Alert can be
>>> added on top of that. Then do we need a MobileAlert and Alert, or can we
>>> not just have a different skin for the 2 versions?
>>>
>>> Tink
>>>
>>>
>>> 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 (look in
>>>> flex-config.template.xml and/or flex-config.xml) so until we come up
>>>> with
>>>> something better that what it will be.
>>>>
>>>> Thanks,
>>>> Justin
>>>>
>>>>
>>>>
>>>
>
Re: MobileAlert - quetwo
Posted by Tink <fl...@tink.ws>.
Mobile wouldn't use modal, and need to make sure its sitting on top of
any other content?
On 16 Mar 2012, at 12:09, Nicholas Kwiatkowski wrote:
> I wouldn't mind switching it over to a SkinablePopUpComponent. I'll
> set
> that as a goal.
>
> My only thought on having two versions (a MobileAlert and an Alert)
> is that
> the MobileAlert would cut out some functionality in order to be a bit
> quicker (for example, not launching via the PopUpManager, because we
> really
> wouldn't use any of that functionality other than the ability to
> display
> the component). I also have the ability to switch skins based on
> the OS
> automatically to make it look more native, which would be harder if
> they
> were all one.
>
> -Nick
>
> On Fri, Mar 16, 2012 at 5:14 AM, Tink <fl...@tink.ws> wrote:
>
>> I immediately noticed when looking at this is that it extends
>> SkinnablePopUpContainer.
>>
>> In my mind an Alert isn't a container. You do not create one and
>> then put
>> contents in it, and therefore you get unnecessary overhead with the
>> container, and from outside the API will look like you can add
>> elements to
>> it.
>>
>> I would suggest we add a SkinnablePopUpComponent, then and Alert
>> can be
>> added on top of that. Then do we need a MobileAlert and Alert, or
>> can we
>> not just have a different skin for the 2 versions?
>>
>> Tink
>>
>>
>> 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
>>> (look in
>>> flex-config.template.xml and/or flex-config.xml) so until we come
>>> up with
>>> something better that what it will be.
>>>
>>> Thanks,
>>> Justin
>>>
>>>
>>
Re: MobileAlert - quetwo
Posted by Omar Gonzalez <s9...@apache.org>.
On Fri, Mar 16, 2012 at 11:42 AM, Tink <fl...@tink.ws> wrote:
> Push itself as a view? i.e. removing the view that the Alert is for? Thats
> not what i see with native iOS and Android apps.
>
> Tink
>
>
>
I agree I don't think it should push itself as a view. What I would expect
out of an Alert type component is to appear over my current view while
blocking interaction with the view underneath it. I would also expect such
a component to give me options to skin the modal layer so I can either use
a s:Rect or maybe use an image or some vector art.
--
Omar Gonzalez
s9tpepper@apache.org
Re: MobileAlert - quetwo
Posted by Tink <fl...@tink.ws>.
Push itself as a view? i.e. removing the view that the Alert is for?
Thats not what i see with native iOS and Android apps.
Tink
On 16 Mar 2012, at 15:45, Alex Harui wrote:
>
>
>
> On 3/16/12 5:09 AM, "Nicholas Kwiatkowski" <ni...@spoon.as> wrote:
>
>> My only thought on having two versions (a MobileAlert and an Alert)
>> is that
>> the MobileAlert would cut out some functionality in order to be a bit
>> quicker (for example, not launching via the PopUpManager, because
>> we really
>> wouldn't use any of that functionality other than the ability to
>> display
>> the component).
> I agree. I would think a MobileAlert would push itself as a view.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
Re: MobileAlert - quetwo
Posted by Alex Harui <ah...@adobe.com>.
On 3/16/12 5:09 AM, "Nicholas Kwiatkowski" <ni...@spoon.as> wrote:
> My only thought on having two versions (a MobileAlert and an Alert) is that
> the MobileAlert would cut out some functionality in order to be a bit
> quicker (for example, not launching via the PopUpManager, because we really
> wouldn't use any of that functionality other than the ability to display
> the component).
I agree. I would think a MobileAlert would push itself as a view.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: MobileAlert - quetwo
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
I wouldn't mind switching it over to a SkinablePopUpComponent. I'll set
that as a goal.
My only thought on having two versions (a MobileAlert and an Alert) is that
the MobileAlert would cut out some functionality in order to be a bit
quicker (for example, not launching via the PopUpManager, because we really
wouldn't use any of that functionality other than the ability to display
the component). I also have the ability to switch skins based on the OS
automatically to make it look more native, which would be harder if they
were all one.
-Nick
On Fri, Mar 16, 2012 at 5:14 AM, Tink <fl...@tink.ws> wrote:
> I immediately noticed when looking at this is that it extends
> SkinnablePopUpContainer.
>
> In my mind an Alert isn't a container. You do not create one and then put
> contents in it, and therefore you get unnecessary overhead with the
> container, and from outside the API will look like you can add elements to
> it.
>
> I would suggest we add a SkinnablePopUpComponent, then and Alert can be
> added on top of that. Then do we need a MobileAlert and Alert, or can we
> not just have a different skin for the 2 versions?
>
> Tink
>
>
> 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 (look in
>> flex-config.template.xml and/or flex-config.xml) so until we come up with
>> something better that what it will be.
>>
>> Thanks,
>> Justin
>>
>>
>