BTW, the Adobe BlazeDS team says the latest public version is 4.6, not 4.5
or 4.0.1.
-Alex
On 4/30/14 9:34 PM, "Alex Harui" wrote:
>I took a look at the BlazeDS ant script. I fixed a few things and it
>completed. The main target does not run any tests and I did not take the
>time to try to ru
I took a look at the BlazeDS ant script. I fixed a few things and it
completed. The main target does not run any tests and I did not take the
time to try to run tests.
-Alex
On 4/30/14 8:12 AM, "Christofer Dutz" wrote:
>Well the problem is, is that the Ant build is completely fu***d up ... it
I'm impressed. Was interesting to see the breakouts of install by OS type.
-Mark
-Original Message-
From: DarkStone [mailto:darkst...@163.com]
Sent: Wednesday, April 30, 2014 8:00 AM
To: dev@flex.apache.org
Subject: Adobe AIR app installs cross a billion
http://blogs.adobe.com/flashplay
I think core.swc is supposed to contain stuff you can use in AS3 projects
w/o pulling in all of the other Flex stuff. Maybe it can go there?
On 4/30/14 1:08 PM, "Frédéric THOMAS" wrote:
>Alex,
>
>Too much time on it, the reason why it didn't stop in the worker is
>because the compiled worker di
Alex,
Too much time on it, the reason why it didn't stop in the worker is because the
compiled worker didn't included the base worker class, better that than what I
thought :P
Also, it's going to work for Flex projects but not for pure AS3 projects if I
put that base class in the existing libs
It is not even that, even if I stop in the main thread, switch to the worker
and try to stop it, it doesn't want, digging into
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: [FDB] Integration
> Date: Wed, 30 Apr 2014 19:47:33 +0100
>
> What I did an
What I did and 1st surprised I thought it was the "halt" command to debug, not
even, it was in the main loop and the trick is, I had to code to stop only on
the main thread, it doesn't work with the current implementation, well, not so
but at the end, given once it is halted we can switch to ano
Hi,
I don't think anybody is actively working on it, but you are welcome to
jump in. Often, when you start on something, it inspires other to join in.
The code is in the flex-utilities repo. We use git for version control.
There are several projects in flex-utilities. You will find a TourDeFl
Looks right. Maybe capabilities.isDebugger isn't true or setInterval
doesn't work?
You've got a new debugger, step through it. ;-)
-Alex
On 4/30/14 9:58 AM, "Frédéric THOMAS" wrote:
>I created a base class that the workers extend but doesn't seem to work,
>did I miss something ?
>
>/**
> * Us
I created a base class that the workers extend but doesn't seem to work, did I
miss something ?
/**
* User: DoubleFx Date: 30/04/2014 Time: 17:34
*/
package {
import flash.display.Sprite;
import flash.system.Capabilities;
import flash.utils.setInterval;
public class DebugWorker extends Sprite
Greetings,
Adobe recently donated the Tour De Flex code to Apache. I think Tour De Flex
is a great way to provide active documentation to Flex users. An updated
application showing all the improvements made with each release of Flex (new
components, features, etc . ) would be great in my opinio
On 4/30/14 8:49 AM, "Frédéric THOMAS" wrote:
>Could be a solution, you meant like the idleTimer in SystemManager ?
Actually, I was referring to debugTickler in Application.as (both mx and
spark).
-Alex
Could be a solution, you meant like the idleTimer in SystemManager ?
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: [FDB] Integration
> Date: Wed, 30 Apr 2014 15:28:26 +
>
>
>
> On 4/30/14 8:15 AM, "Alexander Doroshko"
> wrote:
>
> >On 30.04.2014 17:30,
Ah I guess I see your point now, correct me if I'm wrong, you have the need to
be able set a BP before the next break event, right ?
If it is the case, not sure I can do many things, I don't think I can catch a
worker status change until I receive a myself break event, I check it though.
I plan
Impressive!
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Apache-Most-Active-projects-tp37360p37374.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 4/30/14 8:15 AM, "Alexander Doroshko"
wrote:
>On 30.04.2014 17:30, Frédéric THOMAS wrote:
>>> Why to put some BP in on the suspended ones ?
>> I meant : Why to put some BP only in the suspended ones ?
>You are right, suspending all running workers that contain the file,
>setting breakpoint t
On 30.04.2014 19:20, Frédéric THOMAS wrote:
You are right, suspending all running workers that contain the file,
setting breakpoint there (and probably resuming?) seems to be the best.
Sure resuming it if I halted it.
Unfortunately some workers may fail to suspend if they are doing
nothing.
> You are right, suspending all running workers that contain the file,
> setting breakpoint there (and probably resuming?) seems to be the best.
Sure resuming it if I halted it.
> Unfortunately some workers may fail to suspend if they are doing
> nothing. In the latter case breakpoint could be r
P.S. I have some extra days off this week and will be able to continue
discussion only on Monday.
On 30.04.2014 17:30, Frédéric THOMAS wrote:
>> Why to put some BP in on the suspended ones ?
> I meant : Why to put some BP only in the suspended ones ?
You are right, suspending all running workers that contain the file,
setting breakpoint there (and probably resuming?) seems to be the best.
Unfor
Well the problem is, is that the Ant build is completely fu***d up ... it
doesn't work at all.
And it's no problem at all to call a maven build from Ant and vice-versa.
Chris
Von: Alex Harui
Gesendet: Mittwoch, 30. April 2014 16:38
An: dev@flex.apache.or
Well it actually builds now ... just that it doesn't fail on test-errors ...
All artifacts are create correctly.
Chris
Von: Erik de Bruin
Gesendet: Mittwoch, 30. April 2014 16:23
An: dev@flex.apache.org
Betreff: Re: Has anyone been able to build BlazeDS
Long live Flex.
Sent from BlackBerry® on Airtel
-Original Message-
From: Rushme Nayak
Date: Wed, 30 Apr 2014 20:23:59
To:
Reply-To: dev@flex.apache.org
Subject: Re: Apache Most Active projects
congrats :)
On Wed, Apr 30, 2014 at 8:01 PM, Frédéric THOMAS wrote:
> Just having a look
On 4/30/14 7:40 AM, "Erik de Bruin" wrote:
>>
>> Are you sure we don't need to keep the Ant scripts? BlazeDS is going to
>> be upstream of the Flex SDK.
>> It might be nice if the rest of the SDK committers can debug BlazeDS
>> issues without having to set up Maven?
>>
>
>+1, all Flex projects
congrats :)
On Wed, Apr 30, 2014 at 8:01 PM, Frédéric THOMAS wrote:
> Just having a look at FishEye [1], it seems Apache Flex is rated as the
> 4th most active project in terms of commits, just behind Subversion, Maven
> and Commons, not bad !
>
> Frédéric THOMAS
>
> [1] https://fisheye6.atlassi
On 4/30/14 6:49 AM, "Christofer Dutz" wrote:
>Ok ... I know I'm sort of having quite a monologue here, but I want this
>stuff logged ;-)
Some of us are sleeping while you're working ;-)
>
>Just did another comit fixing most of the testsuite issues and fixing a
>I18N problem.
>
>I couldn't qui
>
> Are you sure we don't need to keep the Ant scripts? BlazeDS is going to
> be upstream of the Flex SDK.
> It might be nice if the rest of the SDK committers can debug BlazeDS
> issues without having to set up Maven?
>
+1, all Flex projects 'are' ant. Hopefully BlazeDS won't become an
exception
On 4/30/14 3:00 AM, "Christofer Dutz" wrote:
>Now a simple "mvn install" in the "modules" directory (not the root of
>the project) should build BlazeDS successfully.
Excellent progress. Thanks for working on it.
>
>Next steps would be:
>- to check the Errors in the Unit tests.
>- to setup a Je
Just having a look at FishEye [1], it seems Apache Flex is rated as the 4th
most active project in terms of commits, just behind Subversion, Maven and
Commons, not bad !
Frédéric THOMAS
[1] https://fisheye6.atlassian.com/browse/?d=asc&sort=commits
Chris,
Let me know when you have BlazeDS building consistently on Windows. I'll
then create a CI job for it on our new server.
EdB
On Wed, Apr 30, 2014 at 3:49 PM, Christofer Dutz
wrote:
> Ok ... I know I'm sort of having quite a monologue here, but I want this
> stuff logged ;-)
>
> Just di
I can't see blazeds in fisheye, did someone did the request for this repo to be
plugged to already ?
Frédéric THOMAS
> From: webdoubl...@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: AW: AW: Has anyone been able to build BlazeDS?
> Date: Wed, 30 Apr 2014 15:05:43 +0100
>
> > Oh cool ...
> Oh cool ... so not only NSA is reading my posts :-)
:-D
> Does anyone here know why the version in the project was 4.5.0.0 (I
incremented that to 4.6.0.0) but the latest released version is
something 4.0.1 ... what happened with all the stuff in between?
The last nightly build was on Tue Ma
Oh cool ... so not only NSA is reading my posts :-)
Does anyone here know why the version in the project was 4.5.0.0 (I incremented
that to 4.6.0.0) but the latest released version is something 4.0.1 ... what
happened with all the stuff in between?
Chris
__
> Ok ... I know I'm sort of having quite a monologue here, but I want this
> stuff logged ;-)I'm interested in what you're doing / discovering and I guess
> / hope I'm not the only one !
Frédéric THOMAS
> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: Has anyone been a
Ok ... I know I'm sort of having quite a monologue here, but I want this stuff
logged ;-)
Just did another comit fixing most of the testsuite issues and fixing a I18N
problem.
I couldn't quite fix all issues as some of the tests require a BlazeDS server
running on localhost:8400, which doesn'
hould
> > remember the breakpoint location and try to set it for all new workers
> > that appear later. Also each time when new code is loaded fdb should try
> > to set breakpoint again for each existing worker that didn't contain the
> > file before.
> >
&
e before.
>
> BTW IntelliJ uses only breakpoints, no watches and displays.
>
> > 3- In the Falcon repo, merge FDB with its classes using the Falcon AST
> >
> > Any comments are welcome.
> >
> > Frédéric THOMAS
> >
> > [1] https://issues.apache.org/ji
Thanks for sharing.
Chinese in just after English with 11.4% ;-)
Maurice
-Message d'origine-
De : DarkStone [mailto:darkst...@163.com]
Envoyé : mercredi 30 avril 2014 14:00
À : dev@flex.apache.org
Objet : Adobe AIR app installs cross a billion
http://blogs.adobe.com/flashplayer/2014/0
http://blogs.adobe.com/flashplayer/2014/04/air-app-installs-cross-a-billion.html
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Adobe-AIR-app-installs-cross-a-billion-tp37350.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
THOMAS
[1] https://issues.apache.org/jira/browse/FLEX-34291
[2] https://issues.apache.org/jira/browse/FLEX-34292
[1]
Apache fdb (Flash Player Debugger) [build 20140430]
Copyright 2013 The Apache Software Foundation. All rights reserved.
(fdb) run
Waiting for Player to connect
Player connecte
I created 2 tickets [1] for the merge, [2] for the fix, I attached it the fixed
FDB.
Next steps:
1- Fix the bad message when a file is not found
2- New feature: Automaticaly set back the breakpoints, watches and displays
when another instance of the worker is created and the "-ide" argument is
Ok ... done :-)
so I just comitted some changes that allow us to build BlazeDS.
Some tests are failling though, but it seems they were already failling with
the BlazeDS team as they configured Maven not to fail on test errors.
- Updated the repository urls to publich to Apache repos
- Updated th
Hi Guys,
ok so I think I found the problem: It seems that the BlazeDS team was fedup
with the Ant build and gave up on this (Actually it is impossible that it was
able to run at all in its current state). To me it looks as if they switched to
Maven a while ago (When having a look at the directo
(copied from wrong VOTE thread):
One minor issue in the release notes:
FLEX-33948 Add touch behaviour to spark DropDownList classes => the ticket is
still open. implementation attempts were not satisfactory, and have not been
committed.
Also, I find that the release notes do not describe acc
Hi,
+1 (binding)
Signatures all good
LICENCE, NOTICE, README etc all good
Can compile from source (with a couple of minor issues - see discussion)
Can make release (also has some minor issues)
XML config files are correct (if you do a ant release rather than just an ant)
compc/mxmlc report correc
Hi,
I have tried for the second evening to get BlazeDS to build. On my windows
machine at first I am getting tons of missing lib directory errors. I seem to
have resolved most of these by making the filesets not fire errors on missing
resources. Unfortunately there are some classes with comme
>From a Maven standpoint there are two types of artifacts SNAPSHOTS and
>RELEASES.
Usualy they are split up into different Repositories and SNAPSHOTS are never
synced to Maven Central.
A Snapshot usually repesents the Maven-Equivalent to our nightly builds to make
the development
version availab
47 matches
Mail list logo
