spark vs. mx controls
i've got large app designed flex 3. project stalled , when resurrected upgraded flex 4. of controls still mx controls occassional spark label needed word wrap.
due size of app, i'm wondering if should stick mx controls or convert possible spark controls?
this internal app , not have if skinning , should relatively change free, once inital bugs removed.
the strange approach of releasing small subset of mx components spark library means stuck using both think kind of defeats purpose of skinning advantages flex 4's spark library touts. assuming more component conversions follow @ point, draws out transition , can make tough justify moving project over.
spark skinning , not else. if you're not going making use of biggest asset, mentioned, why bother? seems waste of time me.
More discussions in Flex (Read Only)
adobe
Comments
Post a Comment