lly get more of the
> > Swiz code officially contributed to Apache Royale. Having renamed lots
> of
> > FlexJS to Royale, I can tell you that renaming still takes time.
> >
> > My 2 cents,
> > -Alex
> >
> > On 7/12/19, 3:41 AM, "Carlos Rovira" wrote:
>
Definitely I will get back to the discussion whether we are ready or not
for 1.0 once I release 0.9.6.
śr., 17 lip 2019 o 10:36 Carlos Rovira napisał(a):
> Piotr,
>
> my guess around low adoption by old flex users and new users is that we are
> still behind 1.0 and docs are still on the works.
Piotr,
my guess around low adoption by old flex users and new users is that we are
still behind 1.0 and docs are still on the works.
When we get to pass that point we'll be able to be more aggressive in
communication efforts. I mean try to be exposed in publications
specialized webs, and more.
The reality is showing that since this project exists I don't see any
single user who came from JS/.NET/Java world to our framework. Everyone who
are interested are from Flex/ActionScript world. At the beginning the
strategy with name changing was great, but it shows that is not working or
even
Hi Yishay,
El mié., 17 jul. 2019 a las 8:05, Yishay Weiss ()
escribió:
>
> It’s true we wanted a separated identity, but as I recall we always had In
> mind to engage the Flex user base. I think it’s important to consider that
> when deciding on a name.
>
>
My point when I pushed the change to
t; > > make it harder to use and then folks start using the short name and
> > then
> > > there can be confusion again.
> > >
> > > AIUI, trademark issues are about confusion. Names like "Basic" and
> > > "Jewel
SwizRoyale is for me very long and
> > > does not
> > > have a meaning inside of what we are doing with the rest of Royale
> > > naming
> > > decision and marketing (making it very difficult to brand along
> with
> > > the
> > > rest of Royale parts for ma
>
> > > AIUI, trademark issues are about confusion. Names like "Basic" and
> > > "Jewel" don't appear to have uses that could be confusing. "Crux"
> > appears
> > > to be some sort of language thing for Jav
ern is that someone may someday want Royale to support a Crux
> library
> > that is based on the Java thing.
> >
> > We are using MXRoyale and SparkRoyale as names for the emulations of
> > Flex's MX and Spark components. "SwizRoyale" would be cons
he Java thing.
> >
> > We are using MXRoyale and SparkRoyale as names for the emulations of
> > Flex's MX and Spark components. "SwizRoyale" would be consistent,
> > especially if the goal is to emulate Swiz and potentially get more
> of the
>
consistent,
> especially if the goal is to emulate Swiz and potentially get more of the
> Swiz code officially contributed to Apache Royale. Having renamed lots of
> FlexJS to Royale, I can tell you that renaming still takes time.
>
> My 2 cents,
> -Alex
&
> My 2 cents,
> -Alex
>
> On 7/12/19, 3:41 AM, "Carlos Rovira" wrote:
>
> Hi Greg!
>
> great progress with the latest touches.
>
> My latest days was in Crux branch so for me is ok to do the merge I
> think
> we cover all the things
es time.
My 2 cents,
-Alex
On 7/12/19, 3:41 AM, "Carlos Rovira" wrote:
Hi Greg!
great progress with the latest touches.
My latest days was in Crux branch so for me is ok to do the merge I think
we cover all the things needed like licensing and avoid name conf
Hi Josh, it's great that you're working on this. Unless I'm mistaken, there
is currently a 'manual' way to do this, which you may have already seen,
using 'exclude-defaults-css-files'
in royale-config, I believe this type of approach works:
MXRoyaleJS.swc:defaults.css
(I saw
I'm working on a fix for the CSS issue that Harbs started a thread about.
I'm almost ready, but I have some edge cases to finish up. I feel like it's
an important one to get into the release because it injects a lot of Jewel
CSS into non-Jewel apps (and CSS from *several* other SWCs too). However,
Hi Greg,
Thanks for update. I'm having again more important tasks and that is why I
didn't start release process yet. It looks like I will have for sure 2 full
working days to start process on upcoming Wednesday. If you make it till
that time it would be great, if not let's stay on the branch.
Just a quick update...
I just fixed the ant builds for the 3 simple crux examples in the branch,
which were not working yet.
There will continue to be improvements and fixes over time, but I actually
think it's at a state where it could be merged into develop. Unless there
is a reason not to, I
Interesting! I didn't know that the capture phase worked for non-bubbling
events. Good to know. Thanks for looking into it and sharing your findings,
Greg.
- Josh
On Thu, Jul 4, 2019, 11:12 PM Greg Dove wrote:
> Hi Josh,
>
> For the addedToStage stuff:
> You made me look! Swiz does not
Hi Josh,
For the addedToStage stuff:
You made me look! Swiz does not actually use the ADDED event, it definitely
does use ADDED_TO_STAGE by default, but you're absolutely right, this does
not bubble.
I did not pay too much attention to the 'bubbling' side of things because I
could see it working
Hi Andrew,
good point! That's without doubt another new point to bring to :
- Royale-docs: We can follow most of the documentation available here [1]
- Examples: In this case I don't see a Tour app since the use cases are
very direct and can be exposed in few examples.
Greg already provide 3
Hi Josh,
thanks for the words! very appreciated :)
I think you're right, and the new name seems ok for me too
(addedToApplication),
maybe event JSStageEvents, should be rethinked too. @Greg Dove
should we need the JS
prefix? what about "ApplicationEvents"
if maybe Application is very generic,
This is great.
However, even with the original Swiz I found the documentation quite thin
and that it made a lot of assumptions about what a general developer might
know and need to know. This site [1] made an attempt about ten years ago to
improve on an intro to Swiz. What plans are in the works
Cool stuff, Greg and Carlos!
One concern: In Flash, the "addedToStage" event does not bubble. It's
actually the "added" event that bubbles and is used by frameworks like
Swiz, Cairngorm, Robotlegs, etc.
To avoid potential confusion for people migrating an existing app from
Flex/Flash that might
Hi all,
thanks Greg for the introduction and for the great work here.
I think you made an excellent task in bringing this project to live :).
Crux is an important piece for all of us trying to make a complex
application.
Until now the Royale option for this kind of "microarquitecture" was
Hi all,
Just a quick advance notice that we are getting something very similar to
Swiz before too long.
There is a new branch called feature/Crux
We can still explore other possible ways to incorporate Swiz code in Royale
(we have looked at having the code donated in the past), but for now at
25 matches
Mail list logo
