You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2018/09/03 06:17:16 UTC
Make Jewel dependent on Basic (Re: [Discuss] Start release process 0.9.3)
Hi,
considering making Jewel dependent on Basic. I'm trying to put my mind in
that place. Since this is a huge effort for me, hope you all try to do the
same as me and considering some thoughts, so we can plan something that
works for all:
Since Basic will be the middle point between Core and Jewel, can we
consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could be
really the common basic library and CSS doesn't mess Jewel things?
If so, we can go that router and test and discuss that integration in a
separate branch and deal with all of that.
this will inevitably delay the release, but maybe is time to solve this
first.
One of the things to do in the final result is to compile Jewel (debug and
release) and comparte results on develop and results on integration branch
Then we can decide what's better and release that
Thoughts?
El lun., 3 sept. 2018 a las 4:53, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> FWIW, I agree with Harbs. Enough time has passed and changes have been
> made that it is time to try making Jewel dependent on Basic so we can see
> in code (not words) what the problems are with doing that.
>
> My 2 cents,
> -Alex
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
thanks for asking. Yes, if we want to try link Jewel is ok to link to
others like HTML.
Carlos
El lun., 3 sept. 2018 a las 10:56, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> I'm doing Maven build and HTML was failing. It is because it need to depend
> again from Basic. I can make the changes.
>
> Carlos are you on that right now ? I don't want to collide with you.
>
> Thanks,
> Piotr
>
> pon., 3 wrz 2018 o 10:28 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Harbs,
> >
> > I'm available for you to help you solve. write me when you need.
> >
> > Just a note: for doing this, I'll take the following path: I'll try to
> > compile and run without make Jewel depend on Basic, since is the actual
> > shape. From there I'll try to link Basic. I think that path will provide
> > you a more safe point from what you could go to next step. Just my advice
> > if you want to take it.
> >
> > Thanks!
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> > El lun., 3 sept. 2018 a las 10:23, Harbs (<ha...@gmail.com>)
> > escribió:
> >
> > > OK. Everything compiles now.
> > >
> > > I’m going to run the branch against some applications and see what
> > > happens. If you could do the same, it would be helpful.
> > >
> > > Carlos, I probably need some direction on how to test Jewel.
> > >
> > > Harbs
> > >
> > > > On Sep 3, 2018, at 10:38 AM, Piotr Zarzycki <
> piotrzarzycki21@gmail.com
> > >
> > > wrote:
> > > >
> > > > Ok! Again good luck! :)
> > > >
> > > > pon., 3 wrz 2018 o 09:34 Harbs <ha...@gmail.com> napisał(a):
> > > >
> > > >> The issues that I see with Jewel are related to the changes that
> were
> > > lost
> > > >> when you merged.
> > > >>
> > > >> I’m hoping I can resolve this quickly. Let’s see how over-optimistic
> > I’m
> > > >> being… ;-)
> > > >>
> > > >> Harbs
> > > >>
> > > >>> On Sep 3, 2018, at 10:28 AM, Piotr Zarzycki <
> > piotrzarzycki21@gmail.com
> > > >
> > > >> wrote:
> > > >>>
> > > >>> Harbs,
> > > >>>
> > > >>> There is also another way. Maybe it is worth that I will spend
> couple
> > > of
> > > >>> hours on my branch and try to understand what was wrong. If I would
> > > >> manage
> > > >>> to do that - maybe you will be able to add your stuff on top of
> that
> > ?
> > > Do
> > > >>> you see value in that approach ?
> > > >>>
> > > >>> I'm just afraid that doing again Jewel depends on Basic end up
> with a
> > > lot
> > > >>> of problems for you and delay for weeks that release.
> > > >>>
> > > >>> Thanks,
> > > >>> Piotr
> > > >>>
> > > >>> pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > > >>> napisał(a):
> > > >>>
> > > >>>> Hi Harbs,
> > > >>>>
> > > >>>> Looking forward to your changes. I'm just interested in release in
> > > >>>> whatever state it is and dealing with discussion later on.
> > > >>>>
> > > >>>> Btw. I have invested also at least 6h with merge stuff and as you
> > can
> > > >> see
> > > >>>> it end up with bigger things. Good Luck! :)
> > > >>>>
> > > >>>> Thanks,
> > > >>>> Piotr
> > > >>>>
> > > >>>> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com>
> napisał(a):
> > > >>>>
> > > >>>>> Right now, my priority is getting all three active branches
> > combined
> > > >> with
> > > >>>>> all code working. That means MX/Spark, Jewel, and all the
> additions
> > > on
> > > >> the
> > > >>>>> revert branch all coexisting nicely in the merge branch.
> > > >>>>>
> > > >>>>> I’m spending the better part of today on that.
> > > >>>>>
> > > >>>>> I’d like to hold off on discussing where to go from here until I
> > > >>>>> understand the issues you went through with Jewel better. I
> expect
> > > I’m
> > > >>>>> going to go through a lot of the pain you already went through
> > > already
> > > >>>>> getting Jewel to compile and work with the merges.
> > > >>>>>
> > > >>>>> I might end up in the same place as you. Don’t know yet…
> > > >>>>>
> > > >>>>> I’m open to all possibilities. Even if we do separate
> depenendies,
> > > >> having
> > > >>>>> the dependencies even temporarily *might* help resolve some of
> the
> > > >>>>> underlying technical issues.
> > > >>>>>
> > > >>>>> Let’s discuss when I come up for air… ;-)
> > > >>>>>
> > > >>>>> Harbs
> > > >>>>>
> > > >>>>>> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <
> > carlosrovira@apache.org>
> > > >>>>> wrote:
> > > >>>>>>
> > > >>>>>> Hi,
> > > >>>>>>
> > > >>>>>> considering making Jewel dependent on Basic. I'm trying to put
> my
> > > mind
> > > >>>>> in
> > > >>>>>> that place. Since this is a huge effort for me, hope you all try
> > to
> > > do
> > > >>>>> the
> > > >>>>>> same as me and considering some thoughts, so we can plan
> something
> > > >> that
> > > >>>>>> works for all:
> > > >>>>>>
> > > >>>>>> Since Basic will be the middle point between Core and Jewel, can
> > we
> > > >>>>>> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic
> > could
> > > >> be
> > > >>>>>> really the common basic library and CSS doesn't mess Jewel
> things?
> > > >>>>>>
> > > >>>>>> If so, we can go that router and test and discuss that
> integration
> > > in
> > > >> a
> > > >>>>>> separate branch and deal with all of that.
> > > >>>>>> this will inevitably delay the release, but maybe is time to
> solve
> > > >> this
> > > >>>>>> first.
> > > >>>>>>
> > > >>>>>> One of the things to do in the final result is to compile Jewel
> > > (debug
> > > >>>>> and
> > > >>>>>> release) and comparte results on develop and results on
> > integration
> > > >>>>> branch
> > > >>>>>>
> > > >>>>>> Then we can decide what's better and release that
> > > >>>>>>
> > > >>>>>> Thoughts?
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> El lun., 3 sept. 2018 a las 4:53, Alex Harui
> > > >> (<aharui@adobe.com.invalid
> > > >>>>>> )
> > > >>>>>> escribió:
> > > >>>>>>
> > > >>>>>>> FWIW, I agree with Harbs. Enough time has passed and changes
> > have
> > > >> been
> > > >>>>>>> made that it is time to try making Jewel dependent on Basic so
> we
> > > can
> > > >>>>> see
> > > >>>>>>> in code (not words) what the problems are with doing that.
> > > >>>>>>>
> > > >>>>>>> My 2 cents,
> > > >>>>>>> -Alex
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Carlos Rovira
> > > >>>>>> http://about.me/carlosrovira
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>> --
> > > >>>>
> > > >>>> Piotr Zarzycki
> > > >>>>
> > > >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >>>> <https://www.patreon.com/piotrzarzycki>*
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>>
> > > >>> Piotr Zarzycki
> > > >>>
> > > >>> Patreon: *https://www.patreon.com/piotrzarzycki
> > > >>> <https://www.patreon.com/piotrzarzycki>*
> > > >>
> > > >>
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
I'm doing Maven build and HTML was failing. It is because it need to depend
again from Basic. I can make the changes.
Carlos are you on that right now ? I don't want to collide with you.
Thanks,
Piotr
pon., 3 wrz 2018 o 10:28 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Harbs,
>
> I'm available for you to help you solve. write me when you need.
>
> Just a note: for doing this, I'll take the following path: I'll try to
> compile and run without make Jewel depend on Basic, since is the actual
> shape. From there I'll try to link Basic. I think that path will provide
> you a more safe point from what you could go to next step. Just my advice
> if you want to take it.
>
> Thanks!
>
> Carlos
>
>
>
>
>
>
> El lun., 3 sept. 2018 a las 10:23, Harbs (<ha...@gmail.com>)
> escribió:
>
> > OK. Everything compiles now.
> >
> > I’m going to run the branch against some applications and see what
> > happens. If you could do the same, it would be helpful.
> >
> > Carlos, I probably need some direction on how to test Jewel.
> >
> > Harbs
> >
> > > On Sep 3, 2018, at 10:38 AM, Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > wrote:
> > >
> > > Ok! Again good luck! :)
> > >
> > > pon., 3 wrz 2018 o 09:34 Harbs <ha...@gmail.com> napisał(a):
> > >
> > >> The issues that I see with Jewel are related to the changes that were
> > lost
> > >> when you merged.
> > >>
> > >> I’m hoping I can resolve this quickly. Let’s see how over-optimistic
> I’m
> > >> being… ;-)
> > >>
> > >> Harbs
> > >>
> > >>> On Sep 3, 2018, at 10:28 AM, Piotr Zarzycki <
> piotrzarzycki21@gmail.com
> > >
> > >> wrote:
> > >>>
> > >>> Harbs,
> > >>>
> > >>> There is also another way. Maybe it is worth that I will spend couple
> > of
> > >>> hours on my branch and try to understand what was wrong. If I would
> > >> manage
> > >>> to do that - maybe you will be able to add your stuff on top of that
> ?
> > Do
> > >>> you see value in that approach ?
> > >>>
> > >>> I'm just afraid that doing again Jewel depends on Basic end up with a
> > lot
> > >>> of problems for you and delay for weeks that release.
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <pi...@gmail.com>
> > >>> napisał(a):
> > >>>
> > >>>> Hi Harbs,
> > >>>>
> > >>>> Looking forward to your changes. I'm just interested in release in
> > >>>> whatever state it is and dealing with discussion later on.
> > >>>>
> > >>>> Btw. I have invested also at least 6h with merge stuff and as you
> can
> > >> see
> > >>>> it end up with bigger things. Good Luck! :)
> > >>>>
> > >>>> Thanks,
> > >>>> Piotr
> > >>>>
> > >>>> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
> > >>>>
> > >>>>> Right now, my priority is getting all three active branches
> combined
> > >> with
> > >>>>> all code working. That means MX/Spark, Jewel, and all the additions
> > on
> > >> the
> > >>>>> revert branch all coexisting nicely in the merge branch.
> > >>>>>
> > >>>>> I’m spending the better part of today on that.
> > >>>>>
> > >>>>> I’d like to hold off on discussing where to go from here until I
> > >>>>> understand the issues you went through with Jewel better. I expect
> > I’m
> > >>>>> going to go through a lot of the pain you already went through
> > already
> > >>>>> getting Jewel to compile and work with the merges.
> > >>>>>
> > >>>>> I might end up in the same place as you. Don’t know yet…
> > >>>>>
> > >>>>> I’m open to all possibilities. Even if we do separate depenendies,
> > >> having
> > >>>>> the dependencies even temporarily *might* help resolve some of the
> > >>>>> underlying technical issues.
> > >>>>>
> > >>>>> Let’s discuss when I come up for air… ;-)
> > >>>>>
> > >>>>> Harbs
> > >>>>>
> > >>>>>> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <
> carlosrovira@apache.org>
> > >>>>> wrote:
> > >>>>>>
> > >>>>>> Hi,
> > >>>>>>
> > >>>>>> considering making Jewel dependent on Basic. I'm trying to put my
> > mind
> > >>>>> in
> > >>>>>> that place. Since this is a huge effort for me, hope you all try
> to
> > do
> > >>>>> the
> > >>>>>> same as me and considering some thoughts, so we can plan something
> > >> that
> > >>>>>> works for all:
> > >>>>>>
> > >>>>>> Since Basic will be the middle point between Core and Jewel, can
> we
> > >>>>>> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic
> could
> > >> be
> > >>>>>> really the common basic library and CSS doesn't mess Jewel things?
> > >>>>>>
> > >>>>>> If so, we can go that router and test and discuss that integration
> > in
> > >> a
> > >>>>>> separate branch and deal with all of that.
> > >>>>>> this will inevitably delay the release, but maybe is time to solve
> > >> this
> > >>>>>> first.
> > >>>>>>
> > >>>>>> One of the things to do in the final result is to compile Jewel
> > (debug
> > >>>>> and
> > >>>>>> release) and comparte results on develop and results on
> integration
> > >>>>> branch
> > >>>>>>
> > >>>>>> Then we can decide what's better and release that
> > >>>>>>
> > >>>>>> Thoughts?
> > >>>>>>
> > >>>>>>
> > >>>>>> El lun., 3 sept. 2018 a las 4:53, Alex Harui
> > >> (<aharui@adobe.com.invalid
> > >>>>>> )
> > >>>>>> escribió:
> > >>>>>>
> > >>>>>>> FWIW, I agree with Harbs. Enough time has passed and changes
> have
> > >> been
> > >>>>>>> made that it is time to try making Jewel dependent on Basic so we
> > can
> > >>>>> see
> > >>>>>>> in code (not words) what the problems are with doing that.
> > >>>>>>>
> > >>>>>>> My 2 cents,
> > >>>>>>> -Alex
> > >>>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Carlos Rovira
> > >>>>>> http://about.me/carlosrovira
> > >>>>>
> > >>>>>
> > >>>>
> > >>>> --
> > >>>>
> > >>>> Piotr Zarzycki
> > >>>>
> > >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> > >>>> <https://www.patreon.com/piotrzarzycki>*
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>>
> > >>> Piotr Zarzycki
> > >>>
> > >>> Patreon: *https://www.patreon.com/piotrzarzycki
> > >>> <https://www.patreon.com/piotrzarzycki>*
> > >>
> > >>
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
That token is working for Moonshine as well, so not sure what is wrong on
your end. :(
pon., 3 wrz 2018 o 20:16 Harbs <ha...@gmail.com> napisał(a):
> I saw that, but for some reason it did not work for me…
>
> > On Sep 3, 2018, at 9:11 PM, Piotr Zarzycki <pi...@gmail.com>
> wrote:
> >
> > It's recognized. Today I have fixed Jewel Alert example by that commit
> [1]
> >
> > [1]
> >
> https://github.com/apache/royale-asjs/commit/37d24b86a674c61be9688f09492978c74a243f3b
> >
> > Thanks,
> > Piotr
> >
> > pon., 3 wrz 2018 o 20:09 Harbs <ha...@gmail.com> napisał(a):
> >
> >> I don’t think theme is recognized by asconfigc and I don’t think
> there’s a
> >> way to use relative paths or tokens as a compiler option. Am I missing
> >> something?
> >>
> >>> On Sep 3, 2018, at 8:59 PM, Piotr Zarzycki <pi...@gmail.com>
> >> wrote:
> >>>
> >>> Harbs,
> >>>
> >>> I believe JewelExample contains TablePlayGround. If you will be playing
> >>> with that. Can you fix VSCode build as well ? Enough if you add missing
> >>> parts in asconfig.json. Check what jewel theme is being used in
> pom.xml.
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
> >>>
> >>>> Hi Carlos,
> >>>>
> >>>> Thanks for checking.
> >>>>
> >>>> Which Jewel examples should I use to fix this?
> >>>>
> >>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
> >>>> wrote:
> >>>>>
> >>>>> Hi, congratulations! jewel example is running almost at 70% aprox
> >>>>>
> >>>>> Things to fix:
> >>>>>
> >>>>> * Table, this will fix DateChooser and this DateField (DateChooser
> >> uses a
> >>>>> Table internally)
> >>>>> The problem here's the changes in DataGroup, we can skip this problem
> >> if
> >>>> we
> >>>>> want for now making Jewel DataGroup be equal to old DataGroup instead
> >> of
> >>>>> extend basic DataGroup,
> >>>>> If not we need to know about the changes in DataGroup and change
> >>>>> TBodyContentArea to work with the new changes
> >>>>>
> >>>>> * List, adding, removing, and so on are reporting errors, due to the
> >> same
> >>>>> problems as before, strangely some things here although give error
> >> works
> >>>> :?
> >>>>>
> >>>>> * ComboBox is not popup the list when clicked, again is a problem
> with
> >>>>> DataGroups since the ComboBox uses a ComboBoxList that has
> IContentView
> >>>>> equal to ComboBoxListDataGroup
> >>>>>
> >>>>> @Alex or someone at MXRoyale could let us know about the changes in
> >>>>> DataGroup so we can adapt the code to new DataGroup??
> >>>>>
> >>>>> Piotr, Harbs good work on merging! :D
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
> >>>> carlosrovira@apache.org>)
> >>>>> escribió:
> >>>>>
> >>>>>> build with maven is ok for me :)
> >>>>>>
> >>>>>> I try examples now
> >>>>>>
> >>>>>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
> >>>>>> escribió:
> >>>>>>
> >>>>>>> Oops. I broke that.
> >>>>>>>
> >>>>>>> Should be fixed now…
> >>>>>>>
> >>>>>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <
> carlosrovira@apache.org>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Hi build with maven fails in MXRoyale:
> >>>>>>>>
> >>>>>>>> COMPC
> >>>>>>>>
> >>>>>>>> Loading configuration:
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>>>>>> col: 8 Warning: Definition
> >>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider could not
> be
> >>>>>>> found.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>>>>>
> >>>>>>>> ^
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>>>>>> col: 129 Error: interface IItemRendererProvider was not found.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> public class ListBase extends UIComponent implements
> >>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>>>>>> ILayoutView,
> >>>>>>>> IItemRendererProvider
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ^
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> mx.controls.RichTextEditor is defined by multiple files:
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>>>>>> col: 8 Definition
> >>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider
> >>>>>>>> could not be found.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>>>>>
> >>>>>>>> ^
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>>>>>> col: 129 interface IItemRendererProvider was not found.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> public class ListBase extends UIComponent implements
> >>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>>>>>> ILayoutView,
> >>>>>>>> IItemRendererProvider
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ^
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> 1.197156816 seconds
> >>>>>>>>
> >>>>>>>> [*INFO*]
> >>>>>>>>
> >>>>>>>
> >>>>
> >>
> *------------------------------------------------------------------------*
> >>>>>>>>
> >>>>>>>> [*INFO*] *Reactor Summary:*
> >>>>>>>>
> >>>>>>>> [*INFO*]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 3.744 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework ...........................
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.355 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Fonts ....................
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.190 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs .....................
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.762 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 7.075 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.989 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.714 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.485 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 6.852 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 2.051 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.190 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.098 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.023 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.990 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.855 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.763 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.715 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.873 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.052 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.694 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.631 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.352 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 2.553 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.888 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.629 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.095 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.448 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.732 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 0.998 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 7.767 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
> >>>> *SUCCESS*
> >>>>>>> [
> >>>>>>>> 1.008 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
> >>>> *FAILURE*
> >>>>>>> [
> >>>>>>>> 1.396 s]
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
> >>>> *SKIPPED*
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
> >>>> *SKIPPED*
> >>>>>>>>
> >>>>>>>> [*INFO*] Apache Royale: Framework:
> >>>>>>>>
> >>>>>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
> >>>>>>>> piotrzarzycki21@gmail.com>) escribió:
> >>>>>>>>
> >>>>>>>>> Maven build should work - I checked it one hour ago.
> >>>>>>>>>
> >>>>>>>>> I will try to get from your plate Tour De Flex.
> >>>>>>>>>
> >>>>>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com>
> wrote:
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <
> >> carlosrovira@apache.org
> >>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Hi Harbs
> >>>>>>>>>>>
> >>>>>>>>>>> just check what I can do:
> >>>>>>>>>>> The branch you're working is "feature/new_merge" right?
> >>>>>>>>>>
> >>>>>>>>>> Yes.
> >>>>>>>>>>
> >>>>>>>>>>> this builds with maven?
> >>>>>>>>>>
> >>>>>>>>>> Theoretically, but I have not tried. Please let me know.
> >>>>>>>>>>
> >>>>>>>>>>> Can I check it out, build and test Jewel now? So I can report
> >> what
> >>>> I
> >>>>>>>>> see?
> >>>>>>>>>>
> >>>>>>>>>> Yes. Please.
> >>>>>>>>>>
> >>>>>>>>>> I’ll check back in tonight.
> >>>>>>>>>>
> >>>>>>>>>> Keeping my fingers crossed!!! ;-)
> >>>>>>>>>>
> >>>>>>>>>> Harbs
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> thanks
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<
> harbs.lists@gmail.com
> >>> )
> >>>>>>>>>> escribió:
> >>>>>>>>>>>
> >>>>>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I’ll try to spend some more time this evening on this.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I still need to:
> >>>>>>>>>>>> * Test the framework against some more of my apps.
> >>>>>>>>>>>> * Make sure the examples work.
> >>>>>>>>>>>> * See if the Jewel examples run.
> >>>>>>>>>>>> * See if Tour de Flex runs.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Anyone who can confirm any of these would be very helpful.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Harbs
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
> >>>>>>> carlosrovira@apache.org>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I'm available for you to help you solve. write me when you
> >> need.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Just a note: for doing this, I'll take the following path:
> I'll
> >>>> try
> >>>>>>>>> to
> >>>>>>>>>>>>> compile and run without make Jewel depend on Basic, since is
> >> the
> >>>>>>>>> actual
> >>>>>>>>>>>>> shape. From there I'll try to link Basic. I think that path
> >> will
> >>>>>>>>>> provide
> >>>>>>>>>>>>> you a more safe point from what you could go to next step.
> Just
> >>>> my
> >>>>>>>>>> advice
> >>>>>>>>>>>>> if you want to take it.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Carlos Rovira
> >>>>>>>>>>> http://about.me/carlosrovira
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Carlos Rovira
> >>>>>>>> http://about.me/carlosrovira
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Carlos Rovira
> >>>>>> http://about.me/carlosrovira
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> Carlos Rovira
> >>>>> http://about.me/carlosrovira
> >>>>
> >>>>
> >>>
> >>> --
> >>>
> >>> Piotr Zarzycki
> >>>
> >>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>> <https://www.patreon.com/piotrzarzycki>*
> >>
> >>
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
I'm glad that you resolved it! :)
pon., 3 wrz 2018 o 20:21 Harbs <ha...@gmail.com> napisał(a):
> Huh. I had an outdated version of asconfigc installed…
>
> > On Sep 3, 2018, at 9:16 PM, Harbs <ha...@gmail.com> wrote:
> >
> > I saw that, but for some reason it did not work for me…
> >
> >> On Sep 3, 2018, at 9:11 PM, Piotr Zarzycki <pi...@gmail.com>
> wrote:
> >>
> >> It's recognized. Today I have fixed Jewel Alert example by that commit
> [1]
> >>
> >> [1]
> >>
> https://github.com/apache/royale-asjs/commit/37d24b86a674c61be9688f09492978c74a243f3b
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pon., 3 wrz 2018 o 20:09 Harbs <ha...@gmail.com> napisał(a):
> >>
> >>> I don’t think theme is recognized by asconfigc and I don’t think
> there’s a
> >>> way to use relative paths or tokens as a compiler option. Am I missing
> >>> something?
> >>>
> >>>> On Sep 3, 2018, at 8:59 PM, Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> >>> wrote:
> >>>>
> >>>> Harbs,
> >>>>
> >>>> I believe JewelExample contains TablePlayGround. If you will be
> playing
> >>>> with that. Can you fix VSCode build as well ? Enough if you add
> missing
> >>>> parts in asconfig.json. Check what jewel theme is being used in
> pom.xml.
> >>>>
> >>>> Thanks,
> >>>> Piotr
> >>>>
> >>>> pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
> >>>>
> >>>>> Hi Carlos,
> >>>>>
> >>>>> Thanks for checking.
> >>>>>
> >>>>> Which Jewel examples should I use to fix this?
> >>>>>
> >>>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hi, congratulations! jewel example is running almost at 70% aprox
> >>>>>>
> >>>>>> Things to fix:
> >>>>>>
> >>>>>> * Table, this will fix DateChooser and this DateField (DateChooser
> >>> uses a
> >>>>>> Table internally)
> >>>>>> The problem here's the changes in DataGroup, we can skip this
> problem
> >>> if
> >>>>> we
> >>>>>> want for now making Jewel DataGroup be equal to old DataGroup
> instead
> >>> of
> >>>>>> extend basic DataGroup,
> >>>>>> If not we need to know about the changes in DataGroup and change
> >>>>>> TBodyContentArea to work with the new changes
> >>>>>>
> >>>>>> * List, adding, removing, and so on are reporting errors, due to the
> >>> same
> >>>>>> problems as before, strangely some things here although give error
> >>> works
> >>>>> :?
> >>>>>>
> >>>>>> * ComboBox is not popup the list when clicked, again is a problem
> with
> >>>>>> DataGroups since the ComboBox uses a ComboBoxList that has
> IContentView
> >>>>>> equal to ComboBoxListDataGroup
> >>>>>>
> >>>>>> @Alex or someone at MXRoyale could let us know about the changes in
> >>>>>> DataGroup so we can adapt the code to new DataGroup??
> >>>>>>
> >>>>>> Piotr, Harbs good work on merging! :D
> >>>>>>
> >>>>>> Thanks!
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
> >>>>> carlosrovira@apache.org>)
> >>>>>> escribió:
> >>>>>>
> >>>>>>> build with maven is ok for me :)
> >>>>>>>
> >>>>>>> I try examples now
> >>>>>>>
> >>>>>>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
> >>>>>>> escribió:
> >>>>>>>
> >>>>>>>> Oops. I broke that.
> >>>>>>>>
> >>>>>>>> Should be fixed now…
> >>>>>>>>
> >>>>>>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <
> carlosrovira@apache.org>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi build with maven fails in MXRoyale:
> >>>>>>>>>
> >>>>>>>>> COMPC
> >>>>>>>>>
> >>>>>>>>> Loading configuration:
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>>>>>>> col: 8 Warning: Definition
> >>>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider could
> not be
> >>>>>>>> found.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>>>>>>
> >>>>>>>>> ^
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>>>>>>> col: 129 Error: interface IItemRendererProvider was not found.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> public class ListBase extends UIComponent implements
> >>>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>>>>>>> ILayoutView,
> >>>>>>>>> IItemRendererProvider
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ^
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> mx.controls.RichTextEditor is defined by multiple files:
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>>>>>>> col: 8 Definition
> >>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider
> >>>>>>>>> could not be found.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>>>>>>
> >>>>>>>>> ^
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>>>>>>> col: 129 interface IItemRendererProvider was not found.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> public class ListBase extends UIComponent implements
> >>>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>>>>>>> ILayoutView,
> >>>>>>>>> IItemRendererProvider
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ^
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> 1.197156816 seconds
> >>>>>>>>>
> >>>>>>>>> [*INFO*]
> >>>>>>>>>
> >>>>>>>>
> >>>>>
> >>>
> *------------------------------------------------------------------------*
> >>>>>>>>>
> >>>>>>>>> [*INFO*] *Reactor Summary:*
> >>>>>>>>>
> >>>>>>>>> [*INFO*]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 3.744 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework ...........................
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.355 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Fonts ....................
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.190 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs .....................
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.762 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 7.075 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.989 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.714 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.485 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 6.852 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 2.051 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.190 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.098 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.023 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.990 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.855 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.763 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.715 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.873 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.052 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.694 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.631 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.352 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 2.553 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.888 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.629 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.095 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.448 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.732 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 0.998 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 7.767 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
> >>>>> *SUCCESS*
> >>>>>>>> [
> >>>>>>>>> 1.008 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
> >>>>> *FAILURE*
> >>>>>>>> [
> >>>>>>>>> 1.396 s]
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
> >>>>> *SKIPPED*
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
> >>>>> *SKIPPED*
> >>>>>>>>>
> >>>>>>>>> [*INFO*] Apache Royale: Framework:
> >>>>>>>>>
> >>>>>>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
> >>>>>>>>> piotrzarzycki21@gmail.com>) escribió:
> >>>>>>>>>
> >>>>>>>>>> Maven build should work - I checked it one hour ago.
> >>>>>>>>>>
> >>>>>>>>>> I will try to get from your plate Tour De Flex.
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <
> >>> carlosrovira@apache.org
> >>>>>>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hi Harbs
> >>>>>>>>>>>>
> >>>>>>>>>>>> just check what I can do:
> >>>>>>>>>>>> The branch you're working is "feature/new_merge" right?
> >>>>>>>>>>>
> >>>>>>>>>>> Yes.
> >>>>>>>>>>>
> >>>>>>>>>>>> this builds with maven?
> >>>>>>>>>>>
> >>>>>>>>>>> Theoretically, but I have not tried. Please let me know.
> >>>>>>>>>>>
> >>>>>>>>>>>> Can I check it out, build and test Jewel now? So I can report
> >>> what
> >>>>> I
> >>>>>>>>>> see?
> >>>>>>>>>>>
> >>>>>>>>>>> Yes. Please.
> >>>>>>>>>>>
> >>>>>>>>>>> I’ll check back in tonight.
> >>>>>>>>>>>
> >>>>>>>>>>> Keeping my fingers crossed!!! ;-)
> >>>>>>>>>>>
> >>>>>>>>>>> Harbs
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> thanks
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<
> harbs.lists@gmail.com
> >>>> )
> >>>>>>>>>>> escribió:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I’ll try to spend some more time this evening on this.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I still need to:
> >>>>>>>>>>>>> * Test the framework against some more of my apps.
> >>>>>>>>>>>>> * Make sure the examples work.
> >>>>>>>>>>>>> * See if the Jewel examples run.
> >>>>>>>>>>>>> * See if Tour de Flex runs.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Anyone who can confirm any of these would be very helpful.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Harbs
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
> >>>>>>>> carlosrovira@apache.org>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'm available for you to help you solve. write me when you
> >>> need.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Just a note: for doing this, I'll take the following path:
> I'll
> >>>>> try
> >>>>>>>>>> to
> >>>>>>>>>>>>>> compile and run without make Jewel depend on Basic, since is
> >>> the
> >>>>>>>>>> actual
> >>>>>>>>>>>>>> shape. From there I'll try to link Basic. I think that path
> >>> will
> >>>>>>>>>>> provide
> >>>>>>>>>>>>>> you a more safe point from what you could go to next step.
> Just
> >>>>> my
> >>>>>>>>>>> advice
> >>>>>>>>>>>>>> if you want to take it.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Carlos Rovira
> >>>>>>>>>>>> http://about.me/carlosrovira
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Carlos Rovira
> >>>>>>>>> http://about.me/carlosrovira
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Carlos Rovira
> >>>>>>> http://about.me/carlosrovira
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Carlos Rovira
> >>>>>> http://about.me/carlosrovira
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>>
> >>>> Piotr Zarzycki
> >>>>
> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>>> <https://www.patreon.com/piotrzarzycki>*
> >>>
> >>>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Huh. I had an outdated version of asconfigc installed…
> On Sep 3, 2018, at 9:16 PM, Harbs <ha...@gmail.com> wrote:
>
> I saw that, but for some reason it did not work for me…
>
>> On Sep 3, 2018, at 9:11 PM, Piotr Zarzycki <pi...@gmail.com> wrote:
>>
>> It's recognized. Today I have fixed Jewel Alert example by that commit [1]
>>
>> [1]
>> https://github.com/apache/royale-asjs/commit/37d24b86a674c61be9688f09492978c74a243f3b
>>
>> Thanks,
>> Piotr
>>
>> pon., 3 wrz 2018 o 20:09 Harbs <ha...@gmail.com> napisał(a):
>>
>>> I don’t think theme is recognized by asconfigc and I don’t think there’s a
>>> way to use relative paths or tokens as a compiler option. Am I missing
>>> something?
>>>
>>>> On Sep 3, 2018, at 8:59 PM, Piotr Zarzycki <pi...@gmail.com>
>>> wrote:
>>>>
>>>> Harbs,
>>>>
>>>> I believe JewelExample contains TablePlayGround. If you will be playing
>>>> with that. Can you fix VSCode build as well ? Enough if you add missing
>>>> parts in asconfig.json. Check what jewel theme is being used in pom.xml.
>>>>
>>>> Thanks,
>>>> Piotr
>>>>
>>>> pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
>>>>
>>>>> Hi Carlos,
>>>>>
>>>>> Thanks for checking.
>>>>>
>>>>> Which Jewel examples should I use to fix this?
>>>>>
>>>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>> Hi, congratulations! jewel example is running almost at 70% aprox
>>>>>>
>>>>>> Things to fix:
>>>>>>
>>>>>> * Table, this will fix DateChooser and this DateField (DateChooser
>>> uses a
>>>>>> Table internally)
>>>>>> The problem here's the changes in DataGroup, we can skip this problem
>>> if
>>>>> we
>>>>>> want for now making Jewel DataGroup be equal to old DataGroup instead
>>> of
>>>>>> extend basic DataGroup,
>>>>>> If not we need to know about the changes in DataGroup and change
>>>>>> TBodyContentArea to work with the new changes
>>>>>>
>>>>>> * List, adding, removing, and so on are reporting errors, due to the
>>> same
>>>>>> problems as before, strangely some things here although give error
>>> works
>>>>> :?
>>>>>>
>>>>>> * ComboBox is not popup the list when clicked, again is a problem with
>>>>>> DataGroups since the ComboBox uses a ComboBoxList that has IContentView
>>>>>> equal to ComboBoxListDataGroup
>>>>>>
>>>>>> @Alex or someone at MXRoyale could let us know about the changes in
>>>>>> DataGroup so we can adapt the code to new DataGroup??
>>>>>>
>>>>>> Piotr, Harbs good work on merging! :D
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
>>>>> carlosrovira@apache.org>)
>>>>>> escribió:
>>>>>>
>>>>>>> build with maven is ok for me :)
>>>>>>>
>>>>>>> I try examples now
>>>>>>>
>>>>>>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
>>>>>>> escribió:
>>>>>>>
>>>>>>>> Oops. I broke that.
>>>>>>>>
>>>>>>>> Should be fixed now…
>>>>>>>>
>>>>>>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi build with maven fails in MXRoyale:
>>>>>>>>>
>>>>>>>>> COMPC
>>>>>>>>>
>>>>>>>>> Loading configuration:
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>>>>>>> col: 8 Warning: Definition
>>>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider could not be
>>>>>>>> found.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>>>>>>
>>>>>>>>> ^
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>>>>>>> col: 129 Error: interface IItemRendererProvider was not found.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> public class ListBase extends UIComponent implements
>>>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>>>>>>> ILayoutView,
>>>>>>>>> IItemRendererProvider
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ^
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> mx.controls.RichTextEditor is defined by multiple files:
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>>>>>>> col: 8 Definition
>>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider
>>>>>>>>> could not be found.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>>>>>>
>>>>>>>>> ^
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>>>>>>> col: 129 interface IItemRendererProvider was not found.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> public class ListBase extends UIComponent implements
>>>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>>>>>>> ILayoutView,
>>>>>>>>> IItemRendererProvider
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ^
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 1.197156816 seconds
>>>>>>>>>
>>>>>>>>> [*INFO*]
>>>>>>>>>
>>>>>>>>
>>>>>
>>> *------------------------------------------------------------------------*
>>>>>>>>>
>>>>>>>>> [*INFO*] *Reactor Summary:*
>>>>>>>>>
>>>>>>>>> [*INFO*]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 3.744 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework ...........................
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.355 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Fonts ....................
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.190 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs .....................
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.762 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 7.075 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.989 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.714 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.485 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 6.852 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 2.051 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.190 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.098 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.023 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.990 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.855 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.763 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.715 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.873 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.052 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.694 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.631 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.352 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 2.553 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.888 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.629 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.095 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.448 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.732 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 0.998 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 7.767 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
>>>>> *SUCCESS*
>>>>>>>> [
>>>>>>>>> 1.008 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
>>>>> *FAILURE*
>>>>>>>> [
>>>>>>>>> 1.396 s]
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
>>>>> *SKIPPED*
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
>>>>> *SKIPPED*
>>>>>>>>>
>>>>>>>>> [*INFO*] Apache Royale: Framework:
>>>>>>>>>
>>>>>>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
>>>>>>>>> piotrzarzycki21@gmail.com>) escribió:
>>>>>>>>>
>>>>>>>>>> Maven build should work - I checked it one hour ago.
>>>>>>>>>>
>>>>>>>>>> I will try to get from your plate Tour De Flex.
>>>>>>>>>>
>>>>>>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <
>>> carlosrovira@apache.org
>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Harbs
>>>>>>>>>>>>
>>>>>>>>>>>> just check what I can do:
>>>>>>>>>>>> The branch you're working is "feature/new_merge" right?
>>>>>>>>>>>
>>>>>>>>>>> Yes.
>>>>>>>>>>>
>>>>>>>>>>>> this builds with maven?
>>>>>>>>>>>
>>>>>>>>>>> Theoretically, but I have not tried. Please let me know.
>>>>>>>>>>>
>>>>>>>>>>>> Can I check it out, build and test Jewel now? So I can report
>>> what
>>>>> I
>>>>>>>>>> see?
>>>>>>>>>>>
>>>>>>>>>>> Yes. Please.
>>>>>>>>>>>
>>>>>>>>>>> I’ll check back in tonight.
>>>>>>>>>>>
>>>>>>>>>>> Keeping my fingers crossed!!! ;-)
>>>>>>>>>>>
>>>>>>>>>>> Harbs
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> thanks
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<harbs.lists@gmail.com
>>>> )
>>>>>>>>>>> escribió:
>>>>>>>>>>>>
>>>>>>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I’ll try to spend some more time this evening on this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I still need to:
>>>>>>>>>>>>> * Test the framework against some more of my apps.
>>>>>>>>>>>>> * Make sure the examples work.
>>>>>>>>>>>>> * See if the Jewel examples run.
>>>>>>>>>>>>> * See if Tour de Flex runs.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anyone who can confirm any of these would be very helpful.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Harbs
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
>>>>>>>> carlosrovira@apache.org>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm available for you to help you solve. write me when you
>>> need.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Just a note: for doing this, I'll take the following path: I'll
>>>>> try
>>>>>>>>>> to
>>>>>>>>>>>>>> compile and run without make Jewel depend on Basic, since is
>>> the
>>>>>>>>>> actual
>>>>>>>>>>>>>> shape. From there I'll try to link Basic. I think that path
>>> will
>>>>>>>>>>> provide
>>>>>>>>>>>>>> you a more safe point from what you could go to next step. Just
>>>>> my
>>>>>>>>>>> advice
>>>>>>>>>>>>>> if you want to take it.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Carlos Rovira
>>>>>>>>>>>> http://about.me/carlosrovira
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Carlos Rovira
>>>>>>>>> http://about.me/carlosrovira
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Carlos Rovira
>>>>>>> http://about.me/carlosrovira
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Carlos Rovira
>>>>>> http://about.me/carlosrovira
>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>> Piotr Zarzycki
>>>>
>>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>>> <https://www.patreon.com/piotrzarzycki>*
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
I saw that, but for some reason it did not work for me…
> On Sep 3, 2018, at 9:11 PM, Piotr Zarzycki <pi...@gmail.com> wrote:
>
> It's recognized. Today I have fixed Jewel Alert example by that commit [1]
>
> [1]
> https://github.com/apache/royale-asjs/commit/37d24b86a674c61be9688f09492978c74a243f3b
>
> Thanks,
> Piotr
>
> pon., 3 wrz 2018 o 20:09 Harbs <ha...@gmail.com> napisał(a):
>
>> I don’t think theme is recognized by asconfigc and I don’t think there’s a
>> way to use relative paths or tokens as a compiler option. Am I missing
>> something?
>>
>>> On Sep 3, 2018, at 8:59 PM, Piotr Zarzycki <pi...@gmail.com>
>> wrote:
>>>
>>> Harbs,
>>>
>>> I believe JewelExample contains TablePlayGround. If you will be playing
>>> with that. Can you fix VSCode build as well ? Enough if you add missing
>>> parts in asconfig.json. Check what jewel theme is being used in pom.xml.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
>>>
>>>> Hi Carlos,
>>>>
>>>> Thanks for checking.
>>>>
>>>> Which Jewel examples should I use to fix this?
>>>>
>>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>>>> wrote:
>>>>>
>>>>> Hi, congratulations! jewel example is running almost at 70% aprox
>>>>>
>>>>> Things to fix:
>>>>>
>>>>> * Table, this will fix DateChooser and this DateField (DateChooser
>> uses a
>>>>> Table internally)
>>>>> The problem here's the changes in DataGroup, we can skip this problem
>> if
>>>> we
>>>>> want for now making Jewel DataGroup be equal to old DataGroup instead
>> of
>>>>> extend basic DataGroup,
>>>>> If not we need to know about the changes in DataGroup and change
>>>>> TBodyContentArea to work with the new changes
>>>>>
>>>>> * List, adding, removing, and so on are reporting errors, due to the
>> same
>>>>> problems as before, strangely some things here although give error
>> works
>>>> :?
>>>>>
>>>>> * ComboBox is not popup the list when clicked, again is a problem with
>>>>> DataGroups since the ComboBox uses a ComboBoxList that has IContentView
>>>>> equal to ComboBoxListDataGroup
>>>>>
>>>>> @Alex or someone at MXRoyale could let us know about the changes in
>>>>> DataGroup so we can adapt the code to new DataGroup??
>>>>>
>>>>> Piotr, Harbs good work on merging! :D
>>>>>
>>>>> Thanks!
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
>>>> carlosrovira@apache.org>)
>>>>> escribió:
>>>>>
>>>>>> build with maven is ok for me :)
>>>>>>
>>>>>> I try examples now
>>>>>>
>>>>>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
>>>>>> escribió:
>>>>>>
>>>>>>> Oops. I broke that.
>>>>>>>
>>>>>>> Should be fixed now…
>>>>>>>
>>>>>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi build with maven fails in MXRoyale:
>>>>>>>>
>>>>>>>> COMPC
>>>>>>>>
>>>>>>>> Loading configuration:
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
>>>>>>>>
>>>>>>>>
>>>>>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>>>>>> col: 8 Warning: Definition
>>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider could not be
>>>>>>> found.
>>>>>>>>
>>>>>>>>
>>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>>>>>
>>>>>>>> ^
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>>>>>> col: 129 Error: interface IItemRendererProvider was not found.
>>>>>>>>
>>>>>>>>
>>>>>>>> public class ListBase extends UIComponent implements
>>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>>>>>> ILayoutView,
>>>>>>>> IItemRendererProvider
>>>>>>>>
>>>>>>>>
>>>>>>>> ^
>>>>>>>>
>>>>>>>>
>>>>>>>> mx.controls.RichTextEditor is defined by multiple files:
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>>>>>> col: 8 Definition
>>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider
>>>>>>>> could not be found.
>>>>>>>>
>>>>>>>>
>>>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>>>>>
>>>>>>>> ^
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>>>>>> col: 129 interface IItemRendererProvider was not found.
>>>>>>>>
>>>>>>>>
>>>>>>>> public class ListBase extends UIComponent implements
>>>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>>>>>> ILayoutView,
>>>>>>>> IItemRendererProvider
>>>>>>>>
>>>>>>>>
>>>>>>>> ^
>>>>>>>>
>>>>>>>>
>>>>>>>> 1.197156816 seconds
>>>>>>>>
>>>>>>>> [*INFO*]
>>>>>>>>
>>>>>>>
>>>>
>> *------------------------------------------------------------------------*
>>>>>>>>
>>>>>>>> [*INFO*] *Reactor Summary:*
>>>>>>>>
>>>>>>>> [*INFO*]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 3.744 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework ...........................
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.355 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Fonts ....................
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.190 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs .....................
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.762 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 7.075 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.989 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.714 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.485 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 6.852 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 2.051 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.190 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.098 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.023 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.990 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.855 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.763 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.715 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.873 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.052 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.694 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.631 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.352 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 2.553 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.888 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.629 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.095 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.448 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.732 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 0.998 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 7.767 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
>>>> *SUCCESS*
>>>>>>> [
>>>>>>>> 1.008 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
>>>> *FAILURE*
>>>>>>> [
>>>>>>>> 1.396 s]
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
>>>> *SKIPPED*
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
>>>> *SKIPPED*
>>>>>>>>
>>>>>>>> [*INFO*] Apache Royale: Framework:
>>>>>>>>
>>>>>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
>>>>>>>> piotrzarzycki21@gmail.com>) escribió:
>>>>>>>>
>>>>>>>>> Maven build should work - I checked it one hour ago.
>>>>>>>>>
>>>>>>>>> I will try to get from your plate Tour De Flex.
>>>>>>>>>
>>>>>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <
>> carlosrovira@apache.org
>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Harbs
>>>>>>>>>>>
>>>>>>>>>>> just check what I can do:
>>>>>>>>>>> The branch you're working is "feature/new_merge" right?
>>>>>>>>>>
>>>>>>>>>> Yes.
>>>>>>>>>>
>>>>>>>>>>> this builds with maven?
>>>>>>>>>>
>>>>>>>>>> Theoretically, but I have not tried. Please let me know.
>>>>>>>>>>
>>>>>>>>>>> Can I check it out, build and test Jewel now? So I can report
>> what
>>>> I
>>>>>>>>> see?
>>>>>>>>>>
>>>>>>>>>> Yes. Please.
>>>>>>>>>>
>>>>>>>>>> I’ll check back in tonight.
>>>>>>>>>>
>>>>>>>>>> Keeping my fingers crossed!!! ;-)
>>>>>>>>>>
>>>>>>>>>> Harbs
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> thanks
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<harbs.lists@gmail.com
>>> )
>>>>>>>>>> escribió:
>>>>>>>>>>>
>>>>>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
>>>>>>>>>>>>
>>>>>>>>>>>> I’ll try to spend some more time this evening on this.
>>>>>>>>>>>>
>>>>>>>>>>>> I still need to:
>>>>>>>>>>>> * Test the framework against some more of my apps.
>>>>>>>>>>>> * Make sure the examples work.
>>>>>>>>>>>> * See if the Jewel examples run.
>>>>>>>>>>>> * See if Tour de Flex runs.
>>>>>>>>>>>>
>>>>>>>>>>>> Anyone who can confirm any of these would be very helpful.
>>>>>>>>>>>>
>>>>>>>>>>>> Harbs
>>>>>>>>>>>>
>>>>>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
>>>>>>> carlosrovira@apache.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm available for you to help you solve. write me when you
>> need.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Just a note: for doing this, I'll take the following path: I'll
>>>> try
>>>>>>>>> to
>>>>>>>>>>>>> compile and run without make Jewel depend on Basic, since is
>> the
>>>>>>>>> actual
>>>>>>>>>>>>> shape. From there I'll try to link Basic. I think that path
>> will
>>>>>>>>>> provide
>>>>>>>>>>>>> you a more safe point from what you could go to next step. Just
>>>> my
>>>>>>>>>> advice
>>>>>>>>>>>>> if you want to take it.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Carlos Rovira
>>>>>>>>>>> http://about.me/carlosrovira
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Carlos Rovira
>>>>>>>> http://about.me/carlosrovira
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Carlos Rovira
>>>>>> http://about.me/carlosrovira
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Carlos Rovira
>>>>> http://about.me/carlosrovira
>>>>
>>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
It's recognized. Today I have fixed Jewel Alert example by that commit [1]
[1]
https://github.com/apache/royale-asjs/commit/37d24b86a674c61be9688f09492978c74a243f3b
Thanks,
Piotr
pon., 3 wrz 2018 o 20:09 Harbs <ha...@gmail.com> napisał(a):
> I don’t think theme is recognized by asconfigc and I don’t think there’s a
> way to use relative paths or tokens as a compiler option. Am I missing
> something?
>
> > On Sep 3, 2018, at 8:59 PM, Piotr Zarzycki <pi...@gmail.com>
> wrote:
> >
> > Harbs,
> >
> > I believe JewelExample contains TablePlayGround. If you will be playing
> > with that. Can you fix VSCode build as well ? Enough if you add missing
> > parts in asconfig.json. Check what jewel theme is being used in pom.xml.
> >
> > Thanks,
> > Piotr
> >
> > pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
> >
> >> Hi Carlos,
> >>
> >> Thanks for checking.
> >>
> >> Which Jewel examples should I use to fix this?
> >>
> >>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
> >> wrote:
> >>>
> >>> Hi, congratulations! jewel example is running almost at 70% aprox
> >>>
> >>> Things to fix:
> >>>
> >>> * Table, this will fix DateChooser and this DateField (DateChooser
> uses a
> >>> Table internally)
> >>> The problem here's the changes in DataGroup, we can skip this problem
> if
> >> we
> >>> want for now making Jewel DataGroup be equal to old DataGroup instead
> of
> >>> extend basic DataGroup,
> >>> If not we need to know about the changes in DataGroup and change
> >>> TBodyContentArea to work with the new changes
> >>>
> >>> * List, adding, removing, and so on are reporting errors, due to the
> same
> >>> problems as before, strangely some things here although give error
> works
> >> :?
> >>>
> >>> * ComboBox is not popup the list when clicked, again is a problem with
> >>> DataGroups since the ComboBox uses a ComboBoxList that has IContentView
> >>> equal to ComboBoxListDataGroup
> >>>
> >>> @Alex or someone at MXRoyale could let us know about the changes in
> >>> DataGroup so we can adapt the code to new DataGroup??
> >>>
> >>> Piotr, Harbs good work on merging! :D
> >>>
> >>> Thanks!
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
> >> carlosrovira@apache.org>)
> >>> escribió:
> >>>
> >>>> build with maven is ok for me :)
> >>>>
> >>>> I try examples now
> >>>>
> >>>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
> >>>> escribió:
> >>>>
> >>>>> Oops. I broke that.
> >>>>>
> >>>>> Should be fixed now…
> >>>>>
> >>>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hi build with maven fails in MXRoyale:
> >>>>>>
> >>>>>> COMPC
> >>>>>>
> >>>>>> Loading configuration:
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
> >>>>>>
> >>>>>>
> >>>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>>>> col: 8 Warning: Definition
> >>>>>> org.apache.royale.core.IContainer.IItemRendererProvider could not be
> >>>>> found.
> >>>>>>
> >>>>>>
> >>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>>>
> >>>>>> ^
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>>>> col: 129 Error: interface IItemRendererProvider was not found.
> >>>>>>
> >>>>>>
> >>>>>> public class ListBase extends UIComponent implements
> >>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>>>> ILayoutView,
> >>>>>> IItemRendererProvider
> >>>>>>
> >>>>>>
> >>>>>> ^
> >>>>>>
> >>>>>>
> >>>>>> mx.controls.RichTextEditor is defined by multiple files:
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>>>> col: 8 Definition
> >>>>> org.apache.royale.core.IContainer.IItemRendererProvider
> >>>>>> could not be found.
> >>>>>>
> >>>>>>
> >>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>>>
> >>>>>> ^
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>>>> col: 129 interface IItemRendererProvider was not found.
> >>>>>>
> >>>>>>
> >>>>>> public class ListBase extends UIComponent implements
> >>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>>>> ILayoutView,
> >>>>>> IItemRendererProvider
> >>>>>>
> >>>>>>
> >>>>>> ^
> >>>>>>
> >>>>>>
> >>>>>> 1.197156816 seconds
> >>>>>>
> >>>>>> [*INFO*]
> >>>>>>
> >>>>>
> >>
> *------------------------------------------------------------------------*
> >>>>>>
> >>>>>> [*INFO*] *Reactor Summary:*
> >>>>>>
> >>>>>> [*INFO*]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
> >> *SUCCESS*
> >>>>> [
> >>>>>> 3.744 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework ...........................
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.355 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Fonts ....................
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.190 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs .....................
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.762 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 7.075 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.989 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.714 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.485 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 6.852 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 2.051 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.190 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.098 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.023 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.990 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.855 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.763 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.715 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.873 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.052 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.694 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.631 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.352 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
> >> *SUCCESS*
> >>>>> [
> >>>>>> 2.553 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.888 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.629 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.095 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.448 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.732 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
> >> *SUCCESS*
> >>>>> [
> >>>>>> 0.998 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
> >> *SUCCESS*
> >>>>> [
> >>>>>> 7.767 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
> >> *SUCCESS*
> >>>>> [
> >>>>>> 1.008 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
> >> *FAILURE*
> >>>>> [
> >>>>>> 1.396 s]
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
> >> *SKIPPED*
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
> >> *SKIPPED*
> >>>>>>
> >>>>>> [*INFO*] Apache Royale: Framework:
> >>>>>>
> >>>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
> >>>>>> piotrzarzycki21@gmail.com>) escribió:
> >>>>>>
> >>>>>>> Maven build should work - I checked it one hour ago.
> >>>>>>>
> >>>>>>> I will try to get from your plate Tour De Flex.
> >>>>>>>
> >>>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
> >>>>>>>
> >>>>>>>>
> >>>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <
> carlosrovira@apache.org
> >>>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi Harbs
> >>>>>>>>>
> >>>>>>>>> just check what I can do:
> >>>>>>>>> The branch you're working is "feature/new_merge" right?
> >>>>>>>>
> >>>>>>>> Yes.
> >>>>>>>>
> >>>>>>>>> this builds with maven?
> >>>>>>>>
> >>>>>>>> Theoretically, but I have not tried. Please let me know.
> >>>>>>>>
> >>>>>>>>> Can I check it out, build and test Jewel now? So I can report
> what
> >> I
> >>>>>>> see?
> >>>>>>>>
> >>>>>>>> Yes. Please.
> >>>>>>>>
> >>>>>>>> I’ll check back in tonight.
> >>>>>>>>
> >>>>>>>> Keeping my fingers crossed!!! ;-)
> >>>>>>>>
> >>>>>>>> Harbs
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> thanks
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<harbs.lists@gmail.com
> >)
> >>>>>>>> escribió:
> >>>>>>>>>
> >>>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
> >>>>>>>>>>
> >>>>>>>>>> I’ll try to spend some more time this evening on this.
> >>>>>>>>>>
> >>>>>>>>>> I still need to:
> >>>>>>>>>> * Test the framework against some more of my apps.
> >>>>>>>>>> * Make sure the examples work.
> >>>>>>>>>> * See if the Jewel examples run.
> >>>>>>>>>> * See if Tour de Flex runs.
> >>>>>>>>>>
> >>>>>>>>>> Anyone who can confirm any of these would be very helpful.
> >>>>>>>>>>
> >>>>>>>>>> Harbs
> >>>>>>>>>>
> >>>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
> >>>>> carlosrovira@apache.org>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I'm available for you to help you solve. write me when you
> need.
> >>>>>>>>>>>
> >>>>>>>>>>> Just a note: for doing this, I'll take the following path: I'll
> >> try
> >>>>>>> to
> >>>>>>>>>>> compile and run without make Jewel depend on Basic, since is
> the
> >>>>>>> actual
> >>>>>>>>>>> shape. From there I'll try to link Basic. I think that path
> will
> >>>>>>>> provide
> >>>>>>>>>>> you a more safe point from what you could go to next step. Just
> >> my
> >>>>>>>> advice
> >>>>>>>>>>> if you want to take it.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Carlos Rovira
> >>>>>>>>> http://about.me/carlosrovira
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Carlos Rovira
> >>>>>> http://about.me/carlosrovira
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> http://about.me/carlosrovira
> >>>>
> >>>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
I don’t think theme is recognized by asconfigc and I don’t think there’s a way to use relative paths or tokens as a compiler option. Am I missing something?
> On Sep 3, 2018, at 8:59 PM, Piotr Zarzycki <pi...@gmail.com> wrote:
>
> Harbs,
>
> I believe JewelExample contains TablePlayGround. If you will be playing
> with that. Can you fix VSCode build as well ? Enough if you add missing
> parts in asconfig.json. Check what jewel theme is being used in pom.xml.
>
> Thanks,
> Piotr
>
> pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
>
>> Hi Carlos,
>>
>> Thanks for checking.
>>
>> Which Jewel examples should I use to fix this?
>>
>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>
>>> Hi, congratulations! jewel example is running almost at 70% aprox
>>>
>>> Things to fix:
>>>
>>> * Table, this will fix DateChooser and this DateField (DateChooser uses a
>>> Table internally)
>>> The problem here's the changes in DataGroup, we can skip this problem if
>> we
>>> want for now making Jewel DataGroup be equal to old DataGroup instead of
>>> extend basic DataGroup,
>>> If not we need to know about the changes in DataGroup and change
>>> TBodyContentArea to work with the new changes
>>>
>>> * List, adding, removing, and so on are reporting errors, due to the same
>>> problems as before, strangely some things here although give error works
>> :?
>>>
>>> * ComboBox is not popup the list when clicked, again is a problem with
>>> DataGroups since the ComboBox uses a ComboBoxList that has IContentView
>>> equal to ComboBoxListDataGroup
>>>
>>> @Alex or someone at MXRoyale could let us know about the changes in
>>> DataGroup so we can adapt the code to new DataGroup??
>>>
>>> Piotr, Harbs good work on merging! :D
>>>
>>> Thanks!
>>>
>>>
>>>
>>>
>>>
>>> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
>> carlosrovira@apache.org>)
>>> escribió:
>>>
>>>> build with maven is ok for me :)
>>>>
>>>> I try examples now
>>>>
>>>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
>>>> escribió:
>>>>
>>>>> Oops. I broke that.
>>>>>
>>>>> Should be fixed now…
>>>>>
>>>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>> Hi build with maven fails in MXRoyale:
>>>>>>
>>>>>> COMPC
>>>>>>
>>>>>> Loading configuration:
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
>>>>>>
>>>>>>
>>>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>>>> col: 8 Warning: Definition
>>>>>> org.apache.royale.core.IContainer.IItemRendererProvider could not be
>>>>> found.
>>>>>>
>>>>>>
>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>>>
>>>>>> ^
>>>>>>
>>>>>>
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>>>> col: 129 Error: interface IItemRendererProvider was not found.
>>>>>>
>>>>>>
>>>>>> public class ListBase extends UIComponent implements
>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>>>> ILayoutView,
>>>>>> IItemRendererProvider
>>>>>>
>>>>>>
>>>>>> ^
>>>>>>
>>>>>>
>>>>>> mx.controls.RichTextEditor is defined by multiple files:
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>>>> col: 8 Definition
>>>>> org.apache.royale.core.IContainer.IItemRendererProvider
>>>>>> could not be found.
>>>>>>
>>>>>>
>>>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>>>
>>>>>> ^
>>>>>>
>>>>>>
>>>>>>
>>>>>
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>>>> col: 129 interface IItemRendererProvider was not found.
>>>>>>
>>>>>>
>>>>>> public class ListBase extends UIComponent implements
>>>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>>>> ILayoutView,
>>>>>> IItemRendererProvider
>>>>>>
>>>>>>
>>>>>> ^
>>>>>>
>>>>>>
>>>>>> 1.197156816 seconds
>>>>>>
>>>>>> [*INFO*]
>>>>>>
>>>>>
>> *------------------------------------------------------------------------*
>>>>>>
>>>>>> [*INFO*] *Reactor Summary:*
>>>>>>
>>>>>> [*INFO*]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
>> *SUCCESS*
>>>>> [
>>>>>> 3.744 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework ...........................
>> *SUCCESS*
>>>>> [
>>>>>> 0.355 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Fonts ....................
>> *SUCCESS*
>>>>> [
>>>>>> 1.190 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs .....................
>> *SUCCESS*
>>>>> [
>>>>>> 0.762 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
>> *SUCCESS*
>>>>> [
>>>>>> 7.075 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
>> *SUCCESS*
>>>>> [
>>>>>> 0.989 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
>> *SUCCESS*
>>>>> [
>>>>>> 0.714 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
>> *SUCCESS*
>>>>> [
>>>>>> 1.485 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
>> *SUCCESS*
>>>>> [
>>>>>> 6.852 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
>> *SUCCESS*
>>>>> [
>>>>>> 2.051 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
>> *SUCCESS*
>>>>> [
>>>>>> 1.190 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
>> *SUCCESS*
>>>>> [
>>>>>> 1.098 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
>> *SUCCESS*
>>>>> [
>>>>>> 1.023 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
>> *SUCCESS*
>>>>> [
>>>>>> 0.990 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
>> *SUCCESS*
>>>>> [
>>>>>> 0.855 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
>> *SUCCESS*
>>>>> [
>>>>>> 0.763 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
>> *SUCCESS*
>>>>> [
>>>>>> 0.715 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
>> *SUCCESS*
>>>>> [
>>>>>> 0.873 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
>> *SUCCESS*
>>>>> [
>>>>>> 1.052 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
>> *SUCCESS*
>>>>> [
>>>>>> 0.694 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
>> *SUCCESS*
>>>>> [
>>>>>> 0.631 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
>> *SUCCESS*
>>>>> [
>>>>>> 0.352 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
>> *SUCCESS*
>>>>> [
>>>>>> 2.553 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
>> *SUCCESS*
>>>>> [
>>>>>> 0.888 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
>> *SUCCESS*
>>>>> [
>>>>>> 0.629 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
>> *SUCCESS*
>>>>> [
>>>>>> 1.095 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
>> *SUCCESS*
>>>>> [
>>>>>> 0.448 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
>> *SUCCESS*
>>>>> [
>>>>>> 0.732 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
>> *SUCCESS*
>>>>> [
>>>>>> 0.998 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
>> *SUCCESS*
>>>>> [
>>>>>> 7.767 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
>> *SUCCESS*
>>>>> [
>>>>>> 1.008 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
>> *FAILURE*
>>>>> [
>>>>>> 1.396 s]
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
>> *SKIPPED*
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
>> *SKIPPED*
>>>>>>
>>>>>> [*INFO*] Apache Royale: Framework:
>>>>>>
>>>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
>>>>>> piotrzarzycki21@gmail.com>) escribió:
>>>>>>
>>>>>>> Maven build should work - I checked it one hour ago.
>>>>>>>
>>>>>>> I will try to get from your plate Tour De Flex.
>>>>>>>
>>>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <carlosrovira@apache.org
>>>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi Harbs
>>>>>>>>>
>>>>>>>>> just check what I can do:
>>>>>>>>> The branch you're working is "feature/new_merge" right?
>>>>>>>>
>>>>>>>> Yes.
>>>>>>>>
>>>>>>>>> this builds with maven?
>>>>>>>>
>>>>>>>> Theoretically, but I have not tried. Please let me know.
>>>>>>>>
>>>>>>>>> Can I check it out, build and test Jewel now? So I can report what
>> I
>>>>>>> see?
>>>>>>>>
>>>>>>>> Yes. Please.
>>>>>>>>
>>>>>>>> I’ll check back in tonight.
>>>>>>>>
>>>>>>>> Keeping my fingers crossed!!! ;-)
>>>>>>>>
>>>>>>>> Harbs
>>>>>>>>
>>>>>>>>>
>>>>>>>>> thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
>>>>>>>> escribió:
>>>>>>>>>
>>>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
>>>>>>>>>>
>>>>>>>>>> I’ll try to spend some more time this evening on this.
>>>>>>>>>>
>>>>>>>>>> I still need to:
>>>>>>>>>> * Test the framework against some more of my apps.
>>>>>>>>>> * Make sure the examples work.
>>>>>>>>>> * See if the Jewel examples run.
>>>>>>>>>> * See if Tour de Flex runs.
>>>>>>>>>>
>>>>>>>>>> Anyone who can confirm any of these would be very helpful.
>>>>>>>>>>
>>>>>>>>>> Harbs
>>>>>>>>>>
>>>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
>>>>> carlosrovira@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I'm available for you to help you solve. write me when you need.
>>>>>>>>>>>
>>>>>>>>>>> Just a note: for doing this, I'll take the following path: I'll
>> try
>>>>>>> to
>>>>>>>>>>> compile and run without make Jewel depend on Basic, since is the
>>>>>>> actual
>>>>>>>>>>> shape. From there I'll try to link Basic. I think that path will
>>>>>>>> provide
>>>>>>>>>>> you a more safe point from what you could go to next step. Just
>> my
>>>>>>>> advice
>>>>>>>>>>> if you want to take it.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Carlos Rovira
>>>>>>>>> http://about.me/carlosrovira
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Carlos Rovira
>>>>>> http://about.me/carlosrovira
>>>>>
>>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>>
>>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Harbs,
I believe JewelExample contains TablePlayGround. If you will be playing
with that. Can you fix VSCode build as well ? Enough if you add missing
parts in asconfig.json. Check what jewel theme is being used in pom.xml.
Thanks,
Piotr
pon., 3 wrz 2018 o 19:54 Harbs <ha...@gmail.com> napisał(a):
> Hi Carlos,
>
> Thanks for checking.
>
> Which Jewel examples should I use to fix this?
>
> > On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi, congratulations! jewel example is running almost at 70% aprox
> >
> > Things to fix:
> >
> > * Table, this will fix DateChooser and this DateField (DateChooser uses a
> > Table internally)
> > The problem here's the changes in DataGroup, we can skip this problem if
> we
> > want for now making Jewel DataGroup be equal to old DataGroup instead of
> > extend basic DataGroup,
> > If not we need to know about the changes in DataGroup and change
> > TBodyContentArea to work with the new changes
> >
> > * List, adding, removing, and so on are reporting errors, due to the same
> > problems as before, strangely some things here although give error works
> :?
> >
> > * ComboBox is not popup the list when clicked, again is a problem with
> > DataGroups since the ComboBox uses a ComboBoxList that has IContentView
> > equal to ComboBoxListDataGroup
> >
> > @Alex or someone at MXRoyale could let us know about the changes in
> > DataGroup so we can adapt the code to new DataGroup??
> >
> > Piotr, Harbs good work on merging! :D
> >
> > Thanks!
> >
> >
> >
> >
> >
> > El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<
> carlosrovira@apache.org>)
> > escribió:
> >
> >> build with maven is ok for me :)
> >>
> >> I try examples now
> >>
> >> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
> >> escribió:
> >>
> >>> Oops. I broke that.
> >>>
> >>> Should be fixed now…
> >>>
> >>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
> >>> wrote:
> >>>>
> >>>> Hi build with maven fails in MXRoyale:
> >>>>
> >>>> COMPC
> >>>>
> >>>> Loading configuration:
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
> >>>>
> >>>>
> >>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>> col: 8 Warning: Definition
> >>>> org.apache.royale.core.IContainer.IItemRendererProvider could not be
> >>> found.
> >>>>
> >>>>
> >>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>
> >>>> ^
> >>>>
> >>>>
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>> col: 129 Error: interface IItemRendererProvider was not found.
> >>>>
> >>>>
> >>>> public class ListBase extends UIComponent implements
> >>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>> ILayoutView,
> >>>> IItemRendererProvider
> >>>>
> >>>>
> >>>> ^
> >>>>
> >>>>
> >>>> mx.controls.RichTextEditor is defined by multiple files:
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> >>>> col: 8 Definition
> >>> org.apache.royale.core.IContainer.IItemRendererProvider
> >>>> could not be found.
> >>>>
> >>>>
> >>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
> >>>>
> >>>> ^
> >>>>
> >>>>
> >>>>
> >>>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> >>>> col: 129 interface IItemRendererProvider was not found.
> >>>>
> >>>>
> >>>> public class ListBase extends UIComponent implements
> >>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
> >>> ILayoutView,
> >>>> IItemRendererProvider
> >>>>
> >>>>
> >>>> ^
> >>>>
> >>>>
> >>>> 1.197156816 seconds
> >>>>
> >>>> [*INFO*]
> >>>>
> >>>
> *------------------------------------------------------------------------*
> >>>>
> >>>> [*INFO*] *Reactor Summary:*
> >>>>
> >>>> [*INFO*]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT ....
> *SUCCESS*
> >>> [
> >>>> 3.744 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework ...........................
> *SUCCESS*
> >>> [
> >>>> 0.355 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Fonts ....................
> *SUCCESS*
> >>> [
> >>>> 1.190 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs .....................
> *SUCCESS*
> >>> [
> >>>> 0.762 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Core ...............
> *SUCCESS*
> >>> [
> >>>> 7.075 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............
> *SUCCESS*
> >>> [
> >>>> 0.989 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........
> *SUCCESS*
> >>> [
> >>>> 0.714 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ...........
> *SUCCESS*
> >>> [
> >>>> 1.485 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Basic ..............
> *SUCCESS*
> >>> [
> >>>> 6.852 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Charts .............
> *SUCCESS*
> >>> [
> >>>> 2.051 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............
> *SUCCESS*
> >>> [
> >>>> 1.190 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ...........
> *SUCCESS*
> >>> [
> >>>> 1.098 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ...........
> *SUCCESS*
> >>> [
> >>>> 1.023 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Express ............
> *SUCCESS*
> >>> [
> >>>> 0.990 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Flat ...............
> *SUCCESS*
> >>> [
> >>>> 0.855 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Formatters .........
> *SUCCESS*
> >>> [
> >>>> 0.763 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........
> *SUCCESS*
> >>> [
> >>>> 0.715 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps .........
> *SUCCESS*
> >>> [
> >>>> 0.873 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: HTML ...............
> *SUCCESS*
> >>> [
> >>>> 1.052 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 ..............
> *SUCCESS*
> >>> [
> >>>> 0.694 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: JQuery .............
> *SUCCESS*
> >>> [
> >>>> 0.631 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Language ...........
> *SUCCESS*
> >>> [
> >>>> 0.352 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite
> *SUCCESS*
> >>> [
> >>>> 2.553 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Mobile .............
> *SUCCESS*
> >>> [
> >>>> 0.888 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Reflection .........
> *SUCCESS*
> >>> [
> >>>> 0.629 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Network ............
> *SUCCESS*
> >>> [
> >>>> 1.095 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............
> *SUCCESS*
> >>> [
> >>>> 0.448 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: XML ................
> *SUCCESS*
> >>> [
> >>>> 0.732 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Text ...............
> *SUCCESS*
> >>> [
> >>>> 0.998 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................
> *SUCCESS*
> >>> [
> >>>> 7.767 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite .........
> *SUCCESS*
> >>> [
> >>>> 1.008 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ...........
> *FAILURE*
> >>> [
> >>>> 1.396 s]
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: Icons ..............
> *SKIPPED*
> >>>>
> >>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........
> *SKIPPED*
> >>>>
> >>>> [*INFO*] Apache Royale: Framework:
> >>>>
> >>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
> >>>> piotrzarzycki21@gmail.com>) escribió:
> >>>>
> >>>>> Maven build should work - I checked it one hour ago.
> >>>>>
> >>>>> I will try to get from your plate Tour De Flex.
> >>>>>
> >>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
> >>>>>
> >>>>>>
> >>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <carlosrovira@apache.org
> >
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi Harbs
> >>>>>>>
> >>>>>>> just check what I can do:
> >>>>>>> The branch you're working is "feature/new_merge" right?
> >>>>>>
> >>>>>> Yes.
> >>>>>>
> >>>>>>> this builds with maven?
> >>>>>>
> >>>>>> Theoretically, but I have not tried. Please let me know.
> >>>>>>
> >>>>>>> Can I check it out, build and test Jewel now? So I can report what
> I
> >>>>> see?
> >>>>>>
> >>>>>> Yes. Please.
> >>>>>>
> >>>>>> I’ll check back in tonight.
> >>>>>>
> >>>>>> Keeping my fingers crossed!!! ;-)
> >>>>>>
> >>>>>> Harbs
> >>>>>>
> >>>>>>>
> >>>>>>> thanks
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
> >>>>>> escribió:
> >>>>>>>
> >>>>>>>> I’m done for the morning and I’ll be out this afternoon.
> >>>>>>>>
> >>>>>>>> I’ll try to spend some more time this evening on this.
> >>>>>>>>
> >>>>>>>> I still need to:
> >>>>>>>> * Test the framework against some more of my apps.
> >>>>>>>> * Make sure the examples work.
> >>>>>>>> * See if the Jewel examples run.
> >>>>>>>> * See if Tour de Flex runs.
> >>>>>>>>
> >>>>>>>> Anyone who can confirm any of these would be very helpful.
> >>>>>>>>
> >>>>>>>> Harbs
> >>>>>>>>
> >>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
> >>> carlosrovira@apache.org>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> I'm available for you to help you solve. write me when you need.
> >>>>>>>>>
> >>>>>>>>> Just a note: for doing this, I'll take the following path: I'll
> try
> >>>>> to
> >>>>>>>>> compile and run without make Jewel depend on Basic, since is the
> >>>>> actual
> >>>>>>>>> shape. From there I'll try to link Basic. I think that path will
> >>>>>> provide
> >>>>>>>>> you a more safe point from what you could go to next step. Just
> my
> >>>>>> advice
> >>>>>>>>> if you want to take it.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Carlos Rovira
> >>>>>>> http://about.me/carlosrovira
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> http://about.me/carlosrovira
> >>>
> >>>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Hi Carlos,
Thanks for checking.
Which Jewel examples should I use to fix this?
> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi, congratulations! jewel example is running almost at 70% aprox
>
> Things to fix:
>
> * Table, this will fix DateChooser and this DateField (DateChooser uses a
> Table internally)
> The problem here's the changes in DataGroup, we can skip this problem if we
> want for now making Jewel DataGroup be equal to old DataGroup instead of
> extend basic DataGroup,
> If not we need to know about the changes in DataGroup and change
> TBodyContentArea to work with the new changes
>
> * List, adding, removing, and so on are reporting errors, due to the same
> problems as before, strangely some things here although give error works :?
>
> * ComboBox is not popup the list when clicked, again is a problem with
> DataGroups since the ComboBox uses a ComboBoxList that has IContentView
> equal to ComboBoxListDataGroup
>
> @Alex or someone at MXRoyale could let us know about the changes in
> DataGroup so we can adapt the code to new DataGroup??
>
> Piotr, Harbs good work on merging! :D
>
> Thanks!
>
>
>
>
>
> El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> build with maven is ok for me :)
>>
>> I try examples now
>>
>> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
>> escribió:
>>
>>> Oops. I broke that.
>>>
>>> Should be fixed now…
>>>
>>>> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>>
>>>> Hi build with maven fails in MXRoyale:
>>>>
>>>> COMPC
>>>>
>>>> Loading configuration:
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
>>>>
>>>>
>>>> Warning: mx.controls.RichTextEditor is defined by multiple files:
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>
>>>>
>>>>
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>> col: 8 Warning: Definition
>>>> org.apache.royale.core.IContainer.IItemRendererProvider could not be
>>> found.
>>>>
>>>>
>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>
>>>> ^
>>>>
>>>>
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>> col: 129 Error: interface IItemRendererProvider was not found.
>>>>
>>>>
>>>> public class ListBase extends UIComponent implements
>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>> ILayoutView,
>>>> IItemRendererProvider
>>>>
>>>>
>>>> ^
>>>>
>>>>
>>>> mx.controls.RichTextEditor is defined by multiple files:
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>>>>
>>>>
>>>>
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>>>> col: 8 Definition
>>> org.apache.royale.core.IContainer.IItemRendererProvider
>>>> could not be found.
>>>>
>>>>
>>>> import org.apache.royale.core.IContainer.IItemRendererProvider;
>>>>
>>>> ^
>>>>
>>>>
>>>>
>>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>>>> col: 129 interface IItemRendererProvider was not found.
>>>>
>>>>
>>>> public class ListBase extends UIComponent implements
>>>> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>>> ILayoutView,
>>>> IItemRendererProvider
>>>>
>>>>
>>>> ^
>>>>
>>>>
>>>> 1.197156816 seconds
>>>>
>>>> [*INFO*]
>>>>
>>> *------------------------------------------------------------------------*
>>>>
>>>> [*INFO*] *Reactor Summary:*
>>>>
>>>> [*INFO*]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT .... *SUCCESS*
>>> [
>>>> 3.744 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework ........................... *SUCCESS*
>>> [
>>>> 0.355 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Fonts .................... *SUCCESS*
>>> [
>>>> 1.190 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs ..................... *SUCCESS*
>>> [
>>>> 0.762 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Core ............... *SUCCESS*
>>> [
>>>> 7.075 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Binding ............ *SUCCESS*
>>> [
>>>> 0.989 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Collections ........ *SUCCESS*
>>> [
>>>> 0.714 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Graphics ........... *SUCCESS*
>>> [
>>>> 1.485 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Basic .............. *SUCCESS*
>>> [
>>>> 6.852 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Charts ............. *SUCCESS*
>>> [
>>>> 2.051 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Effects ............ *SUCCESS*
>>> [
>>>> 1.190 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: CreateJS ........... *SUCCESS*
>>> [
>>>> 1.098 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: DragDrop ........... *SUCCESS*
>>> [
>>>> 1.023 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Express ............ *SUCCESS*
>>> [
>>>> 0.990 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Flat ............... *SUCCESS*
>>> [
>>>> 0.855 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Formatters ......... *SUCCESS*
>>> [
>>>> 0.763 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........ *SUCCESS*
>>> [
>>>> 0.715 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps ......... *SUCCESS*
>>> [
>>>> 0.873 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: HTML ............... *SUCCESS*
>>> [
>>>> 1.052 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: HTML5 .............. *SUCCESS*
>>> [
>>>> 0.694 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: JQuery ............. *SUCCESS*
>>> [
>>>> 0.631 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Language ........... *SUCCESS*
>>> [
>>>> 0.352 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite *SUCCESS*
>>> [
>>>> 2.553 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Mobile ............. *SUCCESS*
>>> [
>>>> 0.888 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Reflection ......... *SUCCESS*
>>> [
>>>> 0.629 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Network ............ *SUCCESS*
>>> [
>>>> 1.095 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Storage ............ *SUCCESS*
>>> [
>>>> 0.448 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: XML ................ *SUCCESS*
>>> [
>>>> 0.732 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Text ............... *SUCCESS*
>>> [
>>>> 0.998 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: TLF ................ *SUCCESS*
>>> [
>>>> 7.767 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite ......... *SUCCESS*
>>> [
>>>> 1.008 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ........... *FAILURE*
>>> [
>>>> 1.396 s]
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: Icons .............. *SKIPPED*
>>>>
>>>> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........ *SKIPPED*
>>>>
>>>> [*INFO*] Apache Royale: Framework:
>>>>
>>>> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
>>>> piotrzarzycki21@gmail.com>) escribió:
>>>>
>>>>> Maven build should work - I checked it one hour ago.
>>>>>
>>>>> I will try to get from your plate Tour De Flex.
>>>>>
>>>>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Harbs
>>>>>>>
>>>>>>> just check what I can do:
>>>>>>> The branch you're working is "feature/new_merge" right?
>>>>>>
>>>>>> Yes.
>>>>>>
>>>>>>> this builds with maven?
>>>>>>
>>>>>> Theoretically, but I have not tried. Please let me know.
>>>>>>
>>>>>>> Can I check it out, build and test Jewel now? So I can report what I
>>>>> see?
>>>>>>
>>>>>> Yes. Please.
>>>>>>
>>>>>> I’ll check back in tonight.
>>>>>>
>>>>>> Keeping my fingers crossed!!! ;-)
>>>>>>
>>>>>> Harbs
>>>>>>
>>>>>>>
>>>>>>> thanks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
>>>>>> escribió:
>>>>>>>
>>>>>>>> I’m done for the morning and I’ll be out this afternoon.
>>>>>>>>
>>>>>>>> I’ll try to spend some more time this evening on this.
>>>>>>>>
>>>>>>>> I still need to:
>>>>>>>> * Test the framework against some more of my apps.
>>>>>>>> * Make sure the examples work.
>>>>>>>> * See if the Jewel examples run.
>>>>>>>> * See if Tour de Flex runs.
>>>>>>>>
>>>>>>>> Anyone who can confirm any of these would be very helpful.
>>>>>>>>
>>>>>>>> Harbs
>>>>>>>>
>>>>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
>>> carlosrovira@apache.org>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I'm available for you to help you solve. write me when you need.
>>>>>>>>>
>>>>>>>>> Just a note: for doing this, I'll take the following path: I'll try
>>>>> to
>>>>>>>>> compile and run without make Jewel depend on Basic, since is the
>>>>> actual
>>>>>>>>> shape. From there I'll try to link Basic. I think that path will
>>>>>> provide
>>>>>>>>> you a more safe point from what you could go to next step. Just my
>>>>>> advice
>>>>>>>>> if you want to take it.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Carlos Rovira
>>>>>>> http://about.me/carlosrovira
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Those probably need to be changed the itemRenderer equivalents (numItemRenderers, etc.)
> On Sep 5, 2018, at 2:28 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi Harbs,
>
> I'm seeing few problems in JewelExample, that pass unnoticed for me
> yesterday. Maybe I was testing release and not debug...don't know:
>
> In List playground:
> * Adding an item works but give this error
> TypeError: null is not an object (evaluating 'dataGroup.numElements')
> * Removing a item is not working, error is:
> TypeError: null is not an object (evaluating 'parent.getElementAt')
> * Update item works right
> * Remove all works right
>
> Table playground:
>
> * Add item, works but:
> TypeError: null is not an object (evaluating
> 'processedRow.numElements')
> * Remove item doesn't work and:
> TypeError: null is not an object (evaluating
> 'processedRow.numElements')
> * Update item doesn't work and doesn't report error
> * Remove all works right
>
> Sorry to not catch this before
>
> can you take a look?
>
> thanks
>
> Carlos
>
>
>
> El mar., 4 sept. 2018 a las 13:41, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> I already did in that commit, we have both now
>>
>> El mar., 4 sept. 2018 a las 13:31, Harbs (<ha...@gmail.com>)
>> escribió:
>>
>>> Great. I’ll add the asconfigc tasks to that later.
>>>
>>>> On Sep 4, 2018, at 2:10 PM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>>
>>>> I found it how to do it
>>>> New VSCode forma 2.0.0 solves this and more :))
>>>>
>>>> one thing it you can configure a task to be default, but I didn't commit
>>>> anyone as default since the others will be less quick to execute
>>>>
>>>> El mar., 4 sept. 2018 a las 12:55, Harbs (<ha...@gmail.com>)
>>> escribió:
>>>>
>>>>> Awesome. :-)
>>>>>
>>>>>> On Sep 4, 2018, at 1:42 PM, Carlos Rovira <ca...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I revert my revert ;), so I can find a non intrusive way. I'm sure
>>> VSCode
>>>>>> should have a way to configure a task but make it not default or block
>>>>> AS3
>>>>>> extension
>>>>>> when I get it I'll commit the solution
>>>>>>
>>>>>> El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>)
>>>>> escribió:
>>>>>>
>>>>>>> I had some errors on missing resources.
>>>>>>>
>>>>>>> I’ve never managed to get maven to work for me. Dunno why.
>>>>>>>
>>>>>>> The tasks.json file overrides the defaults, so the build task uses
>>> maven
>>>>>>> instead of asconfigc.
>>>>>>>
>>>>>>> We should either modify the tasks.json file to allow for multiple
>>> build
>>>>>>> tasks, or include it in gitignore.
>>>>>>>
>>>>>>> Here’s info on defining arbitrary tasks:
>>>>>>>
>>>>>>>
>>>>>
>>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>>>>>>> <
>>>>>>>
>>>>>
>>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <carlosrovira@apache.org
>>>>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I revert latest commit since launch.json works ok with maven, what
>>>>>>> problem
>>>>>>>> did you find? Is what I use in day-by-day to work with VSCode
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Carlos Rovira
>>>>>> http://about.me/carlosrovira
>>>>>
>>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs,
I'm seeing few problems in JewelExample, that pass unnoticed for me
yesterday. Maybe I was testing release and not debug...don't know:
In List playground:
* Adding an item works but give this error
TypeError: null is not an object (evaluating 'dataGroup.numElements')
* Removing a item is not working, error is:
TypeError: null is not an object (evaluating 'parent.getElementAt')
* Update item works right
* Remove all works right
Table playground:
* Add item, works but:
TypeError: null is not an object (evaluating
'processedRow.numElements')
* Remove item doesn't work and:
TypeError: null is not an object (evaluating
'processedRow.numElements')
* Update item doesn't work and doesn't report error
* Remove all works right
Sorry to not catch this before
can you take a look?
thanks
Carlos
El mar., 4 sept. 2018 a las 13:41, Carlos Rovira (<ca...@apache.org>)
escribió:
> I already did in that commit, we have both now
>
> El mar., 4 sept. 2018 a las 13:31, Harbs (<ha...@gmail.com>)
> escribió:
>
>> Great. I’ll add the asconfigc tasks to that later.
>>
>> > On Sep 4, 2018, at 2:10 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>> >
>> > I found it how to do it
>> > New VSCode forma 2.0.0 solves this and more :))
>> >
>> > one thing it you can configure a task to be default, but I didn't commit
>> > anyone as default since the others will be less quick to execute
>> >
>> > El mar., 4 sept. 2018 a las 12:55, Harbs (<ha...@gmail.com>)
>> escribió:
>> >
>> >> Awesome. :-)
>> >>
>> >>> On Sep 4, 2018, at 1:42 PM, Carlos Rovira <ca...@apache.org>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I revert my revert ;), so I can find a non intrusive way. I'm sure
>> VSCode
>> >>> should have a way to configure a task but make it not default or block
>> >> AS3
>> >>> extension
>> >>> when I get it I'll commit the solution
>> >>>
>> >>> El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>)
>> >> escribió:
>> >>>
>> >>>> I had some errors on missing resources.
>> >>>>
>> >>>> I’ve never managed to get maven to work for me. Dunno why.
>> >>>>
>> >>>> The tasks.json file overrides the defaults, so the build task uses
>> maven
>> >>>> instead of asconfigc.
>> >>>>
>> >>>> We should either modify the tasks.json file to allow for multiple
>> build
>> >>>> tasks, or include it in gitignore.
>> >>>>
>> >>>> Here’s info on defining arbitrary tasks:
>> >>>>
>> >>>>
>> >>
>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>> >>>> <
>> >>>>
>> >>
>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>> >>>>>
>> >>>>
>> >>>>
>> >>>>> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <carlosrovira@apache.org
>> >
>> >>>> wrote:
>> >>>>>
>> >>>>> I revert latest commit since launch.json works ok with maven, what
>> >>>> problem
>> >>>>> did you find? Is what I use in day-by-day to work with VSCode
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> http://about.me/carlosrovira
>> >>
>> >>
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
I already did in that commit, we have both now
El mar., 4 sept. 2018 a las 13:31, Harbs (<ha...@gmail.com>) escribió:
> Great. I’ll add the asconfigc tasks to that later.
>
> > On Sep 4, 2018, at 2:10 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > I found it how to do it
> > New VSCode forma 2.0.0 solves this and more :))
> >
> > one thing it you can configure a task to be default, but I didn't commit
> > anyone as default since the others will be less quick to execute
> >
> > El mar., 4 sept. 2018 a las 12:55, Harbs (<ha...@gmail.com>)
> escribió:
> >
> >> Awesome. :-)
> >>
> >>> On Sep 4, 2018, at 1:42 PM, Carlos Rovira <ca...@apache.org>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I revert my revert ;), so I can find a non intrusive way. I'm sure
> VSCode
> >>> should have a way to configure a task but make it not default or block
> >> AS3
> >>> extension
> >>> when I get it I'll commit the solution
> >>>
> >>> El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>)
> >> escribió:
> >>>
> >>>> I had some errors on missing resources.
> >>>>
> >>>> I’ve never managed to get maven to work for me. Dunno why.
> >>>>
> >>>> The tasks.json file overrides the defaults, so the build task uses
> maven
> >>>> instead of asconfigc.
> >>>>
> >>>> We should either modify the tasks.json file to allow for multiple
> build
> >>>> tasks, or include it in gitignore.
> >>>>
> >>>> Here’s info on defining arbitrary tasks:
> >>>>
> >>>>
> >>
> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
> >>>> <
> >>>>
> >>
> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
> >>>>>
> >>>>
> >>>>
> >>>>> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <ca...@apache.org>
> >>>> wrote:
> >>>>>
> >>>>> I revert latest commit since launch.json works ok with maven, what
> >>>> problem
> >>>>> did you find? Is what I use in day-by-day to work with VSCode
> >>>>
> >>>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Great. I’ll add the asconfigc tasks to that later.
> On Sep 4, 2018, at 2:10 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> I found it how to do it
> New VSCode forma 2.0.0 solves this and more :))
>
> one thing it you can configure a task to be default, but I didn't commit
> anyone as default since the others will be less quick to execute
>
> El mar., 4 sept. 2018 a las 12:55, Harbs (<ha...@gmail.com>) escribió:
>
>> Awesome. :-)
>>
>>> On Sep 4, 2018, at 1:42 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>
>>> Hi,
>>>
>>> I revert my revert ;), so I can find a non intrusive way. I'm sure VSCode
>>> should have a way to configure a task but make it not default or block
>> AS3
>>> extension
>>> when I get it I'll commit the solution
>>>
>>> El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>)
>> escribió:
>>>
>>>> I had some errors on missing resources.
>>>>
>>>> I’ve never managed to get maven to work for me. Dunno why.
>>>>
>>>> The tasks.json file overrides the defaults, so the build task uses maven
>>>> instead of asconfigc.
>>>>
>>>> We should either modify the tasks.json file to allow for multiple build
>>>> tasks, or include it in gitignore.
>>>>
>>>> Here’s info on defining arbitrary tasks:
>>>>
>>>>
>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>>>> <
>>>>
>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>>>>>
>>>>
>>>>
>>>>> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <ca...@apache.org>
>>>> wrote:
>>>>>
>>>>> I revert latest commit since launch.json works ok with maven, what
>>>> problem
>>>>> did you find? Is what I use in day-by-day to work with VSCode
>>>>
>>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
I found it how to do it
New VSCode forma 2.0.0 solves this and more :))
one thing it you can configure a task to be default, but I didn't commit
anyone as default since the others will be less quick to execute
El mar., 4 sept. 2018 a las 12:55, Harbs (<ha...@gmail.com>) escribió:
> Awesome. :-)
>
> > On Sep 4, 2018, at 1:42 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi,
> >
> > I revert my revert ;), so I can find a non intrusive way. I'm sure VSCode
> > should have a way to configure a task but make it not default or block
> AS3
> > extension
> > when I get it I'll commit the solution
> >
> > El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>)
> escribió:
> >
> >> I had some errors on missing resources.
> >>
> >> I’ve never managed to get maven to work for me. Dunno why.
> >>
> >> The tasks.json file overrides the defaults, so the build task uses maven
> >> instead of asconfigc.
> >>
> >> We should either modify the tasks.json file to allow for multiple build
> >> tasks, or include it in gitignore.
> >>
> >> Here’s info on defining arbitrary tasks:
> >>
> >>
> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
> >> <
> >>
> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
> >>>
> >>
> >>
> >>> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <ca...@apache.org>
> >> wrote:
> >>>
> >>> I revert latest commit since launch.json works ok with maven, what
> >> problem
> >>> did you find? Is what I use in day-by-day to work with VSCode
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Awesome. :-)
> On Sep 4, 2018, at 1:42 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi,
>
> I revert my revert ;), so I can find a non intrusive way. I'm sure VSCode
> should have a way to configure a task but make it not default or block AS3
> extension
> when I get it I'll commit the solution
>
> El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>) escribió:
>
>> I had some errors on missing resources.
>>
>> I’ve never managed to get maven to work for me. Dunno why.
>>
>> The tasks.json file overrides the defaults, so the build task uses maven
>> instead of asconfigc.
>>
>> We should either modify the tasks.json file to allow for multiple build
>> tasks, or include it in gitignore.
>>
>> Here’s info on defining arbitrary tasks:
>>
>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>> <
>> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
>>>
>>
>>
>>> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>
>>> I revert latest commit since launch.json works ok with maven, what
>> problem
>>> did you find? Is what I use in day-by-day to work with VSCode
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
I revert my revert ;), so I can find a non intrusive way. I'm sure VSCode
should have a way to configure a task but make it not default or block AS3
extension
when I get it I'll commit the solution
El mar., 4 sept. 2018 a las 12:20, Harbs (<ha...@gmail.com>) escribió:
> I had some errors on missing resources.
>
> I’ve never managed to get maven to work for me. Dunno why.
>
> The tasks.json file overrides the defaults, so the build task uses maven
> instead of asconfigc.
>
> We should either modify the tasks.json file to allow for multiple build
> tasks, or include it in gitignore.
>
> Here’s info on defining arbitrary tasks:
>
> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
> <
> https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017
> >
>
>
> > On Sep 4, 2018, at 12:57 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > I revert latest commit since launch.json works ok with maven, what
> problem
> > did you find? Is what I use in day-by-day to work with VSCode
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
I had some errors on missing resources.
I’ve never managed to get maven to work for me. Dunno why.
The tasks.json file overrides the defaults, so the build task uses maven instead of asconfigc.
We should either modify the tasks.json file to allow for multiple build tasks, or include it in gitignore.
Here’s info on defining arbitrary tasks:
https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017 <https://docs.microsoft.com/en-us/visualstudio/ide/customize-build-and-debug-tasks-in-visual-studio?view=vs-2017>
> On Sep 4, 2018, at 12:57 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> I revert latest commit since launch.json works ok with maven, what problem
> did you find? Is what I use in day-by-day to work with VSCode
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Excellent.
I was going to check what classes are included in the playground, but I’ll wait for your observations.
:-)
Harbs
> On Sep 4, 2018, at 1:02 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> With all that merged, we can release
>
> we can in parallel start conversation about how Basic linking affect Jewel.
> I have a compilation with current develop to compare and see what's are the
> actual problems.
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
AMF/RemoteObject examples working as expected!
I think we can merge in develop, if others have tested other example
projects and all is working ok.
With all that merged, we can release
we can in parallel start conversation about how Basic linking affect Jewel.
I have a compilation with current develop to compare and see what's are the
actual problems.
Carlos
El mar., 4 sept. 2018 a las 11:57, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi Harbs,
>
> Jewel all working right!, :)
> good work on merging
>
> I need to test now AMF/RemoteObject
>
> I revert latest commit since launch.json works ok with maven, what problem
> did you find? Is what I use in day-by-day to work with VSCode
>
> Let's go to test AMF
>
> thanks
>
>
> El mar., 4 sept. 2018 a las 11:33, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> Hi Harbs,
>> thanks! I'll be looking at it now. Will be soon reporting
>> Carlos
>>
>> El mar., 4 sept. 2018 a las 10:41, Harbs (<ha...@gmail.com>)
>> escribió:
>>
>>> Please let me know whether you think the merge branch should be merged
>>> back into develop…
>>>
>>> > On Sep 4, 2018, at 11:18 AM, Harbs <ha...@gmail.com> wrote:
>>> >
>>> > DataGroup is not an IItemRendererParent any more, so the Jewel
>>> DataGroup doesn’t work the way it was being used.
>>> >
>>> > I based it on DataContainer and change the access code in the view and
>>> controller to make it work.
>>> >
>>> > It looks to me like the whole Jewel playground functions correctly now.
>>> >
>>> > Let me know what you think.
>>> >
>>> > Harbs
>>> >
>>> >> On Sep 4, 2018, at 10:13 AM, Harbs <ha...@gmail.com> wrote:
>>> >>
>>> >> I fixed everything except ComboBox.
>>> >>
>>> >> I’m not sure why my fix didn’t resolve ComboBox too. Looking into it…
>>> >>
>>> >> Looking good… :-)
>>> >>
>>> >>> On Sep 3, 2018, at 10:04 PM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>> >>>
>>> >>> Hi
>>> >>>
>>> >>> as Piotr said JewelExample is the example to check. Fixing DataGroup
>>> should
>>> >>> fix the four sections involved:
>>> >>>
>>> >>> -TablePlayGround
>>> >>> -DateComponentsPlayGround
>>> >>> -ComboBoxPlayGround
>>> >>> -ListPlayGround
>>> >>>
>>> >>> just as a hint, I move this lines in MainContent.mxml to the bottom
>>> of
>>> >>> ApplicationMainContent, to let the rest of sections render
>>> correctly, so
>>> >>> this are declared later and instantiated later, since when running
>>> prevents
>>> >>> the rest to work right.
>>> >>>
>>> >>> Thanks
>>> >>>
>>> >>> Carlos
>>> >>>
>>> >>>
>>> >>>
>>> >>> El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>)
>>> escribió:
>>> >>>
>>> >>>> I see the problem.
>>> >>>>
>>> >>>> I’m out of time for tonight. I’ll work on fixing this in the
>>> morning.
>>> >>>>
>>> >>>> Thanks,
>>> >>>> Harbs
>>> >>>>
>>> >>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <carlosrovira@apache.org
>>> >
>>> >>>> wrote:
>>> >>>>>
>>> >>>>> The problem here's the changes in DataGroup, we can skip this
>>> problem if
>>> >>>> we
>>> >>>>> want for now making Jewel DataGroup be equal to old DataGroup
>>> instead of
>>> >>>>> extend basic DataGroup,
>>> >>>>> If not we need to know about the changes in DataGroup and change
>>> >>>>> TBodyContentArea to work with the new changes
>>> >>>>
>>> >>>>
>>> >>>
>>> >>> --
>>> >>> Carlos Rovira
>>> >>> http://about.me/carlosrovira
>>> >>
>>> >
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs,
Jewel all working right!, :)
good work on merging
I need to test now AMF/RemoteObject
I revert latest commit since launch.json works ok with maven, what problem
did you find? Is what I use in day-by-day to work with VSCode
Let's go to test AMF
thanks
El mar., 4 sept. 2018 a las 11:33, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi Harbs,
> thanks! I'll be looking at it now. Will be soon reporting
> Carlos
>
> El mar., 4 sept. 2018 a las 10:41, Harbs (<ha...@gmail.com>)
> escribió:
>
>> Please let me know whether you think the merge branch should be merged
>> back into develop…
>>
>> > On Sep 4, 2018, at 11:18 AM, Harbs <ha...@gmail.com> wrote:
>> >
>> > DataGroup is not an IItemRendererParent any more, so the Jewel
>> DataGroup doesn’t work the way it was being used.
>> >
>> > I based it on DataContainer and change the access code in the view and
>> controller to make it work.
>> >
>> > It looks to me like the whole Jewel playground functions correctly now.
>> >
>> > Let me know what you think.
>> >
>> > Harbs
>> >
>> >> On Sep 4, 2018, at 10:13 AM, Harbs <ha...@gmail.com> wrote:
>> >>
>> >> I fixed everything except ComboBox.
>> >>
>> >> I’m not sure why my fix didn’t resolve ComboBox too. Looking into it…
>> >>
>> >> Looking good… :-)
>> >>
>> >>> On Sep 3, 2018, at 10:04 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>> >>>
>> >>> Hi
>> >>>
>> >>> as Piotr said JewelExample is the example to check. Fixing DataGroup
>> should
>> >>> fix the four sections involved:
>> >>>
>> >>> -TablePlayGround
>> >>> -DateComponentsPlayGround
>> >>> -ComboBoxPlayGround
>> >>> -ListPlayGround
>> >>>
>> >>> just as a hint, I move this lines in MainContent.mxml to the bottom of
>> >>> ApplicationMainContent, to let the rest of sections render correctly,
>> so
>> >>> this are declared later and instantiated later, since when running
>> prevents
>> >>> the rest to work right.
>> >>>
>> >>> Thanks
>> >>>
>> >>> Carlos
>> >>>
>> >>>
>> >>>
>> >>> El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>)
>> escribió:
>> >>>
>> >>>> I see the problem.
>> >>>>
>> >>>> I’m out of time for tonight. I’ll work on fixing this in the morning.
>> >>>>
>> >>>> Thanks,
>> >>>> Harbs
>> >>>>
>> >>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>> >>>> wrote:
>> >>>>>
>> >>>>> The problem here's the changes in DataGroup, we can skip this
>> problem if
>> >>>> we
>> >>>>> want for now making Jewel DataGroup be equal to old DataGroup
>> instead of
>> >>>>> extend basic DataGroup,
>> >>>>> If not we need to know about the changes in DataGroup and change
>> >>>>> TBodyContentArea to work with the new changes
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> http://about.me/carlosrovira
>> >>
>> >
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs,
thanks! I'll be looking at it now. Will be soon reporting
Carlos
El mar., 4 sept. 2018 a las 10:41, Harbs (<ha...@gmail.com>) escribió:
> Please let me know whether you think the merge branch should be merged
> back into develop…
>
> > On Sep 4, 2018, at 11:18 AM, Harbs <ha...@gmail.com> wrote:
> >
> > DataGroup is not an IItemRendererParent any more, so the Jewel DataGroup
> doesn’t work the way it was being used.
> >
> > I based it on DataContainer and change the access code in the view and
> controller to make it work.
> >
> > It looks to me like the whole Jewel playground functions correctly now.
> >
> > Let me know what you think.
> >
> > Harbs
> >
> >> On Sep 4, 2018, at 10:13 AM, Harbs <ha...@gmail.com> wrote:
> >>
> >> I fixed everything except ComboBox.
> >>
> >> I’m not sure why my fix didn’t resolve ComboBox too. Looking into it…
> >>
> >> Looking good… :-)
> >>
> >>> On Sep 3, 2018, at 10:04 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >>>
> >>> Hi
> >>>
> >>> as Piotr said JewelExample is the example to check. Fixing DataGroup
> should
> >>> fix the four sections involved:
> >>>
> >>> -TablePlayGround
> >>> -DateComponentsPlayGround
> >>> -ComboBoxPlayGround
> >>> -ListPlayGround
> >>>
> >>> just as a hint, I move this lines in MainContent.mxml to the bottom of
> >>> ApplicationMainContent, to let the rest of sections render correctly,
> so
> >>> this are declared later and instantiated later, since when running
> prevents
> >>> the rest to work right.
> >>>
> >>> Thanks
> >>>
> >>> Carlos
> >>>
> >>>
> >>>
> >>> El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>)
> escribió:
> >>>
> >>>> I see the problem.
> >>>>
> >>>> I’m out of time for tonight. I’ll work on fixing this in the morning.
> >>>>
> >>>> Thanks,
> >>>> Harbs
> >>>>
> >>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
> >>>> wrote:
> >>>>>
> >>>>> The problem here's the changes in DataGroup, we can skip this
> problem if
> >>>> we
> >>>>> want for now making Jewel DataGroup be equal to old DataGroup
> instead of
> >>>>> extend basic DataGroup,
> >>>>> If not we need to know about the changes in DataGroup and change
> >>>>> TBodyContentArea to work with the new changes
> >>>>
> >>>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> http://about.me/carlosrovira
> >>
> >
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Please let me know whether you think the merge branch should be merged back into develop…
> On Sep 4, 2018, at 11:18 AM, Harbs <ha...@gmail.com> wrote:
>
> DataGroup is not an IItemRendererParent any more, so the Jewel DataGroup doesn’t work the way it was being used.
>
> I based it on DataContainer and change the access code in the view and controller to make it work.
>
> It looks to me like the whole Jewel playground functions correctly now.
>
> Let me know what you think.
>
> Harbs
>
>> On Sep 4, 2018, at 10:13 AM, Harbs <ha...@gmail.com> wrote:
>>
>> I fixed everything except ComboBox.
>>
>> I’m not sure why my fix didn’t resolve ComboBox too. Looking into it…
>>
>> Looking good… :-)
>>
>>> On Sep 3, 2018, at 10:04 PM, Carlos Rovira <ca...@apache.org> wrote:
>>>
>>> Hi
>>>
>>> as Piotr said JewelExample is the example to check. Fixing DataGroup should
>>> fix the four sections involved:
>>>
>>> -TablePlayGround
>>> -DateComponentsPlayGround
>>> -ComboBoxPlayGround
>>> -ListPlayGround
>>>
>>> just as a hint, I move this lines in MainContent.mxml to the bottom of
>>> ApplicationMainContent, to let the rest of sections render correctly, so
>>> this are declared later and instantiated later, since when running prevents
>>> the rest to work right.
>>>
>>> Thanks
>>>
>>> Carlos
>>>
>>>
>>>
>>> El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>) escribió:
>>>
>>>> I see the problem.
>>>>
>>>> I’m out of time for tonight. I’ll work on fixing this in the morning.
>>>>
>>>> Thanks,
>>>> Harbs
>>>>
>>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>>>> wrote:
>>>>>
>>>>> The problem here's the changes in DataGroup, we can skip this problem if
>>>> we
>>>>> want for now making Jewel DataGroup be equal to old DataGroup instead of
>>>>> extend basic DataGroup,
>>>>> If not we need to know about the changes in DataGroup and change
>>>>> TBodyContentArea to work with the new changes
>>>>
>>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>
>
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
DataGroup is not an IItemRendererParent any more, so the Jewel DataGroup doesn’t work the way it was being used.
I based it on DataContainer and change the access code in the view and controller to make it work.
It looks to me like the whole Jewel playground functions correctly now.
Let me know what you think.
Harbs
> On Sep 4, 2018, at 10:13 AM, Harbs <ha...@gmail.com> wrote:
>
> I fixed everything except ComboBox.
>
> I’m not sure why my fix didn’t resolve ComboBox too. Looking into it…
>
> Looking good… :-)
>
>> On Sep 3, 2018, at 10:04 PM, Carlos Rovira <ca...@apache.org> wrote:
>>
>> Hi
>>
>> as Piotr said JewelExample is the example to check. Fixing DataGroup should
>> fix the four sections involved:
>>
>> -TablePlayGround
>> -DateComponentsPlayGround
>> -ComboBoxPlayGround
>> -ListPlayGround
>>
>> just as a hint, I move this lines in MainContent.mxml to the bottom of
>> ApplicationMainContent, to let the rest of sections render correctly, so
>> this are declared later and instantiated later, since when running prevents
>> the rest to work right.
>>
>> Thanks
>>
>> Carlos
>>
>>
>>
>> El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>) escribió:
>>
>>> I see the problem.
>>>
>>> I’m out of time for tonight. I’ll work on fixing this in the morning.
>>>
>>> Thanks,
>>> Harbs
>>>
>>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>>
>>>> The problem here's the changes in DataGroup, we can skip this problem if
>>> we
>>>> want for now making Jewel DataGroup be equal to old DataGroup instead of
>>>> extend basic DataGroup,
>>>> If not we need to know about the changes in DataGroup and change
>>>> TBodyContentArea to work with the new changes
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
I fixed everything except ComboBox.
I’m not sure why my fix didn’t resolve ComboBox too. Looking into it…
Looking good… :-)
> On Sep 3, 2018, at 10:04 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi
>
> as Piotr said JewelExample is the example to check. Fixing DataGroup should
> fix the four sections involved:
>
> -TablePlayGround
> -DateComponentsPlayGround
> -ComboBoxPlayGround
> -ListPlayGround
>
> just as a hint, I move this lines in MainContent.mxml to the bottom of
> ApplicationMainContent, to let the rest of sections render correctly, so
> this are declared later and instantiated later, since when running prevents
> the rest to work right.
>
> Thanks
>
> Carlos
>
>
>
> El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>) escribió:
>
>> I see the problem.
>>
>> I’m out of time for tonight. I’ll work on fixing this in the morning.
>>
>> Thanks,
>> Harbs
>>
>>> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>
>>> The problem here's the changes in DataGroup, we can skip this problem if
>> we
>>> want for now making Jewel DataGroup be equal to old DataGroup instead of
>>> extend basic DataGroup,
>>> If not we need to know about the changes in DataGroup and change
>>> TBodyContentArea to work with the new changes
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi
as Piotr said JewelExample is the example to check. Fixing DataGroup should
fix the four sections involved:
-TablePlayGround
-DateComponentsPlayGround
-ComboBoxPlayGround
-ListPlayGround
just as a hint, I move this lines in MainContent.mxml to the bottom of
ApplicationMainContent, to let the rest of sections render correctly, so
this are declared later and instantiated later, since when running prevents
the rest to work right.
Thanks
Carlos
El lun., 3 sept. 2018 a las 20:57, Harbs (<ha...@gmail.com>) escribió:
> I see the problem.
>
> I’m out of time for tonight. I’ll work on fixing this in the morning.
>
> Thanks,
> Harbs
>
> > On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > The problem here's the changes in DataGroup, we can skip this problem if
> we
> > want for now making Jewel DataGroup be equal to old DataGroup instead of
> > extend basic DataGroup,
> > If not we need to know about the changes in DataGroup and change
> > TBodyContentArea to work with the new changes
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
I see the problem.
I’m out of time for tonight. I’ll work on fixing this in the morning.
Thanks,
Harbs
> On Sep 3, 2018, at 3:46 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> The problem here's the changes in DataGroup, we can skip this problem if we
> want for now making Jewel DataGroup be equal to old DataGroup instead of
> extend basic DataGroup,
> If not we need to know about the changes in DataGroup and change
> TBodyContentArea to work with the new changes
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi, congratulations! jewel example is running almost at 70% aprox
Things to fix:
* Table, this will fix DateChooser and this DateField (DateChooser uses a
Table internally)
The problem here's the changes in DataGroup, we can skip this problem if we
want for now making Jewel DataGroup be equal to old DataGroup instead of
extend basic DataGroup,
If not we need to know about the changes in DataGroup and change
TBodyContentArea to work with the new changes
* List, adding, removing, and so on are reporting errors, due to the same
problems as before, strangely some things here although give error works :?
* ComboBox is not popup the list when clicked, again is a problem with
DataGroups since the ComboBox uses a ComboBoxList that has IContentView
equal to ComboBoxListDataGroup
@Alex or someone at MXRoyale could let us know about the changes in
DataGroup so we can adapt the code to new DataGroup??
Piotr, Harbs good work on merging! :D
Thanks!
El lun., 3 sept. 2018 a las 14:34, Carlos Rovira (<ca...@apache.org>)
escribió:
> build with maven is ok for me :)
>
> I try examples now
>
> El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>)
> escribió:
>
>> Oops. I broke that.
>>
>> Should be fixed now…
>>
>> > On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>> >
>> > Hi build with maven fails in MXRoyale:
>> >
>> > COMPC
>> >
>> > Loading configuration:
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
>> >
>> >
>> > Warning: mx.controls.RichTextEditor is defined by multiple files:
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>> >
>> >
>> >
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>> > col: 8 Warning: Definition
>> > org.apache.royale.core.IContainer.IItemRendererProvider could not be
>> found.
>> >
>> >
>> > import org.apache.royale.core.IContainer.IItemRendererProvider;
>> >
>> > ^
>> >
>> >
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>> > col: 129 Error: interface IItemRendererProvider was not found.
>> >
>> >
>> > public class ListBase extends UIComponent implements
>> > IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>> ILayoutView,
>> > IItemRendererProvider
>> >
>> >
>> > ^
>> >
>> >
>> > mx.controls.RichTextEditor is defined by multiple files:
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>> >
>> >
>> >
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
>> > col: 8 Definition
>> org.apache.royale.core.IContainer.IItemRendererProvider
>> > could not be found.
>> >
>> >
>> > import org.apache.royale.core.IContainer.IItemRendererProvider;
>> >
>> > ^
>> >
>> >
>> >
>> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
>> > col: 129 interface IItemRendererProvider was not found.
>> >
>> >
>> > public class ListBase extends UIComponent implements
>> > IContainerBaseStrandChildrenHost, IContainer, ILayoutParent,
>> ILayoutView,
>> > IItemRendererProvider
>> >
>> >
>> > ^
>> >
>> >
>> > 1.197156816 seconds
>> >
>> > [*INFO*]
>> >
>> *------------------------------------------------------------------------*
>> >
>> > [*INFO*] *Reactor Summary:*
>> >
>> > [*INFO*]
>> >
>> > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT .... *SUCCESS*
>> [
>> > 3.744 s]
>> >
>> > [*INFO*] Apache Royale: Framework ........................... *SUCCESS*
>> [
>> > 0.355 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Fonts .................... *SUCCESS*
>> [
>> > 1.190 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs ..................... *SUCCESS*
>> [
>> > 0.762 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Core ............... *SUCCESS*
>> [
>> > 7.075 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Binding ............ *SUCCESS*
>> [
>> > 0.989 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Collections ........ *SUCCESS*
>> [
>> > 0.714 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Graphics ........... *SUCCESS*
>> [
>> > 1.485 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Basic .............. *SUCCESS*
>> [
>> > 6.852 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Charts ............. *SUCCESS*
>> [
>> > 2.051 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Effects ............ *SUCCESS*
>> [
>> > 1.190 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: CreateJS ........... *SUCCESS*
>> [
>> > 1.098 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: DragDrop ........... *SUCCESS*
>> [
>> > 1.023 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Express ............ *SUCCESS*
>> [
>> > 0.990 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Flat ............... *SUCCESS*
>> [
>> > 0.855 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Formatters ......... *SUCCESS*
>> [
>> > 0.763 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........ *SUCCESS*
>> [
>> > 0.715 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: GoogleMaps ......... *SUCCESS*
>> [
>> > 0.873 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: HTML ............... *SUCCESS*
>> [
>> > 1.052 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: HTML5 .............. *SUCCESS*
>> [
>> > 0.694 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: JQuery ............. *SUCCESS*
>> [
>> > 0.631 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Language ........... *SUCCESS*
>> [
>> > 0.352 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Material Design Lite *SUCCESS*
>> [
>> > 2.553 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Mobile ............. *SUCCESS*
>> [
>> > 0.888 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Reflection ......... *SUCCESS*
>> [
>> > 0.629 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Network ............ *SUCCESS*
>> [
>> > 1.095 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Storage ............ *SUCCESS*
>> [
>> > 0.448 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: XML ................ *SUCCESS*
>> [
>> > 0.732 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Text ............... *SUCCESS*
>> [
>> > 0.998 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: TLF ................ *SUCCESS*
>> [
>> > 7.767 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: RoyaleSite ......... *SUCCESS*
>> [
>> > 1.008 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: MXRoyale ........... *FAILURE*
>> [
>> > 1.396 s]
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: Icons .............. *SKIPPED*
>> >
>> > [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........ *SKIPPED*
>> >
>> > [*INFO*] Apache Royale: Framework:
>> >
>> > El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
>> > piotrzarzycki21@gmail.com>) escribió:
>> >
>> >> Maven build should work - I checked it one hour ago.
>> >>
>> >> I will try to get from your plate Tour De Flex.
>> >>
>> >> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>> >>
>> >>>
>> >>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org>
>> >>> wrote:
>> >>>>
>> >>>> Hi Harbs
>> >>>>
>> >>>> just check what I can do:
>> >>>> The branch you're working is "feature/new_merge" right?
>> >>>
>> >>> Yes.
>> >>>
>> >>>> this builds with maven?
>> >>>
>> >>> Theoretically, but I have not tried. Please let me know.
>> >>>
>> >>>> Can I check it out, build and test Jewel now? So I can report what I
>> >> see?
>> >>>
>> >>> Yes. Please.
>> >>>
>> >>> I’ll check back in tonight.
>> >>>
>> >>> Keeping my fingers crossed!!! ;-)
>> >>>
>> >>> Harbs
>> >>>
>> >>>>
>> >>>> thanks
>> >>>>
>> >>>>
>> >>>>
>> >>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
>> >>> escribió:
>> >>>>
>> >>>>> I’m done for the morning and I’ll be out this afternoon.
>> >>>>>
>> >>>>> I’ll try to spend some more time this evening on this.
>> >>>>>
>> >>>>> I still need to:
>> >>>>> * Test the framework against some more of my apps.
>> >>>>> * Make sure the examples work.
>> >>>>> * See if the Jewel examples run.
>> >>>>> * See if Tour de Flex runs.
>> >>>>>
>> >>>>> Anyone who can confirm any of these would be very helpful.
>> >>>>>
>> >>>>> Harbs
>> >>>>>
>> >>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <
>> carlosrovira@apache.org>
>> >>>>> wrote:
>> >>>>>>
>> >>>>>> I'm available for you to help you solve. write me when you need.
>> >>>>>>
>> >>>>>> Just a note: for doing this, I'll take the following path: I'll try
>> >> to
>> >>>>>> compile and run without make Jewel depend on Basic, since is the
>> >> actual
>> >>>>>> shape. From there I'll try to link Basic. I think that path will
>> >>> provide
>> >>>>>> you a more safe point from what you could go to next step. Just my
>> >>> advice
>> >>>>>> if you want to take it.
>> >>>>>
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> Carlos Rovira
>> >>>> http://about.me/carlosrovira
>> >>>
>> >>>
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
build with maven is ok for me :)
I try examples now
El lun., 3 sept. 2018 a las 14:21, Harbs (<ha...@gmail.com>) escribió:
> Oops. I broke that.
>
> Should be fixed now…
>
> > On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi build with maven fails in MXRoyale:
> >
> > COMPC
> >
> > Loading configuration:
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
> >
> >
> > Warning: mx.controls.RichTextEditor is defined by multiple files:
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> > col: 8 Warning: Definition
> > org.apache.royale.core.IContainer.IItemRendererProvider could not be
> found.
> >
> >
> > import org.apache.royale.core.IContainer.IItemRendererProvider;
> >
> > ^
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> > col: 129 Error: interface IItemRendererProvider was not found.
> >
> >
> > public class ListBase extends UIComponent implements
> > IContainerBaseStrandChildrenHost, IContainer, ILayoutParent, ILayoutView,
> > IItemRendererProvider
> >
> >
> > ^
> >
> >
> > mx.controls.RichTextEditor is defined by multiple files:
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
> >
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> > col: 8 Definition org.apache.royale.core.IContainer.IItemRendererProvider
> > could not be found.
> >
> >
> > import org.apache.royale.core.IContainer.IItemRendererProvider;
> >
> > ^
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> > col: 129 interface IItemRendererProvider was not found.
> >
> >
> > public class ListBase extends UIComponent implements
> > IContainerBaseStrandChildrenHost, IContainer, ILayoutParent, ILayoutView,
> > IItemRendererProvider
> >
> >
> > ^
> >
> >
> > 1.197156816 seconds
> >
> > [*INFO*]
> >
> *------------------------------------------------------------------------*
> >
> > [*INFO*] *Reactor Summary:*
> >
> > [*INFO*]
> >
> > [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT .... *SUCCESS* [
> > 3.744 s]
> >
> > [*INFO*] Apache Royale: Framework ........................... *SUCCESS* [
> > 0.355 s]
> >
> > [*INFO*] Apache Royale: Framework: Fonts .................... *SUCCESS* [
> > 1.190 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs ..................... *SUCCESS* [
> > 0.762 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Core ............... *SUCCESS* [
> > 7.075 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Binding ............ *SUCCESS* [
> > 0.989 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Collections ........ *SUCCESS* [
> > 0.714 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Graphics ........... *SUCCESS* [
> > 1.485 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Basic .............. *SUCCESS* [
> > 6.852 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Charts ............. *SUCCESS* [
> > 2.051 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Effects ............ *SUCCESS* [
> > 1.190 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: CreateJS ........... *SUCCESS* [
> > 1.098 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: DragDrop ........... *SUCCESS* [
> > 1.023 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Express ............ *SUCCESS* [
> > 0.990 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Flat ............... *SUCCESS* [
> > 0.855 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Formatters ......... *SUCCESS* [
> > 0.763 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........ *SUCCESS* [
> > 0.715 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: GoogleMaps ......... *SUCCESS* [
> > 0.873 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: HTML ............... *SUCCESS* [
> > 1.052 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: HTML5 .............. *SUCCESS* [
> > 0.694 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: JQuery ............. *SUCCESS* [
> > 0.631 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Language ........... *SUCCESS* [
> > 0.352 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Material Design Lite *SUCCESS* [
> > 2.553 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Mobile ............. *SUCCESS* [
> > 0.888 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Reflection ......... *SUCCESS* [
> > 0.629 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Network ............ *SUCCESS* [
> > 1.095 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Storage ............ *SUCCESS* [
> > 0.448 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: XML ................ *SUCCESS* [
> > 0.732 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Text ............... *SUCCESS* [
> > 0.998 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: TLF ................ *SUCCESS* [
> > 7.767 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: RoyaleSite ......... *SUCCESS* [
> > 1.008 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: MXRoyale ........... *FAILURE* [
> > 1.396 s]
> >
> > [*INFO*] Apache Royale: Framework: Libs: Icons .............. *SKIPPED*
> >
> > [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........ *SKIPPED*
> >
> > [*INFO*] Apache Royale: Framework:
> >
> > El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> >> Maven build should work - I checked it one hour ago.
> >>
> >> I will try to get from your plate Tour De Flex.
> >>
> >> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
> >>
> >>>
> >>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org>
> >>> wrote:
> >>>>
> >>>> Hi Harbs
> >>>>
> >>>> just check what I can do:
> >>>> The branch you're working is "feature/new_merge" right?
> >>>
> >>> Yes.
> >>>
> >>>> this builds with maven?
> >>>
> >>> Theoretically, but I have not tried. Please let me know.
> >>>
> >>>> Can I check it out, build and test Jewel now? So I can report what I
> >> see?
> >>>
> >>> Yes. Please.
> >>>
> >>> I’ll check back in tonight.
> >>>
> >>> Keeping my fingers crossed!!! ;-)
> >>>
> >>> Harbs
> >>>
> >>>>
> >>>> thanks
> >>>>
> >>>>
> >>>>
> >>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
> >>> escribió:
> >>>>
> >>>>> I’m done for the morning and I’ll be out this afternoon.
> >>>>>
> >>>>> I’ll try to spend some more time this evening on this.
> >>>>>
> >>>>> I still need to:
> >>>>> * Test the framework against some more of my apps.
> >>>>> * Make sure the examples work.
> >>>>> * See if the Jewel examples run.
> >>>>> * See if Tour de Flex runs.
> >>>>>
> >>>>> Anyone who can confirm any of these would be very helpful.
> >>>>>
> >>>>> Harbs
> >>>>>
> >>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <carlosrovira@apache.org
> >
> >>>>> wrote:
> >>>>>>
> >>>>>> I'm available for you to help you solve. write me when you need.
> >>>>>>
> >>>>>> Just a note: for doing this, I'll take the following path: I'll try
> >> to
> >>>>>> compile and run without make Jewel depend on Basic, since is the
> >> actual
> >>>>>> shape. From there I'll try to link Basic. I think that path will
> >>> provide
> >>>>>> you a more safe point from what you could go to next step. Just my
> >>> advice
> >>>>>> if you want to take it.
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> http://about.me/carlosrovira
> >>>
> >>>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Oops. I broke that.
Should be fixed now…
> On Sep 3, 2018, at 3:09 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi build with maven fails in MXRoyale:
>
> COMPC
>
> Loading configuration:
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
>
>
> Warning: mx.controls.RichTextEditor is defined by multiple files:
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> col: 8 Warning: Definition
> org.apache.royale.core.IContainer.IItemRendererProvider could not be found.
>
>
> import org.apache.royale.core.IContainer.IItemRendererProvider;
>
> ^
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> col: 129 Error: interface IItemRendererProvider was not found.
>
>
> public class ListBase extends UIComponent implements
> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent, ILayoutView,
> IItemRendererProvider
>
>
> ^
>
>
> mx.controls.RichTextEditor is defined by multiple files:
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
>
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
> col: 8 Definition org.apache.royale.core.IContainer.IItemRendererProvider
> could not be found.
>
>
> import org.apache.royale.core.IContainer.IItemRendererProvider;
>
> ^
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
> col: 129 interface IItemRendererProvider was not found.
>
>
> public class ListBase extends UIComponent implements
> IContainerBaseStrandChildrenHost, IContainer, ILayoutParent, ILayoutView,
> IItemRendererProvider
>
>
> ^
>
>
> 1.197156816 seconds
>
> [*INFO*]
> *------------------------------------------------------------------------*
>
> [*INFO*] *Reactor Summary:*
>
> [*INFO*]
>
> [*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT .... *SUCCESS* [
> 3.744 s]
>
> [*INFO*] Apache Royale: Framework ........................... *SUCCESS* [
> 0.355 s]
>
> [*INFO*] Apache Royale: Framework: Fonts .................... *SUCCESS* [
> 1.190 s]
>
> [*INFO*] Apache Royale: Framework: Libs ..................... *SUCCESS* [
> 0.762 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Core ............... *SUCCESS* [
> 7.075 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Binding ............ *SUCCESS* [
> 0.989 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Collections ........ *SUCCESS* [
> 0.714 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Graphics ........... *SUCCESS* [
> 1.485 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Basic .............. *SUCCESS* [
> 6.852 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Charts ............. *SUCCESS* [
> 2.051 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Effects ............ *SUCCESS* [
> 1.190 s]
>
> [*INFO*] Apache Royale: Framework: Libs: CreateJS ........... *SUCCESS* [
> 1.098 s]
>
> [*INFO*] Apache Royale: Framework: Libs: DragDrop ........... *SUCCESS* [
> 1.023 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Express ............ *SUCCESS* [
> 0.990 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Flat ............... *SUCCESS* [
> 0.855 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Formatters ......... *SUCCESS* [
> 0.763 s]
>
> [*INFO*] Apache Royale: Framework: Libs: FontAwesome ........ *SUCCESS* [
> 0.715 s]
>
> [*INFO*] Apache Royale: Framework: Libs: GoogleMaps ......... *SUCCESS* [
> 0.873 s]
>
> [*INFO*] Apache Royale: Framework: Libs: HTML ............... *SUCCESS* [
> 1.052 s]
>
> [*INFO*] Apache Royale: Framework: Libs: HTML5 .............. *SUCCESS* [
> 0.694 s]
>
> [*INFO*] Apache Royale: Framework: Libs: JQuery ............. *SUCCESS* [
> 0.631 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Language ........... *SUCCESS* [
> 0.352 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Material Design Lite *SUCCESS* [
> 2.553 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Mobile ............. *SUCCESS* [
> 0.888 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Reflection ......... *SUCCESS* [
> 0.629 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Network ............ *SUCCESS* [
> 1.095 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Storage ............ *SUCCESS* [
> 0.448 s]
>
> [*INFO*] Apache Royale: Framework: Libs: XML ................ *SUCCESS* [
> 0.732 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Text ............... *SUCCESS* [
> 0.998 s]
>
> [*INFO*] Apache Royale: Framework: Libs: TLF ................ *SUCCESS* [
> 7.767 s]
>
> [*INFO*] Apache Royale: Framework: Libs: RoyaleSite ......... *SUCCESS* [
> 1.008 s]
>
> [*INFO*] Apache Royale: Framework: Libs: MXRoyale ........... *FAILURE* [
> 1.396 s]
>
> [*INFO*] Apache Royale: Framework: Libs: Icons .............. *SKIPPED*
>
> [*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........ *SKIPPED*
>
> [*INFO*] Apache Royale: Framework:
>
> El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
>> Maven build should work - I checked it one hour ago.
>>
>> I will try to get from your plate Tour De Flex.
>>
>> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>>
>>>
>>>> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>>
>>>> Hi Harbs
>>>>
>>>> just check what I can do:
>>>> The branch you're working is "feature/new_merge" right?
>>>
>>> Yes.
>>>
>>>> this builds with maven?
>>>
>>> Theoretically, but I have not tried. Please let me know.
>>>
>>>> Can I check it out, build and test Jewel now? So I can report what I
>> see?
>>>
>>> Yes. Please.
>>>
>>> I’ll check back in tonight.
>>>
>>> Keeping my fingers crossed!!! ;-)
>>>
>>> Harbs
>>>
>>>>
>>>> thanks
>>>>
>>>>
>>>>
>>>> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
>>> escribió:
>>>>
>>>>> I’m done for the morning and I’ll be out this afternoon.
>>>>>
>>>>> I’ll try to spend some more time this evening on this.
>>>>>
>>>>> I still need to:
>>>>> * Test the framework against some more of my apps.
>>>>> * Make sure the examples work.
>>>>> * See if the Jewel examples run.
>>>>> * See if Tour de Flex runs.
>>>>>
>>>>> Anyone who can confirm any of these would be very helpful.
>>>>>
>>>>> Harbs
>>>>>
>>>>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <ca...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>> I'm available for you to help you solve. write me when you need.
>>>>>>
>>>>>> Just a note: for doing this, I'll take the following path: I'll try
>> to
>>>>>> compile and run without make Jewel depend on Basic, since is the
>> actual
>>>>>> shape. From there I'll try to link Basic. I think that path will
>>> provide
>>>>>> you a more safe point from what you could go to next step. Just my
>>> advice
>>>>>> if you want to take it.
>>>>>
>>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>
>>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi build with maven fails in MXRoyale:
COMPC
Loading configuration:
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/target/compile-swf-config.xml
Warning: mx.controls.RichTextEditor is defined by multiple files:
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
col: 8 Warning: Definition
org.apache.royale.core.IContainer.IItemRendererProvider could not be found.
import org.apache.royale.core.IContainer.IItemRendererProvider;
^
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
col: 129 Error: interface IItemRendererProvider was not found.
public class ListBase extends UIComponent implements
IContainerBaseStrandChildrenHost, IContainer, ILayoutParent, ILayoutView,
IItemRendererProvider
^
mx.controls.RichTextEditor is defined by multiple files:
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.as,
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/RichTextEditor.mxml
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(38):
col: 8 Definition org.apache.royale.core.IContainer.IItemRendererProvider
could not be found.
import org.apache.royale.core.IContainer.IItemRendererProvider;
^
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/frameworks/projects/MXRoyale/src/main/royale/mx/controls/listClasses/ListBase.as(88):
col: 129 interface IItemRendererProvider was not found.
public class ListBase extends UIComponent implements
IContainerBaseStrandChildrenHost, IContainer, ILayoutParent, ILayoutView,
IItemRendererProvider
^
1.197156816 seconds
[*INFO*]
*------------------------------------------------------------------------*
[*INFO*] *Reactor Summary:*
[*INFO*]
[*INFO*] Apache Royale: Framework: Parent 0.9.3-SNAPSHOT .... *SUCCESS* [
3.744 s]
[*INFO*] Apache Royale: Framework ........................... *SUCCESS* [
0.355 s]
[*INFO*] Apache Royale: Framework: Fonts .................... *SUCCESS* [
1.190 s]
[*INFO*] Apache Royale: Framework: Libs ..................... *SUCCESS* [
0.762 s]
[*INFO*] Apache Royale: Framework: Libs: Core ............... *SUCCESS* [
7.075 s]
[*INFO*] Apache Royale: Framework: Libs: Binding ............ *SUCCESS* [
0.989 s]
[*INFO*] Apache Royale: Framework: Libs: Collections ........ *SUCCESS* [
0.714 s]
[*INFO*] Apache Royale: Framework: Libs: Graphics ........... *SUCCESS* [
1.485 s]
[*INFO*] Apache Royale: Framework: Libs: Basic .............. *SUCCESS* [
6.852 s]
[*INFO*] Apache Royale: Framework: Libs: Charts ............. *SUCCESS* [
2.051 s]
[*INFO*] Apache Royale: Framework: Libs: Effects ............ *SUCCESS* [
1.190 s]
[*INFO*] Apache Royale: Framework: Libs: CreateJS ........... *SUCCESS* [
1.098 s]
[*INFO*] Apache Royale: Framework: Libs: DragDrop ........... *SUCCESS* [
1.023 s]
[*INFO*] Apache Royale: Framework: Libs: Express ............ *SUCCESS* [
0.990 s]
[*INFO*] Apache Royale: Framework: Libs: Flat ............... *SUCCESS* [
0.855 s]
[*INFO*] Apache Royale: Framework: Libs: Formatters ......... *SUCCESS* [
0.763 s]
[*INFO*] Apache Royale: Framework: Libs: FontAwesome ........ *SUCCESS* [
0.715 s]
[*INFO*] Apache Royale: Framework: Libs: GoogleMaps ......... *SUCCESS* [
0.873 s]
[*INFO*] Apache Royale: Framework: Libs: HTML ............... *SUCCESS* [
1.052 s]
[*INFO*] Apache Royale: Framework: Libs: HTML5 .............. *SUCCESS* [
0.694 s]
[*INFO*] Apache Royale: Framework: Libs: JQuery ............. *SUCCESS* [
0.631 s]
[*INFO*] Apache Royale: Framework: Libs: Language ........... *SUCCESS* [
0.352 s]
[*INFO*] Apache Royale: Framework: Libs: Material Design Lite *SUCCESS* [
2.553 s]
[*INFO*] Apache Royale: Framework: Libs: Mobile ............. *SUCCESS* [
0.888 s]
[*INFO*] Apache Royale: Framework: Libs: Reflection ......... *SUCCESS* [
0.629 s]
[*INFO*] Apache Royale: Framework: Libs: Network ............ *SUCCESS* [
1.095 s]
[*INFO*] Apache Royale: Framework: Libs: Storage ............ *SUCCESS* [
0.448 s]
[*INFO*] Apache Royale: Framework: Libs: XML ................ *SUCCESS* [
0.732 s]
[*INFO*] Apache Royale: Framework: Libs: Text ............... *SUCCESS* [
0.998 s]
[*INFO*] Apache Royale: Framework: Libs: TLF ................ *SUCCESS* [
7.767 s]
[*INFO*] Apache Royale: Framework: Libs: RoyaleSite ......... *SUCCESS* [
1.008 s]
[*INFO*] Apache Royale: Framework: Libs: MXRoyale ........... *FAILURE* [
1.396 s]
[*INFO*] Apache Royale: Framework: Libs: Icons .............. *SKIPPED*
[*INFO*] Apache Royale: Framework: Libs: SparkRoyale ........ *SKIPPED*
[*INFO*] Apache Royale: Framework:
El lun., 3 sept. 2018 a las 13:37, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Maven build should work - I checked it one hour ago.
>
> I will try to get from your plate Tour De Flex.
>
> On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>
> >
> > > On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org>
> > wrote:
> > >
> > > Hi Harbs
> > >
> > > just check what I can do:
> > > The branch you're working is "feature/new_merge" right?
> >
> > Yes.
> >
> > > this builds with maven?
> >
> > Theoretically, but I have not tried. Please let me know.
> >
> > > Can I check it out, build and test Jewel now? So I can report what I
> see?
> >
> > Yes. Please.
> >
> > I’ll check back in tonight.
> >
> > Keeping my fingers crossed!!! ;-)
> >
> > Harbs
> >
> > >
> > > thanks
> > >
> > >
> > >
> > > El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
> > escribió:
> > >
> > >> I’m done for the morning and I’ll be out this afternoon.
> > >>
> > >> I’ll try to spend some more time this evening on this.
> > >>
> > >> I still need to:
> > >> * Test the framework against some more of my apps.
> > >> * Make sure the examples work.
> > >> * See if the Jewel examples run.
> > >> * See if Tour de Flex runs.
> > >>
> > >> Anyone who can confirm any of these would be very helpful.
> > >>
> > >> Harbs
> > >>
> > >>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <ca...@apache.org>
> > >> wrote:
> > >>>
> > >>> I'm available for you to help you solve. write me when you need.
> > >>>
> > >>> Just a note: for doing this, I'll take the following path: I'll try
> to
> > >>> compile and run without make Jewel depend on Basic, since is the
> actual
> > >>> shape. From there I'll try to link Basic. I think that path will
> > provide
> > >>> you a more safe point from what you could go to next step. Just my
> > advice
> > >>> if you want to take it.
> > >>
> > >>
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> >
> >
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Maven build should work - I checked it one hour ago.
I will try to get from your plate Tour De Flex.
On Mon, Sep 3, 2018, 1:26 PM Harbs <ha...@gmail.com> wrote:
>
> > On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi Harbs
> >
> > just check what I can do:
> > The branch you're working is "feature/new_merge" right?
>
> Yes.
>
> > this builds with maven?
>
> Theoretically, but I have not tried. Please let me know.
>
> > Can I check it out, build and test Jewel now? So I can report what I see?
>
> Yes. Please.
>
> I’ll check back in tonight.
>
> Keeping my fingers crossed!!! ;-)
>
> Harbs
>
> >
> > thanks
> >
> >
> >
> > El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>)
> escribió:
> >
> >> I’m done for the morning and I’ll be out this afternoon.
> >>
> >> I’ll try to spend some more time this evening on this.
> >>
> >> I still need to:
> >> * Test the framework against some more of my apps.
> >> * Make sure the examples work.
> >> * See if the Jewel examples run.
> >> * See if Tour de Flex runs.
> >>
> >> Anyone who can confirm any of these would be very helpful.
> >>
> >> Harbs
> >>
> >>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <ca...@apache.org>
> >> wrote:
> >>>
> >>> I'm available for you to help you solve. write me when you need.
> >>>
> >>> Just a note: for doing this, I'll take the following path: I'll try to
> >>> compile and run without make Jewel depend on Basic, since is the actual
> >>> shape. From there I'll try to link Basic. I think that path will
> provide
> >>> you a more safe point from what you could go to next step. Just my
> advice
> >>> if you want to take it.
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
> On Sep 3, 2018, at 2:22 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi Harbs
>
> just check what I can do:
> The branch you're working is "feature/new_merge" right?
Yes.
> this builds with maven?
Theoretically, but I have not tried. Please let me know.
> Can I check it out, build and test Jewel now? So I can report what I see?
Yes. Please.
I’ll check back in tonight.
Keeping my fingers crossed!!! ;-)
Harbs
>
> thanks
>
>
>
> El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>) escribió:
>
>> I’m done for the morning and I’ll be out this afternoon.
>>
>> I’ll try to spend some more time this evening on this.
>>
>> I still need to:
>> * Test the framework against some more of my apps.
>> * Make sure the examples work.
>> * See if the Jewel examples run.
>> * See if Tour de Flex runs.
>>
>> Anyone who can confirm any of these would be very helpful.
>>
>> Harbs
>>
>>> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>
>>> I'm available for you to help you solve. write me when you need.
>>>
>>> Just a note: for doing this, I'll take the following path: I'll try to
>>> compile and run without make Jewel depend on Basic, since is the actual
>>> shape. From there I'll try to link Basic. I think that path will provide
>>> you a more safe point from what you could go to next step. Just my advice
>>> if you want to take it.
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs
just check what I can do:
The branch you're working is "feature/new_merge" right?
this builds with maven?
Can I check it out, build and test Jewel now? So I can report what I see?
thanks
El lun., 3 sept. 2018 a las 13:17, Harbs (<ha...@gmail.com>) escribió:
> I’m done for the morning and I’ll be out this afternoon.
>
> I’ll try to spend some more time this evening on this.
>
> I still need to:
> * Test the framework against some more of my apps.
> * Make sure the examples work.
> * See if the Jewel examples run.
> * See if Tour de Flex runs.
>
> Anyone who can confirm any of these would be very helpful.
>
> Harbs
>
> > On Sep 3, 2018, at 11:28 AM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > I'm available for you to help you solve. write me when you need.
> >
> > Just a note: for doing this, I'll take the following path: I'll try to
> > compile and run without make Jewel depend on Basic, since is the actual
> > shape. From there I'll try to link Basic. I think that path will provide
> > you a more safe point from what you could go to next step. Just my advice
> > if you want to take it.
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
I’m done for the morning and I’ll be out this afternoon.
I’ll try to spend some more time this evening on this.
I still need to:
* Test the framework against some more of my apps.
* Make sure the examples work.
* See if the Jewel examples run.
* See if Tour de Flex runs.
Anyone who can confirm any of these would be very helpful.
Harbs
> On Sep 3, 2018, at 11:28 AM, Carlos Rovira <ca...@apache.org> wrote:
>
> I'm available for you to help you solve. write me when you need.
>
> Just a note: for doing this, I'll take the following path: I'll try to
> compile and run without make Jewel depend on Basic, since is the actual
> shape. From there I'll try to link Basic. I think that path will provide
> you a more safe point from what you could go to next step. Just my advice
> if you want to take it.
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Harbs,
I'm available for you to help you solve. write me when you need.
Just a note: for doing this, I'll take the following path: I'll try to
compile and run without make Jewel depend on Basic, since is the actual
shape. From there I'll try to link Basic. I think that path will provide
you a more safe point from what you could go to next step. Just my advice
if you want to take it.
Thanks!
Carlos
El lun., 3 sept. 2018 a las 10:23, Harbs (<ha...@gmail.com>) escribió:
> OK. Everything compiles now.
>
> I’m going to run the branch against some applications and see what
> happens. If you could do the same, it would be helpful.
>
> Carlos, I probably need some direction on how to test Jewel.
>
> Harbs
>
> > On Sep 3, 2018, at 10:38 AM, Piotr Zarzycki <pi...@gmail.com>
> wrote:
> >
> > Ok! Again good luck! :)
> >
> > pon., 3 wrz 2018 o 09:34 Harbs <ha...@gmail.com> napisał(a):
> >
> >> The issues that I see with Jewel are related to the changes that were
> lost
> >> when you merged.
> >>
> >> I’m hoping I can resolve this quickly. Let’s see how over-optimistic I’m
> >> being… ;-)
> >>
> >> Harbs
> >>
> >>> On Sep 3, 2018, at 10:28 AM, Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> >> wrote:
> >>>
> >>> Harbs,
> >>>
> >>> There is also another way. Maybe it is worth that I will spend couple
> of
> >>> hours on my branch and try to understand what was wrong. If I would
> >> manage
> >>> to do that - maybe you will be able to add your stuff on top of that ?
> Do
> >>> you see value in that approach ?
> >>>
> >>> I'm just afraid that doing again Jewel depends on Basic end up with a
> lot
> >>> of problems for you and delay for weeks that release.
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <pi...@gmail.com>
> >>> napisał(a):
> >>>
> >>>> Hi Harbs,
> >>>>
> >>>> Looking forward to your changes. I'm just interested in release in
> >>>> whatever state it is and dealing with discussion later on.
> >>>>
> >>>> Btw. I have invested also at least 6h with merge stuff and as you can
> >> see
> >>>> it end up with bigger things. Good Luck! :)
> >>>>
> >>>> Thanks,
> >>>> Piotr
> >>>>
> >>>> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
> >>>>
> >>>>> Right now, my priority is getting all three active branches combined
> >> with
> >>>>> all code working. That means MX/Spark, Jewel, and all the additions
> on
> >> the
> >>>>> revert branch all coexisting nicely in the merge branch.
> >>>>>
> >>>>> I’m spending the better part of today on that.
> >>>>>
> >>>>> I’d like to hold off on discussing where to go from here until I
> >>>>> understand the issues you went through with Jewel better. I expect
> I’m
> >>>>> going to go through a lot of the pain you already went through
> already
> >>>>> getting Jewel to compile and work with the merges.
> >>>>>
> >>>>> I might end up in the same place as you. Don’t know yet…
> >>>>>
> >>>>> I’m open to all possibilities. Even if we do separate depenendies,
> >> having
> >>>>> the dependencies even temporarily *might* help resolve some of the
> >>>>> underlying technical issues.
> >>>>>
> >>>>> Let’s discuss when I come up for air… ;-)
> >>>>>
> >>>>> Harbs
> >>>>>
> >>>>>> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> considering making Jewel dependent on Basic. I'm trying to put my
> mind
> >>>>> in
> >>>>>> that place. Since this is a huge effort for me, hope you all try to
> do
> >>>>> the
> >>>>>> same as me and considering some thoughts, so we can plan something
> >> that
> >>>>>> works for all:
> >>>>>>
> >>>>>> Since Basic will be the middle point between Core and Jewel, can we
> >>>>>> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could
> >> be
> >>>>>> really the common basic library and CSS doesn't mess Jewel things?
> >>>>>>
> >>>>>> If so, we can go that router and test and discuss that integration
> in
> >> a
> >>>>>> separate branch and deal with all of that.
> >>>>>> this will inevitably delay the release, but maybe is time to solve
> >> this
> >>>>>> first.
> >>>>>>
> >>>>>> One of the things to do in the final result is to compile Jewel
> (debug
> >>>>> and
> >>>>>> release) and comparte results on develop and results on integration
> >>>>> branch
> >>>>>>
> >>>>>> Then we can decide what's better and release that
> >>>>>>
> >>>>>> Thoughts?
> >>>>>>
> >>>>>>
> >>>>>> El lun., 3 sept. 2018 a las 4:53, Alex Harui
> >> (<aharui@adobe.com.invalid
> >>>>>> )
> >>>>>> escribió:
> >>>>>>
> >>>>>>> FWIW, I agree with Harbs. Enough time has passed and changes have
> >> been
> >>>>>>> made that it is time to try making Jewel dependent on Basic so we
> can
> >>>>> see
> >>>>>>> in code (not words) what the problems are with doing that.
> >>>>>>>
> >>>>>>> My 2 cents,
> >>>>>>> -Alex
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Carlos Rovira
> >>>>>> http://about.me/carlosrovira
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>>
> >>>> Piotr Zarzycki
> >>>>
> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>>> <https://www.patreon.com/piotrzarzycki>*
> >>>>
> >>>
> >>>
> >>> --
> >>>
> >>> Piotr Zarzycki
> >>>
> >>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>> <https://www.patreon.com/piotrzarzycki>*
> >>
> >>
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
OK. Everything compiles now.
I’m going to run the branch against some applications and see what happens. If you could do the same, it would be helpful.
Carlos, I probably need some direction on how to test Jewel.
Harbs
> On Sep 3, 2018, at 10:38 AM, Piotr Zarzycki <pi...@gmail.com> wrote:
>
> Ok! Again good luck! :)
>
> pon., 3 wrz 2018 o 09:34 Harbs <ha...@gmail.com> napisał(a):
>
>> The issues that I see with Jewel are related to the changes that were lost
>> when you merged.
>>
>> I’m hoping I can resolve this quickly. Let’s see how over-optimistic I’m
>> being… ;-)
>>
>> Harbs
>>
>>> On Sep 3, 2018, at 10:28 AM, Piotr Zarzycki <pi...@gmail.com>
>> wrote:
>>>
>>> Harbs,
>>>
>>> There is also another way. Maybe it is worth that I will spend couple of
>>> hours on my branch and try to understand what was wrong. If I would
>> manage
>>> to do that - maybe you will be able to add your stuff on top of that ? Do
>>> you see value in that approach ?
>>>
>>> I'm just afraid that doing again Jewel depends on Basic end up with a lot
>>> of problems for you and delay for weeks that release.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <pi...@gmail.com>
>>> napisał(a):
>>>
>>>> Hi Harbs,
>>>>
>>>> Looking forward to your changes. I'm just interested in release in
>>>> whatever state it is and dealing with discussion later on.
>>>>
>>>> Btw. I have invested also at least 6h with merge stuff and as you can
>> see
>>>> it end up with bigger things. Good Luck! :)
>>>>
>>>> Thanks,
>>>> Piotr
>>>>
>>>> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
>>>>
>>>>> Right now, my priority is getting all three active branches combined
>> with
>>>>> all code working. That means MX/Spark, Jewel, and all the additions on
>> the
>>>>> revert branch all coexisting nicely in the merge branch.
>>>>>
>>>>> I’m spending the better part of today on that.
>>>>>
>>>>> I’d like to hold off on discussing where to go from here until I
>>>>> understand the issues you went through with Jewel better. I expect I’m
>>>>> going to go through a lot of the pain you already went through already
>>>>> getting Jewel to compile and work with the merges.
>>>>>
>>>>> I might end up in the same place as you. Don’t know yet…
>>>>>
>>>>> I’m open to all possibilities. Even if we do separate depenendies,
>> having
>>>>> the dependencies even temporarily *might* help resolve some of the
>>>>> underlying technical issues.
>>>>>
>>>>> Let’s discuss when I come up for air… ;-)
>>>>>
>>>>> Harbs
>>>>>
>>>>>> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> considering making Jewel dependent on Basic. I'm trying to put my mind
>>>>> in
>>>>>> that place. Since this is a huge effort for me, hope you all try to do
>>>>> the
>>>>>> same as me and considering some thoughts, so we can plan something
>> that
>>>>>> works for all:
>>>>>>
>>>>>> Since Basic will be the middle point between Core and Jewel, can we
>>>>>> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could
>> be
>>>>>> really the common basic library and CSS doesn't mess Jewel things?
>>>>>>
>>>>>> If so, we can go that router and test and discuss that integration in
>> a
>>>>>> separate branch and deal with all of that.
>>>>>> this will inevitably delay the release, but maybe is time to solve
>> this
>>>>>> first.
>>>>>>
>>>>>> One of the things to do in the final result is to compile Jewel (debug
>>>>> and
>>>>>> release) and comparte results on develop and results on integration
>>>>> branch
>>>>>>
>>>>>> Then we can decide what's better and release that
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>>
>>>>>> El lun., 3 sept. 2018 a las 4:53, Alex Harui
>> (<aharui@adobe.com.invalid
>>>>>> )
>>>>>> escribió:
>>>>>>
>>>>>>> FWIW, I agree with Harbs. Enough time has passed and changes have
>> been
>>>>>>> made that it is time to try making Jewel dependent on Basic so we can
>>>>> see
>>>>>>> in code (not words) what the problems are with doing that.
>>>>>>>
>>>>>>> My 2 cents,
>>>>>>> -Alex
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Carlos Rovira
>>>>>> http://about.me/carlosrovira
>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>> Piotr Zarzycki
>>>>
>>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>>> <https://www.patreon.com/piotrzarzycki>*
>>>>
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> <https://www.patreon.com/piotrzarzycki>*
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Ok! Again good luck! :)
pon., 3 wrz 2018 o 09:34 Harbs <ha...@gmail.com> napisał(a):
> The issues that I see with Jewel are related to the changes that were lost
> when you merged.
>
> I’m hoping I can resolve this quickly. Let’s see how over-optimistic I’m
> being… ;-)
>
> Harbs
>
> > On Sep 3, 2018, at 10:28 AM, Piotr Zarzycki <pi...@gmail.com>
> wrote:
> >
> > Harbs,
> >
> > There is also another way. Maybe it is worth that I will spend couple of
> > hours on my branch and try to understand what was wrong. If I would
> manage
> > to do that - maybe you will be able to add your stuff on top of that ? Do
> > you see value in that approach ?
> >
> > I'm just afraid that doing again Jewel depends on Basic end up with a lot
> > of problems for you and delay for weeks that release.
> >
> > Thanks,
> > Piotr
> >
> > pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> >> Hi Harbs,
> >>
> >> Looking forward to your changes. I'm just interested in release in
> >> whatever state it is and dealing with discussion later on.
> >>
> >> Btw. I have invested also at least 6h with merge stuff and as you can
> see
> >> it end up with bigger things. Good Luck! :)
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
> >>
> >>> Right now, my priority is getting all three active branches combined
> with
> >>> all code working. That means MX/Spark, Jewel, and all the additions on
> the
> >>> revert branch all coexisting nicely in the merge branch.
> >>>
> >>> I’m spending the better part of today on that.
> >>>
> >>> I’d like to hold off on discussing where to go from here until I
> >>> understand the issues you went through with Jewel better. I expect I’m
> >>> going to go through a lot of the pain you already went through already
> >>> getting Jewel to compile and work with the merges.
> >>>
> >>> I might end up in the same place as you. Don’t know yet…
> >>>
> >>> I’m open to all possibilities. Even if we do separate depenendies,
> having
> >>> the dependencies even temporarily *might* help resolve some of the
> >>> underlying technical issues.
> >>>
> >>> Let’s discuss when I come up for air… ;-)
> >>>
> >>> Harbs
> >>>
> >>>> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org>
> >>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> considering making Jewel dependent on Basic. I'm trying to put my mind
> >>> in
> >>>> that place. Since this is a huge effort for me, hope you all try to do
> >>> the
> >>>> same as me and considering some thoughts, so we can plan something
> that
> >>>> works for all:
> >>>>
> >>>> Since Basic will be the middle point between Core and Jewel, can we
> >>>> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could
> be
> >>>> really the common basic library and CSS doesn't mess Jewel things?
> >>>>
> >>>> If so, we can go that router and test and discuss that integration in
> a
> >>>> separate branch and deal with all of that.
> >>>> this will inevitably delay the release, but maybe is time to solve
> this
> >>>> first.
> >>>>
> >>>> One of the things to do in the final result is to compile Jewel (debug
> >>> and
> >>>> release) and comparte results on develop and results on integration
> >>> branch
> >>>>
> >>>> Then we can decide what's better and release that
> >>>>
> >>>> Thoughts?
> >>>>
> >>>>
> >>>> El lun., 3 sept. 2018 a las 4:53, Alex Harui
> (<aharui@adobe.com.invalid
> >>>> )
> >>>> escribió:
> >>>>
> >>>>> FWIW, I agree with Harbs. Enough time has passed and changes have
> been
> >>>>> made that it is time to try making Jewel dependent on Basic so we can
> >>> see
> >>>>> in code (not words) what the problems are with doing that.
> >>>>>
> >>>>> My 2 cents,
> >>>>> -Alex
> >>>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> http://about.me/carlosrovira
> >>>
> >>>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> <https://www.patreon.com/piotrzarzycki>*
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
The issues that I see with Jewel are related to the changes that were lost when you merged.
I’m hoping I can resolve this quickly. Let’s see how over-optimistic I’m being… ;-)
Harbs
> On Sep 3, 2018, at 10:28 AM, Piotr Zarzycki <pi...@gmail.com> wrote:
>
> Harbs,
>
> There is also another way. Maybe it is worth that I will spend couple of
> hours on my branch and try to understand what was wrong. If I would manage
> to do that - maybe you will be able to add your stuff on top of that ? Do
> you see value in that approach ?
>
> I'm just afraid that doing again Jewel depends on Basic end up with a lot
> of problems for you and delay for weeks that release.
>
> Thanks,
> Piotr
>
> pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
>> Hi Harbs,
>>
>> Looking forward to your changes. I'm just interested in release in
>> whatever state it is and dealing with discussion later on.
>>
>> Btw. I have invested also at least 6h with merge stuff and as you can see
>> it end up with bigger things. Good Luck! :)
>>
>> Thanks,
>> Piotr
>>
>> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
>>
>>> Right now, my priority is getting all three active branches combined with
>>> all code working. That means MX/Spark, Jewel, and all the additions on the
>>> revert branch all coexisting nicely in the merge branch.
>>>
>>> I’m spending the better part of today on that.
>>>
>>> I’d like to hold off on discussing where to go from here until I
>>> understand the issues you went through with Jewel better. I expect I’m
>>> going to go through a lot of the pain you already went through already
>>> getting Jewel to compile and work with the merges.
>>>
>>> I might end up in the same place as you. Don’t know yet…
>>>
>>> I’m open to all possibilities. Even if we do separate depenendies, having
>>> the dependencies even temporarily *might* help resolve some of the
>>> underlying technical issues.
>>>
>>> Let’s discuss when I come up for air… ;-)
>>>
>>> Harbs
>>>
>>>> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> considering making Jewel dependent on Basic. I'm trying to put my mind
>>> in
>>>> that place. Since this is a huge effort for me, hope you all try to do
>>> the
>>>> same as me and considering some thoughts, so we can plan something that
>>>> works for all:
>>>>
>>>> Since Basic will be the middle point between Core and Jewel, can we
>>>> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could be
>>>> really the common basic library and CSS doesn't mess Jewel things?
>>>>
>>>> If so, we can go that router and test and discuss that integration in a
>>>> separate branch and deal with all of that.
>>>> this will inevitably delay the release, but maybe is time to solve this
>>>> first.
>>>>
>>>> One of the things to do in the final result is to compile Jewel (debug
>>> and
>>>> release) and comparte results on develop and results on integration
>>> branch
>>>>
>>>> Then we can decide what's better and release that
>>>>
>>>> Thoughts?
>>>>
>>>>
>>>> El lun., 3 sept. 2018 a las 4:53, Alex Harui (<aharui@adobe.com.invalid
>>>> )
>>>> escribió:
>>>>
>>>>> FWIW, I agree with Harbs. Enough time has passed and changes have been
>>>>> made that it is time to try making Jewel dependent on Basic so we can
>>> see
>>>>> in code (not words) what the problems are with doing that.
>>>>>
>>>>> My 2 cents,
>>>>> -Alex
>>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Harbs,
There is also another way. Maybe it is worth that I will spend couple of
hours on my branch and try to understand what was wrong. If I would manage
to do that - maybe you will be able to add your stuff on top of that ? Do
you see value in that approach ?
I'm just afraid that doing again Jewel depends on Basic end up with a lot
of problems for you and delay for weeks that release.
Thanks,
Piotr
pon., 3 wrz 2018 o 09:23 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Harbs,
>
> Looking forward to your changes. I'm just interested in release in
> whatever state it is and dealing with discussion later on.
>
> Btw. I have invested also at least 6h with merge stuff and as you can see
> it end up with bigger things. Good Luck! :)
>
> Thanks,
> Piotr
>
> pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
>
>> Right now, my priority is getting all three active branches combined with
>> all code working. That means MX/Spark, Jewel, and all the additions on the
>> revert branch all coexisting nicely in the merge branch.
>>
>> I’m spending the better part of today on that.
>>
>> I’d like to hold off on discussing where to go from here until I
>> understand the issues you went through with Jewel better. I expect I’m
>> going to go through a lot of the pain you already went through already
>> getting Jewel to compile and work with the merges.
>>
>> I might end up in the same place as you. Don’t know yet…
>>
>> I’m open to all possibilities. Even if we do separate depenendies, having
>> the dependencies even temporarily *might* help resolve some of the
>> underlying technical issues.
>>
>> Let’s discuss when I come up for air… ;-)
>>
>> Harbs
>>
>> > On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org>
>> wrote:
>> >
>> > Hi,
>> >
>> > considering making Jewel dependent on Basic. I'm trying to put my mind
>> in
>> > that place. Since this is a huge effort for me, hope you all try to do
>> the
>> > same as me and considering some thoughts, so we can plan something that
>> > works for all:
>> >
>> > Since Basic will be the middle point between Core and Jewel, can we
>> > consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could be
>> > really the common basic library and CSS doesn't mess Jewel things?
>> >
>> > If so, we can go that router and test and discuss that integration in a
>> > separate branch and deal with all of that.
>> > this will inevitably delay the release, but maybe is time to solve this
>> > first.
>> >
>> > One of the things to do in the final result is to compile Jewel (debug
>> and
>> > release) and comparte results on develop and results on integration
>> branch
>> >
>> > Then we can decide what's better and release that
>> >
>> > Thoughts?
>> >
>> >
>> > El lun., 3 sept. 2018 a las 4:53, Alex Harui (<aharui@adobe.com.invalid
>> >)
>> > escribió:
>> >
>> >> FWIW, I agree with Harbs. Enough time has passed and changes have been
>> >> made that it is time to try making Jewel dependent on Basic so we can
>> see
>> >> in code (not words) what the problems are with doing that.
>> >>
>> >> My 2 cents,
>> >> -Alex
>> >>
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Harbs,
Looking forward to your changes. I'm just interested in release in whatever
state it is and dealing with discussion later on.
Btw. I have invested also at least 6h with merge stuff and as you can see
it end up with bigger things. Good Luck! :)
Thanks,
Piotr
pon., 3 wrz 2018 o 09:18 Harbs <ha...@gmail.com> napisał(a):
> Right now, my priority is getting all three active branches combined with
> all code working. That means MX/Spark, Jewel, and all the additions on the
> revert branch all coexisting nicely in the merge branch.
>
> I’m spending the better part of today on that.
>
> I’d like to hold off on discussing where to go from here until I
> understand the issues you went through with Jewel better. I expect I’m
> going to go through a lot of the pain you already went through already
> getting Jewel to compile and work with the merges.
>
> I might end up in the same place as you. Don’t know yet…
>
> I’m open to all possibilities. Even if we do separate depenendies, having
> the dependencies even temporarily *might* help resolve some of the
> underlying technical issues.
>
> Let’s discuss when I come up for air… ;-)
>
> Harbs
>
> > On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi,
> >
> > considering making Jewel dependent on Basic. I'm trying to put my mind in
> > that place. Since this is a huge effort for me, hope you all try to do
> the
> > same as me and considering some thoughts, so we can plan something that
> > works for all:
> >
> > Since Basic will be the middle point between Core and Jewel, can we
> > consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could be
> > really the common basic library and CSS doesn't mess Jewel things?
> >
> > If so, we can go that router and test and discuss that integration in a
> > separate branch and deal with all of that.
> > this will inevitably delay the release, but maybe is time to solve this
> > first.
> >
> > One of the things to do in the final result is to compile Jewel (debug
> and
> > release) and comparte results on develop and results on integration
> branch
> >
> > Then we can decide what's better and release that
> >
> > Thoughts?
> >
> >
> > El lun., 3 sept. 2018 a las 4:53, Alex Harui (<aharui@adobe.com.invalid
> >)
> > escribió:
> >
> >> FWIW, I agree with Harbs. Enough time has passed and changes have been
> >> made that it is time to try making Jewel dependent on Basic so we can
> see
> >> in code (not words) what the problems are with doing that.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Make Jewel dependent on Basic (Re: [Discuss] Start release
process 0.9.3)
Posted by Harbs <ha...@gmail.com>.
Right now, my priority is getting all three active branches combined with all code working. That means MX/Spark, Jewel, and all the additions on the revert branch all coexisting nicely in the merge branch.
I’m spending the better part of today on that.
I’d like to hold off on discussing where to go from here until I understand the issues you went through with Jewel better. I expect I’m going to go through a lot of the pain you already went through already getting Jewel to compile and work with the merges.
I might end up in the same place as you. Don’t know yet…
I’m open to all possibilities. Even if we do separate depenendies, having the dependencies even temporarily *might* help resolve some of the underlying technical issues.
Let’s discuss when I come up for air… ;-)
Harbs
> On Sep 3, 2018, at 9:17 AM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi,
>
> considering making Jewel dependent on Basic. I'm trying to put my mind in
> that place. Since this is a huge effort for me, hope you all try to do the
> same as me and considering some thoughts, so we can plan something that
> works for all:
>
> Since Basic will be the middle point between Core and Jewel, can we
> consider to move Basic CSS and TLCS to a BasicUI swc? So Basic could be
> really the common basic library and CSS doesn't mess Jewel things?
>
> If so, we can go that router and test and discuss that integration in a
> separate branch and deal with all of that.
> this will inevitably delay the release, but maybe is time to solve this
> first.
>
> One of the things to do in the final result is to compile Jewel (debug and
> release) and comparte results on develop and results on integration branch
>
> Then we can decide what's better and release that
>
> Thoughts?
>
>
> El lun., 3 sept. 2018 a las 4:53, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
>> FWIW, I agree with Harbs. Enough time has passed and changes have been
>> made that it is time to try making Jewel dependent on Basic so we can see
>> in code (not words) what the problems are with doing that.
>>
>> My 2 cents,
>> -Alex
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira