FWIW, Express is really just intended to be a pre-packaging of Basic
beads. If you use Basic you have to add beads to the strand. If you use
Express, the beads are already added to the strand. But the beads will
likely be from the Basic set.
This Skinning/Theming effort, IMO is independent. It
Hi Piotr,
Remember that any top-level component is a composition of beads. We
should be able to create most top-level components by take UIBase and
adding beads to the strand.
So, if we find when implementing skinning/themeing that there are
re-usable pieces from Basic great, but what is most im
Alex,
You are saying about simple case where we can extend UIBase for create new
Button, but what about more sophisticated for example Panel ? Do you want
us to create from scratch again all of that instead use Basic ? This is how
I see reading your last email or maybe I missing something.
Thanks
I'm not quite sure what the meaning of "based on Basic" means. I think
someone is about to go and move a bunch of classes around to better
organize our packages and classes, and I think that IUIBase and maybe
UIBase should end up back in Core (where it was before Harbs temporarily
wrapped the Spri
My guess is that, cause this approach emulates JUnit implementation. Let's
say assertFalse - you can pass there one argument Boolean or two arguments
Boolean and message. In AS3 there is no ability to create two functions
with the same name. But in Java method overloading probably exists, so in
JUn
BTW:
Was there a good reason FlexUnit uses the spread operator for assert arguments
instead of typed arguments?
> On Nov 5, 2017, at 11:36 PM, Harbs wrote:
>
> Some progress on the unit tests:
>
> I got the Core tests to run on the swf side when doing a full build. In order
> to do that I ne
Harbs,
You can leave it to me Maven part, but I have to admit that I will be able
to take look into that probably at the end of the upcoming week. Still need
to finish release of Installer and SDK. If you find the time please raise
for me issue on GitHub, unless you would like to touch Maven.
Tha
Some progress on the unit tests:
I got the Core tests to run on the swf side when doing a full build. In order
to do that I needed to move the running of the tests until after Basic finished
building so the test app could be built.
We’re going to need to do something similar with the Maven buil
Basic is going to be the base for anything. I don’t think Express is going to
be very helpful. It should probably just be built out from Basic components
and/or copied from Basic.
For an example of a styleable component, take a look at CSSCheckbox. I think
that’s a good example of a styleable c
I was thinking about that and new component set is the approach which we
should try, but we need to base on something. My first thoughts was that it
should be Basic, cause I bet that once we start create style for each
component we will end up with some issue or we would like to create some
additio
AMP is also very limiting.
I have a feeling that Royale has some loading advantages because there’s very
little actual HTML for the browser to evaluate and (re)render, but it would be
interesting to do some measuring.
I don’t know that I would actually propose to use the amp library, but the be
Hi Harbs,
this sounds very good. I was browsing the site and has good topics to use
in Apache Royale.
What I don't fully understand is if this is created with applications in
mind since the page asks about editors, technologic ad platforms and
advertisers. What do you think?
About the asynchronous
Hi Nicolas,
2017-11-05 16:03 GMT+01:00 Idylog - Nicolas Granon :
> Hi, Carlos,
>
> No doubt theme support for Apache Royale components/containers/controls (I
> will use "components" from now on) would be very valuable.
>
> Obviously, themes could only be applied to components that conform to a
>
“Units” can mean lots of things to different people. I’m not a purist, and I
personally don’t see the value of having tiny unit tests. To me, the importance
of tests is to make sure there’s good coverage and there’s insurance that
regressive bugs are not introduced.
To me, there’s two types of
Hi, Carlos,
No doubt theme support for Apache Royale components/containers/controls (I will
use "components" from now on) would be very valuable.
Obviously, themes could only be applied to components that conform to a
specific interface and who can be extensively CSS-styled.
I agree that it wou
The compiler can only currently understand pre-compiled definitions by
reading the library.swf in a SWC. It does not know how to parse JS to
build definitions. So, in order to have a set of definitions for
COMPILE::SWF and a separate set of definitions for COMPILE::JS, we need
two sets of SWCs.
Hi Harbs,
Yes we are producing both swc, but are you sure that they have same
content? If you take BasicJS.swc - will you be able to build project to swf?
Piotr
On Sun, Nov 5, 2017, 12:01 Harbs wrote:
> Sorry if I’m a bit confused, but over the history of the project, the
> build process has c
Hi Harbs,
Great discussion. Just thought for Bead driven tests. - Is this what you
are describing are "Unit" tests actually or UI specific tests - automation
? Cause I cannot distinguish it from discussion above.
Piotr
2017-11-05 10:55 GMT+01:00 Harbs :
> On these two points:
>
> > Hmm, that w
Sorry if I’m a bit confused, but over the history of the project, the build
process has changed more than once.
As far as I can tell, the framework builds are building swcs twice: Once for
[Project].swc and again for [Project]JS.swc. The weird thing is that both the
SWF build and the JS build i
Hi all,
in this thread I want to join a plan to work on a theme feature for Apache
Royale. Hope you all could comment here if this starting point is in the
good track or if you think we need things not expressed here.
1.- Theme feature will be a pluggable set of styles (colors, drawings,
images,
As I said, it is not such a big deal for now (for us!).
Also, there was a small but important typo in my message.
We tried :
/myoutputdir
with a closing , of course...
When you are at it, it seems that royale specific arguments are not listed when
executing :
I would suggest starting a new component set with a fresh slate called Themed
(or something like that).
The Themed component set should give priority to style-ablitity and ease of use
over just about every other consideration. I think of Express as more of a
middle-of the road approach to make
I wanted to branch this into a separate discussion because I want to discuss
whether this is a good idea or a bad idea on its own.
Harbs
> On Nov 5, 2017, at 11:55 AM, Harbs wrote:
>
> I just had an interesting idea for solving the component testing problem in a
> Royale-specific way which mig
ok Alex,
so if I understand correctly, you mean that we create our own set, with
Basic as base right?
but we should go with Express? It's great that we could create many sets in
Royale, and I think the Basic use
you commented is very licit and didn't think about that. But we must think
in some *ma
On these two points:
> Hmm, that would be cool if we don't need Selenium to report results.
> Keeping Selenium synced up is a PITA.
For tests that are not browser-dependant, we should not need selenium. Testing
directly through node should be much faster besides requiring less setup.
For tests
Alex,
Your answer is quite interesting.
My (somewhat naïve) question made you say a lot of things about the
"philosophy" behind Royale and about some fundamental design decisions.
Believe me, it helped a lot to better understand Royale as a whole.
Also, reading your answer, I realized that I ma
Hmm, that would be cool if we don't need Selenium to report results.
Keeping Selenium synced up is a PITA.
Regarding declarative languages, the reason I chose MXML when writing
Mustella was that, in Flash, you simply have to stop running AS code in
order for the player to render the screen and det
Hi Carlos,
I think we're pretty much in agreement. Regarding Basic, for me, I have
created plenty of web pages with non-styleable checkboxes. I don't care
that the checkbox looks different on different browsers. I just want the
smallest simplest output. Just like taking an HTML editor and slap
Bummer, I think -js-output is currently broken. We'll have to look into
fixing it.
Sorry about that,
-Alex
On 11/4/17, 9:55 AM, "Idylog - Nicolas Granon" wrote:
>It's not such a big issue for now : what I have done is, I have a small
>eclipse plug-in that can copy files from workspace to anoth
Great topic. I think maybe we have enough folks to try to come up with
some naming conventions. My personal philosophy is that I'm bad at
guessing names for things so it is better to just get something out there
and let folks suggest better names.
I did have some considerations in mind though:
1
30 matches
Mail list logo
