Hi Maurice,
This is BRILLIANT news!
Will give this a try sometime this week.
Maurice Amsellem wrote
> Hi Darren,
>
> ILOG Elixir and Apache Flex compatibility issue has been fixed.
> See https://issues.apache.org/jira/browse/FLEX-33421
>
> So there is one less huge reason for not moving your
Hi Darren,
ILOG Elixir and Apache Flex compatibility issue has been fixed.
See https://issues.apache.org/jira/browse/FLEX-33421
So there is one less huge reason for not moving your application to Apache Flex
;-)
It will be available in the next release (4.12.1 and/or 4.13), but you can
already
Hi,
> Maurice, anyone can easily enable telemetry with Renaun's Telemetry
> enabler[1] that you can setup and run in in CommandLine to quick enable
> telemetry without requiring an updated version of the compiler.
The advanced-telemetry flag works in Apache Flex 4.9 and above.
Thanks,
Justin
: RE: Patching Flex 4.6 SDK chart functionality
You did press the button? It's pressing the button that takes 5 seconds to
initialise the axis.
In the main application with the 4 charts it was taking 30 seconds when the
interval was 0.1.
In the test application pressing the button takes 5 secon
As I mentioned, I have inherited this code and the interval was already being
set.
I do not see the need for an interval of 0.1. I think it will be ok to
remove it. The 0 to 100 min/max is purely for example. In reality the data
will range from 0 to 8 (maybe up to 10) so an interval of 0.1 is
appr
You did press the button? It's pressing the button that takes 5 seconds to
initialise the axis.
In the main application with the 4 charts it was taking 30 seconds when the
interval was 0.1.
In the test application pressing the button takes 5 seconds for the axis to
update.
Removing the setting of
dobe.com]
Envoyé : mardi 18 mars 2014 17:24
À : users@flex.apache.org
Objet : Re: Patching Flex 4.6 SDK chart functionality
I haven't found a way to get call counts in Scout. I still find the FB
profiler's call counts a very useful tool in figuring out the root cause of
many perfo
Very useful post.
The "hassle" I spoke of in my previous post was exactly this problem,
advanced telemetry. We got round it eventually but that was the problem.
Going to install Scout and see where the other 5 seconds are going.
João Fernandes wrote
> Maurice, anyone can easily enable telemet
d'origine-
De : DarrenEvans [mailto:darren.ev...@allocatesoftware.com]
Envoyé : mardi 18 mars 2014 17:28
À : users@flex.apache.org
Objet : Re: Patching Flex 4.6 SDK chart functionality
It's showing on my post here.Don't know whether it got removed because it
was in a CDA
14 17:27
À : users@flex.apache.org
Objet : Re: Patching Flex 4.6 SDK chart functionality
Maurice, anyone can easily enable telemetry with Renaun's Telemetry enabler[1]
that you can setup and run in in CommandLine to quick enable telemetry without
requiring an updated version of the compiler.
http://
How big is this chart? 0 to 100 at 0.1 is 1000 intervals. Do you really
need that many?
On 3/18/14 9:28 AM, "DarrenEvans"
wrote:
>It's showing on my post here.Don't know whether it got removed
>because it
>was in a CDATA block
>
>It's simply:
>
> import mx.charts.LinearAx
rice
>>
>> -Message d'origine-----
>> De : João Fernandes [mailto:
> joaopedromartinsfernandes@
> ]
>> Envoyé : mardi 18 mars 2014 16:59
>> À :
> users@.apache
>> Objet : Re: Patching Flex 4.6 SDK chart functionality
>>
>
It's showing on my post here.Don't know whether it got removed because it
was in a CDATA block
It's simply:
import mx.charts.LinearAxis;
private var requiredVsActualDataProvider:Array = [];
private function button1_clickHandler(event:Mouse
data that is used in the chart. Can you
> >> please take the time to build a fully operational test case that show
> >>the
> >> issue, and post the source code here, so that we can help you more
> >> efficiently.
> >>
> >> Thanks
> >>
> >
#x27;s why I suggested the "old" profiler...
>
> Maurice
>
> -Message d'origine-
> De : João Fernandes [mailto:joaopedromartinsfernan...@gmail.com]
> Envoyé : mardi 18 mars 2014 16:59
> À : users@flex.apache.org
> Objet : Re: Patching Flex 4.6 SDK chart
s
>>
>> Maurice
>>
>> -Message d'origine-
>> De : DarrenEvans [mailto:darren.ev...@allocatesoftware.com]
>> Envoyé : mardi 18 mars 2014 15:50
>> À : users@flex.apache.org
>> Objet : RE: Patching Flex 4.6 SDK chart functionality
>>
I think the guts of the script block is missing...
On 3/18/14 8:39 AM, "DarrenEvans"
wrote:
>Here is full code to highlight the problem. This example takes about 5
>seconds when you press "Setup Axis":
>
>
>http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spar
igine-
De : João Fernandes [mailto:joaopedromartinsfernan...@gmail.com]
Envoyé : mardi 18 mars 2014 16:59
À : users@flex.apache.org
Objet : Re: Patching Flex 4.6 SDK chart functionality
A faster way to check the bottlenecks in performance is to use Adobe Scout
instead of the Performance profiler
On
Here is full code to highlight the problem. This example takes about 5
seconds when you press "Setup Axis":
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx">
Doesn't need any data, requiredVsActualDataProvider is a blank array!
private var requiredVsActualDataProvider:Array = [];
I've ruled out actual data being the problem.
Can't running the basic profiler as it just crashes because the application
is so bigand not set up Scout in a while (last
-
> De : DarrenEvans [mailto:darren.ev...@allocatesoftware.com]
> Envoyé : mardi 18 mars 2014 15:50
> À : users@flex.apache.org
> Objet : RE: Patching Flex 4.6 SDK chart functionality
>
> Hi Maurice,
>
> Thanks for helping out too.
>
> Moving to anything above 4.6 is imp
.
Thanks
Maurice
-Message d'origine-
De : DarrenEvans [mailto:darren.ev...@allocatesoftware.com]
Envoyé : mardi 18 mars 2014 15:50
À : users@flex.apache.org
Objet : RE: Patching Flex 4.6 SDK chart functionality
Hi Maurice,
Thanks for helping out too.
Moving to anything above 4
Hi Maurice,
Thanks for helping out too.
Moving to anything above 4.6 is impossible without severe development from
our end. Our primary limiting factor is we use the IBM ILOG Elixir Gantt
Chart component and it is critical to our application. This was not
originally owned by IBM and was well sup
e same code, actually)
I think it's worth the try...
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 18 mars 2014 14:29
À : users@flex.apache.org
Objet : Re: Patching Flex 4.6 SDK chart functionality
Hi Darren,
What change in Apache Flex d
Hi Darren,
What change in Apache Flex do you think or know will solve your
performance issue?
It might be easier to just do monkey-patching. I don't use IntelliJ so we
might need their help otherwise. To monkey patch, just create the folder
structure for whatever changed files you want and put
Evans [mailto:darren.ev...@allocatesoftware.com]
Envoyé : mardi 18 mars 2014 12:01
À : users@flex.apache.org
Objet : Re: Patching Flex 4.6 SDK chart functionality
Hi Alex,
When I say "modules", I'm referring to IntelliJ modules.
This is a whopper of an application! There is only 1 resul
Hi Alex,
When I say "modules", I'm referring to IntelliJ modules.
This is a whopper of an application! There is only 1 resulting SWF file but
it comprises of many modules (libraries).
We have a product platform so have the following base modules:
1. Controls (lib)
2. Resources (lib)
3. Framework
For now, just for the SWF that uses Charts.swc. This is just a temporary
test to make sure the APIs are compatible. If they are then we'll try to
re-enable all of the other RSLs.
-Alex
On 3/17/14 3:50 AM, "DarrenEvans"
wrote:
>Our application is a big stack of modules culminating in Client
>a
Our application is a big stack of modules culminating in Client application
as the top level binding them all together.
Do I need to add the -static-rsls=false compiler option to all modules or
just the top client level?
--
View this message in context:
http://apache-flex-users.246.n4.na
Sorry, Darren, I mistyped your name...
On 3/14/14 11:22 AM, "Alex Harui" wrote:
>Hi Darrell,
>
>First, just try adding the MXMLC option -static-rsls=false. Yes, this
>means your app won't use any RSLs, but I just want to see if your app will
>actually run with mixed code (which is totally not s
Hi Darrell,
First, just try adding the MXMLC option -static-rsls=false. Yes, this
means your app won't use any RSLs, but I just want to see if your app will
actually run with mixed code (which is totally not supported, but might
work). If it does work, then we'll figure out the configuration tha
31 matches
Mail list logo
