I believe he was referring to the cancelation of AVMNext (and AS4) and
FlashNext.
Kevin N.
On 1/30/13 4:08 AM, Frank Martin wrote:
Daniel, what current announcement are you referring to?
Sorry, yes. I was referring to the new roadmap.
http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html
I've blogged about the news here:
http://madskool.wordpress.com/2013/01/30/adobes-cut-price-roadmap-and-mc3dnext
@Kevin, I can accomplish miraculous graphics performance when I
madcompone...@gmail.com
wrote:
I've done some experiments with Stage3D accelerated Flex components,
derived from MadComponents classes.
http://madskool.wordpress.com/2013/01/21/madcomponents3d-part5-stage3d-accelerated-flex/
It is my intention to port MadComponents to ASnext. I
these classes as the basis for
Flexnext - if you want.
On Wed, Jan 23, 2013 at 9:04 AM, Om bigosma...@gmail.com wrote:
On Mon, Jan 21, 2013 at 3:30 AM, Daniel Freeman madcompone...@gmail.com
wrote:
I've done some experiments with Stage3D accelerated Flex components,
derived from MadComponents classes
On Mon, Jan 21, 2013 at 3:30 AM, Daniel Freeman madcompone...@gmail.comwrote:
I've done some experiments with Stage3D accelerated Flex components,
derived from MadComponents classes.
http://madskool.wordpress.com/2013/01/21/madcomponents3d-part5-stage3d-accelerated-flex/
It is my intention
I've done some experiments with Stage3D accelerated Flex components,
derived from MadComponents classes.
http://madskool.wordpress.com/2013/01/21/madcomponents3d-part5-stage3d-accelerated-flex/
It is my intention to port MadComponents to ASnext. I propose that these
ported MadComponents/MC3D
were honest about adding advice it would be right on this list
like we all do.
Mike
Quoting Daniel Freeman madcompone...@gmail.com:
I've done some experiments with Stage3D accelerated Flex components,
derived from MadComponents classes.
http://madskool.wordpress.com/2013/01/21/madcomponents3d
to comment on...
On Jan 21, 2013, at 1:30 PM, Daniel Freeman wrote:
I've done some experiments with Stage3D accelerated Flex components,
derived from MadComponents classes.
http://madskool.wordpress.com/2013/01/21/madcomponents3d-part5-stage3d-accelerated-flex/
It is my intention to port
I would expect the Open Flex group to put in the development work for this
? not me
Let me clarify what I mean. It is my intention to port MadComponents/MC3D
over to ASnext. This is quite an undertaking. Combined with the effort
that I've already put into the framework, and the new
On Mon, Jan 21, 2013 at 10:31 PM, Avi Kessner akess...@gmail.com wrote:
Conceptually, I don't understand why you would want to have more than just
a UI framework, if your goal is to make use of the GPU.
The fewer dependencies the better.
@Avi,
I see memory management, and server
@Mike, I've updated my wording slightly. But it's getting late (Brisbane
time), and I'll see how things look in the morning.
I don't apologies for carefully qualifying my expected contributions, and
my expectations of other people's contribution. While I've changed the
wording and dressed it
I'm on mobile, so please forgive my terseness and Typos'
What I meant is that it doesn't conceptually make sense to me to have one
server code that works in cpu mode and another server code that works in
GPU mode. Same with memory management.
For the record the tone was clear to me.
On Jan 21,
Your blog post says uploads to GPU are slow, but I think that's
incorrect (or at least incomplete). I think the bottle neck is the
conversion from BitmapData to the texture format (
/texture.uploadFromBitmapData())/. If you use
texture.uploadFromByteArray you'll see much faster throughputs.
Hi Kevin,
I like to read your blog and learn a lot from the many interesting code
optimisations. But i'm not so sure about your statements for this particular
one:
running your test a few times gives me different results:
run 1:
Driver,Test,Time,Bytes/Sec
OpenGL,Texture from BitmapData w/o
14 matches
Mail list logo
