I think the most common event should have a simple name like "change". It
makes it easier to remember.
In JS, the actual type of most events is BrowserEvent if it was initiated
by an HTMLElement event. We are sort of taking advantage of the fact that
JS isn't strongly typed and hopefully nobody
BTW, code comments on Github do not propagate to the Apache lists.
If there’s a reason to discuss some code in context, code comments are very
useful. For general discussions on code commits, responding to commit emails is
probably a better way to do it.
Harbs
> On Nov 1, 2017, at 1:30 AM,
You can remove it if it is not fired it up for some other cases in
DateChooser.
Piotr
2017-11-01 0:23 GMT+01:00 Harbs :
> My comment in the commit message needs discussion.
>
> I think the change event should be removed. What do others think?
>
> Harbs
>
> > On Nov 1,
Hi Harbs,
Thanks for look into that. I'm not sure for 100% but those fails seems to
influence application build. If I remove my local cached Royale failes and
try to build Hello World it should download all the swc from the apache
server. Unfortunately pom script complains that Core.swc doesn't
I can say at this point that I really like idea with swappable view. In
most cases view is an ActionScript class where we may have more possibility
to do things. When I was looking last time into the checkbox it for sure
need to more love, some part of the logic should be moved to the View.
Piotr
Ugh, Something has gone bad in the Basic components. Things like
CheckBox and RadioButton should be creating simple
and elements.
The ability to style everything belongs in a different set of components.
Basic is supposed to generate the simplest tree of HTMLElements even if
they can't be
I typically use the strand as the central dispatcher for intra-bead
communication. Sometimes an event from a bead conflicts with an event
dispatched by the strand to the "outside". For example, if a bead were to
need to send a "change" event and another bead was listening for that
event, "change"
Hi Carlos,
I think you should start looking into the Basic module and later make an
upgrades to Express once you have all components visually created. I would
not think on that stage about how we implement them rather look how they
look like currently.
1) Create small app or run example with
Hi Guys,
I just looked into the Maven latest build [1] and I see errors reported in
module Core. Build itself is not failing, but it should be actually.
Just search console build using [ERROR] [2]. The worse thing is that I'm
not getting those problems in my local Maven build.
[1]
Hi,
I'm trying to find a valid workflow to start working in two initial faces
for Royale components.
I'm talking about to generate some kind of UI sheet with all controls and a
basic wireframe style and another one that would be what more people will
be using as default in Royale. From here,
For 1) the rule already is that if you want to access an implicit bead you
have to explicitly declare it. So if a bead is normally brought in via
CSS, you instead declare that bead on the strand and make adjustments.
UIBase doesn't care how the beads get placed on the strand, and all bead
loading
I’ve created a branch data_grid_update that contains my proposed fix to this.
You can see usage here [1].
[1] https://github.com/yishayw/Examples/blob/DataGrid_force_change/Examples.mxml
From: Yishay Weiss
Sent: Monday, October 30,
12 matches
Mail list logo