royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com.INVALID>
Subject Re: Migrating Enterprise Flex Application
Date Thu, 19 Jul 2018 17:21:11 GMT
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.rovira@gmail.com on behalf of Carlos Rovira" <carlos.rovira@gmail.com
on behalf of carlosrovira@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 <aharui@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" <chembali@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&amp;data=02%7C01%7Caharui%40adobe.com%
    > 7C5260d6e737744f16b63008d5ed2f80af%7Cfa7b1b5a7b34438794aed2c178de
    > cee1%7C0%7C1%7C636675710635107707&amp;sdata=jDCl3Gak0jGgzFIzHcgiDs0rfFzsjJ
    > q3e6PgCn5Sy8g%3D&amp;reserved=0
    >
    >
    >
    
    
    -- 
    Carlos Rovira
    https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C09c8f82f80be4a9fafa908d5ed7d80cb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636676045646662630&amp;sdata=kT0BJi8rrYpP7DPz1z0Se5tTGNSofmduvvVD6IcmPtk%3D&amp;reserved=0
    

Mime
View raw message