IMO, a bead is still best, but your proposed implementation isn't what I
would recommend. With beads, we are trying for loose coupling, separation
of concerns, abstraction, encapsulation, and a bunch of other Computer
Science practices. Hopefully, any communication between the strand and
bead is
Gary,
Please try to focus on actual technical issues and let those who want to
try, try it. Some people think making Flex/FlexJS popular again is a long
shot as well.
I'm not that familiar with WebAssembly, but from what I've read today, I
think Josh has hit on the main technical challenge, whic
Thanks, I would love to see how you can get there, W3C started designing
HTML5 in 2009, Firefox is still making exception for Flash Player now,
maybe you can help them get rid of it and unify the web truly.
On Mon, Apr 10, 2017 at 5:24 PM, Jason Taylor wrote:
> Gary, do you even have any idea wh
Hi,
I’ll respond to your email in full later.
Lets assume we make it a bead.
In this case it will add more lines of code (about a dozen) to HTTPService and
will have a bigger cost people who both use it and don’t use it. Currently it’s
only a two line method and there no runtime cost to people
Responding to you and Justin in this post...
On 4/10/17, 1:55 AM, "Greg Dove" wrote:
>Actually I wasn't sure whether the compiler eliminated the dead js code.
>But we know that it can.
>
>I get the point about the 'swiss-army-knife' but I don't think that
>applies
>here, because I think this is
Gary, do you even have any idea what WebAssembly is? You should check out some
articles on it: https://github.com/WebAssembly/design/blob/master/FAQ.md,
https://developer.mozilla.org/en-US/docs/WebAssembly/Concepts
In a nutshell the browser vendors finally realized that HTML+JS will never be
ef
1) It takes a long time to make a powerful system like Flash Player stable
enough, Google Map has been using webGL for a long time, improved a lot
still crash all the time.
2) Politically, none of the major browser vendors would let anything our of
their control grow bigger anymore, Flash Player is
I don't think you can simply compile LightSpark as-is to WebAssembly. I
suspect that its rendering code will need serious modification to be able
to draw to HTML Canvas or WebGL instead of whatever native APIs it uses
now. This part probably wouldn't be trivial.
- Josh
On Mon, Apr 10, 2017 at 1:5
I would be very interested in hearing how an experiment like that would work
out.
> On Apr 10, 2017, at 4:52 PM, Jason Taylor wrote:
>
> Why would we be implementing anything? I'm talking about taking LightSpark as
> is (with their 252 open bugs) compiling it to LLVM, using that input for the
Why would we be implementing anything? I'm talking about taking LightSpark as
is (with their 252 open bugs) compiling it to LLVM, using that input for the
WebAssembly compiler and compiling the output binary as a LightSpark
WebAssembly drop in flash player. This has nothing to do with the exist
No mean to be offensive, implementing everything in WebAssembly feels just
like talking about living in Mars, even with HTML/Javascript/CSS regardless
of performance, after so many years ...
On Mon, Apr 10, 2017 at 4:18 PM, piotrz wrote:
> Hi Gary,
>
> Please be tolerant to Jason's opinion and i
Thank you for your patience on this. I did run maven as well on my
directories and got a clean run.
On 4/10/17, 4:29 PM, "Christofer Dutz" wrote:
>+1 for merging as you say you tested FlexJSStore and it¹s working, we
>might get develop working again, which is a rather desirable thing ;-)
>
>Chri
+1 for merging as you say you tested FlexJSStore and it’s working, we might get
develop working again, which is a rather desirable thing ;-)
Chris
Am 10.04.17, 20:40 schrieb "Peter Ent" :
I now have the feature/chart-work branch in good shape: the frameworks
projects build and so do al
Hi Gary,
Please be tolerant to Jason's opinion and ideas. Apache Flex is an open
source project and if Jason would like to bring some idea here he is very
welcome, same as you.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-developmen
yes because LLVM to LLVM is so difficult... You have actually have anything
constructive to contribute?
-Original Message-
From: Gary Yang [mailto:flashflex...@gmail.com]
Sent: Monday, April 10, 2017 1:09 PM
To: dev@flex.apache.org
Subject: Re: WebAssembly Flash ByPass
Yeah the life
Yeah the life in Mars could be very exciting, let me know when you are
there ...
On Mon, Apr 10, 2017 at 3:17 PM, Jason Taylor wrote:
> WebAssembly is officially supported in both Chrome and Firefox right now,
> and in the rest very soon.
> WebAssembly can take LLVM and compiles to a binary form
WebAssembly is officially supported in both Chrome and Firefox right now, and
in the rest very soon.
WebAssembly can take LLVM and compiles to a binary format that works cross
browser at near native speeds without any plugin.
LightSpark is an open source implemention of the flash player written i
I now have the feature/chart-work branch in good shape: the frameworks
projects build and so do all of the examples; both ANT and maven builds
ran. I'm much, much more confident in the changes and stability of this
feature branch than I was last week.
I ran the following examples successfully: Cha
I know have MDLExample working.
I think I did this unwittingly: The MaterialDesignLite project's
default.css has the IDateProviderItemRendererMapper for the Tabs and
TabBar components specified as TabsItemRendererFactoryForArrayListData.
But the dataProvider being supplied to the tab components we
I will look into it and let you know. I changed the life cycle for lists
just a little. I found that the item renderers were being created more
than once (sometimes) and the layouts were being run several times
(sometimes) so I tracked down redundant event dispatches and eliminated
them. Then I wen
Actually I wasn't sure whether the compiler eliminated the dead js code.
But we know that it can.
I get the point about the 'swiss-army-knife' but I don't think that applies
here, because I think this is more a 'standard tool'. I can only directly
recall one Flex project in the last 6 years that d
Hi,
> And the net result should be that code you didn't in your app, isn't in your
> app.
As Greg pointed out the compiler can removed unused JS code i.e. methods that
are not called. See for instance [1] for details. So in this case if you don’t
use it will not end up in the AS code (as it’s
22 matches
Mail list logo
