I'm not going to be able to look into this before the end of the week. Can
you please file a JIRA issue and assign it to me, so it doesn't get lost in
the deluge of email that is currently joining the Occupy My Inbox movement.
EdB
On Sun, Feb 9, 2014 at 8:16 AM, Erik de Bruin
I'm back home, I'll try to reproduce and if needed fix FalconJX this week.
EdB
On Friday, February 7, 2014, Alex Harui aha...@adobe.com wrote:
On 2/7/14 12:02 AM, OmPrakash Muppirala bigosma...@gmail.comjavascript:;
wrote:
But, when I compile the example app, the file:
On Thu, Feb 6, 2014 at 11:09 PM, Alex Harui aha...@adobe.com wrote:
On 2/6/14 10:49 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Feb 6, 2014 10:42 PM, Alex Harui aha...@adobe.com wrote:
Ack. Read the error incorrectly. It may not be BarChartLayout that is
incorrect. Do you
I got all the code and rebuilt. The issue Om was trying to fix is
definitely fixed - the charts look great in both AS and JS.
I am however, getting this warning when cross-compiling the
BarChartExample from within Flash Builder:
/Users/pent/Documents/Apache
Are you guys only getting this warning when using FB or does the warning
also show up when building from ant?
On 2/7/14 7:01 AM, Peter Ent p...@adobe.com wrote:
I got all the code and rebuilt. The issue Om was trying to fix is
definitely fixed - the charts look great in both AS and JS.
I am
Assuming that I've built and installed things into the right places, I did
not get this warning building the example using ant in the BarChartExample
directory. So just using FB. I'm not yet familiar enough the configuration
differences to see why this would be the case.
--peter
On 2/7/14 10:59
On Feb 7, 2014 7:59 AM, Alex Harui aha...@adobe.com wrote:
Are you guys only getting this warning when using FB or does the warning
also show up when building from ant?
I am getting same error with the ant bold as well.
Thanks,
Om
On 2/7/14 7:01 AM, Peter Ent p...@adobe.com wrote:
I got
On Mon, Feb 3, 2014 at 6:37 AM, Peter Ent p...@adobe.com wrote:
Hi Om,
Sorry for the delayed response. BarChartLayout.changeHandler is the place.
You might need to look at the BarChartView bead as well.
Thanks so much!
Peter
Just checked in a fix. Please take a look.
App works fine
On 2/6/14 6:04 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
App works fine even though I am getting a warning during the JS
compilation
part:
WARNING - Bad type annotation. Unknown type
org.apache.flex.charts.beads.layouts.BarChartLayout
[java] var /** @type
On Feb 6, 2014 8:24 PM, Alex Harui aha...@adobe.com wrote:
On 2/6/14 6:04 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
App works fine even though I am getting a warning during the JS
compilation
part:
WARNING - Bad type annotation. Unknown type
On 2/6/14 9:38 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Feb 6, 2014 8:24 PM, Alex Harui aha...@adobe.com wrote:
On 2/6/14 6:04 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
App works fine even though I am getting a warning during the JS
compilation
part:
WARNING -
On Feb 6, 2014 10:08 PM, Alex Harui aha...@adobe.com wrote:
On 2/6/14 9:38 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Feb 6, 2014 8:24 PM, Alex Harui aha...@adobe.com wrote:
On 2/6/14 6:04 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
App works fine even though
Ack. Read the error incorrectly. It may not be BarChartLayout that is
incorrect. Do you know which .js file is actually complaining?
On 2/6/14 10:29 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Feb 6, 2014 10:08 PM, Alex Harui aha...@adobe.com wrote:
On 2/6/14 9:38 PM,
On Feb 6, 2014 10:42 PM, Alex Harui aha...@adobe.com wrote:
Ack. Read the error incorrectly. It may not be BarChartLayout that is
incorrect. Do you know which .js file is actually complaining?
Yes, it is from XAxisBead.js
On 2/6/14 10:29 PM, OmPrakash Muppirala bigosma...@gmail.com
On 2/6/14 10:49 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Feb 6, 2014 10:42 PM, Alex Harui aha...@adobe.com wrote:
Ack. Read the error incorrectly. It may not be BarChartLayout that is
incorrect. Do you know which .js file is actually complaining?
Yes, it is from
Hi Om,
Sorry for the delayed response. BarChartLayout.changeHandler is the place.
You might need to look at the BarChartView bead as well.
Thanks so much!
Peter
On 1/31/14 7:17 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Fri, Jan 31, 2014 at 11:31 AM, Peter Ent p...@adobe.com wrote:
On Jan 30, 2014 11:32 PM, Alex Harui aha...@adobe.com wrote:
On 1/30/14 11:07 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Jan 30, 2014 10:18 PM, Alex Harui aha...@adobe.com wrote:
On 1/30/14 9:11 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Thu, Jan 30, 2014
Hi,
First, I can confirm that Om's suggestion of *adding* the createElement
override to the cross-compiled/generated BarChart.js does fix the problem.
Secondly - how do we make it possible to allow customization of the
JavaScript that gets cross-compiled? This is bound to be necessary and
Ah, sorry. Somehow I thought you were only adding one line to an existing
createElement method.
So, in FlexJS, if you have to modify the cross-compiled JS for a class in
the FlexJSJX project, that will usually mean that that class can't be in
FlexJSJX and has to be moved back to FlexJSUI and
On 1/31/14 7:03 AM, Peter Ent p...@adobe.com wrote:
Hi,
First, I can confirm that Om's suggestion of *adding* the createElement
override to the cross-compiled/generated BarChart.js does fix the problem.
Secondly - how do we make it possible to allow customization of the
JavaScript that gets
Had a chat with Alex. For this particular issue, we were thinking that
Flex's scrollPolicy should be carried over to FlexJS, but enhanced:
scrollPolicy: on | off | auto | hidden
which map as follows -
on: overflow:scroll, but scrollbars visible always
off:overflow:visible
auto:
On Fri, Jan 31, 2014 at 11:31 AM, Peter Ent p...@adobe.com wrote:
Had a chat with Alex. For this particular issue, we were thinking that
Flex's scrollPolicy should be carried over to FlexJS, but enhanced:
scrollPolicy: on | off | auto | hidden
which map as follows -
on:
I have the BarChart example working in both AS and JS. The AS worked right
away but I discovered an issue with sizing the NonVirtualDataGroup in
JavaScript. Or rather, the lack of sizing it. I am tracking that down now.
There are places in FlexJS where I don't have the size calculation quite
right
I've pushed changes that should have the BarChart example working for both
AS and JS. There is an issue with the axis appearing below the chart that
causes the chart area (the dataGroup) to be larger than the chart space.
This is an issue with getting the HTML/CSS right and any help/advice or
On Thu, Jan 30, 2014 at 1:43 PM, Peter Ent p...@adobe.com wrote:
I've pushed changes that should have the BarChart example working for both
AS and JS. There is an issue with the axis appearing below the chart that
causes the chart area (the dataGroup) to be larger than the chart space.
This
On Jan 30, 2014 5:36 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Thu, Jan 30, 2014 at 1:43 PM, Peter Ent p...@adobe.com wrote:
I've pushed changes that should have the BarChart example working for
both
AS and JS. There is an issue with the axis appearing below the chart that
Om, something is still not configured right. BarChart.js should be coming
from frameworks/js/FlexJS/libs. There is no createElement call in my copy.
-Alex
On 1/30/14 8:18 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Jan 30, 2014 5:36 PM, OmPrakash Muppirala bigosma...@gmail.com
On Thu, Jan 30, 2014 at 8:30 PM, Alex Harui aha...@adobe.com wrote:
Om, something is still not configured right. BarChart.js should be coming
from frameworks/js/FlexJS/libs.
I dont see the libs folder here:
On 1/30/14 9:11 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Thu, Jan 30, 2014 at 8:30 PM, Alex Harui aha...@adobe.com wrote:
Om, something is still not configured right. BarChart.js should be
coming
from frameworks/js/FlexJS/libs.
I dont see the libs folder here:
On Jan 30, 2014 10:18 PM, Alex Harui aha...@adobe.com wrote:
On 1/30/14 9:11 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Thu, Jan 30, 2014 at 8:30 PM, Alex Harui aha...@adobe.com wrote:
Om, something is still not configured right. BarChart.js should be
coming
from
On 1/30/14 11:07 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Jan 30, 2014 10:18 PM, Alex Harui aha...@adobe.com wrote:
On 1/30/14 9:11 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Thu, Jan 30, 2014 at 8:30 PM, Alex Harui aha...@adobe.com wrote:
Om, something is
When I compile and run the BarChartExample, in the JS version, this is what
I am seeing (swf works fine)
http://jsfiddle.net/cvLqE/
Once I tweak the output html like this
http://jsfiddle.net/52uaL/2/
i.e. remove the position: absolute style attribute of 'barChart' div, the
bars show up, but
On Wed, Jan 29, 2014 at 11:40 AM, OmPrakash Muppirala
bigosma...@gmail.comwrote:
When I compile and run the BarChartExample, in the JS version, this is
what I am seeing (swf works fine)
http://jsfiddle.net/cvLqE/
To be clear, in the above version, I dont see any bars in either browsers.
The
Please feel free to make adjustments. I have to admit that the particulars
of CSS escape me sometimes.
Thanks for your help and checking this out.
Peter
On 1/29/14 2:40 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
When I compile and run the BarChartExample, in the JS version, this is
I just discovered that the BarChartExample is stale. It isn't using the
BarChart now checked into FlexJSJX. I'm going to try to get it to compile
and run in AS and then maybe Peter will have time to look at the JS side.
-Alex
On 1/29/14 11:59 AM, Peter Ent p...@adobe.com wrote:
Please feel
I wonder why it is stale? I'll take a look as well since it will help me
remember and help with any JS issues.
-peter
On 1/29/14 4:07 PM, Alex Harui aha...@adobe.com wrote:
I just discovered that the BarChartExample is stale. It isn't using the
BarChart now checked into FlexJSJX. I'm going to
The ActionScript side works for me but JavaScript produces what Om is
seeing, so I will look into that.
--peter
On 1/29/14 4:12 PM, OmPrakash Muppirala bigosma...@gmail.com wrote:
On Wed, Jan 29, 2014 at 1:07 PM, Alex Harui aha...@adobe.com wrote:
I just discovered that the BarChartExample is
It is stale because it was using the custom bar chart and not the one I
moved to FLexJSJX. I have it updated locally but there is a problem now
because we're trying to use the Ifactory code gen in the compiler and it
isn't working right.
-Alex
On 1/29/14 1:49 PM, Peter Ent p...@adobe.com wrote:
OK, things appear to be compiling and running again on the AS side. Make
sure the BarChartExample works and you think it should.
Thanks
-Alex
On 1/29/14 2:12 PM, Alex Harui aha...@adobe.com wrote:
It is stale because it was using the custom bar chart and not the one I
moved to FLexJSJX. I
I think that would involve keeping track of what compilation units
have been processed and then skip the ones from the framework if they
have a counter part in the project files. I'm not sure if Falcon would
like that.
I'm away from computer this week, so above is just a barely educated
guess.
Thanks, Igor. I will look it over.
--peter
On 12/18/13 7:35 PM, Igor Costa igorco...@gmail.com wrote:
Peter
Awesome, there's a particular post I wrote last week about writing from
ground up charts in canvas and javascript. You can use google translate
for
that
Couldn't we simply mark a class with a [Native] metadata? I think randori
framework has a similar approach.
On 19 December 2013 15:30, Erik de Bruin e...@ixsoftware.nl wrote:
I think that would involve keeping track of what compilation units
have been processed and then skip the ones from the
Possible, or we maybe we could mark every FalconJX-generated file with
Generated by FalconJX and not overwrite files that don't have that. But
right now, FalconJX blows away the entire output folder. I'm not sure
what hassles we'll face if we stop doing that.
-Alex
On 12/19/13 8:49 AM, João
Couldn't we somehow deploy automatically a folder (libs/native/whatever)
into the output folder and combine that with the [Native] metadata? Falcon
would delete everything in the output folder, generate everything that it's
not [native] and then deploy everything in the libs(native/whatever)
That's what FalconJX does today when building apps. You specify folders
of .js files that represent classes in a SWC, and specify MXML and AS
source files for cross-compilation. The output directory is deleted and
re-created, and only the MXML and AS source files get cross-compiled and
the JS
Nice!
Harbs
On Dec 17, 2013, at 10:49 PM, Peter Ent wrote:
Hi,
I've added a simple BarChart component to the ActionScript FlexJS SDK; it is
modeled on the MX Charts package. I also included an example of using it,
located in the FlexJS examples directory.
I developed the BarChart in
Peter
Awesome, there's a particular post I wrote last week about writing from
ground up charts in canvas and javascript. You can use google translate for
that http://www.igorcosta.com/criando-graficos-zero-com-canvas-e-javascript/
Maybe help for next couple of charts.
Hi,
I've added a simple BarChart component to the ActionScript FlexJS SDK; it is
modeled on the MX Charts package. I also included an example of using it,
located in the FlexJS examples directory.
I developed the BarChart in ActionScript but it can be cross-compiled into
JavaScript and
Way to go!
The next thing Erik or I have to figure out is the build script and
compiler changes so that certain AS files get cross-compiled to JS without
overwriting the hand-written JS files. Erik, any thoughts on how tricky
that will be?
-Alex
On 12/17/13 12:49 PM, Peter Ent p...@adobe.com
49 matches
Mail list logo