Re: MaterialIcon is not taking effect

Hi Hugo, Show us more code ;) I have a feeling that you are missing bead which allows you for binding. As default binding doesn't work in view - you need to add bead which handle that. Thanks, Piotr On Tue, Jun 30, 2020, 1:43 AM Hugo Ferreira wrote: > This does not take effect: /> > > I'm

MaterialIcon is not taking effect

This does not take effect: I'm using the official 0,9,7 + Jewel. I already check tour the jewel. What I may be missing to use MaterialIcons ?

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

Hi Andrew, ok I can take over that part :) El lun., 29 jun. 2020 a las 23:02, Andrew Wetmore () escribió: > Hi, Carlos: > > It will be great to get your help. Take a look at my proposed presentation > list on the wiki page. I imagine one presentation will be "behind the > scenes of Tour de

MouseDown and MouseUp button are fired with secondary mouse button

Hi, I found that MouseDown and MouseUp can be fired with the secondary mouse button. To avoid it I used this code recently on Jewel SpinnerMouseController COMPILE::JS { if (event.button !== 0) return; } I think we don't really want secondary button do that by default and we all need to add the

Re: Drag and Drop example

Oh,Boy!, this first component seemed easy but forced me to dig and finally it's working as expected ! After tried everything, I inspected the elements in browser and finally see what is happening. While dragging, the element is not "clicable", however after drop the state does not change and I

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

Hi, Carlos: It will be great to get your help. Take a look at my proposed presentation list on the wiki page. I imagine one presentation will be "behind the scenes of Tour de Jewel"! On Mon, Jun 29, 2020 at 4:40 PM Carlos Rovira wrote: > Hi Chris and all > > very good opportunity :D. > > In my

RE: No Event.cancel event present for org.apache.royale.Events.event

Is that something one can add to the event Class Also any alternative to flash.filters.GlowFilter; thanks [blank.gif] Anil Guntur Architect, Radiology Workflow (858) 267-5072 (858) 922-6402 agun...@us.ibm.com

Re: Emulation for flash.ui.ContextMenu and flash.ui.ContextMenuItem

Hi Anil, sorry for the delay in following up on this. I added this issue [1] Thanks for your active interest in this. I hope we can support your enthusiasm with the right type of information and guidance. It would be good to collect your and others' thoughts on this - so please reply here or add

RE: Emulation for flash.utils.Dictionary

Thanks From: "Anil Guntur - agun...@us.ibm.com" Reply-To: "dev@royale.apache.org" Date: Monday, June 29, 2020 at 2:07 PM To: "us...@royale.apache.org" , "dev@royale.apache.org" Subject: [EXTERNAL] RE: No Event.cancel event present for org.apache.royale.Events.event Is that something one can

Re: Jewel Advanced Datagrid

Thank you. I will test Jewel Table shortly. Carlos Rovira escreveu no dia segunda, 29/06/2020 à(s) 11:03: > Hi Hugo, > > Maybe Jewel Table could be an option here with some cell render that opens > and collapse and used TR/TD structure internally since there are only 2 > levels. But I'd need to

Re: Native extensions

Hi, as well we have some examples with Cordova/PhoneGap in our repository. El lun., 29 jun. 2020 a las 1:16, Hugo Ferreira () escribió: > Thank you. > I will preserve that for future use. > > Yishay Weiss escreveu no dia domingo, 28/06/2020 > à(s) 18:12: > > > I’m not an Electron expert, but

Re: Native extensions

Thank you for the info. I will check that. Carlos Rovira escreveu no dia segunda, 29/06/2020 à(s) 11:05: > Hi, > > as well we have some examples with Cordova/PhoneGap in our repository. > > El lun., 29 jun. 2020 a las 1:16, Hugo Ferreira () > escribió: > > > Thank you. > > I will preserve that

Re: Emulation with theme/skin

One thing you could try in the current state of Royale is: 1.- Make a first pass from Flex to Royale with Emularion. That should be very few changes. 2.- From a Royale version, add Jewel and JewelTheme and change most components to the jewel (j) namespace. 3.- Change controls: - Things like

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Hi Harbs, ok, I think it would be better to do something of the following: 1.- add the interface to Spectrum lib as I said before 2.- change Spectrum to use initializers if you want to turn it to the modern implementation (of course if you have time) for now you can solve directly with 1 El

Re: Emulation with theme/skin

Not sure if it fits your needs, but you can also check out Spectrum which uses Adobe’s css framework: https://unhurdle.github.io/spectrum-royale/ https://github.com/unhurdle/spectrum-royale It doesn’t

Re: Jewel Advanced Datagrid

I still have more changes in mind for Table in the following days regarding scrolling not showing in some browsers. Hope to get over there soon. El lun., 29 jun. 2020 a las 12:07, Hugo Ferreira () escribió: > Thank you. > I will test Jewel Table shortly. > > Carlos Rovira escreveu no dia

Re: Rewrite and entire Flex project to Royale Jewel !

Hi Hugo, glad to hear that. Many work was invested in getting Jewel in its actual state. So very appreciate your words here :) I think most of the time match people match numbers when Flex app was well written and organized. migration to jewel in our main app described in this twitter thread was

Re: Show an alternate image when the original is not found

Hi Maria Jose, For ImageButton control we can investigate the way to operate at a later time. Maybe it will need a separate bead. You can do the actual just for Image control. Thanks! El dom., 28 jun. 2020 a las 15:41, Maria Jose Esteve () escribió: > Hi, > thanks for the indications, I hope I

Re: Emulation with theme/skin

That's another strategy for the long term "if" Emulation has a minimum acceptable look & feel, that's not the case "today". So, to make the effort to move from the 2 migration process at once, I decided to rewrite directly in Jewel and JewelTheme :) >From what I check now, Jewel components seem

Re: Emulation with theme/skin

It's a good idea and probably the way to go.Royale it's very good now compared with my last trial experience and I cannot wait forever to be perfect. I use Advanced Datagrid in a single place (but important one), so will not be an uggly component spread everywhere but isolated in a single MXML.

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Hi Harbs I removed it since I created in the past with the objective to deal with the hoverable/selectable states, since Jewel needed. As soon as Alex did the item renderer improvement, that interface was not required anymore. The proof is no code in Royale was using it since Alex cleaned code

Re: Jewel Advanced Datagrid

Hi Hugo, Maybe Jewel Table could be an option here with some cell render that opens and collapse and used TR/TD structure internally since there are only 2 levels. But I'd need to take a look. I think for now you can use ADG emulation that seems to be very evolved now, and doing some CSS to make

Re: Emulation with theme/skin

Hi, "but if you have it in a single place, you can isolate the problem that way, and get an official replacement at later time as we get the components fully working." That's always, always my strategy (back box). I also did that in the past with Flex :) Carlos Rovira escreveu no dia segunda,

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Why did you remove this interface? It’s used by Spectrum and should really be adopted by other components as well. Please ask before removing things in the future. > On Jun 11, 2020, at 6:01 PM, carlosrov...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git

Re: Jewel Advanced Datagrid

Still no Advanced DG in Jewel, I want to solve major problems in the current DG layout to go further. Recently I got better layout results with Jewel Table and need to experiment with DG to see if is a good way to go. El dom., 28 jun. 2020 a las 16:55, Hugo Ferreira () escribió: > Hello, > >

Re: Jewel Advanced Datagrid

I understand. I'm testing the boundaries and running use case tests, before deciding to move on the migration now. I only use Advanced DG in one single place with only 2 levels. Here a screenshot: https://drive.google.com/file/d/1NIV_mYgnY3l3VvU1zVcbXJyky3L3E0P7/view?usp=sharing For this use

Re: Emulation with theme/skin

Hugo, You can always as a replacement of DataGrid using some external library which provides you nice and functional component. We are thinking to do that in our app if we won't fix issues in DataGrid soon, so you shouldn't be blocked here at all in my opinion. :) Good luck! Piotr pon., 29 cze

Re: Emulation with theme/skin

Hi, Piotr posted the same thing I wanted to say. You can always go with some external library that does what you want to cover things that Royale does not do now out of the box. I think it's important we get in Royale all basic things like binding, mxml, basic controls, containers, layouts...then

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

ISelectableItemRenderer does not have the selectable property which is used by Spectrum. > On Jun 29, 2020, at 1:21 PM, Harbs wrote: > > Why did you remove this interface? > > It’s used by Spectrum and should really be adopted by other components as > well. > > Please ask before removing

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

I can add the interface to Spectrum if there’s consensus it does not belong in Royale. I’m not convinced that’s the case. I’d like to hear what others think. Spectrum has been modified to use selection beads, but I encapsulated that all within the components. One of my goals with Spectrum was

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

I’m not sure, but yeah, we do need a way to deprecate things before removing them. > On Jun 29, 2020, at 2:30 PM, Christofer Dutz > wrote: > > Does Royale have something like a "@Deprecated" mechanism, where things could > be scheduled for removal and the compiler could output usage of

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

Hi, So if someone would step up and volunteer to be a track chair, the thing is you could prepare a whole track. The good thing is there you could probably play through all important parts of Royale and porting stuff from Flex to Royale and the stuff will be available asynchronously after the

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Does Royale have something like a "@Deprecated" mechanism, where things could be scheduled for removal and the compiler could output usage of deprecated stuff? Perhaps something like that could avoid problems like that in the future? Chris Am 29.06.20, 13:27 schrieb "Harbs" : I can add

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

If we develop a presentation or a track of presentations, we need a "track chair" to handle communications between Royale and ApacheCon, and within those working on the ApacheCon track. I am aware of how busy everyone is, and I would be happy to do that coordination unless someone else would like

Re: Rewrite and entire Flex project to Royale Jewel !

More or less my percentage of MXML. Many, many MXML views or similar but a few specific one are harder to implement. I hope I can do the same as you did. Carlos Rovira escreveu no dia segunda, 29/06/2020 à(s) 12:01: > Hi Hugo, > > glad to hear that. Many work was invested in getting Jewel in

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

FWIW, it might make sense to change the interface to a generic “IOptionallyInteractive” or something. The interface really has nothing specifically to do with item renderers. > On Jun 29, 2020, at 2:27 PM, Harbs wrote: > > I can add the interface to Spectrum if there’s consensus it does not

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

Over 130 people have registered for ApacheCon already, before any advertising has gone out. The tickets for the online event range upward from free (!) [1] [1] https://app.hopin.to/events/apachecon-home/reception On Mon, Jun 29, 2020 at 10:19 AM Christofer Dutz wrote: > Ok ... you were faster

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

This is a great idea, and might even time nicely with our being able to say "version 1.0 is due to release on $DATE_WHATEVER". On Mon, Jun 29, 2020 at 10:07 AM Christofer Dutz wrote: > Hi folks, > > as finally the cat is out of the bag (I hope the German saying sort of > translates) and we’ll

How about a "royale" or "frontend" track on the virtual ApacheCon?

Hi folks, as finally the cat is out of the bag (I hope the German saying sort of translates) and we’ll have a virtual ApacheCon this year. Perhaps you folks should raise your hands and perhaps whip up a “Royale” or a “Frontend” track … what do you think? I know in the past there were always

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

Ok ... you were faster ;-) Am 29.06.20, 15:16 schrieb "Andrew Wetmore" : If we develop a presentation or a track of presentations, we need a "track chair" to handle communications between Royale and ApacheCon, and within those working on the ApacheCon track. I am aware of how busy

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

ActionScript has [Deprecated] metadata that is supported by the Royale compiler. The compiler will output warnings when deprecated APIs are used. Editors/IDEs can also use this information to render things differently. Example: https://twitter.com/as3mxml/status/1192101486563483649 -- Josh

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

> the cat is out of the bag This is exactly how we say it in English too. :) -- Josh Tynjala Bowler Hat LLC On Mon, Jun 29, 2020 at 6:07 AM Christofer Dutz wrote: > Hi folks, > > as finally the cat is out of the bag (I hope the German saying sort of > translates) and

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Great. Thanks! > On Jun 29, 2020, at 6:45 PM, Josh Tynjala wrote: > > ActionScript has [Deprecated] metadata that is supported by the Royale > compiler. The compiler will output warnings when deprecated APIs are used. > Editors/IDEs can also use this information to render things differently. >

Is there a emulation available for flash.display.DisplayObject

I need to get the PopupManager.CreatePopup working.. the first parameter for the parent is of type DisplayObject according to the API documentation.. Thanks

RE: Is there a emulation available for flash.display.DisplayObject

In Royale [1] the first param is an Object [1] https://royale.apache.org/asdoc/#!mx.managers/PopUpManager/createPopUp From: Anil Guntur - agun...@us.ibm.com Sent: Monday, June 29, 2020 8:51 PM To: us...@royale.apache.org Cc:

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

I have created a wiki page [1] which we can use to work out a) do we want to present at ApacheCon and b) what we will present. We need to decide a) fairly quickly so we can inform the ApacheCon organizers. If it takes a formal decision, I propose that Royale presents at ApacheCon 2020. Andrew

Re: [royale-asjs] branch develop updated: Test commit [raudjcholo]

Welcome Raul! :) pon., 29 cze 2020 o 19:39 napisał(a): > This is an automated email from the ASF dual-hosted git repository. > > raudjcholo pushed a commit to branch develop > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git > > > The following commit(s) were added to

Re: How about a "royale" or "frontend" track on the virtual ApacheCon?

Hi Chris and all very good opportunity :D. In my case it's almost impossible to go to another country, but making it online is just the opposite for me, so count on me. If Andrew can manage the track, I can work on some presentation. Of course my knowledge if Jewel focused, so I think we should

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Hi Harbs El lun., 29 jun. 2020 a las 13:27, Harbs () escribió: > I can add the interface to Spectrum if there’s consensus it does not > belong in Royale. I’m not convinced that’s the case. I’d like to hear what > others think. > Well, my point was since when I did this change Alex pointed to

Re: Image, does not flush when link value is null or blank

Hi, thanks for the dissection :) could be possible to handle errors with a throw-catch block to avoid browser errors and have control over it? I think you have almost all right? thanks El dom., 28 jun. 2020 a las 19:18, Maria Jose Esteve () escribió: > These are the test results: > > - Inject

Re: [royale-asjs] branch develop updated: Test commit [raudjcholo]

Welcome! :D El lun., 29 jun. 2020 a las 19:43, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Welcome Raul! :) > > pon., 29 cze 2020 o 19:39 napisał(a): > > > This is an automated email from the ASF dual-hosted git repository. > > > > raudjcholo pushed a commit to branch develop > >

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

very cool Josh! :D El lun., 29 jun. 2020 a las 17:45, Josh Tynjala () escribió: > ActionScript has [Deprecated] metadata that is supported by the Royale > compiler. The compiler will output warnings when deprecated APIs are used. > Editors/IDEs can also use this information to render things

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

hi Chris, I think we have @Deprected in Royale, at least we I think I remember from Flex...so we should have it too. My point is that we are still under 1.0 so we need to have more flexibility. That will end as we get 1.0 since that means things should be taken more carefully, and use more

Re: [royale-asjs] branch develop updated: core-IRuntimeSelectableItemRenderer: remove unused interface

Hi Harbs, if that's the case, and no other code will use it in Royale, I think would be better to host in Spectrum? I must say that I don't mind really if it stay in Royale, and others will say opinion, but just saying trying to think on coherence since no code in royale uses it. El lun., 29

RE: Is there a emulation available for flash.display.DisplayObject

Thanks, that is weird, I thought I saw the first parameter as DisplayObject and the return statement as IFlexDisplayObject. May be I am losing my mind  On another area, that I could not find documentation on is Flash.utils.getQualifiedClassName. Is there an equivalent in royale emulation From: