I like it.
> There is no direct equivalent of SkinnableContainer in Royale (at this
> time). A reasonable alternative is the Container.
Maybe we could mention that Royale components typically have views which can
be used to control appearance without changing behavior. To me, spark skins
sort
Hi Peter,
Thanks for the detailed explanation. As I understand it, the vision you
outlined is already implemented, we just need to listen to more of these
fine-grained events in the mappers which can happen DAYG.
I personally don't see anything wrong with this architecture, maybe Harbs
who's
If we want HTML elements to contain other elements they need to extend Group
or something similar. We depend on that in various places in our app.
Carlos, how are we supposed to nest HTML elements now?
Thanks.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
I changed it back so NodeElementBase extends Group. Let's continue this
discussion, but we need our app to work...
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Hi Carlos,
Just to get one thing out of the way, I changed NodeElementBase to extend
Group, not because I'm sure that's the way it should be permanently, but
because leaving your change as it was, was breaking our app which had
previously worked.
Changes in base classes are always tricky, so I
Carlos Rovira-2 wrote
> This
> have many advantages, the most visible is a 40% drop off in Apps file
> size
> that uses Jewel, since Basic things that never was used are there any
> more.
> Another thing is that Basic things that could mess the intended behaviour
> in Jewel will never happen
Piotr Zarzycki wrote
> If yes - what does that mean that such controller like
> ItemRendererMouseController is in HTML?
It's only there by name, the source is under Basic (which makes sense to me,
I think controllers are part of the component set).
I'm not sure why it can't be named
d this here by running
> another layout at a later time but I’m interested to hear others on how
> this should be solved.
>
> From: yishayw@mailto:yishayw@;
> Sent: Sunday, June 3, 2018 1:12 PM
> To: commits@.apachemailto:commits@.apache;
> Subject: [royale-asjs] branch develop updated:
Alex Harui-2 wrote
> UIBase used to set position=relative on all positioners. We took that
> away so that the "flex" and other display/layout styles would not have to
> deal with the excess clutter and overhead of having set position on so
> many elements in the DOM.
Can you give an example of
Looking at it some more it has nothing to do with data binding. I pushed a
different fix (799f1878250d8c69347f08442c2c333740efdb8d) that changes the
layout itself. Here it's assumed the offsetParent is explicitly set before
children's x and y are set. Should this be a general pattern?
--
Sent
My workaround for now is to clean all modifications resulting from ant -f
InstallAdobeSDKs.xml, rebuild, and run it again.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Peter, if you look in royale-asjs README isn't the following set of
instructions consistent with your results?
> ## Additional Prerequisites For SWF Output
>
> ### *playerglobal.swc*
>
> The Adobe Flash Player *playerglobal.swc* (version 11.1) can be downloaded
> from:
>
>
I'd like to get an idea of what the workflow would be to implement this. Is
there an example in the repo that I can play around with, compile, and see
what happens? Where's the best place to start?
Thanks.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
I've created an ace-1.2.3.swc but am not able to run a simple example that
uses it.
If anyone has time to look at the ace branches maybe they can help me figure
out why the Ace example isn't compiling...
Thanks.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
The issue is that the typedefs (ace-1.2.3.swc) is being read by the example
app, but I can't import ace.Editor in the code.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
I also think this is a great initiative. Regarding SEO there are some
optimizations that can be applied to single page apps as well so maybe it's
worth testing that before we convert it to a multipage. I'm not in front of
the computer but when I am I'll share the links I read, if there's interest
chembali wrote
> I tried to get an emulation component working. I
> struggled.
I think once you set up your IDE to work with Royale a lot of the struggles
go away. I would encourage you to do that first, with our help, and then
judge your productivity.
--
Sent from:
To be more precise, they will have a subset of the functionality. The API
reports are supposed to help us find the relevant subset.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Did you see Alex's response?
Alex wrote
> COMPC only produces a SWC. If you ended up with a SWC, unzip the SWC and
> see if there are .js files in there. If not, you may need to set
> compiler.targets. Post a link to the console output so we can see what it
> is doing. Also make sure you got
>Does this have any disadvantages or leads to unpredictable behavior when
>using public vars?
In light of this [1] comment it looks like you might run into trouble when
using classes with public vars from within MXML.
[1]
Confused about this, now that I'm using Jewel.
I want to add shadow to a Jewel group. So I do this:
But then I see raisedShadow removed in in run-time in favor of classes such
as "itemsExpand itemsCenter itemsCentered layout vertical"
Where should I be specifying my application
Without knowing much about the compiler, what about incremental compilation?
Can gains be made by checking for source update timestamps and making a
decision as to whether or not to transpile based on that?
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
22 matches
Mail list logo
