Please let me know If there is anything I can do to help :)
On Fri, Feb 13, 2015 at 12:44 PM, Alex Harui wrote:
> It depends on what files he changed. Many of the files used by the
> installer can be put on flex.a.o or dist and the install scripts will use
> them. If you check it into the repo
It depends on what files he changed. Many of the files used by the
installer can be put on flex.a.o or dist and the install scripts will use
them. If you check it into the repo, then I’ll know what files changed
and we can discuss how to deploy them.
On 2/12/15, 9:42 PM, "piotrz" wrote:
>I thi
I think we should push russian translation, because these changes AFAIK was
introduced even before release of sdk. Now I know that it should be pushed,
so the question is when and what to do to have at least changes in our
nightly build? Shouldn't we use urls from staging website in nightly build?
Normally things go in the develop branch. Depending on which file is
changing, we can copy files out to the dist server or flex.a.o.
On 2/12/15, 9:01 PM, "piotrz" wrote:
>Anyone know should I push to this location properties file from develope
>branch to have fixed Russian translation and other
Anyone know should I push to this location properties file from develope
branch to have fixed Russian translation and other?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Discussion-FLEX-34623-Russia
We developers, the rest of the world consumers, professional and
businesses do not care about the personal feeling of Silicon Valley
CEOs, not do we care or are concerned by their thoughts about the
competition. If Apple helped Adobe become the company it is today good
for Apple, the helped a compa
On Thu, Feb 12, 2015 at 3:56 PM, Alex Harui wrote:
>
>
> On 2/12/15, 3:45 PM, "OmPrakash Muppirala" wrote:
>
> >Okay good, the warnings are gone now. I had removed the spark project as
> >a
> >dependency on my test app. Once I added it and did a clean-compile, the
> >warnings are now gone.
> >
On 2/12/15, 3:45 PM, "OmPrakash Muppirala" wrote:
>Okay good, the warnings are gone now. I had removed the spark project as
>a
>dependency on my test app. Once I added it and did a clean-compile, the
>warnings are now gone.
>
>I will check in the code, can you please do a code/comment review?
Okay good, the warnings are gone now. I had removed the spark project as a
dependency on my test app. Once I added it and did a clean-compile, the
warnings are now gone.
I will check in the code, can you please do a code/comment review?
Thanks,
Om
On Thu, Feb 12, 2015 at 3:36 PM, Alex Harui w
What is the simplest test case for reproducing this problem?
If you are using FB, did you restart FB? Otherwise it might be using
cached SWCs.
-Alex
On 2/12/15, 3:30 PM, "OmPrakash Muppirala" wrote:
>It looks like the 'mobile' theme is different from the 'spark' theme. So,
>I changed
>
>spar
It looks like the 'mobile' theme is different from the 'spark' theme. So,
I changed
spark/src/spark/components/supportClasses/SkinnableTextBase.as:
[Style(name="borderColor", type="uint", format="Color", inherit="no",
theme="spark")]
to
[Style(name="borderColor", type="uint", format="Color", i
On Thu, Feb 12, 2015 at 2:23 PM, Alex Harui wrote:
> The metadata on components like this one setup what the compiler cares
> about:
>
> spark/src/spark/components/supportClasses/SkinnableTextBase.as:[Style(name=
> "borderColor", type="uint", format="Color", inherit="no", theme="spark")]
>
>
>
>
The metadata on components like this one setup what the compiler cares
about:
spark/src/spark/components/supportClasses/SkinnableTextBase.as:[Style(name=
"borderColor", type="uint", format="Color", inherit="no", theme="spark")]
Do use the iOS and Android skins, do you change certain compiler op
I am guessing that the warning messages are hardcoded somewhere. I don't
see any reason it should think it not a spark skin.
Thanks,
Om
On Thu, Feb 12, 2015 at 2:14 PM, Alex Harui wrote:
> Probably need to look into it in the compiler. It thinks the theme is no
> longer Spark. Why would that
Probably need to look into it in the compiler. It thinks the theme is no
longer Spark. Why would that be the case?
-Alex
On 2/12/15, 2:09 PM, "OmPrakash Muppirala" wrote:
>(Moving discussion to @dev)
>
>Actually, we do support borderColor in the new iOS and Android skins. I
>am
>not sure how
Changing the subject line.
On Thu, Feb 12, 2015 at 2:09 PM, OmPrakash Muppirala
wrote:
> (Moving discussion to @dev)
>
> Actually, we do support borderColor in the new iOS and Android skins. I
> am not sure how to remove the warnings in this case.
>
> A less elegant solution would be to give it
(Moving discussion to @dev)
Actually, we do support borderColor in the new iOS and Android skins. I am
not sure how to remove the warnings in this case.
A less elegant solution would be to give it a different name.
Thoughts?
Thanks,
Om
On Thu, Feb 12, 2015 at 2:00 PM, Piotr Zarzycki (JIRA)
w
I have an historical note about Apple and Adobe.
Adobe would not exist without Apple and the generous $1,000 Postscript license
fee for every LaserWriter that Apple paid Adobe in the mid-1980s.
Adobe was originally a Mac shop.
Adobe switched to a Windows shop in the early 1990s. I think we can
Les,
I have checked in a fix here
https://git1-us-west.apache.org/repos/asf?p=flex-sdk.git;a=commit;h=5c98108c
You should be able to copy the changes into your local copy of the SDK.
Thanks,
Om
On Wed, Feb 11, 2015 at 5:37 PM, leswoolsey wrote:
> My IOS app is a Spark ViewNavigatorApplication
19 matches
Mail list logo
