royale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] aharui commented on issue #343: Question : IS there a way to embed third party components within a Royale app
Date Sun, 11 Nov 2018 02:44:20 GMT
aharui commented on issue #343: Question : IS there a way to embed third party components within
a Royale app
   First a side-comment:  I'm sure you have finished your port to HTML/JS, but keep in mind
that with Royale you can develop your JS code in AS and gain the benefits of strict type-checking
at compile-time.
   OK, so I thinK i now understand the markup you showed above.  If you add Event metadata
like in Flex to the AS class that represents your component, then the Royale compiler will
set up the call to addEventListener and bind 'this' to the appropriate object.  You'll see
that most Royale components have Event metadata on them.  Ace doesn't, but MaterialDesignLite
   In the Ace example, Ace is the object set up by loading the JS code for the Ace Editor.
   I don't think anyone has tried using an unwrapped JS component in Royale.  It is theoretically
possible and I and hopefully others would be willing to help make it work.  The reasons we've
wrapped everything so far is to avoid touching the 3rd-party code since we don't control the
source for it.  Similar to Flex and IUIComponent/IFlexDisplayObject, all Royale UI widgets
must implement IUIBase.  So if you are willing to modify your code or subclass your JS grid
to implement IUIBase, then you have a shot at making it work.  And you may need to add getter/setters,
and metadata.  And then you may expose some bugs we have where we are assuming UIBase instead
of IUIBase, but those are things we want to find and fix.
   Fundamentally, Royale is less of a framework and more of a workflow for integrating existing
chunks of JS.  We have some required contracts like IUIBase so we have a common way to size
and position UI widgets from different providers, but otherwise, we are trying to have few
"must haves". 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message