Hi Alex, right, but to reach DataGrid, we should first get Button/CheckBox/TextInput. That will help me (at least) to understand things needed and craft the rest of components with the things learned. Or, in other words, I don't see us going directly to try DataGrid without go that route first. Think that you have very clear things implied in emulation comps, while I don't have my mind in that part. The same happens to the inverse regarding Jewel since I'm all day in that front. What I'm saying is that we should put a little project together to start seeing how things can combine and see if it's possible right now, or in opposite we are going paths that are separating each days little by little, but will be bad to be able to do something in the future as we have many code in place and make a change can suppose a huge refactor to whats done at that time. If we take a look now, we can see problems and code accordingly to what we see.
Just my 2 ctns. thanks Carlos 2018-07-23 2:10 GMT+02:00 Alex Harui <aha...@adobe.com.invalid>: > Hi Carlos, > > IMO, Jewel has lots of cool new components, but the Emulation Components > don't need a Drawer view, they need a DataGridView. Fitting Jewel views > for Button/CheckBox/TextInput onto Emulation Components will probably > work. The real test would be trying something like DataGrid. > > My 2 cents, > -Alex > > On 7/22/18, 2:11 PM, "carlos.rov...@gmail.com on behalf of Carlos > Rovira" <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> > wrote: > > Hi Alex, > > I think Jewel has now several components, so my perception is that we > don't > need to wait much more. I mean we have around 15 Jewel components?... I > think it's time so we can see what things are still needed. > > Just my opinion, but don't want to make anyone precipitate if don't > think > is the time... > > Thanks > > Carlos > > > > 2018-07-19 19:21 GMT+02:00 Alex Harui <aha...@adobe.com.invalid>: > > > Hi Carlos, > > > > Until Jewel has more of the views for existing Flex controls, it > isn't > > worth trying to re-use Jewel view beads in the emulation > components. Once > > you have more of them working, then we'll simply try them and fix > bugs. > > > > -Alex > > > > On 7/19/18, 6:42 AM, "carlos.rov...@gmail.com on behalf of Carlos > > Rovira" <carlos.rov...@gmail.com on behalf of > carlosrov...@apache.org> > > wrote: > > > > Hi Alex, > > > > about trying to use Jewel as view part, I think we should trace a > > plan. I > > still have work in my TODO list, for example I think my next > stop is > > Jewel > > DateFiels and Jewel DropDownList/ComboBox... but I still want to > try > > the > > "exploded" component route. So using StyledUIBase in MXML adding > beads > > I > > can get a Jewel Button, a Jewel Slider and so on... > > > > But as well although I think I'll not use emulation components > on our > > App, > > I think will be good if I must have some rules into account to > make > > Jewel > > visualization reusable. > > > > For this I think we should create a thread, and maybe a example > project > > where we could work together and make the convergence of code > possible. > > > > I think one problem is that if we expect from others to code > what we > > have > > in mind, that will never happen, since I think although we share > a > > "macro" > > view perspective, in the "micro" view we all have, as normal, > different > > ways of approach, so the only way I see is to join forces in > > integrating > > things, more over where you have a huge knowledge of things > happening > > in > > emulation, while I have the same on things happening on Jewel. > > > > Thoughts? > > > > > > > > > > Carlos > > > > > > > > > > 2018-07-19 9:35 GMT+02:00 Alex Harui <aha...@adobe.com.invalid>: > > > > > I think you can look at mx.controls.DateField and > > > mx.controls.NumericStepper. The key piece is their entries in > the > > > defaults.css in the MXRoyale project. That dictates which > beads are > > used. > > > If a bead has a package name starting with mx, then it is > probably a > > > subclass of an org.apache.royale bead. > > > > > > I hope to finish up MenuBar shortly and then try to write up a > wiki > > page > > > or something about what it takes to get these emulation > components to > > > function. > > > > > > HTH, > > > -Alex > > > > > > On 7/18/18, 9:24 PM, "chembali" <chemb...@hotmail.com> wrote: > > > > > > Very helpful posts indeed. Can you tell me a couple of > classic > > > emulation > > > examples that I can look at? I am hoping to take a look at > them > > and > > > understand the pattern. > > > > > > > > > > > > -- > > > Sent from: https://na01.safelinks. > protection.outlook.com/?url= > > > http%3A%2F%2Fapache-royale-development.20373.n8.nabble. > > > com%2F&data=02%7C01%7Caharui%40adobe.com% > > > 7C5260d6e737744f16b63008d5ed2f80af% > 7Cfa7b1b5a7b34438794aed2c178de > > > cee1%7C0%7C1%7C636675710635107707&sdata= > > jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJ > > > q3e6PgCn5Sy8g%3D&reserved=0 > > > > > > > > > > > > > > > -- > > Carlos Rovira > > https://na01.safelinks.protection.outlook.com/?url= > > http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02% > > 7C01%7Caharui%40adobe.com%7C09c8f82f80be4a9fafa908d5ed7d80cb% > > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636676045646662630& > sdata= > > kT0BJi8rrYpP7DPz1z0Se5tTGNSofmduvvVD6IcmPtk%3D&reserved=0 > > > > > > > > > -- > Carlos Rovira > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02% > 7C01%7Caharui%40adobe.com%7Ca7d16ed43a3846ca053008d5f017a899% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636678906761736958&sdata= > XkcaoPYP0qGLKaC7VHC5mlBAqW%2BXzNHfIRQ%2FaFnYIUo%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
