> RT: what if the rc builds only built on changes to the repo (and never on
> timer) and always sent a message to dev@ even on successful builds? That
> way we’d be able to see what changed and when.
Good plan.
I'm making the changes to the build as we speak.
EdB
--
Ix Multimedia Software
> Erik, do you think I should fix this before 4.14 gets released or do you
> think this can impact on the release schedule? I'm not really sure how this
> goes.
Sure, it is an issue with a new feature. Please commit to
'release4.14', it will be merged into develop after we've released.
EdB
--
Chris,
Just commit to the 'release4.14' branch. I'll merge that back into
develop when we've released (or maybe sooner, if my time permits).
Thanks,
EdB
On Wed, Dec 17, 2014 at 10:44 PM, Chris Martin wrote:
>
>
>
> Okay, I got a change to the script that will detect the OS. Basically it
>
; > Erik, looks like this change did go through. Can you confirm when
> the RC
> >> > job would refresh the build?
> >> >
> >> > Thanks,
> >> > Om
> >> > On Dec 17, 2014 1:42 AM, "Krüger, Olaf" wrote:
> >> >
> &g
ranch.
>>> >
>>> > Erik, looks like this change did go through. Can you confirm when
>>>the RC
>>> > job would refresh the build?
>>> >
>>> > Thanks,
>>> > Om
>>> > On Dec 17, 2014 1:42 AM, "Krüger, Ola
>
> Anyway: all works fine now and apart from the flatspark theme, I haven't
> had any issues in upgrading to the new sdk. All I had to do is modify the
> html template file because our projects need a bit of custom code in those.
>
Thank you for helping Dany.
I'm just wondering if there was any c
> The SharpKit project (C# to JS) also has a ton and served as some of
Randori's inspiration as the first version of Randori was written for C#
I really enjoyed C# programming when I used it more. Why didn't you
continue down the C# path for Randori?
On Wed, Dec 17, 2014 at 12:14 PM, Michael A. L
I've just build Flow.swf (testApps in our TLF source code) application which
is Flex TLF app created for testing TLF framework. It's working without any
problems with SDK 4.14 RC, but more unit tests are failing than before.
Tests run: 428, Failures: 6, Errors: 6,
I've tried debugging some of th
Okay, I got a change to the script that will detect the OS. Basically it will
look for linux emulated in windows (CYGWIN and MINGW), if one of those are
detected, then it will choose a file set for that environment to copy
(basically the adl.exe and adt.bat. If it detects any other environm
Hi Darkstone,
I would prefer 1A) which is to revert the change, prove that Type
Selectors work, and change the documentation for SkinnableComponent to
guide people to use Type Selectors. Then overriding styleName should not
be needed, and folks will build components following the same pattern as
Hi Alex,
I got what you saying, I understand why you don't agree to the changes, you've
got your point, I think you are right.
But that won't prevent others from doing it in the wrong ways.
There is a paragraph in SkinnableComponent online help about implementing the
constructor:
"Use the con
Om-
>Thanks for the link. I went through the whole documentation (still have some
>questions, though). It looks pretty solid. Any reason there has not been
>much activity on Randori for a while? Are you planning some new updates any
>time soon?
Nope. There wasn't enough interest in cross-c
Ha So simple! :) It's working! Thank you Mihai!
I owe you a big beer! :)
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-3-3-git-commit-flex-sdk-refs-heads-release4-14-0-Changed-prepare-SDK-section-
> Saying "removing sdk" you mean removing it in the Intellij configuration or
> physically from the directory ?
In the IntelliJ configuration.
Hi Mihai,
Saying "removing sdk" you mean removing it in the Intellij configuration or
physically from the directory ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-3-3-git-commit-flex-sdk-refs-hea
On 12/17/14, 9:25 AM, "Erik de Bruin" wrote:
>Alex,
>
>I thought there was no need to compile BlazeDS before being able to
>compile the SDK. I thought the SDK just took some code from the
>BlazeDS repo and compiled that into the required jar?
I haven’t made any changes there yet. I’ll look int
Neil,
This doesn’t look right. 4.14 shouldn’t have any BlazeDS options.
On 12/17/14, 11:00 AM, "nmad...@apache.org" wrote:
>Repository: flex-sdk
>Updated Branches:
> refs/heads/release4.14.0 feb40f628 -> 53962a03d
>
>
>Updated installer config file. Added OFL Fonts section and updated
>compon
Hi Darkstone,
Think of the general case. Let’s say that you also call:
myComponent.setStyle(“fontWeight", “bold");
myComponent.setStyle(“color", #ff);
When you later call:
myComponent.styleName = “otherSkin” and you have
.otherskin {
skinClass : MyOtherSkin;
fontWeight : “normal”;
co
Hi Alex,
Actually, this bug is reported to me by a Flex Developer, who is a friend of
mine.
The demand is, he wants to set a default skin class for his component (which
extends SkinnableComponent), so inside the constructor of his component, he
writes this:
setStyle("skinClass", MyDefaultSkin)
Awesome!
Thanks for hangin' in there and figuring it out.
EdB
On Wed, Dec 17, 2014 at 6:37 PM, Mihai Chira wrote:
> I found the issue! Whoa, this is a relief!
>
> I defined the source SDK ("FlexSDKSource") when it wasn't well built,
> and IntelliJ only detected the swcs that it could find the
I found the issue! Whoa, this is a relief!
I defined the source SDK ("FlexSDKSource") when it wasn't well built,
and IntelliJ only detected the swcs that it could find there - i.e.
not all of them (just comparing the list to the installer-installed
SDK made that obvious). So after simply removing
That's the one I'm using. All in all, here are all the commands I ran:
ant super-clean
cd ../flex-blazeds
ant clean
ant main
cd ../sdk
ant main
ant frameworks-rsls
ant -f installer.xml -Dflash.sdk.version=15.0 -Dair.sdk.version=15.0
After all this (everything finally ran successfully), I get exac
Yep, thanks for all your help so far, Erik.
On 17 December 2014 at 17:30, OmPrakash Muppirala wrote:
> On Wed, Dec 17, 2014 at 9:28 AM, Erik de Bruin wrote:
>>
>> Oh, never mind. I just read the subject of the thread...
>>
>> It's been a busy few days, all things Flex 4.14 are starting to become
On Wed, Dec 17, 2014 at 9:28 AM, Erik de Bruin wrote:
>
> Oh, never mind. I just read the subject of the thread...
>
> It's been a busy few days, all things Flex 4.14 are starting to become
> a blur ;-)
>
You are doing a fantastic job! Hang in there :-)
Thanks,
Om
>
> EdB
>
>
>
> On Wed, Dec
Hi Darkstone,
By this description, this is not a bug. Any style set via setStyle
overrides styles in CSS selectors. The more common case is someone does
want to always have myComponent use SkinA regardless of underlying changes
to the selectors, like when style modules are loaded. If you want a
Oh, never mind. I just read the subject of the thread...
It's been a busy few days, all things Flex 4.14 are starting to become
a blur ;-)
EdB
On Wed, Dec 17, 2014 at 6:26 PM, Erik de Bruin wrote:
> Mihai,
>
> Are you following the latest version of the README? The one that has
> you use the
Mihai,
Are you following the latest version of the README? The one that has
you use the 'installer.xml' instead of the 'ide' build scripts? If
not, would you try it?
Thanks,
EdB
On Wed, Dec 17, 2014 at 6:17 PM, Mihai Chira wrote:
> I compiled blazeds separately (cd ../flex-blazeds & ant clea
> I compiled blazeds separately (cd ../flex-blazeds & ant clean & ant
> main), and now it seems to be working. I'll let you know once it's
> done if I can compile an app.
Alex,
I thought there was no need to compile BlazeDS before being able to
compile the SDK. I thought the SDK just took some co
>>Why not commit the 2nd option for this fix to the 'develop' branch, ...
>
> I've done the change (the 2nd option), and pushed it to the 'develop' branch.
>
> Awaiting review and vote.
I'll let Mustella have a go at the new code first. I'm sure some other
committers will have an opinion as well.
OK, so we do get a good fix with the updated config. Then I'll ask you
to commit that to the 'release4.14' branch.
The rest goes into the 'flex-utilities' repo, of course, so that won't
interfere with the upcoming SDK release.
Good work!
EdB
On Wed, Dec 17, 2014 at 5:44 PM, Neil Madsen
wrote
I compiled blazeds separately (cd ../flex-blazeds & ant clean & ant
main), and now it seems to be working. I'll let you know once it's
done if I can compile an app.
On 17 December 2014 at 16:52, Mihai Chira wrote:
> I did a super-clean, and now the error changed: it failed when trying
> to compil
I did a super-clean, and now the error changed: it failed when trying
to compile blazeds:
compile:
[javac]
c:\Users\evolverine\workspace\flex-blazeds\modules\common\build.xml:54:
warning: 'includeantruntime' was not set, defa
ulting to build.sysclasspath=last; set to false for repeatable buil
Hi Erik,
>Why not commit the 2nd option for this fix to the 'develop' branch, ...
I've done the change (the 2nd option), and pushed it to the 'develop' branch.
Awaiting review and vote.
DarkStone
2014-12-18
At 2014-12-17 18:54:51, "Erik de Bruin" wrote:
>DarkStone,
>
>Why not commit the 2nd
To fix the initial issue it was only the config file but as I dug into it I
discovered a couple other things. There were acutally a few separate issues.
The original issue should still be able to be fixed by updating the config
file.
The other thing that Justin noticed with the check boxes needed
>> So, "all" that is needed are changes to the installer config file(s) in
> the SDK?
>
> Yes, the only changes for the flex-sdk are in the
> 'apache-flex-sdk-installer-config.xml' file. All other changes are in the
> installer code.
OK. I must have misunderstood something earlier in the thread(s)
Erik,
I haven't been able to log into Git yet. Still trying to determine what the
problem is.
I could create a patch and attach it to the JIRA ticket though.
> So, "all" that is needed are changes to the installer config file(s) in
the SDK?
Yes, the only changes for the flex-sdk are in the
'ap
Do a 'super-clean' instead of a clean, and make sure your workspace is
up to date. The fix for the 'flex-tool-api' download is in there
(https instead of http)...
EdB
On Wed, Dec 17, 2014 at 5:22 PM, Mihai Chira wrote:
> Running
>
> ant clean
> ant main
>
> should work just fine, right? I'm on
Running
ant clean
ant main
should work just fine, right? I'm on the release4.14.0 branch, but
when I run ant main I keep getting
BUILD FAILED
c:\Users\evolverine\workspace\sdk\build.xml:411: The following error
occurred while executing this line:
c:\Users\evolverine\workspace\sdk\modules\build.x
> Sorry for making some more noise but I've one more question;-)
No need to apologize for wanting to learn something! We love to see
new people get involved in the project and never consider them noisy
:-)
> Is JIRA for issues (bugs) only or could I use a JIRA ticket for improvement
> suggestion
>The best way to make sure no issues are lost in the noise on this list, is to
>file a JIRA ticket.
Sorry for making some more noise but I've one more question;-)
Is JIRA for issues (bugs) only or could I use a JIRA ticket for improvement
suggestions also?
Olaf
[Merry Christmas - Frohe Weihnacht
> If I'll find other issues regarding 'flatspark', is it the right way to
> create a new topic here at the 'dev-list'?
The best way to make sure no issues are lost in the noise on this
list, is to file a JIRA ticket. This is where that happens:
https://issues.apache.org/jira/browse/FLEX
That wa
>I will take at look at this tonight, are you using the same example in the
>GitHub page, just changing the chrome color?
No, I just create a new project with only one button inside:
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
This looks great. I'll try it hopefully today. It also probably means
we can delete those sh and bat files, which should simplify work with
the SDK.
On 17 December 2014 at 13:41, wrote:
> Changed 'prepare SDK' section again
>
> After Mihai's effort, I looked into this some more. Turns out the ea
You could just do a command prompt version [1]. The /s allows it to be
recursive. The greator than specifies it to dump the output into a new text
file rather than show it on the screen. This will be formatted like windows
though instead of a linux list (ls).
[1] dir /s > dump.txt
-Mark
>
> I've copy and paste some code from the "WebAppTest.mxml" inside the
> "flatspark git repository":
>
> https://github.com/akamud/FlatSpark/blob/master/samples/WebAppTest/src/WebAppTest.mxml
The examples are outdated, I'll update it once we release the 4.14 SDK.
They only work with the old vers
Thanks for testing, Dany!
I really helps us feel more confident about an upcoming release if
others have positive experiences with the pre-release nightlies.
I hope you will help out again testing the official release packages
once we start the vote.
EdB
On Wed, Dec 17, 2014 at 1:12 PM, Dany
Hi all,
Eric, I did what you asked and re-installed the sdk using the installer. Now it
works as a charm!!
What I noticed was that the installer itself is extremely slow in finding the
config xml. It took 2 restarts of the installer and then about 15 secs to load.
Don't know if this means any
I’ve had trouble in the past. For some reason my Apache login got messed up.
IIRC, resetting the password did it for me.
On Dec 17, 2014, at 1:07 PM, DarkStone wrote:
> I have trouble connecting to the git, I don't know why
Yes. Please.
If you do find something broken, small test cases would be very helpful in
getting it fixed.
Thanks,
Harbs
On Dec 17, 2014, at 1:06 PM, Erik de Bruin wrote:
> Hi,
>
> For the upcoming 4.14 release we hope to include an update to TLF that
> adds support for tables. This is a big
Hi Erik,
I have trouble connecting to the git, I don't know why, I think I will use some
VPN, then try to do this.
DarkStone
2014-12-17
At 2014-12-17 18:54:51, "Erik de Bruin" wrote:
>DarkStone,
>
>Why not commit the 2nd option for this fix to the 'develop' branch,
>and let Mustella run it's t
Hi,
For the upcoming 4.14 release we hope to include an update to TLF that
adds support for tables. This is a big change to TLF, so we need to
make sure that:
1) the addition of the tables feature didn't break any existing
functionality, and
2) the new feature is working correctly.
So, I'd like
I've just found that using flatspark and setting the applications chrome
color results in and error:
Error message for :
Error #1069: Property iconDisplay not found on flatspark.skins.ButtonSkin
and there is no default value.
Error message for :
Error #1069: Property dot not found on flatspark.sk
DarkStone,
Why not commit the 2nd option for this fix to the 'develop' branch,
and let Mustella run it's tests to see if nothing breaks? If someone
objects, well, we "commit then review" and if someone vetoes the
commit, we simply revert and have another look at the issue.
Thanks,
EdB
On Wed,
On 17/12/14 10:35, Devesh Mishra(NABFS00) wrote:
What I am supposed to do in order to test Apache Flex 4.14 ? Kindly let me know.
I install it, and then at least build, deploy to testing and debug our
main applications.
Where there are formal unit tests, run those against the new SDK.
Tom
Hi,
I'm sorry, my bad, I missed a condition on that bug fix:
This is wrong:
clearStyle("skinClass");
This is correct:
styleProp == "styleName" ? clearStyle("skinClass") : null;
But even with this change, there is still a bug if you do the followings:
1. Inside the constructor function of a Ski
Devesh,
The easiest way to help out is to download the 4.14 RC nightly build
using the Apache Flex Installer
(http://flex.apache.org/installer.html). In order to make the 4.14 RC
option visible, you right click anywhere on the Installer window and
select 'Show Dev Builds'.
Once the 4.14 RC SDK is
What I am supposed to do in order to test Apache Flex 4.14 ? Kindly let me know.
--
Thanks & Regards,
Devesh Mishra
-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Sunday, December 14, 2014 10:46 PM
To: us...@flex.apache.org
S
Neil,
Awesome! Thanks for following through.
So, "all" that is needed are changes to the installer config file(s) in the SDK?
Have you been able to log into Git in order to commit your change(s)?
EdB
On Tue, Dec 16, 2014 at 9:17 PM, Neil Madsen
wrote:
> So I think I have it all sorted out n
gt; > job would refresh the build?
>> >
>> > Thanks,
>> > Om
>> > On Dec 17, 2014 1:42 AM, "Krüger, Olaf" wrote:
>> >
>> >> Om,
>> >> thanks for solving this issue and solving it so fast.
>> >> I’m impressed o
gt; >
> > Thanks,
> > Om
> > On Dec 17, 2014 1:42 AM, "Krüger, Olaf" wrote:
> >
> >> Om,
> >> thanks for solving this issue and solving it so fast.
> >> I’m impressed of this Flex community again and again!
> >>
> >> O
>Where is the camel case? In a config file, or do you mean in the filename
>itself?
I've copy and paste some code from the "WebAppTest.mxml" inside the "flatspark
git repository":
https://github.com/akamud/FlatSpark/blob/master/samples/WebAppTest/src/WebAppTest.mxml
So this is no real issue...
Where is the camel case? In a config file, or do you mean in the
filename itself?
EdB
On Wed, Dec 17, 2014 at 11:02 AM, okrue...@edscha.com
wrote:
> Perhaps this is helpful:
> I've installed 4.14. RC yesterday and to make flatspark working I have to
> remove the camel case in 'flatSpark' and i
Perhaps this is helpful:
I've installed 4.14. RC yesterday and to make flatspark working I have to
remove the camel case in 'flatSpark' and import the flatspark.swc manually
to the lib folder.
Environment is Windows 7 64bit, FlashBuilder 4.5
--
View this message in context:
http://apache-flex
Hi Alex,
I've located the problem:
Step 1. Using MySkinnableComponent.setStyle("skinClass", SkinA) to apply an
initial skin is ok.
Step 2. Then using MySkinnableComponent.styleName = "skinB" won't work, the
skin won't change.
When [Step 2] happens, inside the validateSkinChange() function of
>> I’m impressed of this Flex community again and again!
>>
>> One question:
>> I’ve just installed the latest ‘4.14. build 20141217’ to be able to test
>> the solved issue but it seems that your commit is not included.
>> Surfing through the repository I’ve seen th
t so fast.
> I’m impressed of this Flex community again and again!
>
> One question:
> I’ve just installed the latest ‘4.14. build 20141217’ to be able to test
> the solved issue but it seems that your commit is not included.
> Surfing through the repository I’ve seen that you revert th
Om,
thanks for solving this issue and solving it so fast.
I’m impressed of this Flex community again and again!
One question:
I’ve just installed the latest ‘4.14. build 20141217’ to be able to test the
solved issue but it seems that your commit is not included.
Surfing through the repository
I've just installed SDK 4.14 in my work and create new project and I see
playerglobal.swc in project configuration. It's compiling without problem.
I will let you know whether re-installation of my IDE helped.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in contex
>From the SDK contents comparison the only differences seem to be
-I have many more folders and files in ./lib/aot - does someone know
what that folder contains? They look like mobile stuff, so I guess
they shouldn't impact desktop compiling.
-you're using flash player 14, I'm using 15
-you're mis
Om,
thanks for solving this issue and solving it so fast.
I’m impressed of this Flex community again and again!
One question:
I’ve just installed the latest ‘4.14. build 20141217’ to be able to test the
solved issue but it seems that your commit is not included.
Surfing through the repository
>
> I believe he might have an environment issue, since I don't have that issue
> with a fresh install of 4.14.
>
Yeah, probably. The weirdest part, for me, is that it will work if I import
the swc.
I checked all the fonts comparing with the mobile theme and the actual
path, and everything looks c
71 matches
Mail list logo
