Hi, yes I'm working on Jewel DataGrid this days, so this question is around that. It seems to me that the interface seems ok for Basic and Jewel DataGrid, since Jewel use to be based in part on Basic philosophy. So if I understand correctly, if I use in Jewel I can move it to Core right? This is still not sure that will be that way
Thanks El lun., 25 nov. 2019 a las 17:49, Alex Harui (<[email protected]>) escribió: > > > On 11/25/19, 7:48 AM, "Yishay Weiss" <[email protected]> wrote: > > It appears to me like a question of how much energy we want to invest > in abstractions. If we can make a good abstraction that is likely to be > used in most component sets, then it should belong in Core. But I’m not > sure if that’s the case for Basic’s IDataGridView. > > +1. And the test is who else needs it. If some other component set does > need it, then it can be moved to core (or maybe a subset of it). DataGrid > is somewhat opinionated which is why it is in Basic for now. I think there > are some 3rd party datagrids that folks might want to use in Royale that > wouldn't even have a separate view. > > My 2 cents, > -Alex > > From: Carlos Rovira<mailto:[email protected]> > Sent: Monday, November 25, 2019 4:24 PM > To: [email protected]<mailto:[email protected]> > Subject: IDataGridView in Basic instead of Core > > Hi, > > is right to have IDataGridView in Basic instead of Core? > We use to have interfaces in Core. > If this is right I can move from one Basic to Core > > -- > Carlos Rovira > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C46dd12bf579f45da6b5508d771bef7b0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637102937328803376&sdata=y0846%2BWKLJJg5ybLh2V8ferTrv%2BvCbyfru4VrretfLY%3D&reserved=0 > > > > -- Carlos Rovira http://about.me/carlosrovira
