You type "<" and the name of a component, let's say MyCustomComponent, that
is in the library with a namespace manifest.
FB will add, in the root element of the mxml, a declaration
(xmlns:ns="<manifest-uri>") and apply that prefix ("<ns:MyCustomComponent ")
There's no way, AFAK, to associate to each uri a preferred prefix, to avoid
fixing the ns, ns1 ecc. generated prefixes.
2013/5/10 Alex Harui <aha...@adobe.com>
> I guess I still don't understand the steps. What are you typing and how is
> FB responding?
>
>
> On 5/10/13 8:37 AM, "Cosma Colanicchia" <cosma...@gmail.com> wrote:
>
> > I am creating an swc library that includes a namespace manifest, using
> the
> > documented COMPC compiler API.
> >
> > When referencing and using a library with a manifest, the first time you
> > use a component in a MXML document FB will autodeclare the namespace uri
> > for you, using a prefix like "ns", "ns1", ecc.
> >
> > I was searching for a way to tell FB that, for the namespace uri "
> > http://my.domain/ns/mylib"; I'd like to use the <mylib:...> prefix,
> without
> > declaring it in advance or correcting the declaration after each first
> > usage on new MXML documents (like FB already does for standard mx/s/fx
> > namespaces).
> >
> >
> >
> >
> > 2013/5/10 Alex Harui <aha...@adobe.com>
> >
> >> None of us worked on FB, so we don't know how it works. I'm not clear
> what
> >> the steps you are using to reproduce this issue is. Are you just typing
> >> xmlns in an MXML file or is it the auto-complete suggestions or
> something
> >> else?
> >>
> >>
> >> On 5/10/13 5:04 AM, "Carlos Rovira" <carlos.rov...@codeoscopic.com>
> wrote:
> >>
> >>> Hi Cosma,
> >>>
> >>> very interesting, I have the same issue with my as3 libraries. My
> defined
> >>> library namespace is "r" but FB throws "ns"
> >>>
> >>> I couldn't get this to work again since FB4.7
> >>>
> >>> Maybe Alex, Carol or Peter could point what's happening and if
> something
> >>> could be done to fixit or is something
> >>> that only a patch in FB could solve.
> >>>
> >>>
> >>>
> >>> 2013/5/10 Cosma Colanicchia <cosma...@gmail.com>
> >>>
> >>>> I have a SWC library declaring a custom namespace, when I use it I'd
> >> like
> >>>> to have FB suggest a custom prefix declaration in MXML.
> >>>>
> >>>> Currently, FB is able to provide the default "s", "fx" and "mx"
> prefixes
> >>>> automatically, any other is declared as "ns", "ns1" and so on.
> >>>>
> >>>> In previous version there was an undocumented way using a design.xml
> to
> >> set
> >>>> a default in the swc library itself, but was probably part of the
> design
> >>>> view feature and doesn't work anymore in FB 4.7 (see [1] for details).
> >>>>
> >>>> Documentation of FB 4.7 [2] about the file template customization
> >> describes
> >>>> an ${xmlns} token (for new MXML components) that should be gather info
> >> from
> >>>> some namespace preferences, but I can't find any such preferences
> >> settings.
> >>>>
> >>>> I also found that the only place in Flash Builder folders with
> >> references
> >>>> these prefixes settings in clear text is the plugin.xml file of
> >>>> the com.adobe.flexide.mxml.core_4.7.0.349722 plugin , in the
> >>>> "com.adobe.flexbuilder.codemodel.mxmlNamespaceRegistry" extension, I
> >> tried
> >>>> adding additional MXMLNamespace nodes specifiny the prefix and uri,
> >> with no
> >>>> effects (SDK contains the namespaces uri in various XML files, but I
> >> found
> >>>> no traces of the default prefixes).
> >>>>
> >>>> Anyone had luck? Am I the only one trying to use custom prefix? :)
> >>>>
> >>>>
> >>>> [1]
> >>>>
> >>>>
> >>
> http://stackoverflow.com/questions/6453919/how-can-i-make-flashbuilder-use-a-
> >>>> custom-namespace-prefix/6456120#6456120
> >>>>
> >>>> [2]
> >>>>
> >>>>
> >>
> http://help.adobe.com/en_US/flashbuilder/using/WSe4e4b720da9dedb5344c6f711358
> >>>> acdda1d-7fff.html#WSe4e4b720da9dedb56fd3caca12e6bb494bb-7fee
> >>>>
> >>>
> >>>
> >>
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >> http://blogs.adobe.com/aharui
> >>
> >>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
