I think the other important point about components is the usability
factor.
It's about having a consistent user experience across different Flash
applications, which can only really happen we use the same components.
Otherwise behaviours change from application to application and the
user
Hi there,
I would say MM ones are, but that's my personal point of view. Every
time I tried to used them, I ran into problems. And, if you care about
performance, (and you should care even more if you're targeting mobile
devices) i wouldn't recommend them.
Nonetheless, components are not evil
I have the same impression.
I found it easier to develop my own scroll bar component (or class )
including support for mouse weel, targeting textfields and masked
movieclips , than dealing with the graphic customization of the UI
Components.
I've also noticed they add about 200KB to your SWF file.
Using a component someone else made to suit a general audience is
almost always going to be less good than creating a custom component
for a specific task/project, given a sufficiently skilled developer,
no matter how good the general component is. So if you use a 3rd
party component, it
.
regards,
Muzak
- Original Message -
From: JulianG [EMAIL PROTECTED]
To: Flashcoders mailing list flashcoders@chattyfig.figleaf.com
Sent: Saturday, November 25, 2006 10:22 PM
Subject: Re: [Flashcoders] components are Evil?
I have the same impression.
I found it easier to develop my own
yes. sorry. it wasn't 200k
perhaps I was doing something of about 20k, and adding 32kb just for a
scrollbar left an awfull impression on me.
I need to get my hands on Flex 2 for my next RIA.
JG
___
Flashcoders@chattyfig.figleaf.com
To change your
putting flameproof pants on...
re components::
I've looked at them. Everybody I know who's doing serious Flash stuff
doesn't them because they're big, awkward, buggy and hard to customize.
My impression is that, if they're used at all, mostly they seem to be
used by non-programmers or very
7 matches
Mail list logo
