I just added a brief statement about using a URL instead of embedding assets in Royale in the "Flex Equivalents" page [1].
@Carlos Rovira <carlosrov...@apache.org> , where does that page appear when a user is looking through the documentation? I can't find my way to it through the compiled Help Docs, or in the ToC. [1] royale-docs <https://github.com/apache/royale-docs>/user-interface <https://github.com/apache/royale-docs/tree/master/user-interface>/ flex-equivalents.md On Thu, Jun 6, 2019 at 9:26 AM Frost, Andrew <andrew.fr...@harman.com> wrote: > Thanks, Alex & Carlos > > Yes I agree basically, embedding something in terms of how Flex does it > isn't something that's relevant for Royale or HTTP-based solutions in the > same way, and we certainly don't want to end up encoding something into > text base64 formats.. > > It might be nice to have the compiler do some magic to recognise this > scenario and to grab the swf file, extract the image and then change the > mxml so that it just becomes a url reference.. but that's probably a lot of > work compared to just doing this as a manual operation which is just a > one-off update needed in the code. > > So that: > <mx:Button icon="@Embed('icons.swf#our_button')"/> > is turned into something like > <mx:Button icon="icons/our_button.png"/> > > Anyway, if we get asked to do this then I'll take a look to see whether it > could be merged into the toolchain somehow.. having a quick look into the > SWF it could be fun as these icons are actually not just pure images but > include some shape output from the Flash/Animate authoring tools too.. but > I guess we can just have some quick AS3 tool to extract these with the > appropriate shape and save them to png.. > > For now I'll wait to see whether the project does actually go ahead!! > > thanks > > Andrew > > > -----Original Message----- > From: Carlos Rovira [mailto:carlosrov...@apache.org] > Sent: 06 June 2019 11:33 > To: dev@royale.apache.org > Subject: [EXTERNAL] Re: Embedded Assets (was Re: AIR and Royale) > > Hi, > > I think in the case of HTML, does not have sense to me the concept of > Embed like in Flex. Maybe of SWF target or others (don't know if WebAsm > could benefit from something like this) Maybe for HTML use something like > Embed metadata, could just copy the assets to the resources folder to be > available, since like Alex said, a request per asset is needed and making > other kind of big file seems strange in this case (maybe not). Although we > have solved the copying of assets in different ways through compiler for > libraries and ANT/MAVEN automation in Application. > > for me this could be something to investigate in the future, but with low > priority, since I think we still have bigger fish to fry > > just my 2... > > > El mié., 5 jun. 2019 a las 18:07, Alex Harui (<aha...@adobe.com.invalid>) > escribió: > > > Regarding embedded assets in Royale: > > > > There is no embedded asset support at this time because it is not > > obvious to me it will be worth it. We need a volunteer to devise a > > strategy that works and implement it. > > > > In Flex/Flash, my understanding is that folks embedded assets to save > > on server requests for assets like images. That makes sense because, > > since a SWF is a compressed binary and most assets are compressed > > binaries, you can essentially append the assets to the SWF. > > > > However, for Royale in the browser, every implementation of "embedding" > > I've seen seems to Base64 encode the asset, converting it to text and > > increasing the number of bytes. And the resulting Base64 bytes may > > deteriorate the gzip compression of the .html file. > > > > Flash also had frames in the SWF and assets could be embedded on later > > frames allowing a download progress bar to show up before all of the > > rest of the SWF is downloaded. I don't know what the equivalent for > > that is without Flash. > > > > I believe another advantage of embedding in Flash was that the asset > > was ready to be instantiated and placed on the display list right > > away. I'm not clear that an embedded Base64 image can be used in an > > <img> tag and prevent "popping" given that Royale generates the <img> > tags dynamically. > > > > So, we need a volunteer to create some examples of how to use browser > > embedding in dynamically generated <img> tags so we can see if there > > will be any benefit or not. And if not, possibly explore other > > options, such as delivering all assets in one true binary blob somehow. > > > > HTH, > > -Alex > > > > On 6/5/19, 7:05 AM, "Frost, Andrew" <andrew.fr...@harman.com> wrote: > > > > Yes, me :-) > > > > I'm pushing Royale internally, I think it has a lot of promise - > > although I still do find it a little frustrating at times internally! > > In terms of what support you can give, the sorts of things you're > > already doing are great, but yes it might mean we lean a little more > > on this mailing list if we're facing tricky issues. > > > > We have one sales case in particular at the moment which has the > > potential to be very big, we're hoping they move forwards with a proof > > of concept project which would take a small part of their app and port > > this to Royale. A few issues we've found so far from investigations: > > - their flex code is embedding icons that are contained within a SWF. > > Royale compiler didn't seem to like this, not sure whether it's just > > syntax or whether we need to pull all the assets out (not a big job, > > we can automate that..) > > - they have binding using functions e.g. > > text="{localizationHelper.getString('fieldName')}", which caused an > > issue when generating the JavaScript code as the > > string-within-a-string seemed to upset the parser. We can look at this > later perhaps though.. > > - when we got it compiling, the main thing was with responsiveness > > i.e. trying to get the app to resize and for all the internal elements > > to then resize. We may use the MX emulation classes for this but it > > still looked like more support is needed - although we only looked > > briefly at this. > > > > Once those issues are sorted though, we would have one big task > > (to recreate a very advanced data grid control that they'd developed > > in > > Flex/Flash) and a lot of the rest - around the AS3 logic - should fall > > into place! I'm hoping we can convince them to go with this solution.. > > > > > > thanks > > > > Andrew > > > > > > > > -----Original Message----- > > From: Harbs [mailto:harbs.li...@gmail.com] > > Sent: 04 June 2019 14:41 > > To: dev@royale.apache.org > > Subject: [EXTERNAL] Re: AIR and Royale > > > > Well to start with: Does anyone know anyone working for them? > > > > I’d like to hear from them what it would take for them to push > > Royale more. > > > > > On Jun 4, 2019, at 4:10 PM, Carlos Rovira > > <carlosrov...@apache.org> > > wrote: > > > > > > Hi, > > > > > > what's the kind of support you're thinking ? > > > > > > > > > > > > El mar., 4 jun. 2019 a las 9:36, Piotr Zarzycki > > > (<piotrzarzyck...@gmail.com>) > > > escribió: > > > > > >> Hi Harbs, > > >> > > >> I was exactly think the same about that, so I'm keeping finger > > >> crossed to that effort. > > >> > > >> Thanks, > > >> Piotr > > >> > > >> wt., 4 cze 2019 o 09:34 Harbs <harbs.li...@gmail.com> napisał(a): > > >> > > >>> I just heard about this announcement.[1] > > >>> > > >>> I went over to the Harman site and was reading this page.[2] > > >>> > > >>> I was particularly struck by this statement: > > >>> > > >>> HARMAN’s offerings also include consultancy, support and > migration > > >>> services for companies looking to move their applications away > > from > > >>> Flash technologies over to HTML5 via solutions such as Angular, > > >>> Apache Royale > > >> and > > >>> other JavaScript based frameworks. > > >>> > > >>> > > >>> Considering that they mention Royale explicitly as the number 2 > > >> framework, > > >>> I’m guessing they will be pushing Royale to a certain degree. We > > >>> should probably look to support that effort. > > >>> > > >>> [1] > > > https://clicktime.symantec.com/32oEG4umRJbbKxx17siAFwa7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F3L9wbF4uCYccj7EQCUBeXbp7Vc%253Fu%253Dhttps%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171832330%26sdata%3DXSKi6AAdovaj5CSqDxp4JKUXM%252Fu5uTzKYfJhrsWjO4s%253D%26reserved%3D0 > > >>> %3A%2F%2Ftheblog.adobe.com%2Fthe-future-of-adobe-air%2F < > > >>> > > > https://clicktime.symantec.com/3LTnHE8ZRpM1rsYjqUUg5xV7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F3L9wbF4uCYccj7EQCUBeXbp7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3D7Cp77z%252FW16Gf%252B9Q8P0%252Fs7qOBZdGYOh71F0bX%252BYLwXp8%253D%26reserved%3D0 > > >>> %2F%2Ftheblog.adobe.com%2Fthe-future-of-adobe-air%2F> > > >>> [2] > > > https://clicktime.symantec.com/32YzRLFVBkACau1g6fYnSyR7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F36DC33RH3RXctPTGAK4XztY7Vc%253Fu%253Dhttps%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3DWmyyWadQQ1saSrBkTeuYmPiM0vDW49J3Lob%252BC7eejfg%253D%26reserved%3D0 > > >>> %3A%2F%2Fservices.harman.com%2Fpartners%2Fadobe < > > >>> > > > https://clicktime.symantec.com/3FbC1ESabdLRDQj4WKt3mvF7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F36DC33RH3RXctPTGAK4XztY7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3DJGO%252Fg99Iey8nKvQN5Hzd2EmXkle35QSllbc5UyDaj%252FE%253D%26reserved%3D0 > > >>> %2F%2Fservices.harman.com%2Fpartners%2Fadobe> > > >> > > >> > > >> > > >> -- > > >> > > >> Piotr Zarzycki > > >> > > >> Patreon: > > >> * > > > https://clicktime.symantec.com/3Jpifi5EEL2icEQYT7KGyLz7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F32dvoAS1WTaQP1E2yQmx5pn7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3D%252FDiwRHFQCxdxO7pjeV85svwoRoI8nZmWpWBKDNgzr3w%253D%26reserved%3D0 > > >> %2F%2Fwww.patreon.com%2Fpiotrzarzycki > > >> < > > > https://clicktime.symantec.com/3Jpifi5EEL2icEQYT7KGyLz7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F32dvoAS1WTaQP1E2yQmx5pn7Vc%253Fu%253Dhttps%25253A%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3D%252FDiwRHFQCxdxO7pjeV85svwoRoI8nZmWpWBKDNgzr3w%253D%26reserved%3D0 > > >> %2F%2Fwww.patreon.com%2Fpiotrzarzycki>* > > >> > > > > > > > > > -- > > > Carlos Rovira > > > > > > https://clicktime.symantec.com/32xi5m2jt6cypwahMZPza5b7Vc?u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fclicktime.symantec.com%252F3Peb7VMJWFagYLtTD2HSBGD7Vc%253Fu%253Dhttp%25253A%25252F%26data%3D02%257C01%257Caharui%2540adobe.com%257C1c133b6b710344d4bf3f08d6e9bed52a%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636953403171842325%26sdata%3DPE5%252FahFsZHO5iuUE9pbP3jnax2KYXkxJBvBS%252Bfxb22Y%253D%26reserved%3D0 > > > %2Fabout.me%2Fcarlosrovira > > > > > > > > -- > Carlos Rovira > > https://clicktime.symantec.com/338hPRiMe7pQWFRqHyrJDfV7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira > -- Andrew Wetmore http://cottage14.blogspot.com/
