Skip to main content
April 1, 2009
Question

IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries

  • April 1, 2009
  • 17 replies
  • 2512 views




Hi folks — we’re running into a few more roadblocks in our plans to drop the Fx prefix, that we need some fast input from the community on.



It turns out there’s a lot of poorly written XML library code out there.  After doing the work to drop the prefixes from all the spark components, we’re discovering that a large number of XML libraries — both open source and 3rd party libraries used in the Flex compiler, as well as those used by other community tools that process MXML,  simply cannot handle having multiple tags with the same leaf name.  Silly, given that’s exactly the reason XML namespaces exist, but it’s a fact of life.



So simply dropping the prefix off of the new components doesn’t fly.   But we’ve heard loud and clear from the community that adding a prefix is also a non-starter.   We’ve got a proposal up on the wiki for alternate ways to avoid duplicate names that don’t require unsightly prefixes or too much extra typing.



You can read the details, and comment, here:



http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix



Please comment by EOD today, 4/1/2009, as we are trying to get this work wrapped up as soon as possible.



Ely.

This topic has been closed for replies.

17 replies

Participant
April 1, 2009
Deepa, I think that naming scheme is a little dated. Wouldn't it be better to use something more state-of-the-art, like...

DataGroup --> ICanHasData
FxPanel --> ICanHasComponents
FxTitleBar --> IInYourApplication
TextView --> IInYourApplicationLookinAtYourText
FxFade --> KThxBye
etc.

- Peter
Participating Frequently
April 1, 2009
Yeah I think Deepas link makes that far more obvious. The first link<br />simply looked like Ely couldn't copy and paste from his excel document<br />correctly :)<br><br /><br><br />Leif Wells Atlanta wrote:<br /><blockquote<br /> cite="mid:83e37f7e0904011306re166602vdb8098a3ada5620@mail.gmail.com"<br /> type="cite">A new message was posted by Leif Wells Atlanta in <br><br /> <br><br /> <b>Developers</b> --<br><br />  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries<br><br /> <br><br />Uh,... Sean... um... what is today?<br><br /> <br><br /> <br><br />On Wed, Apr 1, 2009 at 3:42 PM, Sean Christmann <span dir="ltr">&lt;<a<br /> moz-do-not-send="true" href="mailto:member@adobeforums.com">member@adobeforums.com</a>&gt;</span><br />wrote:<br><br /> <blockquote class="gmail_quote"<br /> style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">A<br />new message was posted by Sean Christmann in <br><br /> <br><br /> <b>Developers</b> --<br><br />  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries<br><br /> <br><br />I'm glad to see you doing this, regardless of whether it ends up<br />solving XML conflicts. Changing the root namespace to either spark.* or<br />fx.* will make it much easier for all of us to mentally separate old<br />from new when browsing through packages.<br><br /> <br><br />BTW the chart on the linked page is cutting off the first character of<br />each class name in the destination name column<br><br /> <br><br />Greenfield Eliot wrote:<br /> <blockquote type="cite"> A new discussion was started by Greenfield<br />Eliot in <br><br /> <br><br /> <b>Developers</b> --<br><br />  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries<br><br /> <br><br /> <font face="Calibri, Verdana, Helvetica, Arial"><span<br /> style="font-size: 11pt;"><br><br /> <br><br />Hi folks were running into a few more roadblocks in our plans to<br />drop the Fx prefix, that we need some fast input from the community on.<br><br /> <br><br />It turns out theres a lot of poorly written XML library code out<br />there.  After doing the work to drop the prefixes from all the spark<br />components, were discovering that a large number of XML libraries <br />both open source and 3rd party libraries used in the Flex compiler, as<br />well as those used by other community tools that process MXML,  simply<br />cannot handle having multiple tags with the same leaf name.  Silly,<br />given thats exactly the reason XML namespaces exist, but its a fact<br />of life.<br><br /> <br><br />So simply dropping the prefix off of the new components doesnt fly.<br />  But weve heard loud and clear from the community that adding a<br />prefix is also a non-starter.   Weve got a proposal up on the wiki for<br />alternate ways to avoid duplicate names that dont require unsightly<br />prefixes or too much extra typing. <br><br /> <br><br />You can read the details, and comment, here:<br><br /> <br><br /> <font color="#0000ff"><u><a moz-do-not-send="true"<br /> href="http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix"<br /> target="_blank">http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix</a><br><br /> </u></font><br><br />Please comment by EOD today, 4/1/2009, as we are trying to get this<br />work wrapped up as soon as possible.<br><br /> <br><br />Ely.<br><br /> </span></font> <br><br /> <br><br /> <hr align="left" width="200">View/reply at <a<br /> moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?13@@.59b87933" target="_blank">IMPORTANT:<br />Dropping the Fx Prefix - dealing with XML libraries</a><br><br />Replies by email are OK.<br><br />Use the <a moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?280@@.59b87933%21folder=.3c060fa3"<br /> target="_blank">unsubscribe</a><br />form to cancel your email subscription.<br><br /> <br><br /> </blockquote><br /> <br><br /> <br><br /> <hr align="left" width="200">View/reply at <a<br /> moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?13@@.59b87933/0" target="_blank">IMPORTANT:<br />Dropping the Fx Prefix - dealing with XML libraries</a><br><br />Replies by email are OK.<br><br />Use the <a moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?280@@.59b87933%21folder=.3c060fa3"<br /> target="_blank">unsubscribe</a> form to cancel your email subscription.<br><br /> <br><br /> </blockquote><br /> <br><br /> <br><br /> <br><br /> <hr align="left" width="200">View/reply at <a moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?13@@.59b87933/1">IMPORTANT:<br />Dropping the Fx Prefix - dealing with XML libraries</a><br><br />Replies by email are OK.<br><br />Use the <a moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?280@@.59b87933%21folder=.3c060fa3">unsubscribe</a><br />form to cancel your email subscription.<br><br /></blockquote>
Nate Beck
Known Participant
April 1, 2009
I think you guys should add support for 1337 speak after April 1st as well :)

On Wed, Apr 1, 2009 at 1:10 PM, Deepa Subramaniam < member@adobeforums.com> wrote:

A new message was posted by Deepa Subramaniam in



Developers --

  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries



So we got a lot of pushback on Ely's proposal because it wasn't smart enough. We really want to solve this in a smart way. Smart is key - we think our powerusers will really appreciate this second proposal so please check it out here and comment by end of day.


Thanks!

deepa

View/reply at IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries


Replies by email are OK.

Use the unsubscribe form to cancel your email subscription.





--

Cheers,
Nate
----------------------------------------
http://blog.natebeck.net


Participating Frequently
April 1, 2009
So we got a lot of pushback on Ely's proposal because it wasn't smart enough. We really want to solve this in a smart way. Smart is key - we think our powerusers will really appreciate this second proposal so please check it out here and comment by end of day.

Thanks!
deepa

http://opensource.adobe.com/wiki/display/flexsdk/Updated+133t+plan+for+dropping+the+Fx+prefix
Participating Frequently
April 1, 2009
So, we got a lot of pushback on Ely's proposal and deemed it wasn't smart enough. We really want to solve this in a smart way - smart is key. So please check out the second proposal I've posted here:

http://opensource.adobe.com/wiki/display/flexsdk/Updated+133t+plan+for+dropping+the+Fx+prefix

Comments are due by end of day.
Participating Frequently
April 1, 2009
Uh,... Sean... um... what is today?



On Wed, Apr 1, 2009 at 3:42 PM, Sean Christmann < member@adobeforums.com> wrote:

A new message was posted by Sean Christmann in



Developers --

  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries




I'm glad to see you doing this, regardless of whether it ends up
solving XML conflicts. Changing the root namespace to either spark.* or
fx.* will make it much easier for all of us to mentally separate old
from new when browsing through packages.



BTW the chart on the linked page is cutting off the first character of
each class name in the destination name column




Greenfield Eliot wrote:


A new discussion was started by Greenfield Eliot in



Developers --

  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries







Hi folks were running into a few more roadblocks in our plans to
drop the Fx prefix, that we need some fast input from the community on.



It turns out theres a lot of poorly written XML library code out
there.  After doing the work to drop the prefixes from all the spark
components, were discovering that a large number of XML libraries
both open source and 3rd party libraries used in the Flex compiler, as
well as those used by other community tools that process MXML,  simply
cannot handle having multiple tags with the same leaf name.  Silly,
given thats exactly the reason XML namespaces exist, but its a fact
of life.



So simply dropping the prefix off of the new components doesnt fly.
  But weve heard loud and clear from the community that adding a
prefix is also a non-starter.   Weve got a proposal up on the wiki for
alternate ways to avoid duplicate names that dont require unsightly
prefixes or too much extra typing.



You can read the details, and comment, here:



http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix




Please comment by EOD today, 4/1/2009, as we are trying to get this
work wrapped up as soon as possible.



Ely.







View/reply at IMPORTANT:
Dropping the Fx Prefix - dealing with XML libraries


Replies by email are OK.

Use the unsubscribe
form to cancel your email subscription.






--

Sean Christmann | Experience Architect | EffectiveUI | 720.937.2696







View/reply at IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries

Replies by email are OK.

Use the unsubscribe form to cancel your email subscription.



Participating Frequently
April 1, 2009
I'm glad to see you doing this, regardless of whether it ends up<br />solving XML conflicts. Changing the root namespace to either spark.* or<br />fx.* will make it much easier for all of us to mentally separate old<br />from new when browsing through packages.<br><br /><br><br />BTW the chart on the linked page is cutting off the first character of<br />each class name in the destination name column<br><br /><br><br />Greenfield Eliot wrote:<br /><blockquote cite="mid:C5F9080F.551B%25egreenfi@adobe.com" type="cite"><br /> <meta http-equiv="Content-Type" content="text/html; "><br />A new discussion was started by Greenfield Eliot in <br><br /> <br><br /> <b>Developers</b> --<br><br />  IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries<br><br /> <br><br /> <font face="Calibri, Verdana, Helvetica, Arial"><span<br /> style="font-size: 11pt;"><br><br /> <br><br />Hi folks were running into a few more roadblocks in our plans to<br />drop the Fx prefix, that we need some fast input from the community on.<br><br /> <br><br />It turns out theres a lot of poorly written XML library code out<br />there.  After doing the work to drop the prefixes from all the spark<br />components, were discovering that a large number of XML libraries <br />both open source and 3rd party libraries used in the Flex compiler, as<br />well as those used by other community tools that process MXML,  simply<br />cannot handle having multiple tags with the same leaf name.  Silly,<br />given thats exactly the reason XML namespaces exist, but its a fact<br />of life.<br><br /> <br><br />So simply dropping the prefix off of the new components doesnt fly.<br />  But weve heard loud and clear from the community that adding a<br />prefix is also a non-starter.   Weve got a proposal up on the wiki for<br />alternate ways to avoid duplicate names that dont require unsightly<br />prefixes or too much extra typing. <br><br /> <br><br />You can read the details, and comment, here:<br><br /> <br><br /> <font color="#0000ff"><u><a moz-do-not-send="true"<br /> href="http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix">http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix</a><br><br /> </u></font><br><br />Please comment by EOD today, 4/1/2009, as we are trying to get this<br />work wrapped up as soon as possible.<br><br /> <br><br />Ely.<br><br /> </span></font><br /> <br><br /> <br><br /> <hr align="left" width="200">View/reply at <a moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?13@@.59b87933">IMPORTANT:<br />Dropping the Fx Prefix - dealing with XML libraries</a><br><br />Replies by email are OK.<br><br />Use the <a moz-do-not-send="true"<br /> href="http://www.adobeforums.com/webx?280@@.59b87933%21folder=.3c060fa3">unsubscribe</a><br />form to cancel your email subscription.<br><br /> <br><br /></blockquote><br /><br><br /><pre class="moz-signature" cols="72">-- <br />Sean Christmann | Experience Architect | EffectiveUI | 720.937.2696</pre>