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

[Carlos Rovira]

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 don't break anything: P
>
> I have put it in the package that you indicate.
>
> I have included the examples in TDJ: in jewel image there is no problem,
> everything works as expected, but with ImageButton it does not work and I
> think you should check it, right? I see that the image in ImageButton.as is
> HTMLInputElement and in Image.as is HTMLImageElement, could we do it or
> would it be better to duplicate the bead?
>
> Hiedra.
>
> -Mensaje original-
> De: Carlos Rovira 
> Enviado el: domingo, 28 de junio de 2020 9:50
> Para: Apache Royale Development 
> Asunto: Re: Show an alternate image when the original is not found
>
> Hi,
>
> about the package Harbs is right, I didn't remember that it was a bead
> that can be used across other ui sets. Path
> Basic/src/main/royale/org/apache/royale/html/beads/ErrorImage.as seems ok
> to me.
>
> @Maria Jose Esteve  It's important you can ensure the
> code does not break things before submit and that the PR is done from a
> clean fork state, so your PR is merged without causing issues to the rest
> of the project and users. Depending on what you're doing that could be more
> easy or not.
>
> In this case it seems easy to check. Since it's a new bead in Basic that
> should not affect other parts of the SDK, just building Basic with Maven
> and ANT will ensure you're ok. Other times, for changes in compiler or
> making changes in core framework code would require you to rebuild the
> entire framework and check change doesn't break tests.
>
> thanks
>
> Carlos
>
>
>
> El dom., 28 jun. 2020 a las 1:41, Maria Jose Esteve ()
> escribió:
>
> > I was missing the license text.
> > Yes now.
> > Hiedra.
> >
> > -Mensaje original-
> > De: Maria Jose Esteve  Enviado el: domingo, 28 de
> > junio de 2020 1:08
> > Para: dev@royale.apache.org
> > Asunto: RE: Show an alternate image when the original is not found
> >
> > Yishay, thanks to you too, the bead is a copy of the one you proposed.
> > 😊
> >
> > I have modified my fork but cannot compile and check that everything
> > works fine in the SDK. I also couldn't compile the TDJ.
> > The compilation error of my fork is:
> >
> > Files with unapproved licenses:
> >
> >
> > D:/…/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/
> > beads/ErrorImage.as
> >
> > Can I do the PR like this? Sorry, but it's the first one at this level
> > that I do.
> > Thank you.
> > De: Maria Jose Esteve  Enviado el: domingo, 28 de
> > junio de 2020 0:08
> > Para: us...@royale.apache.org
> > Asunto: RE: Show an alternate image when the original is not found
> >
> > Thanks for answering Carlos and Harbs, to see if I have understood ...
> >
> > 1.- Rename the bead to “ErrorImage” (this name is more identifying,
> > yes)
> > 2.- hahaha, I don't know what package to put it in. Harbs, you mean
> > org.apache.royale.html.beads?
> > 3.- Change the name of the property to “src”
> > 4.- TDJ example, yes, without problems. (I will look where to put it
> > and I will propose something to you Carlos)
> >
> > I wait for you to confirm the name of the package.
> > Thank you very much.
> >
> >
> > De: Harbs mailto:harbs.li...@gmail.com>>
> > Enviado el: sábado, 27 de junio de 2020 20:48
> > Para: us...@royale.apache.org
> > Asunto: Re: Show an alternate image when the original is not found
> >
> > 2.- About package. the right one for image controls is
> > "org.apache.royale.jewel.beads.controls.image"
> >
> > I don’t see anything specific to Jewel here, so I think this belongs
> > in Basic.
> >
> >
> > On Jun 27, 2020, at 9:36 PM, Carlos Rovira  > > wrote:
> >
> > Hi Maria Jose,
> >
> > Thanks for the contribution!. Some points:
> >
> > 1.- About the name: In Jewel the we don't suffix it with "Bead", to
> > make names less verbose since is extendin IBead, so we know it is a bead.
> > Apart from that I see more descriptive "ErrorImage" or maybe it's just
> me?
> > Since "AlternativeImage" seems to me a bead that could switch the
> > current imagen with another alternative one, and not specifically one
> > that is a replacement when we get a load error.
> > 2.- About package. the right one for image controls is
> > "org.apache.royale.jewel.beads.controls.image"
> > 3.- property could be just "src", since the name of the bead class
> > already give context.(so both the image control and the bead will have
> "src"
> > property what seems to me more coherent for naming.
> >
> > Apart from that, if you tried your code and worked you can submit it.
> > As well if you want you can add a TDJ example in the image page and I
> > can prepare an official image for jewel error image placeholder. 

Re: Jewel Advanced Datagrid

[Carlos Rovira]

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,
>
> There is any option of parent/child on the Jewel grid as we achieve that
> with Flex Advanced Datagrid ?
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Emulation with theme/skin

[Carlos Rovira]

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 buttons, checkboxes, datefields, numericstepper, should
   have a very similar API or the same
   - Jewel List should be very close too since it is very evolved.
   - Then others like ComboBox, DropDownList, could need more attention by
   using beads (for example RequireSelection is a bead not a property)
   - For components still not available in Jewel like Tree and
   AdvancedDataGrid, you can maintain them in emulation until we have jewel
   versions.

4.- Go further and start changing containers and layouts:

   - Layouts in Jewel is more efficient since it uses (when possible)
   browser layout, avoiding extra process
   - Containers tries to have the best from flex and the best from the
   modern web and Royale and use jewel layouts.

5.- If needed and make sense for your app: Try to add some new
global layout like the one exposed in TDJ that uses Drawer and
Responsiveness to make the App more accessible in Tablets and Mobile
devices.




El dom., 28 jun. 2020 a las 15:10, Hugo Ferreira ()
escribió:

> I'm using the Nabble.
> It worked every time before and from the last months to now, it works 1 in
> 10 times.
> I will use e-mail.
> I already configured the mailing list to receive every message.
>
> I tested Apache Royal Emulation a year ago and was an alpha quality
> product.
> I practically could not do much to it from my trial.
>
> I tested now I can tell for my very short trial that I almost copy/past and
> change very few things and compile straight and see running on the browser,
> however without any skin (tested with version 0.9.7).
>
> MX Emulation it's OK for internal purposes as you said but for public Jewel
> it's the way.
> However MX Emulation can be done probably in a record time and Jewel with
> not be a port but a rewrite that can take a lot of time and a learning
> curve.
>
> I'm "playing" with Jewel right now.
>
> Piotr Zarzycki  escreveu no dia domingo,
> 28/06/2020 à(s) 10:57:
>
> > I think sooner or later someone make Emulation Components beautiful. I
> > hope there will appear on horizonts client who would pay to make it
> happen.
> > Even if it maybe more work he will still benefits cause his code will be
> > migrated to JS without so much changes.
> >
> > On Sun, Jun 28, 2020, 10:58 AM Carlos Rovira 
> > wrote:
> >
> >> Hi Hugo,
> >>
> >> actually I see 2 paths in Royale for Flex apps migration:
> >>
> >> 1.- Choose MX emulation: That's the fastest migration path with very few
> >> code changes, but look and feel is not considered
> >> 2.- Choose Jewel or other UI set that consider look and feel. That will
> be
> >> not so fast as MX but will give you look and feel out of the box.
> >>
> >> Depending on your needs you must choose one path or the other. If the
> app
> >> is something internal to a company (i.e: an intranet) that just needs to
> >> continue working, I think 1 is a good option. If you need to go open and
> >> look and feel is important, maybe 2 is a better way since it prepares
> your
> >> app for modern UI.
> >>
> >>
> >>
> >>
> >> El dom., 28 jun. 2020 a las 6:59, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Hi Hugo,
> >> >
> >> > Did you overcome your problems with mailing list?
> >> >
> >> > As for your question - I don't things anyone tried make Emulation
> >> > Components beautiful, with some decent css styles. So far any new
> >> client of
> >> > Royale just trying to reach porting app without thinking about make UI
> >> > beautiful.
> >> >
> >> > You may try and see, but I would really recommend first see whether
> your
> >> > app is be able to smoothly build trough Royale. Over the road you may
> >> find
> >> > how things work.
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> > On Sun, Jun 28, 2020, 6:18 AM Hugo Ferreira 
> >> > wrote:
> >> >
> >> > > Hello,
> >> > >
> >> > > How to apply a theme/skin to Royale Emulation ?
> >> > > The standard version seems wireframes.
> >> > > For example Google Material Design.
> >> > >
> >> > > Regards,
> >> > > Hugo.
> >> > >
> >> >
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Jewel Advanced Datagrid

[Hugo Ferreira]

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 case, do you know any workaround besides Advanced DG ?

Carlos Rovira  escreveu no dia segunda, 29/06/2020
à(s) 09:43:

> 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,
> >
> > There is any option of parent/child on the Jewel grid as we achieve that
> > with Flex Advanced Datagrid ?
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: Emulation with theme/skin

[Hugo Ferreira]

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 to fill the most needs
(fortunately, I don't need a tree at all) except for Advanced Datagrid,
that's a blocker.
Another approach to try to emulate my needs about Advanced DG is to
workaround with tabs and bold in normal Datagrid and rows enabled and
disabled (I don't know if would be possible). I will check later.

Carlos Rovira  escreveu no dia segunda, 29/06/2020
à(s) 09:56:

> 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 buttons, checkboxes, datefields, numericstepper, should
>have a very similar API or the same
>- Jewel List should be very close too since it is very evolved.
>- Then others like ComboBox, DropDownList, could need more attention by
>using beads (for example RequireSelection is a bead not a property)
>- For components still not available in Jewel like Tree and
>AdvancedDataGrid, you can maintain them in emulation until we have jewel
>versions.
>
> 4.- Go further and start changing containers and layouts:
>
>- Layouts in Jewel is more efficient since it uses (when possible)
>browser layout, avoiding extra process
>- Containers tries to have the best from flex and the best from the
>modern web and Royale and use jewel layouts.
>
> 5.- If needed and make sense for your app: Try to add some new
> global layout like the one exposed in TDJ that uses Drawer and
> Responsiveness to make the App more accessible in Tablets and Mobile
> devices.
>
>
>
>
> El dom., 28 jun. 2020 a las 15:10, Hugo Ferreira ( >)
> escribió:
>
> > I'm using the Nabble.
> > It worked every time before and from the last months to now, it works 1
> in
> > 10 times.
> > I will use e-mail.
> > I already configured the mailing list to receive every message.
> >
> > I tested Apache Royal Emulation a year ago and was an alpha quality
> > product.
> > I practically could not do much to it from my trial.
> >
> > I tested now I can tell for my very short trial that I almost copy/past
> and
> > change very few things and compile straight and see running on the
> browser,
> > however without any skin (tested with version 0.9.7).
> >
> > MX Emulation it's OK for internal purposes as you said but for public
> Jewel
> > it's the way.
> > However MX Emulation can be done probably in a record time and Jewel with
> > not be a port but a rewrite that can take a lot of time and a learning
> > curve.
> >
> > I'm "playing" with Jewel right now.
> >
> > Piotr Zarzycki  escreveu no dia domingo,
> > 28/06/2020 à(s) 10:57:
> >
> > > I think sooner or later someone make Emulation Components beautiful. I
> > > hope there will appear on horizonts client who would pay to make it
> > happen.
> > > Even if it maybe more work he will still benefits cause his code will
> be
> > > migrated to JS without so much changes.
> > >
> > > On Sun, Jun 28, 2020, 10:58 AM Carlos Rovira 
> > > wrote:
> > >
> > >> Hi Hugo,
> > >>
> > >> actually I see 2 paths in Royale for Flex apps migration:
> > >>
> > >> 1.- Choose MX emulation: That's the fastest migration path with very
> few
> > >> code changes, but look and feel is not considered
> > >> 2.- Choose Jewel or other UI set that consider look and feel. That
> will
> > be
> > >> not so fast as MX but will give you look and feel out of the box.
> > >>
> > >> Depending on your needs you must choose one path or the other. If the
> > app
> > >> is something internal to a company (i.e: an intranet) that just needs
> to
> > >> continue working, I think 1 is a good option. If you need to go open
> and
> > >> look and feel is important, maybe 2 is a better way since it prepares
> > your
> > >> app for modern UI.
> > >>
> > >>
> > >>
> > >>
> > >> El dom., 28 jun. 2020 a las 6:59, Piotr Zarzycki (<
> > >> piotrzarzyck...@gmail.com>)
> > >> escribió:
> > >>
> > >> > Hi Hugo,
> > >> >
> > >> > Did you overcome your problems with mailing list?
> > >> >
> > >> > As for your question - I don't things anyone tried make Emulation
> > >> > Components beautiful, with some decent css styles. So far any new
> > >> client of
> > >> > Royale just trying to reach porting app without thinking about make
> UI
> > >> > beautiful.
> > >> >
> > >> > You may try and see, but I would really recommend first see whether
> > your
> > >> > app is be able to smoothly build trough Royale. Over the road you
> may
> > >> find
> > >> > how things work.
> > >> >
> > >> > Thanks,
> > >> > Piotr
> > >> >
> > >> > On Sun, Jun 28, 2020, 6:18 AM Hugo Ferreira  >
> 

Re: Emulation with theme/skin

[Piotr Zarzycki]

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 2020 o 11:11 Hugo Ferreira  napisał(a):

> 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 to fill the most needs
> (fortunately, I don't need a tree at all) except for Advanced Datagrid,
> that's a blocker.
> Another approach to try to emulate my needs about Advanced DG is to
> workaround with tabs and bold in normal Datagrid and rows enabled and
> disabled (I don't know if would be possible). I will check later.
>
> Carlos Rovira  escreveu no dia segunda,
> 29/06/2020
> à(s) 09:56:
>
> > 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 buttons, checkboxes, datefields, numericstepper, should
> >have a very similar API or the same
> >- Jewel List should be very close too since it is very evolved.
> >- Then others like ComboBox, DropDownList, could need more attention
> by
> >using beads (for example RequireSelection is a bead not a property)
> >- For components still not available in Jewel like Tree and
> >AdvancedDataGrid, you can maintain them in emulation until we have
> jewel
> >versions.
> >
> > 4.- Go further and start changing containers and layouts:
> >
> >- Layouts in Jewel is more efficient since it uses (when possible)
> >browser layout, avoiding extra process
> >- Containers tries to have the best from flex and the best from the
> >modern web and Royale and use jewel layouts.
> >
> > 5.- If needed and make sense for your app: Try to add some new
> > global layout like the one exposed in TDJ that uses Drawer and
> > Responsiveness to make the App more accessible in Tablets and Mobile
> > devices.
> >
> >
> >
> >
> > El dom., 28 jun. 2020 a las 15:10, Hugo Ferreira (<
> hferreira...@gmail.com
> > >)
> > escribió:
> >
> > > I'm using the Nabble.
> > > It worked every time before and from the last months to now, it works 1
> > in
> > > 10 times.
> > > I will use e-mail.
> > > I already configured the mailing list to receive every message.
> > >
> > > I tested Apache Royal Emulation a year ago and was an alpha quality
> > > product.
> > > I practically could not do much to it from my trial.
> > >
> > > I tested now I can tell for my very short trial that I almost copy/past
> > and
> > > change very few things and compile straight and see running on the
> > browser,
> > > however without any skin (tested with version 0.9.7).
> > >
> > > MX Emulation it's OK for internal purposes as you said but for public
> > Jewel
> > > it's the way.
> > > However MX Emulation can be done probably in a record time and Jewel
> with
> > > not be a port but a rewrite that can take a lot of time and a learning
> > > curve.
> > >
> > > I'm "playing" with Jewel right now.
> > >
> > > Piotr Zarzycki  escreveu no dia domingo,
> > > 28/06/2020 à(s) 10:57:
> > >
> > > > I think sooner or later someone make Emulation Components beautiful.
> I
> > > > hope there will appear on horizonts client who would pay to make it
> > > happen.
> > > > Even if it maybe more work he will still benefits cause his code will
> > be
> > > > migrated to JS without so much changes.
> > > >
> > > > On Sun, Jun 28, 2020, 10:58 AM Carlos Rovira <
> carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > >> Hi Hugo,
> > > >>
> > > >> actually I see 2 paths in Royale for Flex apps migration:
> > > >>
> > > >> 1.- Choose MX emulation: That's the fastest migration path with very
> > few
> > > >> code changes, but look and feel is not considered
> > > >> 2.- Choose Jewel or other UI set that consider look and feel. That
> > will
> > > be
> > > >> not so fast as MX but will give you look and feel out of the box.
> > > >>
> > > >> Depending on your needs you must choose one path or the other. If
> the
> > > app
> > > >> is something internal to a company (i.e: an intranet) that just
> needs
> > to
> > > >> continue working, I think 1 is a good option. If you need to go open
> > and
> > > >> look and feel is important, maybe 2 is a better way since it
> prepares
> > > your
> > > >> app for modern UI.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> El dom., 28 jun. 2020 a las 6:59, Piotr Zarzycki (<
> > > >> piotrzarzyck...@gmail.com>)
> > > >> escribió:
> > > >>
> > > >> > Hi Hugo,
> > > >> >
> > > >> >

Re: Emulation with theme/skin

[Hugo Ferreira]

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.

I'm still facing issues with my isualted trial with drag-drop Panel (Card)
- posted in another thread.
Then, I will probably study Advanced Datagrid alternatives.

Piotr Zarzycki  escreveu no dia segunda,
29/06/2020 à(s) 10:15:

> 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 2020 o 11:11 Hugo Ferreira 
> napisał(a):
>
> > 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 to fill the most needs
> > (fortunately, I don't need a tree at all) except for Advanced Datagrid,
> > that's a blocker.
> > Another approach to try to emulate my needs about Advanced DG is to
> > workaround with tabs and bold in normal Datagrid and rows enabled and
> > disabled (I don't know if would be possible). I will check later.
> >
> > Carlos Rovira  escreveu no dia segunda,
> > 29/06/2020
> > à(s) 09:56:
> >
> > > 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 buttons, checkboxes, datefields, numericstepper,
> should
> > >have a very similar API or the same
> > >- Jewel List should be very close too since it is very evolved.
> > >- Then others like ComboBox, DropDownList, could need more attention
> > by
> > >using beads (for example RequireSelection is a bead not a property)
> > >- For components still not available in Jewel like Tree and
> > >AdvancedDataGrid, you can maintain them in emulation until we have
> > jewel
> > >versions.
> > >
> > > 4.- Go further and start changing containers and layouts:
> > >
> > >- Layouts in Jewel is more efficient since it uses (when possible)
> > >browser layout, avoiding extra process
> > >- Containers tries to have the best from flex and the best from the
> > >modern web and Royale and use jewel layouts.
> > >
> > > 5.- If needed and make sense for your app: Try to add some new
> > > global layout like the one exposed in TDJ that uses Drawer and
> > > Responsiveness to make the App more accessible in Tablets and Mobile
> > > devices.
> > >
> > >
> > >
> > >
> > > El dom., 28 jun. 2020 a las 15:10, Hugo Ferreira (<
> > hferreira...@gmail.com
> > > >)
> > > escribió:
> > >
> > > > I'm using the Nabble.
> > > > It worked every time before and from the last months to now, it
> works 1
> > > in
> > > > 10 times.
> > > > I will use e-mail.
> > > > I already configured the mailing list to receive every message.
> > > >
> > > > I tested Apache Royal Emulation a year ago and was an alpha quality
> > > > product.
> > > > I practically could not do much to it from my trial.
> > > >
> > > > I tested now I can tell for my very short trial that I almost
> copy/past
> > > and
> > > > change very few things and compile straight and see running on the
> > > browser,
> > > > however without any skin (tested with version 0.9.7).
> > > >
> > > > MX Emulation it's OK for internal purposes as you said but for public
> > > Jewel
> > > > it's the way.
> > > > However MX Emulation can be done probably in a record time and Jewel
> > with
> > > > not be a port but a rewrite that can take a lot of time and a
> learning
> > > > curve.
> > > >
> > > > I'm "playing" with Jewel right now.
> > > >
> > > > Piotr Zarzycki  escreveu no dia domingo,
> > > > 28/06/2020 à(s) 10:57:
> > > >
> > > > > I think sooner or later someone make Emulation Components
> beautiful.
> > I
> > > > > hope there will appear on horizonts client who would pay to make it
> > > > happen.
> > > > > Even if it maybe more work he will still benefits cause his code
> will
> > > be
> > > > > migrated to JS without so much changes.
> > > > >
> > > > > On Sun, Jun 28, 2020, 10:58 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > > > wrote:
> > > > >
> > > > >> Hi Hugo,
> > > > >>
> > > > >> actually I see 2 paths in Royale for Flex apps migration:
> > > > >>
> > > > >> 1.- Choose MX emulation: That's the fastest migration path with
> very
> > > few
> > > > >> code changes, but look and feel is not cons

Re: Emulation with theme/skin

[Carlos Rovira]

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
we'll go further with time and effort, but in these days if I find
something I need that is not here I try to search in js world and bring to
my project. Of course, list-tables-datagrids are important to get it done
in the right way since use things that should play nicely with the rest of
the infrastructure, 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.

El lun., 29 jun. 2020 a las 11:23, Hugo Ferreira ()
escribió:

> 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.
>
> I'm still facing issues with my isualted trial with drag-drop Panel (Card)
> - posted in another thread.
> Then, I will probably study Advanced Datagrid alternatives.
>
> Piotr Zarzycki  escreveu no dia segunda,
> 29/06/2020 à(s) 10:15:
>
> > 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 2020 o 11:11 Hugo Ferreira 
> > napisał(a):
> >
> > > 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 to fill the most needs
> > > (fortunately, I don't need a tree at all) except for Advanced Datagrid,
> > > that's a blocker.
> > > Another approach to try to emulate my needs about Advanced DG is to
> > > workaround with tabs and bold in normal Datagrid and rows enabled and
> > > disabled (I don't know if would be possible). I will check later.
> > >
> > > Carlos Rovira  escreveu no dia segunda,
> > > 29/06/2020
> > > à(s) 09:56:
> > >
> > > > 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 buttons, checkboxes, datefields, numericstepper,
> > should
> > > >have a very similar API or the same
> > > >- Jewel List should be very close too since it is very evolved.
> > > >- Then others like ComboBox, DropDownList, could need more
> attention
> > > by
> > > >using beads (for example RequireSelection is a bead not a
> property)
> > > >- For components still not available in Jewel like Tree and
> > > >AdvancedDataGrid, you can maintain them in emulation until we have
> > > jewel
> > > >versions.
> > > >
> > > > 4.- Go further and start changing containers and layouts:
> > > >
> > > >- Layouts in Jewel is more efficient since it uses (when possible)
> > > >browser layout, avoiding extra process
> > > >- Containers tries to have the best from flex and the best from
> the
> > > >modern web and Royale and use jewel layouts.
> > > >
> > > > 5.- If needed and make sense for your app: Try to add some new
> > > > global layout like the one exposed in TDJ that uses Drawer and
> > > > Responsiveness to make the App more accessible in Tablets and Mobile
> > > > devices.
> > > >
> > > >
> > > >
> > > >
> > > > El dom., 28 jun. 2020 a las 15:10, Hugo Ferreira (<
> > > hferreira...@gmail.com
> > > > >)
> > > > escribió:
> > > >
> > > > > I'm using the Nabble.
> > > > > It worked every time before and from the last months to now, it
> > works 1
> > > > in
> > > > > 10 times.
> > > > > I will use e-mail.
> > > > > I already configured the mailing list to receive every message.
> > > > >
> > > > > I tested Apache Royal Emulation a year ago and was an alpha quality
> > > > > product.
> > > > > I practically could not do much to it from my trial.
> > > > >
> > > > > I tested now I can tell for my very short trial that I almost
> > copy/past
> > > > and
> > > > > change very few things and compile straight and see running on the
> > > > browser,
> > > > > however without any skin (tested with version 0.9.7).
> > > > >
> > > > > MX Emulation it's OK for internal purposes as you said but for
> public
> > > > Jewel
> > 

Re: Jewel Advanced Datagrid

[Carlos Rovira]

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 it look a bit better should not be a
problem in this case (I think).

To avoid CSS collisions between Jewel and MX use this

-compiler.exclude-defaults-css-files=MXRoyale-${royale.framework.version}-js.swc:defaults.css;

And add the ADG CSS you need.




El lun., 29 jun. 2020 a las 11:01, Hugo Ferreira ()
escribió:

> 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 case, do you know any workaround besides Advanced DG ?
>
> Carlos Rovira  escreveu no dia segunda,
> 29/06/2020
> à(s) 09:43:
>
> > 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 (<
> hferreira...@gmail.com
> > >)
> > escribió:
> >
> > > Hello,
> > >
> > > There is any option of parent/child on the Jewel grid as we achieve
> that
> > > with Flex Advanced Datagrid ?
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Native extensions

[Carlos Rovira]

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 this [1] might help.
> >
> > [1]
> >
> https://royale.apache.org/how-to-create-a-desktop-application-with-royale-and-electron/
> >
> > From: Hugo Ferreira
> > Sent: Sunday, June 28, 2020 7:56 PM
> > To: Apache Royale Development
> > Subject: Native extensions
> >
> > What is the Flex (AIR) native extensions alternative for Apache Royale ?
> > In fact it's only for one use case because I will use Royale just for
> > Desktop.
> >
> > The idea it's to build a connection to a device in C# (Windows Desktop
> > only) and communicate with Apache Royale when it's deployed in a WIndows
> > Desktop environment for example with Electron (I never did) ?
> >
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Native extensions

[Hugo Ferreira]

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 for future use.
> >
> > Yishay Weiss  escreveu no dia domingo,
> 28/06/2020
> > à(s) 18:12:
> >
> > > I’m not an Electron expert, but this [1] might help.
> > >
> > > [1]
> > >
> >
> https://royale.apache.org/how-to-create-a-desktop-application-with-royale-and-electron/
> > >
> > > From: Hugo Ferreira
> > > Sent: Sunday, June 28, 2020 7:56 PM
> > > To: Apache Royale Development
> > > Subject: Native extensions
> > >
> > > What is the Flex (AIR) native extensions alternative for Apache Royale
> ?
> > > In fact it's only for one use case because I will use Royale just for
> > > Desktop.
> > >
> > > The idea it's to build a connection to a device in C# (Windows Desktop
> > > only) and communicate with Apache Royale when it's deployed in a
> WIndows
> > > Desktop environment for example with Electron (I never did) ?
> > >
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: Jewel Advanced Datagrid

[Hugo Ferreira]

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 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 it look a bit better should not be a
> problem in this case (I think).
>
> To avoid CSS collisions between Jewel and MX use this
>
>
> -compiler.exclude-defaults-css-files=MXRoyale-${royale.framework.version}-js.swc:defaults.css;
>
> And add the ADG CSS you need.
>
>
>
>
> El lun., 29 jun. 2020 a las 11:01, Hugo Ferreira ( >)
> escribió:
>
> > 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 case, do you know any workaround besides Advanced DG ?
> >
> > Carlos Rovira  escreveu no dia segunda,
> > 29/06/2020
> > à(s) 09:43:
> >
> > > 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 (<
> > hferreira...@gmail.com
> > > >)
> > > escribió:
> > >
> > > > Hello,
> > > >
> > > > There is any option of parent/child on the Jewel grid as we achieve
> > that
> > > > with Flex Advanced Datagrid ?
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: Emulation with theme/skin

[Hugo Ferreira]

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, 29/06/2020
à(s) 11:02:

> 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
> we'll go further with time and effort, but in these days if I find
> something I need that is not here I try to search in js world and bring to
> my project. Of course, list-tables-datagrids are important to get it done
> in the right way since use things that should play nicely with the rest of
> the infrastructure, 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.
>
> El lun., 29 jun. 2020 a las 11:23, Hugo Ferreira ( >)
> escribió:
>
> > 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.
> >
> > I'm still facing issues with my isualted trial with drag-drop Panel
> (Card)
> > - posted in another thread.
> > Then, I will probably study Advanced Datagrid alternatives.
> >
> > Piotr Zarzycki  escreveu no dia segunda,
> > 29/06/2020 à(s) 10:15:
> >
> > > 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 2020 o 11:11 Hugo Ferreira 
> > > napisał(a):
> > >
> > > > 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 to fill the most needs
> > > > (fortunately, I don't need a tree at all) except for Advanced
> Datagrid,
> > > > that's a blocker.
> > > > Another approach to try to emulate my needs about Advanced DG is to
> > > > workaround with tabs and bold in normal Datagrid and rows enabled and
> > > > disabled (I don't know if would be possible). I will check later.
> > > >
> > > > Carlos Rovira  escreveu no dia segunda,
> > > > 29/06/2020
> > > > à(s) 09:56:
> > > >
> > > > > 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 buttons, checkboxes, datefields, numericstepper,
> > > should
> > > > >have a very similar API or the same
> > > > >- Jewel List should be very close too since it is very evolved.
> > > > >- Then others like ComboBox, DropDownList, could need more
> > attention
> > > > by
> > > > >using beads (for example RequireSelection is a bead not a
> > property)
> > > > >- For components still not available in Jewel like Tree and
> > > > >AdvancedDataGrid, you can maintain them in emulation until we
> have
> > > > jewel
> > > > >versions.
> > > > >
> > > > > 4.- Go further and start changing containers and layouts:
> > > > >
> > > > >- Layouts in Jewel is more efficient since it uses (when
> possible)
> > > > >browser layout, avoiding extra process
> > > > >- Containers tries to have the best from flex and the best from
> > the
> > > > >modern web and Royale and use jewel layouts.
> > > > >
> > > > > 5.- If needed and make sense for your app: Try to add some new
> > > > > global layout like the one exposed in TDJ that uses Drawer and
> > > > > Responsiveness to make the App more accessible in Tablets and
> Mobile
> > > > > devices.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El dom., 28 jun. 2020 a las 15:10, Hugo Ferreira (<
> > > > hferreira...@gmail.com
> > > > > >)
> > > > > escribió:
> > > > >
> > > > > > I'm using the Nabble.
> > > > > > It worked every time before and from the last months to now, it
> > > works 1
> > > > > in
> > > > > > 10 times.
> > > > > > I will use e-mail.
> > > > > > I already configured the mailing list to receive

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

[Harbs]

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 repository.
> 
> carlosrovira pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
> new d997c70  core-IRuntimeSelectableItemRenderer: remove unused interface
> d997c70 is described below
> 
> commit d997c703461167b2072ba75d6ff9215124814d0f
> Author: Carlos Rovira 
> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> 
>core-IRuntimeSelectableItemRenderer: remove unused interface
> ---
> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64 --
> 2 files changed, 65 deletions(-)
> 
> diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as 
> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> index ff662a0..cba38dc 100644
> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> @@ -146,7 +146,6 @@ internal class CoreClasses
>   import org.apache.royale.core.IScrollBarModel; IScrollBarModel;
>   }
>   import org.apache.royale.core.IListDataItemRenderer; 
> IListDataItemRenderer;
> - import org.apache.royale.core.IRuntimeSelectableItemRenderer; 
> IRuntimeSelectableItemRenderer;
>   import org.apache.royale.core.ISelectableItemRenderer; 
> ISelectableItemRenderer;
>   import org.apache.royale.core.ISelectable; ISelectable;
>   import org.apache.royale.core.ISelectionModel; ISelectionModel;
> diff --git 
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> deleted file mode 100644
> index d5df28b..000
> --- 
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> +++ /dev/null
> @@ -1,64 +0,0 @@
> -
> -//
> -//  Licensed to the Apache Software Foundation (ASF) under one or more
> -//  contributor license agreements.  See the NOTICE file distributed with
> -//  this work for additional information regarding copyright ownership.
> -//  The ASF licenses this file to You under the Apache License, Version 2.0
> -//  (the "License"); you may not use this file except in compliance with
> -//  the License.  You may obtain a copy of the License at
> -//
> -//  http://www.apache.org/licenses/LICENSE-2.0
> -//
> -//  Unless required by applicable law or agreed to in writing, software
> -//  distributed under the License is distributed on an "AS IS" BASIS,
> -//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> -//  See the License for the specific language governing permissions and
> -//  limitations under the License.
> -//
> -
> -package org.apache.royale.core
> -{
> - import org.apache.royale.events.IEventDispatcher;
> -
> -/**
> - *  The IItemRenderer interface is the basic interface for item 
> renderers.
> - *  More complex item renderers may implements extensions of this 
> interface.
> - *  
> - *  @langversion 3.0
> - *  @playerversion Flash 10.2
> - *  @playerversion AIR 2.6
> - *  @productversion Royale 0.0
> - */
> - public interface IRuntimeSelectableItemRenderer extends 
> ISelectableItemRenderer
> - {
> - /**
> - *  true if the item renderer is can be selected
> - *  false otherwise. Use to configure a renderer to be non 
> - *  selectable.
> - *  
> - *  Defaults to true
> - * 
> - *  @langversion 3.0
> - *  @playerversion Flash 10.2
> - *  @playerversion AIR 2.6
> - *  @productversion Royale 0.9.3
> - */
> - function get selectable():Boolean;
> - function set selectable(value:Boolean):void;
> -
> -/**
> - *  true if the item renderer is can be hovered
> - *  false otherwise. Use to configure a renderer to be non 
> - *  hoverable.
> - *  
> - *  Defaults to true
> - * 
> - *  @langversion 3.0
> - *  @playerversion Flash 10.2
> - *  @playerversion AIR 2.6
> - *  @productversion Royale 0.9.3
> - */
> - function get hoverable():Boolean;
> - function set hoverable(value:Boolean):void;
> - }
> -}
> 

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

[Harbs]

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 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 repository.
>> 
>> carlosrovira pushed a commit to branch develop
>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>> 
>> 
>> The following commit(s) were added to refs/heads/develop by this push:
>>new d997c70  core-IRuntimeSelectableItemRenderer: remove unused interface
>> d997c70 is described below
>> 
>> commit d997c703461167b2072ba75d6ff9215124814d0f
>> Author: Carlos Rovira 
>> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
>> 
>>   core-IRuntimeSelectableItemRenderer: remove unused interface
>> ---
>> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
>> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64 
>> --
>> 2 files changed, 65 deletions(-)
>> 
>> diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as 
>> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> index ff662a0..cba38dc 100644
>> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> @@ -146,7 +146,6 @@ internal class CoreClasses
>>  import org.apache.royale.core.IScrollBarModel; IScrollBarModel;
>>  }
>>  import org.apache.royale.core.IListDataItemRenderer; 
>> IListDataItemRenderer;
>> -import org.apache.royale.core.IRuntimeSelectableItemRenderer; 
>> IRuntimeSelectableItemRenderer;
>>  import org.apache.royale.core.ISelectableItemRenderer; 
>> ISelectableItemRenderer;
>>  import org.apache.royale.core.ISelectable; ISelectable;
>>  import org.apache.royale.core.ISelectionModel; ISelectionModel;
>> diff --git 
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>>  
>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>> deleted file mode 100644
>> index d5df28b..000
>> --- 
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>> +++ /dev/null
>> @@ -1,64 +0,0 @@
>> -
>> -//
>> -//  Licensed to the Apache Software Foundation (ASF) under one or more
>> -//  contributor license agreements.  See the NOTICE file distributed with
>> -//  this work for additional information regarding copyright ownership.
>> -//  The ASF licenses this file to You under the Apache License, Version 2.0
>> -//  (the "License"); you may not use this file except in compliance with
>> -//  the License.  You may obtain a copy of the License at
>> -//
>> -//  http://www.apache.org/licenses/LICENSE-2.0
>> -//
>> -//  Unless required by applicable law or agreed to in writing, software
>> -//  distributed under the License is distributed on an "AS IS" BASIS,
>> -//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>> -//  See the License for the specific language governing permissions and
>> -//  limitations under the License.
>> -//
>> -
>> -package org.apache.royale.core
>> -{
>> -import org.apache.royale.events.IEventDispatcher;
>> -
>> -/**
>> - *  The IItemRenderer interface is the basic interface for item 
>> renderers.
>> - *  More complex item renderers may implements extensions of this 
>> interface.
>> - *  
>> - *  @langversion 3.0
>> - *  @playerversion Flash 10.2
>> - *  @playerversion AIR 2.6
>> - *  @productversion Royale 0.0
>> - */
>> -public interface IRuntimeSelectableItemRenderer extends 
>> ISelectableItemRenderer
>> -{
>> -/**
>> - *  true if the item renderer is can be selected
>> - *  false otherwise. Use to configure a renderer to be non 
>> - *  selectable.
>> - *  
>> - *  Defaults to true
>> - * 
>> - *  @langversion 3.0
>> - *  @playerversion Flash 10.2
>> - *  @playerversion AIR 2.6
>> - *  @productversion Royale 0.9.3
>> - */
>> -function get selectable():Boolean;
>> -function set selectable(value:Boolean):void;
>> -
>> -/**
>> - *  true if the item renderer is can be hovered
>> - *  false otherwise. Use to configure a renderer to be non 
>> - *  hoverable.
>> - *  
>> - *  Defaults to true
>> - * 
>> - *  @langversion 3.0
>> - *  @playerversion Flash 10.2
>> - *  @playerversion AIR 2.6
>> - *  @productversion Royale

Re: Jewel Advanced Datagrid

[Carlos Rovira]

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 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 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 it look a bit better should not be a
> > problem in this case (I think).
> >
> > To avoid CSS collisions between Jewel and MX use this
> >
> >
> >
> -compiler.exclude-defaults-css-files=MXRoyale-${royale.framework.version}-js.swc:defaults.css;
> >
> > And add the ADG CSS you need.
> >
> >
> >
> >
> > El lun., 29 jun. 2020 a las 11:01, Hugo Ferreira (<
> hferreira...@gmail.com
> > >)
> > escribió:
> >
> > > 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 case, do you know any workaround besides Advanced DG ?
> > >
> > > Carlos Rovira  escreveu no dia segunda,
> > > 29/06/2020
> > > à(s) 09:43:
> > >
> > > > 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 (<
> > > hferreira...@gmail.com
> > > > >)
> > > > escribió:
> > > >
> > > > > Hello,
> > > > >
> > > > > There is any option of parent/child on the Jewel grid as we achieve
> > > that
> > > > > with Flex Advanced Datagrid ?
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Carlos Rovira]

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 from using it and the actual initializer architecture made us
use "has" instead of turn on/off behaviors.

Sorry for the problems of removing it. I was in the belief that if the code
is not used in Royale we should remove it to avoid dead code.
My opinion is that if you still need to use that interface in Spectrum
should go to that library, since Royale doesn't use it, and in that way we
avoid confusion for us and for new users

Thoughts?

Thanks




El lun., 29 jun. 2020 a las 12:29, Harbs () escribió:

> 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 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 repository.
> >>
> >> carlosrovira pushed a commit to branch develop
> >> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >>
> >>
> >> The following commit(s) were added to refs/heads/develop by this push:
> >>new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
> interface
> >> d997c70 is described below
> >>
> >> commit d997c703461167b2072ba75d6ff9215124814d0f
> >> Author: Carlos Rovira 
> >> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> >>
> >>   core-IRuntimeSelectableItemRenderer: remove unused interface
> >> ---
> >> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> >> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> --
> >> 2 files changed, 65 deletions(-)
> >>
> >> diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> index ff662a0..cba38dc 100644
> >> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> @@ -146,7 +146,6 @@ internal class CoreClasses
> >>  import org.apache.royale.core.IScrollBarModel;
> IScrollBarModel;
> >>  }
> >>  import org.apache.royale.core.IListDataItemRenderer;
> IListDataItemRenderer;
> >> -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
> IRuntimeSelectableItemRenderer;
> >>  import org.apache.royale.core.ISelectableItemRenderer;
> ISelectableItemRenderer;
> >>  import org.apache.royale.core.ISelectable; ISelectable;
> >>  import org.apache.royale.core.ISelectionModel; ISelectionModel;
> >> diff --git
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >> deleted file mode 100644
> >> index d5df28b..000
> >> ---
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >> +++ /dev/null
> >> @@ -1,64 +0,0 @@
> >>
> -
> >> -//
> >> -//  Licensed to the Apache Software Foundation (ASF) under one or more
> >> -//  contributor license agreements.  See the NOTICE file distributed
> with
> >> -//  this work for additional information regarding copyright ownership.
> >> -//  The ASF licenses this file to You under the Apache License,
> Version 2.0
> >> -//  (the "License"); you may not use this file except in compliance
> with
> >> -//  the License.  You may obtain a copy of the License at
> >> -//
> >> -//  http://www.apache.org/licenses/LICENSE-2.0
> >> -//
> >> -//  Unless required by applicable law or agreed to in writing, software
> >> -//  distributed under the License is distributed on an "AS IS" BASIS,
> >> -//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> >> -//  See the License for the specific language governing permissions and
> >> -//  limitations under the License.
> >> -//
> >>
> -
> >> -package org.apache.royale.core
> >> -{
> >> -import org.apache.royale.events.IEventDispatcher;
> >> -
> >> -/**
> >> - *  The IItemRenderer interface is the basic interface for item
> renderers.
> >> - *  More complex item renderers may implements extensions of this
> interface.
> >> - *
> >> - *  @langversion 3.0
> >> - *  @playerversion Flash 10.2
> >> - *  @playerversion AIR 2.6
> >> - *  @productversion Royale 0.0
> >> - */
> >> -public interface IRuntimeSelectableItemRenderer extends
> ISelectableItemRenderer
> >

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

[Carlos Rovira]

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 lun., 29 jun. 2020 a las 12:29, Harbs () escribió:

> 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 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 repository.
> >>
> >> carlosrovira pushed a commit to branch develop
> >> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >>
> >>
> >> The following commit(s) were added to refs/heads/develop by this push:
> >>new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
> interface
> >> d997c70 is described below
> >>
> >> commit d997c703461167b2072ba75d6ff9215124814d0f
> >> Author: Carlos Rovira 
> >> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> >>
> >>   core-IRuntimeSelectableItemRenderer: remove unused interface
> >> ---
> >> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> >> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> --
> >> 2 files changed, 65 deletions(-)
> >>
> >> diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> index ff662a0..cba38dc 100644
> >> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> @@ -146,7 +146,6 @@ internal class CoreClasses
> >>  import org.apache.royale.core.IScrollBarModel;
> IScrollBarModel;
> >>  }
> >>  import org.apache.royale.core.IListDataItemRenderer;
> IListDataItemRenderer;
> >> -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
> IRuntimeSelectableItemRenderer;
> >>  import org.apache.royale.core.ISelectableItemRenderer;
> ISelectableItemRenderer;
> >>  import org.apache.royale.core.ISelectable; ISelectable;
> >>  import org.apache.royale.core.ISelectionModel; ISelectionModel;
> >> diff --git
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >> deleted file mode 100644
> >> index d5df28b..000
> >> ---
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >> +++ /dev/null
> >> @@ -1,64 +0,0 @@
> >>
> -
> >> -//
> >> -//  Licensed to the Apache Software Foundation (ASF) under one or more
> >> -//  contributor license agreements.  See the NOTICE file distributed
> with
> >> -//  this work for additional information regarding copyright ownership.
> >> -//  The ASF licenses this file to You under the Apache License,
> Version 2.0
> >> -//  (the "License"); you may not use this file except in compliance
> with
> >> -//  the License.  You may obtain a copy of the License at
> >> -//
> >> -//  http://www.apache.org/licenses/LICENSE-2.0
> >> -//
> >> -//  Unless required by applicable law or agreed to in writing, software
> >> -//  distributed under the License is distributed on an "AS IS" BASIS,
> >> -//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> >> -//  See the License for the specific language governing permissions and
> >> -//  limitations under the License.
> >> -//
> >>
> -
> >> -package org.apache.royale.core
> >> -{
> >> -import org.apache.royale.events.IEventDispatcher;
> >> -
> >> -/**
> >> - *  The IItemRenderer interface is the basic interface for item
> renderers.
> >> - *  More complex item renderers may implements extensions of this
> interface.
> >> - *
> >> - *  @langversion 3.0
> >> - *  @playerversion Flash 10.2
> >> - *  @playerversion AIR 2.6
> >> - *  @productversion Royale 0.0
> >> - */
> >> -public interface IRuntimeSelectableItemRenderer extends
> ISelectableItemRenderer
> >> -{
> >> -/**
> >> - *  true if the item renderer is can be selected
> >> - *  false otherwise. Use to configure a renderer to be non
> >> - *  selectable.
> >> - *
> >> - *  Defaults to true
> >> - *
> >> - *  @langversion 3.0
> >> - *  @playerversion Flash 10.2
> >> - *  @playerversion AIR 2.6
> >> - *  @productversion Royale 0.9.3
> >> - */
> >> - 

Re: Emulation with theme/skin

[Harbs]

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 have an advanced data grid, but you can use Spectrum item renderers 
inside Basic components. I’m not sure if/how well that works with Jewel.

HTH,
Harbs

> On Jun 29, 2020, at 1:09 PM, Hugo Ferreira  wrote:
> 
> 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, 29/06/2020
> à(s) 11:02:
> 
>> 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
>> we'll go further with time and effort, but in these days if I find
>> something I need that is not here I try to search in js world and bring to
>> my project. Of course, list-tables-datagrids are important to get it done
>> in the right way since use things that should play nicely with the rest of
>> the infrastructure, 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.
>> 
>> El lun., 29 jun. 2020 a las 11:23, Hugo Ferreira (>> )
>> escribió:
>> 
>>> 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.
>>> 
>>> I'm still facing issues with my isualted trial with drag-drop Panel
>> (Card)
>>> - posted in another thread.
>>> Then, I will probably study Advanced Datagrid alternatives.
>>> 
>>> Piotr Zarzycki  escreveu no dia segunda,
>>> 29/06/2020 à(s) 10:15:
>>> 
 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 2020 o 11:11 Hugo Ferreira 
 napisał(a):
 
> 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 to fill the most needs
> (fortunately, I don't need a tree at all) except for Advanced
>> Datagrid,
> that's a blocker.
> Another approach to try to emulate my needs about Advanced DG is to
> workaround with tabs and bold in normal Datagrid and rows enabled and
> disabled (I don't know if would be possible). I will check later.
> 
> Carlos Rovira  escreveu no dia segunda,
> 29/06/2020
> à(s) 09:56:
> 
>> 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 buttons, checkboxes, datefields, numericstepper,
 should
>>   have a very similar API or the same
>>   - Jewel List should be very close too since it is very evolved.
>>   - Then others like ComboBox, DropDownList, could need more
>>> attention
> by
>>   using beads (for example RequireSelection is a bead not a
>>> property)
>>   - For components still not available in Jewel like Tree and
>>   AdvancedDataGrid, you can maintain them in emulation until we
>> have
> jewel
>>   versions.
>> 
>> 4.- Go further and start changing containers and layouts:
>> 
>>   - Layouts in Jewel is more efficient since it uses (when
>> possible)
>>   browser layout, avoiding extra process
>>   - Containers tries to have the best from flex and the best from
>>> the
>>   modern web and Royale and use jewel layouts.
>> 
>> 5.- If needed and make sense for your app: Try to add some new
>> global layout like the one exposed in TDJ that uses Drawer and
>> Responsiveness to make the App more accessible in Tablets and
>> Mobile
>> d

Re: Rewrite and entire Flex project to Royale Jewel !

[Carlos Rovira]

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 [1]
around 70-80% of as3 code (businees logic) from Flex and 20-30% of code in
mxml tweaked to work in jewel.

Thanks :)

Carlos

[1 https://twitter.com/carlosrovira/status/1098333642751950848





El lun., 29 jun. 2020 a las 1:22, Hugo Ferreira ()
escribió:

> Hi Piotr,
>
> That's great and it's good to know that someone is already doing it !
>
>
> Piotr Zarzycki  escreveu no dia domingo,
> 28/06/2020 à(s) 16:01:
>
> > Hi Hugo,
> >
> > Great to hear that! :) We are going more or less with MyAccount[1] where
> > 30% of code is preserved and the rest is being rewritten on Jewel.
> > It's going to really well. There are couple of huge problems but we have
> > managed to overcome with some workarounds. There literally wasn't
> problems
> > which Holds us from moving forward.
> >
> > [1] https://x.prominic.net/MyAccount
> >
> > Good Luck!
> > Piotr
> >
> > On Sun, Jun 28, 2020, 4:49 PM Hugo Ferreira 
> > wrote:
> >
> > > Hello,
> > >
> > > After my trial with Royal 0.9.7 MX Emulation, I'm dedicating time for
> > > Jewel.
> > > I have to say, congrats.It's very good.
> > >
> > > Apache Royale is much more stable now.
> > > From a year ago to now I can find some documentation and not feel that
> > I'm
> > > totally lost (even so, it's need to dig a little - for example: MX
> > > Emulation requires a special parameter that no one could't know without
> > > searching).
> > > Tour de Jewel it's very, very good and a source of knowledge for a
> > starter
> > > like me, a precious source.
> > >
> > > From someone that comes from Flex and never tried Jewel before, I
> started
> > > to read and understand the concept of Strands and Beads. It's essential
> > and
> > > a different concept from Flex.
> > >
> > > I have a Flex project with 1000 files (only 25% is MXML) but I'm only
> one
> > > and the development can't stop.
> > > I'm considering starting a side project with Jewel, recreating the
> > current
> > > one without stop the development of the current one.
> > > Starting from the basics, then the stable modules that don't change a
> lot
> > > and then the others, replicating every change until the Jewel version
> has
> > > 100% of the MXML functionalities.
> > >
> > > It's a lot of work but seems that Royal and Jewel it's now more ready
> for
> > > that than ever.
> > >
> > > I still have to do a lot of small trials before starting this idea to
> see
> > > if it is really viable.
> > >
> > > I will create the correspondence topics:
> > > - Draggable Cards
> > > - Shareable folder
> > > - Advanced Datagrid
> > >
> > > Regards,
> > > Hugo.
> > >
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Harbs]

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 to make it as easy to 
use as possible without messing with beads more than necessary. One of those 
was having selectable and hoverable getter/setter.

Either way, you should always assume that there’s the possibility that someone 
is using a piece of Royale and if you want to change or remove something, 
please bring it up so we can discuss it.

In the meantime I reverted your commit. If there’s consensus that we should 
remove it, we can do that once I (and anyone else who is using it) has an 
opportunity to modify their code.

Thanks,
Harbs

> On Jun 29, 2020, at 2:00 PM, Carlos Rovira  wrote:
> 
> 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 lun., 29 jun. 2020 a las 12:29, Harbs () escribió:
> 
>> 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 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 repository.
 
 carlosrovira pushed a commit to branch develop
 in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
 
 
 The following commit(s) were added to refs/heads/develop by this push:
   new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
>> interface
 d997c70 is described below
 
 commit d997c703461167b2072ba75d6ff9215124814d0f
 Author: Carlos Rovira 
 AuthorDate: Thu Jun 11 17:01:15 2020 +0200
 
  core-IRuntimeSelectableItemRenderer: remove unused interface
 ---
 .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
 .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
>> --
 2 files changed, 65 deletions(-)
 
 diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
 index ff662a0..cba38dc 100644
 --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
 +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
 @@ -146,7 +146,6 @@ internal class CoreClasses
 import org.apache.royale.core.IScrollBarModel;
>> IScrollBarModel;
 }
 import org.apache.royale.core.IListDataItemRenderer;
>> IListDataItemRenderer;
 -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
>> IRuntimeSelectableItemRenderer;
 import org.apache.royale.core.ISelectableItemRenderer;
>> ISelectableItemRenderer;
 import org.apache.royale.core.ISelectable; ISelectable;
 import org.apache.royale.core.ISelectionModel; ISelectionModel;
 diff --git
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
 deleted file mode 100644
 index d5df28b..000
 ---
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
 +++ /dev/null
 @@ -1,64 +0,0 @@
 
>> -
 -//
 -//  Licensed to the Apache Software Foundation (ASF) under one or more
 -//  contributor license agreements.  See the NOTICE file distributed
>> with
 -//  this work for additional information regarding copyright ownership.
 -//  The ASF licenses this file to You under the Apache License,
>> Version 2.0
 -//  (the "License"); you may not use this file except in compliance
>> with
 -//  the License.  You may obtain a copy of the License at
 -//
 -//  http://www.apache.org/licenses/LICENSE-2.0
 -//
 -//  Unless required by applicable law or agreed to in writing, software
 -//  distributed under the License is distributed on an "AS IS" BASIS,
 -//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
 -//  See the License for the specific language governing permissions and
 -//  limitations under the License.
 -//
 
>> -
 -package org.apache.royale.core
 -{
 -import org.apache.r

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

[Christofer Dutz]

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 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 to make it as easy 
to use as possible without messing with beads more than necessary. One of those 
was having selectable and hoverable getter/setter.

Either way, you should always assume that there’s the possibility that 
someone is using a piece of Royale and if you want to change or remove 
something, please bring it up so we can discuss it.

In the meantime I reverted your commit. If there’s consensus that we should 
remove it, we can do that once I (and anyone else who is using it) has an 
opportunity to modify their code.

Thanks,
Harbs

> On Jun 29, 2020, at 2:00 PM, Carlos Rovira  
wrote:
> 
> 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 lun., 29 jun. 2020 a las 12:29, Harbs () 
escribió:
> 
>> 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 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 repository.
 
 carlosrovira pushed a commit to branch develop
 in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
 
 
 The following commit(s) were added to refs/heads/develop by this push:
   new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
>> interface
 d997c70 is described below
 
 commit d997c703461167b2072ba75d6ff9215124814d0f
 Author: Carlos Rovira 
 AuthorDate: Thu Jun 11 17:01:15 2020 +0200
 
  core-IRuntimeSelectableItemRenderer: remove unused interface
 ---
 .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
 .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
>> --
 2 files changed, 65 deletions(-)
 
 diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
 index ff662a0..cba38dc 100644
 --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
 +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
 @@ -146,7 +146,6 @@ internal class CoreClasses
 import org.apache.royale.core.IScrollBarModel;
>> IScrollBarModel;
 }
 import org.apache.royale.core.IListDataItemRenderer;
>> IListDataItemRenderer;
 -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
>> IRuntimeSelectableItemRenderer;
 import org.apache.royale.core.ISelectableItemRenderer;
>> ISelectableItemRenderer;
 import org.apache.royale.core.ISelectable; ISelectable;
 import org.apache.royale.core.ISelectionModel; ISelectionModel;
 diff --git
>> 
a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>> 
b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
 deleted file mode 100644
 index d5df28b..000
 ---
>> 
a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
 +++ /dev/null
 @@ -1,64 +0,0 @@
 
>> 
-
 -//
 -//  Licensed to the Apache Software Foundation (ASF) under one or more
 -//  contributor license agreements.  See the NOTICE file distributed
>> with
 -//  this work for additional information regarding copyright 
ownership.
 -//  The ASF licenses this file to You under the Apache License,
>> Version 2.0
 -//  (the "License"); you may not use this file except in compliance
>> with
>

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

[Harbs]

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 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 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 to make it as 
> easy to use as possible without messing with beads more than necessary. One 
> of those was having selectable and hoverable getter/setter.
> 
>Either way, you should always assume that there’s the possibility that 
> someone is using a piece of Royale and if you want to change or remove 
> something, please bring it up so we can discuss it.
> 
>In the meantime I reverted your commit. If there’s consensus that we 
> should remove it, we can do that once I (and anyone else who is using it) has 
> an opportunity to modify their code.
> 
>Thanks,
>Harbs
> 
>> On Jun 29, 2020, at 2:00 PM, Carlos Rovira  wrote:
>> 
>> 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 lun., 29 jun. 2020 a las 12:29, Harbs () escribió:
>> 
>>> 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 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 repository.
> 
> carlosrovira pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
>  new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
>>> interface
> d997c70 is described below
> 
> commit d997c703461167b2072ba75d6ff9215124814d0f
> Author: Carlos Rovira 
> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> 
> core-IRuntimeSelectableItemRenderer: remove unused interface
> ---
> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
>>> --
> 2 files changed, 65 deletions(-)
> 
> diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>>> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> index ff662a0..cba38dc 100644
> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> @@ -146,7 +146,6 @@ internal class CoreClasses
>import org.apache.royale.core.IScrollBarModel;
>>> IScrollBarModel;
>}
>import org.apache.royale.core.IListDataItemRenderer;
>>> IListDataItemRenderer;
> -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
>>> IRuntimeSelectableItemRenderer;
>import org.apache.royale.core.ISelectableItemRenderer;
>>> ISelectableItemRenderer;
>import org.apache.royale.core.ISelectable; ISelectable;
>import org.apache.royale.core.ISelectionModel; ISelectionModel;
> diff --git
>>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> deleted file mode 100644
> index d5df28b..000
> ---
>>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> +++ /dev/null
> @@ -1,64 +0,0 @@
> 
>>> -
> -//
> -//  Licensed to the Apache Software Foundation (ASF) under one or more
> -//  contributor license agreements.  See the NOTICE file distributed
>>> with
> -//  this work for additional information regarding copyright ownership.
> -//  The ASF licenses this file to You under the Apache License,
>>> Version 2.0
> -//  (the "License"); you may not use this file except in compliance
>>> with
> -//  the License.  You may obtain a copy of the License at
> -//
> -//  

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

[Harbs]

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 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 to make it as 
> easy to use as possible without messing with beads more than necessary. One 
> of those was having selectable and hoverable getter/setter.
> 
> Either way, you should always assume that there’s the possibility that 
> someone is using a piece of Royale and if you want to change or remove 
> something, please bring it up so we can discuss it.
> 
> In the meantime I reverted your commit. If there’s consensus that we should 
> remove it, we can do that once I (and anyone else who is using it) has an 
> opportunity to modify their code.
> 
> Thanks,
> Harbs
> 
>> On Jun 29, 2020, at 2:00 PM, Carlos Rovira  wrote:
>> 
>> 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 lun., 29 jun. 2020 a las 12:29, Harbs () escribió:
>> 
>>> 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 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 repository.
> 
> carlosrovira pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
>  new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
>>> interface
> d997c70 is described below
> 
> commit d997c703461167b2072ba75d6ff9215124814d0f
> Author: Carlos Rovira 
> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> 
> core-IRuntimeSelectableItemRenderer: remove unused interface
> ---
> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
>>> --
> 2 files changed, 65 deletions(-)
> 
> diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>>> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> index ff662a0..cba38dc 100644
> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> @@ -146,7 +146,6 @@ internal class CoreClasses
>import org.apache.royale.core.IScrollBarModel;
>>> IScrollBarModel;
>}
>import org.apache.royale.core.IListDataItemRenderer;
>>> IListDataItemRenderer;
> -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
>>> IRuntimeSelectableItemRenderer;
>import org.apache.royale.core.ISelectableItemRenderer;
>>> ISelectableItemRenderer;
>import org.apache.royale.core.ISelectable; ISelectable;
>import org.apache.royale.core.ISelectionModel; ISelectionModel;
> diff --git
>>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> deleted file mode 100644
> index d5df28b..000
> ---
>>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> +++ /dev/null
> @@ -1,64 +0,0 @@
> 
>>> -
> -//
> -//  Licensed to the Apache Software Foundation (ASF) under one or more
> -//  contributor license agreements.  See the NOTICE file distributed
>>> with
> -//  this work for additional information regarding copyright ownership.
> -//  The ASF licenses this file to You under the Apache License,
>>> Version 2.0
> -//  (the "License"); you may not use this file except in compliance
>>> with
> -//  the License.  You may obtain a copy of the License at
> -//
> -//  http://www.apache.org/licenses/LICENSE-2.0
> -//
> -//  Unless required by applicable law or agreed to in writing, software
> -//  distributed under the License is distributed on an "AS IS" BASIS,
> -//  WITHOUT WARRANT

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

[Christofer Dutz]

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 discussions about if it’s worth to travel 
to ApacheCons or if there would be a better invest for the time and the bucks.

Now that the invest is really minimal without any travelling, how about 
participating?

Just a thought ….

Chris

Re: Rewrite and entire Flex project to Royale Jewel !

[Hugo Ferreira]

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 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 [1]
> around 70-80% of as3 code (businees logic) from Flex and 20-30% of code in
> mxml tweaked to work in jewel.
>
> Thanks :)
>
> Carlos
>
> [1 https://twitter.com/carlosrovira/status/1098333642751950848
>
>
>
>
>
> El lun., 29 jun. 2020 a las 1:22, Hugo Ferreira ()
> escribió:
>
> > Hi Piotr,
> >
> > That's great and it's good to know that someone is already doing it !
> >
> >
> > Piotr Zarzycki  escreveu no dia domingo,
> > 28/06/2020 à(s) 16:01:
> >
> > > Hi Hugo,
> > >
> > > Great to hear that! :) We are going more or less with MyAccount[1]
> where
> > > 30% of code is preserved and the rest is being rewritten on Jewel.
> > > It's going to really well. There are couple of huge problems but we
> have
> > > managed to overcome with some workarounds. There literally wasn't
> > problems
> > > which Holds us from moving forward.
> > >
> > > [1] https://x.prominic.net/MyAccount
> > >
> > > Good Luck!
> > > Piotr
> > >
> > > On Sun, Jun 28, 2020, 4:49 PM Hugo Ferreira 
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > After my trial with Royal 0.9.7 MX Emulation, I'm dedicating time for
> > > > Jewel.
> > > > I have to say, congrats.It's very good.
> > > >
> > > > Apache Royale is much more stable now.
> > > > From a year ago to now I can find some documentation and not feel
> that
> > > I'm
> > > > totally lost (even so, it's need to dig a little - for example: MX
> > > > Emulation requires a special parameter that no one could't know
> without
> > > > searching).
> > > > Tour de Jewel it's very, very good and a source of knowledge for a
> > > starter
> > > > like me, a precious source.
> > > >
> > > > From someone that comes from Flex and never tried Jewel before, I
> > started
> > > > to read and understand the concept of Strands and Beads. It's
> essential
> > > and
> > > > a different concept from Flex.
> > > >
> > > > I have a Flex project with 1000 files (only 25% is MXML) but I'm only
> > one
> > > > and the development can't stop.
> > > > I'm considering starting a side project with Jewel, recreating the
> > > current
> > > > one without stop the development of the current one.
> > > > Starting from the basics, then the stable modules that don't change a
> > lot
> > > > and then the others, replicating every change until the Jewel version
> > has
> > > > 100% of the MXML functionalities.
> > > >
> > > > It's a lot of work but seems that Royal and Jewel it's now more ready
> > for
> > > > that than ever.
> > > >
> > > > I still have to do a lot of small trials before starting this idea to
> > see
> > > > if it is really viable.
> > > >
> > > > I will create the correspondence topics:
> > > > - Draggable Cards
> > > > - Shareable folder
> > > > - Advanced Datagrid
> > > >
> > > > Regards,
> > > > Hugo.
> > > >
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

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

[Andrew Wetmore]

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 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 discussions about if it’s worth to
> travel to ApacheCons or if there would be a better invest for the time and
> the bucks.
>
> Now that the invest is really minimal without any travelling, how about
> participating?
>
> Just a thought ….
>
> Chris
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[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 everyone is,
and I would be happy to do that coordination unless someone else would like
to.

a

On Mon, Jun 29, 2020 at 10:12 AM Andrew Wetmore  wrote:

> 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 <
> christofer.d...@c-ware.de> wrote:
>
>> 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 discussions about if it’s worth to
>> travel to ApacheCons or if there would be a better invest for the time and
>> the bucks.
>>
>> Now that the invest is really minimal without any travelling, how about
>> participating?
>>
>> Just a thought ….
>>
>> Chris
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Christofer Dutz]

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 conference (At least I'm pretty sure about that).

If you need help to who you should contact and what you need to do ... just 
ping me.

Chris



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 everyone is,
and I would be happy to do that coordination unless someone else would like
to.

a

On Mon, Jun 29, 2020 at 10:12 AM Andrew Wetmore  wrote:

> 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 <
> christofer.d...@c-ware.de> wrote:
>
>> 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 discussions about if it’s worth to
>> travel to ApacheCons or if there would be a better invest for the time 
and
>> the bucks.
>>
>> Now that the invest is really minimal without any travelling, how about
>> participating?
>>
>> Just a thought ….
>>
>> Chris
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Christofer Dutz]

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 everyone is,
and I would be happy to do that coordination unless someone else would like
to.

a

On Mon, Jun 29, 2020 at 10:12 AM Andrew Wetmore  wrote:

> 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 <
> christofer.d...@c-ware.de> wrote:
>
>> 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 discussions about if it’s worth to
>> travel to ApacheCons or if there would be a better invest for the time 
and
>> the bucks.
>>
>> Now that the invest is really minimal without any travelling, how about
>> participating?
>>
>> Just a thought ….
>>
>> Chris
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Andrew Wetmore]

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 ;-)
>
> 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 everyone
> is,
> and I would be happy to do that coordination unless someone else would
> like
> to.
>
> a
>
> On Mon, Jun 29, 2020 at 10:12 AM Andrew Wetmore 
> wrote:
>
> > 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 <
> > christofer.d...@c-ware.de> wrote:
> >
> >> 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 discussions about if it’s
> worth to
> >> travel to ApacheCons or if there would be a better invest for the
> time and
> >> the bucks.
> >>
> >> Now that the invest is really minimal without any travelling, how
> about
> >> participating?
> >>
> >> Just a thought ….
> >>
> >> Chris
> >>
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
> >
> >
> >
> >
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Josh Tynjala]

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 Tynjala
Bowler Hat LLC 


On Mon, Jun 29, 2020 at 4:40 AM 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
> 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 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 to make
> it as easy to use as possible without messing with beads more than
> necessary. One of those was having selectable and hoverable getter/setter.
>
> Either way, you should always assume that there’s the possibility that
> someone is using a piece of Royale and if you want to change or remove
> something, please bring it up so we can discuss it.
>
> In the meantime I reverted your commit. If there’s consensus that we
> should remove it, we can do that once I (and anyone else who is using it)
> has an opportunity to modify their code.
>
> Thanks,
> Harbs
>
> > On Jun 29, 2020, at 2:00 PM, Carlos Rovira 
> wrote:
> >
> > 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 lun., 29 jun. 2020 a las 12:29, Harbs ()
> escribió:
> >
> >> 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 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
> repository.
> 
>  carlosrovira pushed a commit to branch develop
>  in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
>  The following commit(s) were added to refs/heads/develop by this
> push:
>    new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
> >> interface
>  d997c70 is described below
> 
>  commit d997c703461167b2072ba75d6ff9215124814d0f
>  Author: Carlos Rovira 
>  AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> 
>   core-IRuntimeSelectableItemRenderer: remove unused interface
>  ---
>  .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
>  .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> >> --
>  2 files changed, 65 deletions(-)
> 
>  diff --git
> a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  index ff662a0..cba38dc 100644
>  --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  @@ -146,7 +146,6 @@ internal class CoreClasses
>  import org.apache.royale.core.IScrollBarModel;
> >> IScrollBarModel;
>  }
>  import org.apache.royale.core.IListDataItemRenderer;
> >> IListDataItemRenderer;
>  -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
> >> IRuntimeSelectableItemRenderer;
>  import org.apache.royale.core.ISelectableItemRenderer;
> >> ISelectableItemRenderer;
>  import org.apache.royale.core.ISelectable; ISelectable;
>  import org.apache.royale.core.ISelectionModel;
> ISelectionModel;
>  diff --git
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >>
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  deleted file mode 100644
>  index d5df28b..000
>  ---
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  +++ /dev

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

[Josh Tynjala]

> 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 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 discussions about if it’s worth to
> travel to ApacheCons or if there would be a better invest for the time and
> the bucks.
>
> Now that the invest is really minimal without any travelling, how about
> participating?
>
> Just a thought ….
>
> Chris
>

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

[Harbs]

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.
> 
> Example:
> https://twitter.com/as3mxml/status/1192101486563483649
> 
> --
> Josh Tynjala
> Bowler Hat LLC 
> 
> 
> On Mon, Jun 29, 2020 at 4:40 AM 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
>> 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 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 to make
>> it as easy to use as possible without messing with beads more than
>> necessary. One of those was having selectable and hoverable getter/setter.
>> 
>>Either way, you should always assume that there’s the possibility that
>> someone is using a piece of Royale and if you want to change or remove
>> something, please bring it up so we can discuss it.
>> 
>>In the meantime I reverted your commit. If there’s consensus that we
>> should remove it, we can do that once I (and anyone else who is using it)
>> has an opportunity to modify their code.
>> 
>>Thanks,
>>Harbs
>> 
>>> On Jun 29, 2020, at 2:00 PM, Carlos Rovira 
>> wrote:
>>> 
>>> 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 lun., 29 jun. 2020 a las 12:29, Harbs ()
>> escribió:
>>> 
 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 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
>> repository.
>> 
>> carlosrovira pushed a commit to branch develop
>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>> 
>> 
>> The following commit(s) were added to refs/heads/develop by this
>> push:
>>  new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
 interface
>> d997c70 is described below
>> 
>> commit d997c703461167b2072ba75d6ff9215124814d0f
>> Author: Carlos Rovira 
>> AuthorDate: Thu Jun 11 17:01:15 2020 +0200
>> 
>> core-IRuntimeSelectableItemRenderer: remove unused interface
>> ---
>> .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
>> .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
 --
>> 2 files changed, 65 deletions(-)
>> 
>> diff --git
>> a/frameworks/projects/Core/src/main/royale/CoreClasses.as
 b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> index ff662a0..cba38dc 100644
>> --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>> @@ -146,7 +146,6 @@ internal class CoreClasses
>>import org.apache.royale.core.IScrollBarModel;
 IScrollBarModel;
>>}
>>import org.apache.royale.core.IListDataItemRenderer;
 IListDataItemRenderer;
>> -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
 IRuntimeSelectableItemRenderer;
>>import org.apache.royale.core.ISelectableItemRenderer;
 ISelectableItemRenderer;
>>import org.apache.royale.core.ISelectable; ISelectable;
>>import org.apache.royale.core.ISelectionModel;
>> ISelectionModel;
>> diff --git
 
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
 
>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>> deleted file mode 100644
>> index d5df28b..000
>> ---
 
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>> +++ /dev/null
>> @@ -1,64 +0,0 @@
>> 
 
>> -
>> -//
>> 

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

[Andrew Wetmore]

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

[1] https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2020

On Mon, Jun 29, 2020 at 12:47 PM Josh Tynjala 
wrote:

> > 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 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 discussions about if it’s worth to
> > travel to ApacheCons or if there would be a better invest for the time
> and
> > the bucks.
> >
> > Now that the invest is really minimal without any travelling, how about
> > participating?
> >
> > Just a thought ….
> >
> > Chris
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Piotr Zarzycki]

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 refs/heads/develop by this push:
>  new 0b7b465  Test commit [raudjcholo]
> 0b7b465 is described below
>
> commit 0b7b4655fde20f31927fce4f862426cadae2ca6b
> Author: Raul Nuñez 
> AuthorDate: Mon Jun 29 10:05:50 2020 +0200
>
> Test commit [raudjcholo]
> ---
>  GIT-TEST.txt | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/GIT-TEST.txt b/GIT-TEST.txt
> index e9c1205..31d3f2b 100644
> --- a/GIT-TEST.txt
> +++ b/GIT-TEST.txt
> @@ -24,3 +24,4 @@ Test Commit
>  Test Commit [Piotr]
>  Test Coomit [carlos, having issues to push]
>  Test Commit [AlinaKazi]
> +Test Commit [raudjcholo]
>
>

-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Is there a emulation available for flash.display.DisplayObject

[Anil Guntur - agun...@us.ibm.com]

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

[Yishay Weiss]

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: dev@royale.apache.org
Subject: 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: [royale-asjs] branch develop updated: Test commit [raudjcholo]

[Carlos Rovira]

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
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > The following commit(s) were added to refs/heads/develop by this push:
> >  new 0b7b465  Test commit [raudjcholo]
> > 0b7b465 is described below
> >
> > commit 0b7b4655fde20f31927fce4f862426cadae2ca6b
> > Author: Raul Nuñez 
> > AuthorDate: Mon Jun 29 10:05:50 2020 +0200
> >
> > Test commit [raudjcholo]
> > ---
> >  GIT-TEST.txt | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/GIT-TEST.txt b/GIT-TEST.txt
> > index e9c1205..31d3f2b 100644
> > --- a/GIT-TEST.txt
> > +++ b/GIT-TEST.txt
> > @@ -24,3 +24,4 @@ Test Commit
> >  Test Commit [Piotr]
> >  Test Coomit [carlos, having issues to push]
> >  Test Commit [AlinaKazi]
> > +Test Commit [raudjcholo]
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Carlos Rovira]

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 team to share the time and present emulation and other
opportunities in Royale.

I can talk about it more tomorrow

Thanks!

Carlos


El lun., 29 jun. 2020 a las 18:41, Andrew Wetmore ()
escribió:

> 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
>
> [1] https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2020
>
> On Mon, Jun 29, 2020 at 12:47 PM Josh Tynjala 
> wrote:
>
> > > 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 <
> christofer.d...@c-ware.de
> > >
> > wrote:
> >
> > > 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 discussions about if it’s worth to
> > > travel to ApacheCons or if there would be a better invest for the time
> > and
> > > the bucks.
> > >
> > > Now that the invest is really minimal without any travelling, how about
> > > participating?
> > >
> > > Just a thought ….
> > >
> > > Chris
> > >
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Carlos Rovira]

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 the problem
of adding functionality that was not PAYG. I think Initializers are really
a better option than that, so for that reason my opinion is once we got new
initializers, better to remove it from royale core. Of course, others can
use it, but maybe better outside the project enhancing the PAYG nature of
Royale.


>
> Spectrum has been modified to use selection beads, but I encapsulated that
> all within the components. One of my goals with Spectrum was to make it as
> easy to use as possible without messing with beads more than necessary. One
> of those was having selectable and hoverable getter/setter.
>

In jewel the target was the same. But I was ok with Alex removing it and
making it configurable through CSS. I don't think I loose easeness. and I
had the opportunity to play lot with it in TDJ, todomvc and other side
projects I'm doing.


> Either way, you should always assume that there’s the possibility that
> someone is using a piece of Royale and if you want to change or remove
> something, please bring it up so we can discuss it.
>

Yeah, I think this is new casuistic now, since until now I only need to
check Royale code and see that I was not breaking anything. This is
changing with this issue.


>
> In the meantime I reverted your commit. If there’s consensus that we
> should remove it, we can do that once I (and anyone else who is using it)
> has an opportunity to modify their code.
>

That's ok.

Thanks

Carlos


>
> Thanks,
> Harbs
>
> > On Jun 29, 2020, at 2:00 PM, Carlos Rovira 
> wrote:
> >
> > 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 lun., 29 jun. 2020 a las 12:29, Harbs ()
> escribió:
> >
> >> 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 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 repository.
> 
>  carlosrovira pushed a commit to branch develop
>  in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
>  The following commit(s) were added to refs/heads/develop by this push:
>    new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
> >> interface
>  d997c70 is described below
> 
>  commit d997c703461167b2072ba75d6ff9215124814d0f
>  Author: Carlos Rovira 
>  AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> 
>   core-IRuntimeSelectableItemRenderer: remove unused interface
>  ---
>  .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
>  .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> >> --
>  2 files changed, 65 deletions(-)
> 
>  diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  index ff662a0..cba38dc 100644
>  --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  @@ -146,7 +146,6 @@ internal class CoreClasses
>  import org.apache.royale.core.IScrollBarModel;
> >> IScrollBarModel;
>  }
>  import org.apache.royale.core.IListDataItemRenderer;
> >> IListDataItemRenderer;
>  -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
> >> IRuntimeSelectableItemRenderer;
>  import org.apache.royale.core.ISelectableItemRenderer;
> >> ISelectableItemRenderer;
>  import org.apache.royale.core.ISelectable; ISelectable;
>  import org.apache.royale.core.ISelectionModel; ISelectionModel;
>  diff --git
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >>
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  deleted file mode 100644
>  index d5df28b..000
>  ---
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  +++ /dev/null
>  @@ -1,64 +0,0 @@
> 
> >>
> -
>  -//
>

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

[Carlos Rovira]

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 semantic versioning to plan.

El lun., 29 jun. 2020 a las 13:40, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> 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 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 to make
> it as easy to use as possible without messing with beads more than
> necessary. One of those was having selectable and hoverable getter/setter.
>
> Either way, you should always assume that there’s the possibility that
> someone is using a piece of Royale and if you want to change or remove
> something, please bring it up so we can discuss it.
>
> In the meantime I reverted your commit. If there’s consensus that we
> should remove it, we can do that once I (and anyone else who is using it)
> has an opportunity to modify their code.
>
> Thanks,
> Harbs
>
> > On Jun 29, 2020, at 2:00 PM, Carlos Rovira 
> wrote:
> >
> > 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 lun., 29 jun. 2020 a las 12:29, Harbs ()
> escribió:
> >
> >> 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 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
> repository.
> 
>  carlosrovira pushed a commit to branch develop
>  in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
>  The following commit(s) were added to refs/heads/develop by this
> push:
>    new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
> >> interface
>  d997c70 is described below
> 
>  commit d997c703461167b2072ba75d6ff9215124814d0f
>  Author: Carlos Rovira 
>  AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> 
>   core-IRuntimeSelectableItemRenderer: remove unused interface
>  ---
>  .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
>  .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> >> --
>  2 files changed, 65 deletions(-)
> 
>  diff --git
> a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  index ff662a0..cba38dc 100644
>  --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
>  @@ -146,7 +146,6 @@ internal class CoreClasses
>  import org.apache.royale.core.IScrollBarModel;
> >> IScrollBarModel;
>  }
>  import org.apache.royale.core.IListDataItemRenderer;
> >> IListDataItemRenderer;
>  -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
> >> IRuntimeSelectableItemRenderer;
>  import org.apache.royale.core.ISelectableItemRenderer;
> >> ISelectableItemRenderer;
>  import org.apache.royale.core.ISelectable; ISelectable;
>  import org.apache.royale.core.ISelectionModel;
> ISelectionModel;
>  diff --git
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >>
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  deleted file mode 100644
>  index d5df28b..000
>  ---
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
>  

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

[Carlos Rovira]

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 jun. 2020 a las 14:35, Harbs () escribió:

> 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
> 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 to make
> it as easy to use as possible without messing with beads more than
> necessary. One of those was having selectable and hoverable getter/setter.
> >
> > Either way, you should always assume that there’s the possibility that
> someone is using a piece of Royale and if you want to change or remove
> something, please bring it up so we can discuss it.
> >
> > In the meantime I reverted your commit. If there’s consensus that we
> should remove it, we can do that once I (and anyone else who is using it)
> has an opportunity to modify their code.
> >
> > Thanks,
> > Harbs
> >
> >> On Jun 29, 2020, at 2:00 PM, Carlos Rovira 
> wrote:
> >>
> >> 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 lun., 29 jun. 2020 a las 12:29, Harbs ()
> escribió:
> >>
> >>> 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 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 repository.
> >
> > carlosrovira pushed a commit to branch develop
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > The following commit(s) were added to refs/heads/develop by this
> push:
> >  new d997c70  core-IRuntimeSelectableItemRenderer: remove unused
> >>> interface
> > d997c70 is described below
> >
> > commit d997c703461167b2072ba75d6ff9215124814d0f
> > Author: Carlos Rovira 
> > AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> >
> > core-IRuntimeSelectableItemRenderer: remove unused interface
> > ---
> > .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> > .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> >>> --
> > 2 files changed, 65 deletions(-)
> >
> > diff --git a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >>> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> > index ff662a0..cba38dc 100644
> > --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> > +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> > @@ -146,7 +146,6 @@ internal class CoreClasses
> >import org.apache.royale.core.IScrollBarModel;
> >>> IScrollBarModel;
> >}
> >import org.apache.royale.core.IListDataItemRenderer;
> >>> IListDataItemRenderer;
> > -import org.apache.royale.core.IRuntimeSelectableItemRenderer;
> >>> IRuntimeSelectableItemRenderer;
> >import org.apache.royale.core.ISelectableItemRenderer;
> >>> ISelectableItemRenderer;
> >import org.apache.royale.core.ISelectable; ISelectable;
> >import org.apache.royale.core.ISelectionModel; ISelectionModel;
> > diff --git
> >>>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> >>>
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> > deleted file mode 100644
> > index d5df28b..000
> > ---
> >>>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/core/IRuntimeSelectableItemRenderer.as
> > +++ /dev/null
> > @@ -1,64 +0,0 @@
> >
> >>>
> -
> > -//
> > -//  Licensed to the Apache Software Foundation (ASF) under one or
> more
> > -//  contributor license agreements.  See the NOTICE file distributed
> >>> with
> > -//  this work for additional information regarding

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

[Carlos Rovira]

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 differently.
>
> Example:
> https://twitter.com/as3mxml/status/1192101486563483649
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, Jun 29, 2020 at 4:40 AM 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
> > 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 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 to make
> > it as easy to use as possible without messing with beads more than
> > necessary. One of those was having selectable and hoverable
> getter/setter.
> >
> > Either way, you should always assume that there’s the possibility
> that
> > someone is using a piece of Royale and if you want to change or remove
> > something, please bring it up so we can discuss it.
> >
> > In the meantime I reverted your commit. If there’s consensus that we
> > should remove it, we can do that once I (and anyone else who is using it)
> > has an opportunity to modify their code.
> >
> > Thanks,
> > Harbs
> >
> > > On Jun 29, 2020, at 2:00 PM, Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> > >
> > > 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 lun., 29 jun. 2020 a las 12:29, Harbs ()
> > escribió:
> > >
> > >> 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 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
> > repository.
> > 
> >  carlosrovira pushed a commit to branch develop
> >  in repository
> https://gitbox.apache.org/repos/asf/royale-asjs.git
> > 
> > 
> >  The following commit(s) were added to refs/heads/develop by this
> > push:
> >    new d997c70  core-IRuntimeSelectableItemRenderer: remove
> unused
> > >> interface
> >  d997c70 is described below
> > 
> >  commit d997c703461167b2072ba75d6ff9215124814d0f
> >  Author: Carlos Rovira 
> >  AuthorDate: Thu Jun 11 17:01:15 2020 +0200
> > 
> >   core-IRuntimeSelectableItemRenderer: remove unused interface
> >  ---
> >  .../projects/Core/src/main/royale/CoreClasses.as   |  1 -
> >  .../royale/core/IRuntimeSelectableItemRenderer.as  | 64
> > >> --
> >  2 files changed, 65 deletions(-)
> > 
> >  diff --git
> > a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> > >> b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >  index ff662a0..cba38dc 100644
> >  --- a/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >  +++ b/frameworks/projects/Core/src/main/royale/CoreClasses.as
> >  @@ -146,7 +146,6 @@ internal class CoreClasses
> >  import org.apache.royale.core.IScrollBarModel;
> > >> IScrollBarModel;
> >  }
> >  import org.apache.royale.core.IListDataItemRenderer;
> > >> IListDataItemRenderer;
> >  -import
> org.apache.royale.core.IRuntimeSelectableItemRenderer;
> > >> IRuntimeSelectableItemRenderer;
> >  import org.apache.royale.core.ISelectableItemRenderer;
> > >> ISelectableItemRenderer;
> >  import org.apache.royale.core.ISelectable; ISelectable;
> >  import org.apache.royale.core.ISelectionModel;
> > ISelectionModel;
> >  diff --git
> > >>
> >
> a/frameworks/projects/Core/src/main/royale/org/apache

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

[Carlos Rovira]

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 HTML
> The error event is dispatched in all three cases: "", null or "not found".
> The images displayed are as expected.
>
> - Jewel Image / Basic Image control, with the ErrorImage bead
> The error event is received only with "not found".
> The expected image is displayed if it does not exist but if it is "" or
> null, it does not update it and shows the last source displayed.
> (This is the case we are reviewing)
>
> In summary, we did not receive the error event, in the bead, because the
> source is not really being changed (in HTML the source is always assigned
> and therefore the error event always occurs), therefore the ErrorImage bead
> does not work for us .
>
> Viewing the test result confirms that if we don't want to change
> ImageViewBase.as, I think Carlos's second option (create a
> RemoveImageFromDisplay bead) would be the way to go.
>
> When an image is still, the scenarios are only two: The image exists and
> there are no problems, or the image is not found, the error occurs and the
> alternative image is loaded. This need is covered.
>
> When an image is dynamic and the developer does not control the value to
> be assigned, the scenarios are duplicated:
> 1.- Specific image, source is found (ok)
> 2.- Specific image, source is not found (with the bead ErrorImage, ok)
> 3.- No image, source "" / null:
> 3.1.- It may be necessary to "show an alternative image" (for
> example, an image indicating that a source must be added)
> In this case, we shouldn't remove the DOM element.
> 3.2.- or not show any.
> In this case, the DOM element could be removed.
>
> I will read your comments.
>
> Hiedra.
>
> -Mensaje original-
> De: Maria Jose Esteve 
> Enviado el: domingo, 28 de junio de 2020 18:00
> Para: dev@royale.apache.org
> Asunto: RE: Image, does not flush when link value is null or blank
>
> Hello,
> When I tried it I also noticed the error but I did not understand it
> because the Image control had the ErrorImage bead.
>
> I am checking the operation with the old html injected because the onerror
> did jump with white or null.
> I tell you what I see.
>
> hiedra
>
> -Mensaje original-
> De: Carlos Rovira  Enviado el: domingo, 28 de
> junio de 2020 10:41
> Para: Apache Royale Development 
> Asunto: Re: Image, does not flush when link value is null or blank
>
> Hi,
>
> I'm checking it, and I found that setting src to null makes the browser
> throw an error: Failed to load resource: net::ERR_FILE_NOT_FOUND (also
> tried to set to '' but it didn't change anything)
>
> so that doesn't seem the solution Royale should do by default, since apps
> will be getting lots of errors in browsers console.
>
> Searching on the internet people use to remove the image from the DOM or
> remove from display, I think we can do that. What do others think about it?
>
> Also since we are adding ErrorImage.as bead, we can manage it there. So a
> normal image control only can load an image.
> If people want to set it to null or empty string and remove it add
> ErrorImage bead and display the alternative image.
> Also we could have another "RemoveImageFromDisplay" and
> "RemoveImageFromDOM" bead that instead of add alternative image will remove
> from DOM or display or DOM respectively.
>
> thoughts?
>
>
>
>
> El sáb., 27 jun. 2020 a las 18:10, Maria Jose Esteve ()
> escribió:
>
> > Do you get the attached screens? I don't see them ...
> > I'm sorry, I put it in text:
> >
> > De: Maria Jose Esteve mailto:mjest...@iest.com>>
> > Enviado el: sábado, 27 de junio de 2020 15:00
> > Para: dev@royale.apache.org
> > Asunto: Image, does not flush when link value is null or blank
> >
> > Hi,
> > Setting up a detail form, where I have a jewel image component, I have
> > noticed that when a "" (empty string) or null is assigned to the src
> > property, the image is not emptied..
> > I have detected the origin of the problem and I present a possible
> > solution, to see how you see it.
> >
> > When the url / src is "" or null it does not enter through the if
> > (_model.url) and consequently it does not call applyImageDate and the
> > img is not updated:
> >
> > [ImageViewBase.as]
> >
> > protected function handleUrlChange(event:Event):void
> > {
> > COMPILE::SWF
> > {
> > if (_model.url) {
> > setupLoader();
> > loader.load(new URLRequest(_model.url));
> > }
> > }
> > COMPILE::JS
> > {
> > if (_model.url) {
> > setupLoader();
> > (host as IImage).applyImageData(_m

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

[Anil Guntur - agun...@us.ibm.com]

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: Yishay Weiss 
Reply-To: "us...@royale.apache.org" 
Date: Monday, June 29, 2020 at 11:25 AM
To: "dev@royale.apache.org" , "us...@royale.apache.org" 

Cc: "dev@royale.apache.org" 
Subject: [EXTERNAL] 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: dev@royale.apache.org
Subject: 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: How about a "royale" or "frontend" track on the virtual ApacheCon?

[Andrew Wetmore]

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 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 team to share the time and present emulation and other
> opportunities in Royale.
>
> I can talk about it more tomorrow
>
> Thanks!
>
> Carlos
>
>
> El lun., 29 jun. 2020 a las 18:41, Andrew Wetmore ()
> escribió:
>
> > 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
> >
> > [1] https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2020
> >
> > On Mon, Jun 29, 2020 at 12:47 PM Josh Tynjala  >
> > wrote:
> >
> > > > 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 <
> > christofer.d...@c-ware.de
> > > >
> > > wrote:
> > >
> > > > 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 discussions about if it’s worth
> to
> > > > travel to ApacheCons or if there would be a better invest for the
> time
> > > and
> > > > the bucks.
> > > >
> > > > Now that the invest is really minimal without any travelling, how
> about
> > > > participating?
> > > >
> > > > Just a thought ….
> > > >
> > > > Chris
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Anil Guntur - agun...@us.ibm.com]

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

[WH_Email_Sig_Logo.png]



From: "Anil Guntur - agun...@us.ibm.com" 
Reply-To: "us...@royale.apache.org" 
Date: Monday, June 29, 2020 at 1:35 PM
To: "us...@royale.apache.org" , 
"dev@royale.apache.org" 
Subject: [EXTERNAL] 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: Yishay Weiss 
Reply-To: "us...@royale.apache.org" 
Date: Monday, June 29, 2020 at 11:25 AM
To: "dev@royale.apache.org" , "us...@royale.apache.org" 

Cc: "dev@royale.apache.org" 
Subject: [EXTERNAL] 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: dev@royale.apache.org
Subject: 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: Emulation for flash.ui.ContextMenu and flash.ui.ContextMenuItem

[Greg Dove]

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 your thoughts/ideas directly to the github issue.
I think this is probably the best first step... but there are no hard and
fast 'rules' for how we work on these things, just general collaboration,
usually consistent with the approaches already used in the current
codebase.



thanks,
Greg



1. https://github.com/apache/royale-asjs/issues/877


On Sat, Jun 27, 2020 at 10:32 AM Anil Guntur - agun...@us.ibm.com <
agun...@us.ibm.com> wrote:

> Hello,
> As per Greg Dove, This is to start a thread on implementing
> flash.ui.ContextMenuItem into one of the Royale packages. I am happy to
> contribute as much as I can.. Let me know the next steps
>
> Thanks
>
>
> From: Greg Dove 
> Reply-To: "us...@royale.apache.org" 
> Date: Friday, June 26, 2020 at 11:24 AM
> To: "us...@royale.apache.org" 
> Subject: [EXTERNAL] Re: Emulation for flash.ui.ContextMenu and
> flash.ui.ContextMenuItem
>
> This is not yet done. I have intention to work on this at some point, but
> I cannot give a fixed timeframe yet.
> Of course we also welcome contributions from others who may be interested
> to help if you, or anyone else, are interested in contributing. If so
> please start a discussion on the dev mailing list.
> Meanwhile, I will add a github issue for ContextMenu emulation later today
> and reply in here with a link. That way, you could add yourself to receive
> updates from the issue so you know if others are working on it.
>
>
> Hope this helps.
> Greg
>
>
>
>
>
>
>
> On Sat, 27 Jun 2020, 05:26 Anil Guntur - agun...@us.ibm.com agun...@us.ibm.com>, mailto:agun...@us.ibm.com>>
> wrote:
> Hello,
> I found the equivalent class for flash.ui.ContextMenu in
> org.adobe.royale.textLayout.dummy package but could not find for
> flash.ui.ContextMenuItem
> Is there one available for flash.ui.ContextMenuItem
>
> Thanks again
> Anil
>

RE: Emulation for flash.utils.Dictionary

[Anil Guntur - agun...@us.ibm.com]

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 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

[WH_Email_Sig_Logo.png]



From: "Anil Guntur - agun...@us.ibm.com" 
Reply-To: "us...@royale.apache.org" 
Date: Monday, June 29, 2020 at 1:35 PM
To: "us...@royale.apache.org" , 
"dev@royale.apache.org" 
Subject: [EXTERNAL] 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: Yishay Weiss 
Reply-To: "us...@royale.apache.org" 
Date: Monday, June 29, 2020 at 11:25 AM
To: "dev@royale.apache.org" , "us...@royale.apache.org" 

Cc: "dev@royale.apache.org" 
Subject: [EXTERNAL] 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: dev@royale.apache.org
Subject: 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: How about a "royale" or "frontend" track on the virtual ApacheCon?

[Carlos Rovira]

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 Jewel"!
>
> On Mon, Jun 29, 2020 at 4:40 PM Carlos Rovira 
> wrote:
>
> > 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 team to share the time and present emulation and other
> > opportunities in Royale.
> >
> > I can talk about it more tomorrow
> >
> > Thanks!
> >
> > Carlos
> >
> >
> > El lun., 29 jun. 2020 a las 18:41, Andrew Wetmore ( >)
> > escribió:
> >
> > > 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
> > >
> > > [1]
> https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2020
> > >
> > > On Mon, Jun 29, 2020 at 12:47 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev
> > >
> > > wrote:
> > >
> > > > > 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 <
> > > christofer.d...@c-ware.de
> > > > >
> > > > wrote:
> > > >
> > > > > 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 discussions about if it’s
> worth
> > to
> > > > > travel to ApacheCons or if there would be a better invest for the
> > time
> > > > and
> > > > > the bucks.
> > > > >
> > > > > Now that the invest is really minimal without any travelling, how
> > about
> > > > > participating?
> > > > >
> > > > > Just a thought ….
> > > > >
> > > > > Chris
> > > > >
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

MouseDown and MouseUp button are fired with secondary mouse button

[Carlos Rovira]

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 previous code in all our handlers right?

what do you think about it? what should we do to prevent it?

Thanks

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Drag and Drop example

[Hugo Ferreira]

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 need to reset that with a style change.
For sure that's exists a better solution but it's working and I tested
everything.

This is my final code for future reference - a drag and drop Card:

Panel.mxml:

http://ns.adobe.com/mxml/2009";
xmlns:js="library://ns.apache.org/royale/basic"
xmlns:html="library://ns.apache.org/royale/html"
xmlns:j="library://ns.apache.org/royale/jewel">















App.mxml:


http://ns.adobe.com/mxml/2009";
xmlns:html="library://ns.apache.org/royale/html"
xmlns:j="library://ns.apache.org/royale/jewel"
xmlns:js="library://ns.apache.org/royale/basic"
xmlns:f="framework.*">
























Hugo Ferreira  escreveu no dia segunda, 29/06/2020
à(s) 01:25:

> Here my mini project for recreate movable Flex Panel:
>
> https://drive.google.com/file/d/19qaHGIlK3Xj-ub3h66vl5SePLxlgnM9l/view?usp=sharing
>
> The only thing that I can't solve it's that after a drop, I can't start
> dragging again.
> I already tried all the options that I could find.
>
> Harbs  escreveu no dia domingo, 28/06/2020 à(s)
> 19:52:
>
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/royale/DragAndDropExample
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/royale/MultiDragDropExample
>>
>> > On Jun 28, 2020, at 9:27 PM, Hugo Ferreira 
>> wrote:
>> >
>> > Hello,
>> >
>> > With Flex I can easy drag and drop a Flex Panel.
>> > Just listen for mouse down and up and use the built in startDrag and
>> > stopDrag functions:
>> >
>> > private function handleDown(event:MouseEvent):void
>> > {
>> >this.startDrag();
>> > }
>> >
>> > private function handleUp(event:MouseEvent):void
>> > {
>> >this.stopDrag();
>> > }
>> >
>> > How to do the same with Royale ?
>> >
>> > Thank you,
>> >
>> > Hugo.
>>
>>

MaterialIcon is not taking effect

[Hugo Ferreira]

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: MaterialIcon is not taking effect

[Piotr Zarzycki]

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 using the official 0,9,7 + Jewel.
>
> I already check tour the jewel.
>
> What I may be missing to use MaterialIcons ?
>