Hi Harbs, I'm seeing as well that Container can return to Basic, and ContainerBase be in Core. I think it was part of the hard fight I had to do to deal with the refactoring. ItemRendererMouseController not sure, maybe can be as well in Basic and a copy in Jewel... I'll be in my computer in an hour or so and can look at it.
As I said in my email, normaly this problems can be fixed just upgrading package namespaces to the new ones. I think some isolated issues can arise like this, but I think this change is important, more thinking to reach a 1.0 and settle the API for many time, so for that reason I want to do this now that Jewel is still with few components. btw, just to notice, I'm seeing all jewel examples reduced to 40% in size thanks to this change. Since Basic was carrying a lot of unused stuff. 2018-05-06 9:14 GMT+02:00 Harbs <harbs.li...@gmail.com>: > org.apache.royale.html.beads.controllers.ItemRendererMouseController was > changed to the core package as well (which also broke my app) > > I did not notice discussion about this. Why the package name change? How > many more changes were there like this? > > Harbs > > > On May 6, 2018, at 10:07 AM, Harbs <harbs.li...@gmail.com> wrote: > > > > Why did Container become org.apache.royale.core.Container instead of > org.apache.royale.html.Container? > > > > Why is Container Core at all? > > > > This change broke my app. While it’s not a big deal to fix it, I don’t > understand why the change. Unless we decide on a wholesale change of > components, this seems like a gratuitous breaking change for no good reason. > > > > Harbs > > -- Carlos Rovira http://about.me/carlosrovira
