On Dec 10, 2014 11:11 PM, "Erik de Bruin" wrote:
>
> > The wiki page does not seem to exist, btw.
>
> That's weird ... I just clicked and it takes me to the page with the
> example code.
Actually the page loads fine now. Looks awesome!
Thanks,
Om
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
>
Alex, did BlazeDS integration fully land, as far as the docs are concerned?
EdB
On Wed, Dec 10, 2014 at 6:30 PM, Alex Harui wrote:
> The BlazeDS integration will affect all of these documents, so folks
> should wait until it lands.
>
> -Alex
>
> On 12/10/14, 1:17 AM, "OmPrakash Muppirala" wro
> The wiki page does not seem to exist, btw.
That's weird ... I just clicked and it takes me to the page with the
example code.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
I have tested the TDF Mobile code [1] with the new iOS and Android skins
from the nightly version of 4.14.0. For the most part, things are looking
great. There are a few minor things that will need to get fixed. I plan
to add some more features and examples before cutting the final releases.
It
Sorry, sometimes my communication skills leave to be desired... I'll do my
best:
1.- Setting values: Right now FDB only allows to set the value of simple
variables (numeric types, strings, and booleans). I improved some debugging
features in FlashDevelop, like live edition of variables, however, n
First, did the locale compile work? Are there _rb.swc files in the sdk’s
frameworks/locale/fr_FR folder?
Are you adding a test to an existing file of tests or creating a whole new
thing? There are .compile files that control what locales get compiled
into a SWF. See the mustella/tests/RuntimeLo
Very nice! Looking forward to using this in a project sometime soon.
The wiki page does not seem to exist, btw.
Thanks,
Om
On Wed, Dec 10, 2014 at 5:05 AM, Erik de Bruin wrote:
> Hi,
>
> I have just committed the 'Promise' class to the SDK. This class
> follows the JavaScript Promise/A+ patte
Well, I was hoping compiling for all locales would do the trick, but i'm still
getting the same error. Silly me was only looking at the readme for mustella
and didn't think to check the readme for the SDK itself. Any other ideas? I'm
thinking it's a compile switch for the swf that is generate
It might also be a good idea to create a JIRA ticket.
I'm actually not quite sure what you mean in your two "wishes": setting values
and determining types. Can you give me an example or more details?
Thanks,
-Ale
From: Héctor A [neverbi...@gmail.com]
Sen
> Try doing ant other.locales first? That's what the README seems to
indicate.
Actually no. Thanks Om! I'll give that a go.
From: OmPrakash Muppirala
Sent: Wednesday, December 10, 2014 1:33 PM
To: dev@flex.apache.org
Try doing ant other.locales first? That's what the READ
I know Apache has the code, and I wouldn't mind looking into it myself, but
my lack of time makes it imposible, so I'm posting here, since support for
workers was added by a team member not long ago, maybe he or someone else
knows about the feasibility of this, which would be enough at this moment.
Lately I have moved from Intellij 12 to Intellij 14 and after one of the
launch of IDE I got prompt about some survey. They had a question:
"Are there any features you'd like to have but did not find in IntelliJ
IDEA?" - I have answered - Support for FlexJS. :)
They have responded me back almost
Apache Flex has the code for FDB, so feel free to try to improve it. I
don’t know it that well, but some of the features you are talking about
may require player/VM changes and therefore unlikely to happen.
Do you have a link to information about the “rewind” debugger? It might
have also require
Try doing ant other.locales first? That's what the README seems to
indicate.
If you want only fr_FR, you could try ant -Dlocale=fr_FR
Thanks,
Om
On Wed, Dec 10, 2014 at 12:28 PM, Chris Martin wrote:
> Hey everyone,
>
> In trying to create a new mustella test case for ResourceManager, i'm
> t
Hey everyone,
In trying to create a new mustella test case for ResourceManager, i'm trying to
run the tests to get a baseline. When I run the tests I get a failure.
[java] =
[java] Failed:
[java] ===
On Wed, Dec 10, 2014 at 12:18 PM, Héctor A wrote:
> I'd be interested in seeing it supported in FlashDevelop, but I'm currently
> too busy improving and adding several features to it. Philippe started
> working on it time ago, but left it in a very preliminar state and didn't
> commit the changes
I'd be interested in seeing it supported in FlashDevelop, but I'm currently
too busy improving and adding several features to it. Philippe started
working on it time ago, but left it in a very preliminar state and didn't
commit the changes.
On Tue, Dec 9, 2014 at 12:40 PM, piotrz wrote:
> Hi,
>
I've been looking at FDB lately, and got a bit disappointed when I saw that
it only allows to set the value of scalar variables. Do any of you think is
it possible to improve it?
Also, Adobe showed some years ago some experimental work that allowed to
rewind some code back while debugging, I guess
On Wed, Dec 10, 2014 at 8:40 AM, Nick Collins wrote:
> Personally, I would see a lot of value to re-engineering the MXML
> components we're familiar with using Angular Directives or custom Polymer
> tags, then make the other services, such as data binding, HTTP services,
> etc., additional librar
The BlazeDS integration will affect all of these documents, so folks
should wait until it lands.
-Alex
On 12/10/14, 1:17 AM, "OmPrakash Muppirala" wrote:
>Thanks for reminding. I will take a look tomorrow.
>
>Thanks,
>Om
>On Dec 10, 2014 1:14 AM, "Erik de Bruin" wrote:
>
>> Bump...
>>
>> EdB
Personally, I would see a lot of value to re-engineering the MXML
components we're familiar with using Angular Directives or custom Polymer
tags, then make the other services, such as data binding, HTTP services,
etc., additional libraries that can be included as needed using Bower or
something sim
I think i'll just bake my own solution - we shouldnt be making changes
to the sdk on one persons whim
Lee Burrows
ActionScripter
On 10/12/2014 01:00, OmPrakash Muppirala wrote:
On Tue, Dec 9, 2014 at 1:39 PM, Alex Harui wrote:
Om, I haven’t really followed what you are doing, but is it impr
On 10/12/14 14:21, Erik de Bruin wrote:
[flexunit] Using the following settings for compilation:
[flexunit] FLEX_HOME: [c:\Jenkins\workspace\flex-sdk_test]
[flexunit] player: [flash]
Maybe that SDK hasn't been build with the new bits ?
Tom
Doh! First build the SDK, dude ;-)
All is well now, the tests run cleanly on the CI server.
EdB
On Wed, Dec 10, 2014 at 3:21 PM, Erik de Bruin wrote:
> And, like it's software development or something, stuff is not working
> on the CI machine. This is my ant 'stack trace':
>
> test-run:
>
And, like it's software development or something, stuff is not working
on the CI machine. This is my ant 'stack trace':
test-run:
[echo] Unit tests for
'c:\Jenkins\workspace\flex-sdk_test\frameworks\projects\apache'
[flexunit] Validating task attributes ...
[flexunit] Generating default val
I'm trying to avoid 'last-minute' finds, and long discussions at a
late stage that might block the release. Basically I'm starting early
on calling on people to help out with the various tasks that have
proved 'contentious' during previous releases :-)
EdB
On Wed, Dec 10, 2014 at 2:06 PM, Tom C
Ah, and before I forget: I have added a new job to the build VM that
runs all tests on every commit or once daily (like the other jobs).
EdB
On Wed, Dec 10, 2014 at 2:17 PM, Erik de Bruin wrote:
> Hi,
>
> While working on the Promise class, I very much wanted to be able to
> use FlexUnit to te
Oh, sorry, you just seemed really keen :-)
Tom
On 10/12/14 12:53, Erik de Bruin wrote:
This is about the documentation. Especially these files: README,
RELEASE_NOTES, NOTICE, LICENSE and CONTRIBUTORS.
These are in their 'final' state, not likely to substantially change,
whether we include the
Hi,
While working on the Promise class, I very much wanted to be able to
use FlexUnit to test the code. As I could not find SDK wide support
for FlexUnit, I went ahead and started building it.
I'm working on an article [1] that will eventually explain it all,
here is the rough guide:
1) the main
Hi,
I have just committed the 'Promise' class to the SDK. This class
follows the JavaScript Promise/A+ pattern [1].
I'm working on a Wiki article [2] to explain how cool Promises are and
what they can mean for Flex projects, but for now, here is some
reading:
http://spring.io/understanding/javas
This is about the documentation. Especially these files: README,
RELEASE_NOTES, NOTICE, LICENSE and CONTRIBUTORS.
These are in their 'final' state, not likely to substantially change,
whether we include the TLF 'tables' contribution or not.
Thanks,
EdB
On Wed, Dec 10, 2014 at 1:42 PM, Tom Chi
One thing that altering the major version number is the publicity and
public perception that would come from it. Sure, it's just a number, but
according to the Apache rules, we can put out a bonafide press-release that
gets pushed out all the PR channels. Also, with a major version number the
pub
Given the flex-tlf unit tests are all failing on apacheflexbuild and
have been for two weeks, I don't imagine there is much rush as I
understand there is a bunch of TLF changes in the release ?
Tom
On 10/12/14 09:12, Erik de Bruin wrote:
Bump...
EdB
On Thu, Dec 4, 2014 at 11:53 AM, Erik d
Here's the thing. Since Adobe donated Flex to the Apache Project, I've
made a lot of money on the excellent work of many of my colleagues here at
Apache. I've made enough to pay my mortgage, utilities, buy a new car and
be very comfortable. Sure, the number of web projects involving Flex is on
a
The businesses that use the end products will not be on here discussing the
apps they use or have developed. But in the end Flex has the ability to make
strong, well supported apps. Having it be able to compile into multiple
destinations such as flash, air, native android/apple, html/js is fan
It's not a mute point as getting Adobe to release an update will be a
lot of work, for us, them and the end users, when there is no need at
all to alter the major version number.
Tom
On 10/12/14 11:48, Kessler CTR Mark J wrote:
So would that mean if FB was incompatible with our version number
So would that mean if FB was incompatible with our version number they would
release an update that corrects FB to support it? If the answer is yes, then
it's a moot issue about version number for it.
-Mark
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent:
Hi,
> AFAIK Builder still gets updates. The Adobe white paper has a commitment to
> make it continue to work with Apache Flex.
You may be interested in this. [1] Flex Builder 4.7 support goes up to 2018
extended support goes up to 2020.
Justin
1. https://www.adobe.com/support/products/enterpr
Hi All,
I'm convinced that there are a lot of developers out there who are still
committed to Flex. Many of us (as I am) aren't nearly as good as you committers
so we rely on you to keep up the fantastic work you're doing!
Respect!!
Dany
Op 10 dec 2014 om 10:51 uur uur schreef Justin Mclean
Hi,
Even if AS / Flex isn't as popular as it once was we do still get quite a bit
of interest. The Flex web site gets 3/4 of a million visits a year. There's
been 20,000+ users of TourDdFlex over the past few months, the last SDK version
has had more than 10,000+ installs of the SDK via the ins
Thanks for reminding. I will take a look tomorrow.
Thanks,
Om
On Dec 10, 2014 1:14 AM, "Erik de Bruin" wrote:
> Bump...
>
> EdB
>
>
>
> On Thu, Dec 4, 2014 at 11:53 AM, Erik de Bruin wrote:
> > Hi,
> >
> > I want to make sure that the SDK documentation (README, RELEASE_NOTES,
> > NOTICE, LICEN
On 09/12/14 23:53, Jesse Nicholson wrote:
You made it clear you're in maintenance mode and that this project is
actually for corporate interest when you told me to hush and not use words
that might upset adobe customers.
You can say what you like about Adobe.
I've been out spoken about what I th
Bump...
EdB
On Thu, Dec 4, 2014 at 11:53 AM, Erik de Bruin wrote:
> Hi,
>
> I want to make sure that the SDK documentation (README, RELEASE_NOTES,
> NOTICE, LICENSE and CONTRIBUTORS) is in order BEFORE we enter the
> release cycle. This will avoid discussion and delay, so please
> contribute i
AFAIK Builder still gets updates. The Adobe white paper has a commitment
to make it continue to work with Apache Flex.
We shouldn't break (any) 3rd party products if we can avoid doing so.
Chris' point is also valid about companies being slow to move
development platforms, and we'd probably tra
44 matches
Mail list logo
