Peter,
The new style explorer's great, but man you guys are killing me with
the roll over to show the advanced color picker. Makes the whole thing
look buggy IMHO, can you just show them all the time?
Brian..
From: flexcoders@yahoogroups.com [mailto:[EMAIL
Also, I noticed when I select new colors for the Application background, it
doesn't refresh and show that color unless I first select a background
image, then select none to force it to redraw.
On 2/13/07, Brian Holmes [EMAIL PROTECTED] wrote:
Peter,
The new style explorer's great, but man
Eh, personal preference I guess. Personally, I didn¹t care for all the
visual clutter that a million color wheels added.
The good news, however, is that the source code is available to you with
view source (from the online version at
I love it. And thanks for the source. That functionality for mini-nav on
the left looks like it might make a pretty awesome standalone extended
list component.
I'd agree with the suggestion of always showing the advanced color
picker icon.
Doug
Nick Collins wrote:
Also, I noticed when I
Peter,
Yeah I saw that. Just so you guys know, MyriadWebPro.ttf and
MyriadWebPro-Bold.ttf isn't included in the download, so it won't
compile until you go get the files off your server or remove the
reference from the css.
thanks again,
B..
From:
Hey Peter
Thanks for kind realese, but loved the ASCII Adobe logo than Style Explorer
hehehe.
Best.
On 2/13/07, Peter Baird [EMAIL PROTECTED] wrote:
Hello All,
I wanted to let you all know that we've just released a new version of the
Flex Style Explorer with Tons of new features,
Yes, those were not included intentionally (license issues with distributing
the font and all). So, you would have to select a different font for the
header as well, just replace references to Myriad with Arial, or something.
-p
On 2/13/07 2:45 PM, Brian Holmes [EMAIL PROTECTED] wrote:
Any chance of import functionality? or perhaps, if one was so inclined,
what might be a good direction to start in to implement something like
that?
B..
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Peter Baird
Sent: Tuesday, February
Peter, isn't that a bug in the Flex compiler?
CSS specification is pretty clear that bad rules should be ignored. Compilation
errors are an inherent flaw in the Flex compiler if they are generated by CSS
rules, especially if those rules include specific binary font requirements.
-
It makes sense to ignore CSS errors when a CSS file is first parsed at
runtime. You want a best effort rendering of the CSS.
Web pages aren't required to be compiled and typechecked before they're
put on the server. If they were, you would in fact want to catch the
error at authoring time.
10 matches
Mail list logo
