Yes, it is Peter deHaan's website. I contacted him off list and he
promised to take a look into it. Apparently his webhosting company dropped
the ball. I will keep you all updated.
Thanks,
Om
P.S. Thanks for the cache link. Saved me a lot of trouble tonight :-)
On Tue, Jul 2, 2013 at 9:37 P
On 7/3/2013 10:11 AM, OmPrakash Muppirala wrote:
Any chance the content from that website can be retrieved and added to our
website?
that was peter deHaan's site? yeah that was an excellent flex resource. its sort
of still "available" via google's cache:
http://webcache.googleusercontent.com
http://blog.flexexamples.com/ has been a great resource for Flex tutorials.
I was glad that this website was around because a lot of google searches
lead to this site.
Any chance the content from that website can be retrieved and added to our
website?
And perhaps a redirect to flex.apache.org?
Hmm,
No matter what code, JavaScript or ActionScript, they will run slower on a
slower processor, and mobile is slower because the processors are slow. I
cannot tell you how much I dislike PhoneGap because the UI is much less
responsible.
As for graphs, I am not sure if you are referring to Flex
The feed at the bottom of our site does not seem to be updating anymore.
Can someone take a look, please?
Thanks,
Om
That's a frustrating issue, however Adobe just removed tlf and as2 from
CC. I think we can follow suite and safely ignore backward
compatibility. We need the player to be backwards compatible, not the
codebase.
If a team needs more performance they are not going to be concerned with
backwar
Great!
That worked. When I received the data, i just updated the detailed data in
the main collection, for specific item and this triggered set data within
the renderer, where I handled the data display part.
Thanks Jude : )
On Sun, Jun 30, 2013 at 8:52 PM, jude wrote:
> Once you've recei
I have created one app for the mobile banking they want to see the graphs
and in the app I have used 6-7 types of graphs. It will take time to load
the graphs and also taking time in switching one graph to another if I want
to go back to previous graph it will load again.
I think the main problem
Is it possible to make the backward compatible a branch which only fixes
bugs, and break UIComponent in another new branch which alway cutting edge?
Flex Spark is the one architecture, maintaining back compatibility makes it
not perfect.
On Tue, Jul 2, 2013 at 12:57 AM, Alex Harui wrote:
>
>
>