Re: [FlexJS] rowIndex in item renderer

[Alex Harui]

On 12/10/16, 10:02 PM, "Yishay Weiss"  wrote:

>
>
>From: Yishay Weiss
>Sent: Sunday, December 11, 2016 8:01 AM
>To: Carlos Rovira
>Subject: RE: [FlexJS] rowIndex in item renderer
>
>
>Try reading index instead of rowIndex. rowIndex doesn’t look like it gets
>updated which is probably a bug. Also, try overriding function set data()
>for displaying data and index based info.
>

Hmm.  Looks like some of these interfaces need some cleaning up.
IItemRenderer shouldn't have listData, DataItemRenderer probably doesn't
need quite so many properties.

FWIW, whenever you need more properties passed to the ItemRenderer, you
can replace the IDataProviderItemRendererMapper and pass more things into
the IItemRenderer.

-Alex

Re: [LAST CALL] Flex SDK 4.16

[OmPrakash Muppirala]

Hmm, I dint realize there was a 4.16 branch.  I checked it into develop.
Should I cherry pick them into 4.16 branch?

On Sat, Dec 10, 2016 at 10:36 PM, Justin Mclean 
wrote:

> Hi,
>
> > I don't see my changes to installer.xml in this RC.  Did you get the
> latest
> > code before building the RC?
>
> I made the release before you checked in the fix.
>
> However I don’t see any changes to the installer.xml in the 4.16 release
> branch?
>
> Thanks,
> Justin

Re: [LAST CALL] Flex SDK 4.16

[Justin Mclean]

Hi,

> I don't see my changes to installer.xml in this RC.  Did you get the latest
> code before building the RC?

I made the release before you checked in the fix. 

However I don’t see any changes to the installer.xml in the 4.16 release branch?

Thanks,
Justin

Re: [LAST CALL] Flex SDK 4.16

[OmPrakash Muppirala]

I don't see my changes to installer.xml in this RC.  Did you get the latest
code before building the RC?

Thanks,
Om

On Sat, Dec 10, 2016 at 12:13 PM, Justin Mclean 
wrote:

> Hi,
>
> Just to make sure everything is working before we make an official release
> candidate I’ve up up an RC0 here:
> https://dist.apache.org/repos/dist/dev/flex/sdk/4.16.0/rc0/
>
> It would be great if people could take a look and report back any issues
> they find.
>
> Thanks,
> Justin

FW: [FlexJS] rowIndex in item renderer

[Yishay Weiss]

From: Yishay Weiss
Sent: Sunday, December 11, 2016 8:01 AM
To: Carlos Rovira
Subject: RE: [FlexJS] rowIndex in item renderer


Try reading index instead of rowIndex. rowIndex doesn’t look like it gets 
updated which is probably a bug. Also, try overriding function set data() for 
displaying data and index based info.



From: Carlos Rovira
Sent: Saturday, December 10, 2016 8:00 PM
To: dev@flex.apache.org
Subject: [FlexJS] rowIndex in item renderer



Hi,

I have a IR extended from MXMLItemRenderer, so I should have "rowIndex"
property available, but I get nothing when I tried to write the value to
span tag.
Is this variable updated?

What I wan to get is the row index printed in the IR, how is the most safe
way to get it?

additionaly, If I want to make a subcomponent in the MXML IR to output
based on rowIndex how could I get this done? (i.e : output only if is the
first row in the list)

--
Carlos Rovira
http://about.me/carlosrovira

Re: [LAST CALL] Flex SDK 4.16

[Justin Mclean]

Hi,

Just to make sure everything is working before we make an official release 
candidate I’ve up up an RC0 here:
https://dist.apache.org/repos/dist/dev/flex/sdk/4.16.0/rc0/

It would be great if people could take a look and report back any issues they 
find.

Thanks,
Justin

[FlexJS] rowIndex in item renderer

[Carlos Rovira]

Hi,

I have a IR extended from MXMLItemRenderer, so I should have "rowIndex"
property available, but I get nothing when I tried to write the value to
span tag.
Is this variable updated?

What I wan to get is the row index printed in the IR, how is the most safe
way to get it?

additionaly, If I want to make a subcomponent in the MXML IR to output
based on rowIndex how could I get this done? (i.e : output only if is the
first row in the list)

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: flex-asjs git commit: Change innerHTML for a textNode to avoid remove text when using beads that “append” html tags

[Carlos Rovira]

Hi Piotr,

this change is to handle the case where a tag node has mxml inner elements
or has simple text. So normaly what you say is true, but here we are
handling if user wants text (so creating a text node) or if he wants other
nested tags (something I was struggling to get for the last month and
finaly this is the way to do it)



2016-12-10 17:49 GMT+01:00 Piotr Zarzycki :

> Hi Carlos,
>
> Is it creation of internal elements shouldn't be in createElement instead
> in some setter?
>
> Piotr
>
> On Sat, Dec 10, 2016, 17:36  wrote:
>
> > Repository: flex-asjs
> > Updated Branches:
> >   refs/heads/develop 07dfd97bb -> 9b467ea51
> >
> >
> > Change innerHTML for a textNode to avoid remove text when using beads
> that
> > “append” html tags
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/9b467ea5
> > Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/9b467ea5
> > Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/9b467ea5
> >
> > Branch: refs/heads/develop
> > Commit: 9b467ea5129b93d12e785b7a73de7a60303a01c2
> > Parents: 07dfd97
> > Author: Carlos Rovira 
> > Authored: Sat Dec 10 17:36:13 2016 +0100
> > Committer: Carlos Rovira 
> > Committed: Sat Dec 10 17:36:13 2016 +0100
> >
> > --
> >  .../HTML/src/main/flex/org/apache/flex/html/Span.as   | 14
> --
> >  1 file changed, 12 insertions(+), 2 deletions(-)
> > --
> >
> >
> >
> > http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> 9b467ea5/frameworks/projects/HTML/src/main/flex/org/apache/
> flex/html/Span.as
> > --
> > diff --git
> > a/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> > b/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> > index 1771948..7dbe220 100644
> > --- a/frameworks/projects/HTML/src/main/flex/org/apache/flex/
> html/Span.as
> > +++ b/frameworks/projects/HTML/src/main/flex/org/apache/flex/
> html/Span.as
> > @@ -70,13 +70,23 @@ package org.apache.flex.html
> >
> > COMPILE::JS
> > {
> > -   if(MXMLDescriptor == null) {
> > -   element.innerHTML = text;
> > +   if(MXMLDescriptor == null)
> > +{
> > +if(textNode == null)
> > +{
> > +textNode = document.createTextNode('') as Text;
> > +element.appendChild(textNode);
> > +}
> > +
> > +textNode.nodeValue = value;
> > }
> > }
> >
> > }
> >
> > +COMPILE::JS
> > +private var textNode:Text;
> > +
> >  /**
> >   * @flexjsignorecoercion org.apache.flex.core.
> WrappedHTMLElement
> >   */
> >
> >
>



-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: flex-asjs git commit: Change innerHTML for a textNode to avoid remove text when using beads that “append” html tags

[Piotr Zarzycki]

Hi Carlos,

Is it creation of internal elements shouldn't be in createElement instead
in some setter?

Piotr

On Sat, Dec 10, 2016, 17:36  wrote:

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop 07dfd97bb -> 9b467ea51
>
>
> Change innerHTML for a textNode to avoid remove text when using beads that
> “append” html tags
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/9b467ea5
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/9b467ea5
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/9b467ea5
>
> Branch: refs/heads/develop
> Commit: 9b467ea5129b93d12e785b7a73de7a60303a01c2
> Parents: 07dfd97
> Author: Carlos Rovira 
> Authored: Sat Dec 10 17:36:13 2016 +0100
> Committer: Carlos Rovira 
> Committed: Sat Dec 10 17:36:13 2016 +0100
>
> --
>  .../HTML/src/main/flex/org/apache/flex/html/Span.as   | 14 --
>  1 file changed, 12 insertions(+), 2 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/9b467ea5/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> --
> diff --git
> a/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> b/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> index 1771948..7dbe220 100644
> --- a/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> +++ b/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/Span.as
> @@ -70,13 +70,23 @@ package org.apache.flex.html
>
> COMPILE::JS
> {
> -   if(MXMLDescriptor == null) {
> -   element.innerHTML = text;
> +   if(MXMLDescriptor == null)
> +{
> +if(textNode == null)
> +{
> +textNode = document.createTextNode('') as Text;
> +element.appendChild(textNode);
> +}
> +
> +textNode.nodeValue = value;
> }
> }
>
> }
>
> +COMPILE::JS
> +private var textNode:Text;
> +
>  /**
>   * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
>   */
>
>

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

[flex capacitor]

In Radiate I convert Flex UIComponents to HTML components and had this
problem. I made an option to allow styles to be defined inline or in a
style sheet. If the option was stylesheet then if the component had an id
the styles were declared by id. This included position, size, etc:

#myLabel {
 style: value;
}

If the component didn't have an id too bad. I'd give it an id using Flex
naming utils class and again declare styles there.

But I added an option to let developers override the styles per component
and that might work here.

So you would have a components style declaration by id and then in Radiate
there is a user styles field. Any values in that field would be declared in
the style declaration but they would be placed at the end. Everybody knows
that last declaration wins, even grandma.

#myLabel {
 style: value; /*define by framework */
 style: newValue; /*  defined by user */
}

You could also declare style: inherit and I think that resets the value.
Yes, the style is declared twice. Who cares. But yes to look pretty, I plan
to remove the first declaration or comment it out in a future update.

If Flex JS made some combination of class and class#id it might be an
option so that you can declare your own style declaration afterwards and
restore the defaults. Yes there might be two style declarations but at
least then they wouldn't be defined inline.

On Dec 2, 2016 11:52 AM, "Carlos Rovira" 
wrote:

> Hi Josh,
>
> right. As I get some few components more, I think I could refactor removing
> the dependencies from some HTML comps so we could manage better MDL set. So
> for example, I will took things from Core, like UIBase or ContainerBase
> while removing html things like TextButton, Container and so on...(in the
> end removing HTML.swc dependency at all). In this way I think MDL will be
> more independent.
>
> 2016-12-02 16:55 GMT+01:00 Josh Tynjala :
>
> > Alex's first point about using the same beads, but not subclassing sounds
> > cleaner to me, Carlos. Kind of the same idea from the other day where all
> > components should be possible to recreate from UIBase with the right set
> of
> > beads. You should consider trying that out for MDL.
> >
> > - Josh
> >
> > On Dec 1, 2016 11:09 PM, "Alex Harui"  wrote:
> >
> > > Re-ordering your post so I can address higher-level points first:
> > >
> > >
> > > On 12/1/16, 4:55 PM, "carlos.rov...@gmail.com on behalf of Carlos
> > Rovira"
> > >  wrote:
> > > >
> > > >But Basic set is at the core of
> > > >all. Is at the core of MDL set
> > > >
> > > >
> > >
> > > This statement doesn't have to be true, and makes me think that the old
> > > Flex SDK mentality is persisting.  IMO, the MDL set has no obligation
> to
> > > subclass the Basic set.  The top-level components in the Basic set are
> > > supposed to be compositions of beads.  MDL can just compose the same or
> > > different beads without having to subclass Basic components.
> > >
> > > One of the problems of having a core and inheritance is that you have
> to
> > > get it right, but often there isn't one right answer.
> > >
> > > >I think
> > > >Basic set (as is) will not be used at all since the final visuals are
> > not
> > > >production ready, so you know people will need this level of
> > customization
> > > >or they will never join FleJS for sure. and here you have the first
> > > >example of many
> > > >of the styles in flexjs needs to be removed in order to get the MDL
> > branch
> > > >working ok, and so will happen with others like Bootstrap, and so
> on...
> > > >Only if we create our own FlexJS style design could take into account
> > the
> > > >actual styles, but I think that if MDL or Bootstrap does not need all
> of
> > > >that, we should not need creating our own CSS set in the end (I can't
> > say
> > > >much more here since I'm not a CSS expert to affirm that, but based on
> > > >what
> > > >I see...is clear that it's the reality).
> > > >
> > >
> > > In my mind, there are going to be two kinds of themes: pre-existing
> ones
> > > like MDL and custom ones like the themes that regular Flex SDK
> customers
> > > used to brand their applications.  In the second kind, I don't think it
> > > matters as much as to what default styles are. Folks will simply
> override
> > > the defaults in their themes.
> > >
> > > I was a bit surprised that MDL didn't override everything we set as
> > > defaults for HTML.swc.  That means to me that if someone has certain
> > > styles set elsewhere, even in their browser settings, that could cause
> > > really strange and unexpected results.  But OK, that's the way it is,
> and
> > > so we should think of other ways to have a default look for HTML.swc,
> > > although again, as I said above, the MDL library has no obligation to
> > > inherit from HTML.swc.
> > >
> > > If we really need to support more inheritance, 

Re: [FlexJS] How Binding works?

[Christofer Dutz]

Ah oh ... then I mixed up two things ;-)

The way I changed the maven plugin to allow setting of failure on warning is 
deffinitely the way to go, but there are other problems causing the warning to 
appear in the first place. 

So I’ll leave things the way they are now.

Chris


Am 10.12.16, 11:11 schrieb "carlos.rov...@gmail.com im Auftrag von Carlos 
Rovira" :

Hi Chris, VO = ValueObject a simple class to carry data.
I tried to say that the fix is needed since we want sometimes to quick
prototype and we can't always introducing ValueObjects. But I`ll introduced
that VOs for my example in MDL since I'm trying to create components that
adhiere to best practices.


2016-12-10 9:18 GMT+01:00 Christofer Dutz :

> hi Carlos,
>
> What  do you mean with VO? What does that abbreviation stand for?
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
>  Ursprüngliche Nachricht 
> Von: Carlos Rovira 
> Datum: 09.12.16 23:46 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] How Binding works?
>
> Hi,
>
> @Chris, Thanks for the quick fix, I tested it and it works now without.
> Although I think as Alex that a VO is better, I think that is not related
> to get the build working although there's a warning. Thanks! :)
>
> @Alex, as you mentioned the current IR is not working. So I think, I'll
> continue with the raw version as I understand you need to fix some
> internals. Thanks
>
>
>
>
> 2016-12-09 23:06 GMT+01:00 Christofer Dutz :
>
> > So I just pushed a new version which allows configuring if the build
> > should fail on warnings (default is false)
> >
> > Chris
> >
> > Am 09.12.16, 22:40 schrieb "Christofer Dutz"  >:
> >
> > Ok ... for now 2 is ok ... I’ll probably just add a config option to
> > allow „fail on warnings“ which defaults to false and can be turned on if
> > required.
> >
> > Chris
> >
> > Am 09.12.16, 22:31 schrieb "Alex Harui" :
> >
> >
> >
> > On 12/9/16, 1:08 PM, "Christofer Dutz" <
> christofer.d...@c-ware.de>
> > wrote:
> >
> > >I just comitted a fix that doesn’t make the build fail on a
> > return code
> > >of 2 (Didn’t know that 2 was also ok)
> >
> > I think 2 means that there were warnings but no errors.  That
> > gives folks
> > the option of failing on warnings if they do have a "no 
warnings"
> > policy.
> > In Ant, I use a Fail ant task to check for and allow both 
values.
> > Someone
> > can not do that and just fail on any non-zero which would fail 
if
> > there
> > were warnings.
> >
> > I don't know why the compilers do that.  Maybe they should have
> an
> > option
> > instead.  I think Java compiler has it as an option.
> >
> > Thanks,
> > -Alex
> >
> >
> >
> >
> >
> >
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05
> http://www.codeoscopic.com
> http://www.avant2.es
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le 
comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a 
nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.
>



-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted 

Re: [FlexJS] How Binding works?

[Carlos Rovira]

Hi Chris, VO = ValueObject a simple class to carry data.
I tried to say that the fix is needed since we want sometimes to quick
prototype and we can't always introducing ValueObjects. But I`ll introduced
that VOs for my example in MDL since I'm trying to create components that
adhiere to best practices.


2016-12-10 9:18 GMT+01:00 Christofer Dutz :

> hi Carlos,
>
> What  do you mean with VO? What does that abbreviation stand for?
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
>  Ursprüngliche Nachricht 
> Von: Carlos Rovira 
> Datum: 09.12.16 23:46 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] How Binding works?
>
> Hi,
>
> @Chris, Thanks for the quick fix, I tested it and it works now without.
> Although I think as Alex that a VO is better, I think that is not related
> to get the build working although there's a warning. Thanks! :)
>
> @Alex, as you mentioned the current IR is not working. So I think, I'll
> continue with the raw version as I understand you need to fix some
> internals. Thanks
>
>
>
>
> 2016-12-09 23:06 GMT+01:00 Christofer Dutz :
>
> > So I just pushed a new version which allows configuring if the build
> > should fail on warnings (default is false)
> >
> > Chris
> >
> > Am 09.12.16, 22:40 schrieb "Christofer Dutz"  >:
> >
> > Ok ... for now 2 is ok ... I’ll probably just add a config option to
> > allow „fail on warnings“ which defaults to false and can be turned on if
> > required.
> >
> > Chris
> >
> > Am 09.12.16, 22:31 schrieb "Alex Harui" :
> >
> >
> >
> > On 12/9/16, 1:08 PM, "Christofer Dutz" <
> christofer.d...@c-ware.de>
> > wrote:
> >
> > >I just comitted a fix that doesn’t make the build fail on a
> > return code
> > >of 2 (Didn’t know that 2 was also ok)
> >
> > I think 2 means that there were warnings but no errors.  That
> > gives folks
> > the option of failing on warnings if they do have a "no warnings"
> > policy.
> > In Ant, I use a Fail ant task to check for and allow both values.
> > Someone
> > can not do that and just fail on any non-zero which would fail if
> > there
> > were warnings.
> >
> > I don't know why the compilers do that.  Maybe they should have
> an
> > option
> > instead.  I think Java compiler has it as an option.
> >
> > Thanks,
> > -Alex
> >
> >
> >
> >
> >
> >
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05
> http://www.codeoscopic.com
> http://www.avant2.es
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.
>



-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [FlexJS] VO Constructor Bug

[Carlos Rovira]

Thanks Alex, that was driving me crazy. I'll try it today again

2016-12-10 1:03 GMT+01:00 Alex Harui :

> I think I see a semi-colon after ActorVO(actorName:String = null)
>
> On 12/9/16, 3:59 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi,
> >
> >this simple VO
> >
> >package vos
> >{
> >[Bindable]
> >public class ActorVO
> >{
> >public function ActorVO(actorName:String = null);
> >{
> >this.actorName = actorName;
> >}
> >
> >public var actorName:String = "";
> >}
> >}
> >
> >
> >is failing in something very basic:
> >
> >ActorVO.as(26): col: 4 The 'this' keyword can not be used in static
> >methods. It can only be used in instance methods, function closures, and
> >global code.
> >this.actorName = actorName;
> >^
> >/Users/carlosrovira/Dev/Flex/source/flexjs/flex-asjs/
> examples/flexjs/MDLEx
> >ample/src/main/flex/vos/ActorVO.as(26):
> >col: 21 Access of possibly undefined property actorName.
> >this.actorName = actorName;
> >^
> >[INFO]
> >
> >[INFO] BUILD FAILURE
> >
> >
> >or I'm missing something that I can't see at this night hours?...If the
> >later I'll be filling a bug tomorrow
> >
> >Thanks
> >
> >--
> >Carlos Rovira
> >http://about.me/carlosrovira
>
>


-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

AW: [FlexJS] How Binding works?

[Christofer Dutz]

hi Carlos,

What  do you mean with VO? What does that abbreviation stand for?

Chris



Von meinem Samsung Galaxy Smartphone gesendet.


 Ursprüngliche Nachricht 
Von: Carlos Rovira 
Datum: 09.12.16 23:46 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [FlexJS] How Binding works?

Hi,

@Chris, Thanks for the quick fix, I tested it and it works now without.
Although I think as Alex that a VO is better, I think that is not related
to get the build working although there's a warning. Thanks! :)

@Alex, as you mentioned the current IR is not working. So I think, I'll
continue with the raw version as I understand you need to fix some
internals. Thanks




2016-12-09 23:06 GMT+01:00 Christofer Dutz :

> So I just pushed a new version which allows configuring if the build
> should fail on warnings (default is false)
>
> Chris
>
> Am 09.12.16, 22:40 schrieb "Christofer Dutz" :
>
> Ok ... for now 2 is ok ... I’ll probably just add a config option to
> allow „fail on warnings“ which defaults to false and can be turned on if
> required.
>
> Chris
>
> Am 09.12.16, 22:31 schrieb "Alex Harui" :
>
>
>
> On 12/9/16, 1:08 PM, "Christofer Dutz" 
> wrote:
>
> >I just comitted a fix that doesn’t make the build fail on a
> return code
> >of 2 (Didn’t know that 2 was also ok)
>
> I think 2 means that there were warnings but no errors.  That
> gives folks
> the option of failing on warnings if they do have a "no warnings"
> policy.
> In Ant, I use a Fail ant task to check for and allow both values.
> Someone
> can not do that and just fail on any non-zero which would fail if
> there
> were warnings.
>
> I don't know why the compilers do that.  Maybe they should have an
> option
> instead.  I think Java compiler has it as an option.
>
> Thanks,
> -Alex
>
>
>
>
>
>


--

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.