Re: BinaryData compress/uncompress methods (like ByteArray) missing

PathBuilder was designed to be drawing agnostic and the Graphics package is mostly interfaces. Theoretically, anything in Graphics should be usable with both SVG and Canvas implementations. The org.apache.royale.svg classes are SVG implementations and can be used within any Royale components.

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Thanks Harbs, to understand better about the code you said, this is done creating a Canvas where the drawing is done? If so what is the canvas component in Royale? I'll want to try that, if there's some example code in same place, please let me know. thanks! 2018-05-18 13:19 GMT+02:00 Harbs

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Take a look at the Graphics package. Specifically, PathBuilder lets you use commands very similar to Flash drawing commands. Also, CompoundGraphic in Basic offers a number of drawing commands. org.apache.royale.svg (in Basic) has many basic shape types which simplify drawing of those. I’ve

Re: BinaryData compress/uncompress methods (like ByteArray) missing

I think this is all very interesting. We have still a part of what we could make with Flex uncovered. I talk about "drawing things" that was something more related to the Flash API. There's some efforts like spriteflexjs, but I think the problem with that project is that is "isolated" and seems

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Hi Greg, I think I understand your point. I want to point out, though, that the current plan for the emulation set is to make Basic beads the fundamental workhorse of this emulation set. What we are doing is taking, say, the beads used in Basic ImageButton and re-using those beads with no or

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Alex, your comment about a full-blown emulation component set built on openfl display objects could perhaps be a different (and interesting) approach or 'parallel' option in time. But I wasn't really meaning that at this point. I wasn't thinking so much on the 'displaylist' side of things. I was

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Hi Greg, That's an interesting idea. My inclination is to recommend that migrators get rid of their flash*.* dependencies for two reasons: 1) I think in many cases there are other JS implementations that will work better. Having a Button be an HTMLButtonElement should be better than it being

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Just a quick suggestion about 'emulation' options. I notice Joshua Granick has been active in terms of working to get the openfl js lib to work as an extern. That does sound interesting because I think that gives access to the work that has already been done there in terms of emulation of a lot

Re: BinaryData compress/uncompress methods (like ByteArray) missing

IMO, because of PAYG, BinaryData should not have compress/uncompress. Feel free to create a BinaryDataWithZLib or something like that. BinaryData has no requirement to fully replace ByteArray. The emulation components will probably have a better emulation of ByteArray. My 2 cents, -Alex

Re: BinaryData compress/uncompress methods (like ByteArray) missing

So great! I'll be trying it :-) 2018-05-17 15:41 GMT+02:00 Harbs : > Hah! I forgot I wrote that class… ;-) > > Yes. Pako is a zlib port. > > Thanks, > Harbs > > > On May 17, 2018, at 4:22 PM, Carlos Rovira > wrote: > > > > I see we already has

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Hah! I forgot I wrote that class… ;-) Yes. Pako is a zlib port. Thanks, Harbs > On May 17, 2018, at 4:22 PM, Carlos Rovira wrote: > > I see we already has Compressionutils that uses pako, this uses zlib? > > thanks > > 2018-05-17 15:17 GMT+02:00 Carlos Rovira

Re: BinaryData compress/uncompress methods (like ByteArray) missing

I'm sorry Carlos! Serkan is working on something else! 2018-05-17 15:24 GMT+02:00 Carlos Rovira : > Ok right, for me is ok to use that class and inflate/deflate methods, > do you know if that methods use the zlib algorithm? if use that we are > done, since is the same

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Ok right, for me is ok to use that class and inflate/deflate methods, do you know if that methods use the zlib algorithm? if use that we are done, since is the same algorithm used in ByteArray 2018-05-17 15:22 GMT+02:00 Harbs : > Yes. The big issue with compression is that

Re: BinaryData compress/uncompress methods (like ByteArray) missing

I see we already has Compressionutils that uses pako, this uses zlib? thanks 2018-05-17 15:17 GMT+02:00 Carlos Rovira : > Hi, > > BinaryData is the new ByteArray in royale right? > I was searching for compress/uncompress methods but seems we don't have yet > > I'm

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Yes. The big issue with compression is that it adds a lot of code. The most commonly used JS library for compression is pako.[1] I’m using that personally. We don’t want to include something like this in BinaryData because it adds a lot of bulk. HTH, Harbs [1]http://nodeca.github.io/pako/

Re: BinaryData compress/uncompress methods (like ByteArray) missing

Hi Carlos, Yes and it is in progress. Serkan is working on that [1]. I made several comments and waiting for his update. [1] https://github.com/apache/royale-asjs/pull/227 Thanks, Piotr 2018-05-17 15:17 GMT+02:00 Carlos Rovira : > Hi, > > BinaryData is the new

BinaryData compress/uncompress methods (like ByteArray) missing

Hi, BinaryData is the new ByteArray in royale right? I was searching for compress/uncompress methods but seems we don't have yet I'm missing something here? maybe the compress/uncompress algorithms has some license issues and for that reason wasn't implemented? thanks -- Carlos Rovira