On 9/8/13 10:01 PM, "flexcapaci...@gmail.com"
wrote:
>Yes, I agree. What might alleviate that pain would be:
>
>€ move all the styles metadata into the skin instead of the component.
>have
>the component declare skin styles like we declare skin parts, so
>[SkinStyle(name="color", required=true)
Yes, I agree. What might alleviate that pain would be:
• move all the styles metadata into the skin instead of the component. have
the component declare skin styles like we declare skin parts, so
[SkinStyle(name="color", required=true)]
• or allow styles to be declared in the skin and make the com
ratyoosh
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Wednesday, September 04, 2013 12:17 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] General questions
On 9/4/13 9:04 AM, "Cosma Colanicchia" wrote:
>2013/9/4 Alex Harui
>
>> Maybe we'l
Maybe we could follow W3C rules, if any, in this case. Its the "custom"
prefix that feels just too broad to me, and could lead to confusion..
2013/9/4 Alex Harui
>
>
> On 9/4/13 9:04 AM, "Cosma Colanicchia" wrote:
>
> >2013/9/4 Alex Harui
> >
> >> Maybe we'll have an 'customStyles' object for
here near term in the enterprises
>for sure & people would be tempted to use CSS goodies provided by the
>modern browsers, does SCSS makes more sense?
>
>Thanks,
>Pratyoosh
>-Original Message-
>From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrak
On 9/4/13 9:04 AM, "Cosma Colanicchia" wrote:
>2013/9/4 Alex Harui
>
>> Maybe we'll have an 'customStyles' object for styles that aren't in CSS
>
>
>+1 (I would prefer simply "styles" as for the name)
Maybe, but then folks might stuff all of their styles in there. Which
would work, but maybe
2013/9/4 Alex Harui
> Maybe we'll have an 'customStyles' object for styles that aren't in CSS
+1 (I would prefer simply "styles" as for the name)
Just a random comment for the IE8 issue.
We have IE8 here on our enterprise network. IE9 is approved already, but who
knows when they will actually setup a package for it and push it (they are
really slow about it, sometimes years). I would rather keeping using standard
flex web-apps than use
CSS goodies provided by the modern
browsers, does SCSS makes more sense?
Thanks,
Pratyoosh
-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Tuesday, September 03, 2013 8:13 PM
To: dev@flex.apache.org
Subject: Re: [FlexJS] General
>
> IMO, a pain point in Flex was that styles had to be specified on the
> component when the style implementation was actually in the skin/theme.
> The skinning model is different in FlexJS anyway so I think that gives us
> license to change the styling model as well. If you ever set a style on a
On Tue, Sep 3, 2013 at 5:03 PM, Alex Harui wrote:
>
>
> On 9/3/13 4:55 PM, "OmPrakash Muppirala" wrote:
>
> >On Tue, Sep 3, 2013 at 4:38 PM, Alex Harui wrote:
> >
> >> Good question. I added a FalconJX and FlexJS component to JIRA. Please
> >> submit patches there. There is already a Falcon
On 9/3/13 4:55 PM, "OmPrakash Muppirala" wrote:
>On Tue, Sep 3, 2013 at 4:38 PM, Alex Harui wrote:
>
>> Good question. I added a FalconJX and FlexJS component to JIRA. Please
>> submit patches there. There is already a Falcon component.
>>
>> In theory, if you have problems compiling a SWF
On Tue, Sep 3, 2013 at 4:38 PM, Alex Harui wrote:
> Good question. I added a FalconJX and FlexJS component to JIRA. Please
> submit patches there. There is already a Falcon component.
>
> In theory, if you have problems compiling a SWF that FB/MXMLC compiled,
> then file the bug against Falcon
Good question. I added a FalconJX and FlexJS component to JIRA. Please
submit patches there. There is already a Falcon component.
In theory, if you have problems compiling a SWF that FB/MXMLC compiled,
then file the bug against Falcon. If Falcon compiled the SWF but you get
an error creating t
14 matches
Mail list logo
