I undertand about having a lot of work :). I have used the wiki to
generate the flexlib project, I also installed subclipse and I was able
to download all the files, but now I get the following error
1045:Type was not found or was not a compile-time
constat:IMenuBarItemRenderer
is there
I think this is from the 2.0.1 update to the Flex framework. You need to
upgrade to Flex 2.0.1 for the flexlib library to work. Go get the update and
try to recompile.
Doug
On 06 Mar 2007 13:57:40 -0800, Guillermo Villasana [EMAIL PROTECTED]
wrote:
I undertand about having a lot of work
Skip using the actual dialog, really... I've not dug in far enough to find
out exactly what it is that's different, but I know how to do it by editing
the project settings files directly. Just copy what's already done for the
playerglobal.swc, etc., they basically point to the swc then have an
Hey, sorry we haven't replied about you trying to use the SWC. I'm working
on getting a new zip file uploaded to the project page that has the SWC and
a sample app to show how to use the components. We're having some issues
with Google Code, but Ihopefully we'll get something up in the next few
I added it in the the Library path tab. Or i should add it int source path?
Thanks
Terius
Troy Gilbert wrote:
You've added the SWC to your project? Go to the Project Properties and
its on one of the build related tabs.
Troy.
Doug and Darron,
This is awesome and many thanks for initiating the project.
I have one question... why the emphasis on pure AS3 vs. MXML?
-Engkee
--- In flexcoders@yahoogroups.com, Doug McCune [EMAIL PROTECTED] wrote:
I'm pleased to announce FlexLib: a new open-source project for Flex
2
In my mind, the main reason to shoot for pure AS3 is for consistency. You
can accomplish everything in AS3 that you can do in MXML. I know sometimes
it's easier to hack together something quickly by using a combination of
MXML with AS3 script blocks, but the exact same component can be built with
another advantage is you can use the components in the DesignView of FB.
DK
On 3/1/07, Doug McCune [EMAIL PROTECTED] wrote:
In my mind, the main reason to shoot for pure AS3 is for consistency. You
can accomplish everything in AS3 that you can do in MXML. I know sometimes
it's easier to hack
Wait, are you saying that making the components in MXML is the only way to
use the components in the Design View? I haven't confirmd it, but I find
that highly suspect... AS3 == MXML, i.e. MXML becomes AS3 code before its
actually compiled. All of the Flex native components are AS3... Making them
I downloaded the .swc file, but I don't seem to be able to use the
components. I added the xmlns=flexunit.flexui.* is there something
else I should be doing?
Thanks.
Great!
2007/3/2, Guillermo Villasana [EMAIL PROTECTED]:
I downloaded the .swc file, but I don't seem to be able to use the
components. I added the xmlns=flexunit.flexui.* is there something
else I should be doing?
Thanks.
--
闲云孤鹤 - 清冷香中抱膝吟
You've added the SWC to your project? Go to the Project Properties and its
on one of the build related tabs.
Troy.
On 3/1/07, Guillermo Villasana [EMAIL PROTECTED] wrote:
I downloaded the .swc file, but I don't seem to be able to use the
components. I added the xmlns=flexunit.flexui.* is
12 matches
Mail list logo