Jules,
Many thanks for your reply....to cut to the
quick....
So what we are really wondering is, bearing in mind that our goals are the same as those you mention but that we also require flexibility and the ability to reskin our own custom controls, should we be using code behind or inline AS?
So I'm
not quite understanding your challenge here; how the existence of ActionScript
inline or in a code-behind class is impacting upon how you skin your
controls ? Is there a snippet you can share that might elaborate
?
We've
skinned some pretty non-Flex looking applications (check out the mortgage
calculator at www.if.com for example) where a
huge majority of the skinning is achieved through the use of CSS styles, the
rest through many of the usual HTML-esque tricks of getting margins
right, and dropping background images in places where we need a graphic
rather than a colour.
The
existence of ActionScript code in the MXML file or not, has never impacted on
the strategy for skinning.
Do you
have an example you could give so we could have a more concrete discussion
? I'm out of office most of tomorrow, so forgive me if I don't
get a reply to you...
Best,
Steven
--
Steven
Webster
Practice Director (Rich
Internet Applications)
Macromedia Consulting
EMEA
Office: + 44 (0) 131 338
6108
Mobile: +44 (0) 7917 428
947
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
