On 12/10/14, 11:25 PM, "Erik de Bruin" wrote:
>Alex, did BlazeDS integration fully land, as far as the docs are
>concerned?
It seems to be working for me. It could use more testing. It would be
great if someone took the nightly and tried to follow the README to build
the source package.
Sho
Om,
Thank you!
> P.S. Do hit me in the head and let me know if I am not following the new
> release process. I am a bit confused about that.
You've declared your intention to create a release, to be RM and asked
the people to start testing. Seems like you're already halfway to a
release ;-) So
Please forgive my question if it’s a dumb one, but I did not find this info on
a casual search…
When a new project is created, where does the app.xml file come from? Is that
something controlled by the AIR package, Flash Builder, or Flex?
The primary reason I’m asking this question is because t
On Dec 11, 2014 12:46 AM, "Harbs" wrote:
>
> Please forgive my question if it’s a dumb one, but I did not find this
info on a casual search…
>
> When a new project is created, where does the app.xml file come from? Is
that something controlled by the AIR package, Flash Builder, or Flex?
>
> The pr
Could it be this file?
frameworks/AIRSDK_Compiler/templates/air/descriptor-template.xml
On Dec 11, 2014, at 10:46 AM, Harbs wrote:
> Please forgive my question if it’s a dumb one, but I did not find this info
> on a casual search…
>
> When a new project is created, where does the app.xml file
MacBook Pro 15 inch Retina Display.
I think I found a template here
frameworks/AIRSDK_Compiler/templates/air/descriptor-template.xml, but I don’t
know if that’s the one which is actually used…
On Dec 11, 2014, at 10:58 AM, OmPrakash Muppirala wrote:
> On Dec 11, 2014 12:46 AM, "Harbs" wrote:
I just confirmed that the template used is the one in the built SDK here:
[SDK]/templates/air/descriptor-template.xml
A made a change to one of the comments, and the change was reflected in the
app.xml of a new project.
I have not studied the build scripts, but it seems like a fair assumption t
No objections on my part, but does it need to be changed?
On 11 Dec 2014 10:23, "Harbs" wrote:
> I just confirmed that the template used is the one in the built SDK here:
> [SDK]/templates/air/descriptor-template.xml
>
> A made a change to one of the comments, and the change was reflected in
> th
Any app run on a retina Mac needs it to be high. The average developer will
probably not know that (and might not even have a retina Mac to test it on).
I’m not aware of any real problems with making it high by default. (If I’m
wrong here, I’d really like to be corrected.)
These seem like prett
To be clear: I’m talking about the requestedDisplayResolution inside the
initialWindow tag. This one is for desktop apps.
There’s another one inside the iPhone tag which I am not discussing.
On Dec 11, 2014, at 12:20 PM, Harbs wrote:
> Any app run on a retina Mac needs it to be high. The avera
Ah is this an IOS centric default? I am a Windows and Linux man, never used
a Mac and never developed for any Apple platform
On 11 Dec 2014 11:22, "Harbs" wrote:
> Any app run on a retina Mac needs it to be high. The average developer
> will probably not know that (and might not even have a retin
+1 on 'high' - but hey, I'm Dutch, that's our default anyway :-P
Unless there are serious performance issues. Isn't there an
'auto-high' maybe. Some possible setting that is 'intelligent'?
EdB
On Thu, Dec 11, 2014 at 11:20 AM, Harbs wrote:
> Any app run on a retina Mac needs it to be high. Th
as long as the high setting is cross platform happy, I see no objection on
my part to the change
On 11 Dec 2014 11:22, "Harbs" wrote:
> Any app run on a retina Mac needs it to be high. The average developer
> will probably not know that (and might not even have a retina Mac to test
> it on). I’m
I’m discussing Mac desktop, but there’s also a setting for iOS.
AFAIK, this setting does not affect Windows or Linux at all.
On Dec 11, 2014, at 12:29 PM, aYo ~ wrote:
> Ah is this an IOS centric default? I am a Windows and Linux man, never used
> a Mac and never developed for any Apple platfor
Not that I know of, but I am not familiar with the inner workings here…
On Dec 11, 2014, at 12:30 PM, Erik de Bruin wrote:
> Isn't there an 'auto-high' maybe. Some possible setting that is 'intelligent'?
Alright. I’m feeling pretty stupid right now…
That file was not in flex-sdk. It was in the AIR SDK dependency.
Unless we modify that file as part of the build script, I don’t see how we can
change the default…
On Dec 11, 2014, at 10:57 AM, Harbs wrote:
> Could it be this file?
> frameworks/AI
OK. Maybe file a JIRA documenting this issue and the workaround, with
the suggestion someone look at the build script that adds AIR to the
SDK to change that template?
EdB
On Thu, Dec 11, 2014 at 11:45 AM, Harbs wrote:
> Alright. I’m feeling pretty stupid right now…
>
> That file was not in fl
Hi,
Apart from TLF, are there any issues that require more time and
therefore a delay in the cutting of the release branch?
Remember, we're not trying to be perfect, we can stabilize the branch
in the next few weeks, but if you want something included and are
"nearly" done, speak up now!
If I do
Hey Alex,
The compile worked fine and I have do have the fr_FR folder at
frameworks/locale along with many others. The fr_FR folder does contain the
_rb.swc files.
I'm going to add a new mustella test to the mxml for getString(). I am running
all tests for the ResourceManager to make sure
I just checked in at first attempt to the the OFL font warnings in the
install. I still need to test the Ant-only install. When the CI server
finished building it would be good to have folks try it out. It pointed
out one thing: you can’t install if you don’t accept the OFL license. It
would b
I ran the ResourceManager tests. They all pass for me. I haven’t looked
at the tests to see if any actually test for multiple locales, so the
issue may be that those tests will now need a .compile file like the kind
in RuntimeLocalization.
But if you haven’t made any changes and you can’t get th
On 12/11/14, 12:40 AM, "Erik de Bruin" wrote:
>Om,
>
>Thank you!
>
>> P.S. Do hit me in the head and let me know if I am not following the
>>new
>> release process. I am a bit confused about that.
>
>You've declared your intention to create a release, to be RM and asked
>the people to start t
Alex,
Here ya go. Thanks for helping me out with this.
CMartin@CMARTINDT ~/Documents/GitHub/flex-sdk/mustella (develop)
$ ./mini_run.sh tests/resources/ResourceManager
Skipping testcase check
Doing a regular mini run
Buildfile: c:\Users\cmartin\Documents\GitHub\flex-sdk\mustella\build.xml
[lo
I have updated the homepage [1] to include a section for FlexJS - An
Introduction presentation.
Thanks,
Om
[1] http://flex.apache.org/
On Thu, Dec 4, 2014 at 1:57 PM, Mihai Chira wrote:
>
> +1
>
> On 4 December 2014 at 18:39, OmPrakash Muppirala
> wrote:
> > Cool, thanks! SVN is down right no
Hi Chris,
OK, I didn’t fully grok what you were asking about until I saw the console
and re-read your original question. One of the un-polished aspects of
Mustella is that there are some tests that fail when run in the full set
yet pass when run individually. Our CI servers actually run two pas
Sweet! Unfortunately even running with the -failures flag, the test still
fails, but for a different reason.
Error #2044: Unhandled ioError:. text=Error #2032: Stream Error. URL:
file:///c:/tmp/IncludeList.txt
at
IncludeFileLocation$/init()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustella
On 12/11/14, 1:45 PM, "Chris Martin" wrote:
>Sweet! Unfortunately even running with the -failures flag, the test
>still fails, but for a different reason.
>
>Error #2044: Unhandled ioError:. text=Error #2032: Stream Error. URL:
>file:///c:/tmp/IncludeList.txt
> at
>IncludeFileLocation$/init()
Okay, verified there are no duplicate test names. I added
tests/resources/ResourceManager/SWFs/ResourceManagerApp.compile which contains:
-locale=fr_FR,ja_JP,en_US,de_DE
-library-path+=${sdk.dir}/frameworks/locale/{locale}
As the tests do use those for getting resource bundles. Still getting
This is odd. I also tried to change the locale reference from fr_FR to en_US
just to see if I can get a little further along, and I still get same error,
but it references not being able to find it for 'en_US'. Do you think this
suggests a deeper issue than a .compile file?
Chris
> From: ch
OK, I wonder if the exception is fooling the output report.
So, let’s just try to fix the test. The test run should also leave a
ResourceManagerApp.lnk.xml file in the SWFs folder. Open that and you
should be able to find en_US/containers.properties etc. Is
fr_FR/containers.properties or any me
OK, I dug into it and have a better guess why it fails in the full set and
passes on its own. I added a .compile file (just the -locale, the library
path should already be set) and verified the fr_FR bundle was in the app.
However, in looking at these tests, you aren’t supposed to have a fr_FR
lo
This says it applies to Macbook Pro with a Retina display:
If the requestedDisplayResolution element is nested in the initialWindow
element, it applies to desktop AIR applications on MacBook Pro computers
that support high-resolution displays. [1]
It other words this setting does not apply to app
Hey Alex,
Yeah I see what you mean. I think I figured out what happened. We have a
commit made to ResourceManagerImpl.as[1] which I believe now obsoletes those
types of tests because we now throw an exception if it was unable to find the
locale. So really we cannot get ourselves into that s
Hi Chris,
Right now, I think I want to know why that one test fails when run as the
full set and passes on the failures run. I think if it had failed on the
failures run then we’d have looked deeper earlier and realized we broke
the ‘missing bundle’ case for findResourceBundleWithResource(). We
Sure! I too am curious why it fails in the group but passes when we run it by
itself. The exception throw didn't go anywhere.
I did take out the exception throw and got only 4 failures. Then I decided to
take out the .compile file as I noted that for the tests we are building up
custom bundle
I'm ready for a release branch if you are.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Alex Harui wrote:
I just checked in at first attempt to the the OFL font warnings in the
install. I still need to test the Ant-only install. When the CI server
finished building it would be go
36 matches
Mail list logo
