Hi Alex, El mar., 13 nov. 2018 a las 3:02, Alex Harui (<aha...@adobe.com.invalid>) escribió:
> If VSCode and Moonshine cannot handle the way we build the projects right > now from the command-line, then they should probably make changes so it > works. I would guess that they do but the project files are not set up > correctly. There are separate manifests for the SWF-only classes. Any > Royale user of these IDEs should be allowed to do that and not have every > file in the source-path included in the compilation. So, IMO, the > COMPILE::SWF changes should be reverted and the IDE projects fixed or the > IDEs themselves should be fixed. > > ok, I reverted the commits. It seems to me that classes that targets to concrete platforms (like flash.*) should be on COMPILE::SWF, but maybe I'm missing something there > Regarding making a bead for FocusEvent, I don't know how to predict what > you will need. We already have application level beads like > SimpleStatesImpl.as. Hopefully FocusEvents can be added in that way. If > the code in HTMLElementWrapper needs refactoring to allow plugging in > different handlers that may be ok. It occurred to me that maybe we > shouldn't even bake in MouseConverter. I haven't looked at how Touch is > handled on touch devices and whether it is an either/or with Mouse or not. > Alex, you plan to make focus events for MX/Spark? I think one of the greatness of flex was the smart use of entry data through TAB key. So mouse events are maybe the most standard, but advanced users of flex apps use to be quick with Tab+keyboard. I think this is essential to flex and I'm finding it as I migrate my app. If you plan to make this happen, maybe I should wait so you can wire the infrastructure, looking at what you say, probably I can do what you have in mind. Touch events are as well important to start adding some actual functionality in Royale Apps like swipe from any direction and things like that. What's clear is that I'm very busy right now just migrating, so maybe things that required setup of core things and discussion, and many time to invest are probably off my possibilities right now. Thanks > > HTH, > -Alex > > > On 11/12/18, 2:55 AM, "Carlos Rovira" <carlosrov...@apache.org> wrote: > > Hi Alex, > > I put the COMPILE::SWF in the imports due to all the warnings in VS > Code > (and suppose that will be the same in Moonlight since uses the same > core > and other IDEs using the compiler model as the source for warnings and > errors) > > If this doesn't make a problem, I think we could have as is to avoid > all > those warnings and keep the IDEs clean (at least from royale framework > code), if that causes another some side problem we can revert the > commit. I > suppose for your message that is not a problem, and is just that I > didn't > write to give the reason behind this, right? > > Regarding FocusEvent, ok I'll make it a bead, but I'd want to know more > about this. There's something more I should need to take into account > apart > from the starting pieces a committed to the branch? something in the > compiler or in typedefs?. IOW, if you tell me there's no more pieces, > I can > focus on make the converter a bead and look why my tries are not > working > right now. > > @Harbs <ha...@in-tools.com> you +1 is to all the thread or only to > make > focus a bead? > > thanks > > > > > El lun., 12 nov. 2018 a las 8:00, Harbs (<harbs.li...@gmail.com>) > escribió: > > > +1 > > > > > On Nov 12, 2018, at 2:20 AM, Alex Harui <aha...@adobe.com.INVALID> > > wrote: > > > > > > I don't think FocusEventConverter should be baked into > > HTMLElementWrapper. > > > > > > -- > Carlos Rovira > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C98e283d1afcb415645d108d6488d537a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636776169156260064&sdata=FhOQfnQqdDUW8yTagY4VHiFD8Ih5s76ZJ4ObZzk80Vo%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
