Hey Manish, one more question about your response. It seems like the only way to use the compiled namespaces is with the "local" namespace in mxml, like:
<local:MyComponent label="Click Me"/> Is this correct? I don't see a way to specifically allow you to compile in a component so that you can use mxml like so: <foo:MyComponent label="Click Me"/> Thanks. On Tue, Dec 23, 2008 at 4:16 PM, aaron smith <[email protected]> wrote: > Thanks Manish! perfect explanation. Thanks again! > > On Tue, Dec 23, 2008 at 2:02 PM, Manish Jethani > <[email protected]> wrote: >> On Wed, Dec 24, 2008 at 1:33 AM, aaron smith >> <[email protected]> wrote: >>> Does the -include-namespace correlate to the mxmlc >>> namespaces.namespace switch? Also, (this is kind of broad), but in >> >> Yes. >> >>> what situation do the namespace flags need to be used? I'm thinking >>> it's for the namespaces in mxml (like <myNameSpace:..>) Thanks yo. >> >> include-namespace is an alternate way of doing include-classes. >> >> compc ... >> -namespace http://example.com/foo $foo_dir/manifest.xml >> -include-namespaces http://example.com/foo >> >> Here you're: >> >> 1. mapping the namespace http://example.com/foo to the manifest.xml >> file in $foo_dir >> 2. including all classes listed in that namespace >> >> The manifest.xml file looks like this: >> >> <?xml version="1.0" encoding="utf-8"?> >> <componentPackage> >> <component id="FooComponent" class="com.example.foo.FooComponent" /> >> ... >> </componentPackage> >> >> The advantage of course is that you can use the namespace directly in >> any application that uses the SWC. >> >> <Application> >> <foo:FooComponent xmlns:foo="http://example.com/foo"; /> >> ... >> </Application> >> >> -- >> manishjethani.com >> >> >
