Re: [Flex JS] Font support

[Carlos Rovira]

Hi Justin,

that's an important error. With things like that we can't call us 1.0

For include external sheets have you try to use  in
Constructor?
Search for an example in Dialog.as MDL class, there are others in other
libraries like CreateJS



2017-02-17 8:10 GMT+01:00 Justin Mclean :

> Hi,
>
> Also this which I though I'd try also fails to compile (assumes source is
> local):
>
> https://fonts.googleapis.com/css?family=Roboto; />
>
> How can you include external styles sheets located on other domains?
>
> Thanks,
> Justin
>
>
>


-- 

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 JS] Font support

[Justin Mclean]

Hi,

Also this which I though I'd try also fails to compile (assumes source is 
local):

https://fonts.googleapis.com/css?family=Roboto; />

How can you include external styles sheets located on other domains?

Thanks,
Justin

[Flex JS] Font support

[Justin Mclean]

Hi,

Trying to get fonts working in JS. Now I should be able to edit the produced 
HTML after it been generated to add fonts I need, but is there a way to link or 
@import fonts by referring to it the MXML?

Just for giggles I tried the following:


@import url('https://fonts.googleapis.com/css?family= Roboto');


And I get a stack trace error like so  Error: Internal error in ABC generator 
subsystem, when generating code for: 
/Users/justinmclean/IdeaProjects/FlexJSTest/src/FontFace.mxml: 
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:102)
…

Not that I expected that to work.

I also tried:


@font-face {
src: url("https://fonts.googleapis.com/css?family=Roboto;);
fontFamily: Roboto;
}


And got this rather strange error:

WARNING: 
/Users/justinmclean/IdeaProjects/FlexJSTest/target/javascript/bin/js-debug/FontFace.js:39:
 WARNING - attempted re-definition of type FontFace
found   : function (new:FontFace): undefined
expected: function (new:FontFace, string, 
(ArrayBuffer|ArrayBufferView|null|string), FontFaceDescriptors=): ?
FontFace = function() {

It seems you can’t call your main file FontFace.mxml.

Re-nameing it mean it can compile but the font fails to download with the error:
index.html:1 Failed to decode downloaded font: 
https://fonts.googleapis.com/css?family=Roboto
index.html:1 OTS parsing error: invalid version tag

Anyone got JS font to work in a FlexJS application?

Thanks,
Justin

[4.16.0] # Apache Flex SDK 4.16.0 nightly build 237: Successful

[flex . ci . builds]

flex-sdk_release-candidate - Build #237 - Successful

Changes since last build:
No changes

For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/237/.

[VOTE][CANCEL] Release Apache Flex SDK 4.16 RC2

[Justin Mclean]

Hi,

This vote is cancelled as an issue with asdocs / saxon9 was discovered.

Thanks,
Justin

Re: [FlexJS] Text binding showing undefined

[Alex Harui]

On 2/16/17, 2:21 PM, "Justin Mclean"  wrote:

>Hi,
>
>> It is totally fine, however, to have a TextModelWithEmptyStringDefaults.
>> And have Express use it and Harbs could use it in his app.  Again, what
>> percentage of the time in production will a label's text property not be
>> set to something other than “"?
>
>It would be a reasonably common with binding I think. (I ran into the
>issue reasonably quickly multiple times in this app I making). But there
>are work arounds so it's not a big issue.

Only if you haven't initialized your variables.

Flex definitely had checks for this, but IMO all these extra helpful bits
of code added up to something.

>
>Basically between creating a component and setting the value, if the
>values that is need to be set to comes from a HTTP call then the time
>between those two events could be noticeable by the user.

IMO, the framework doesn't know if you want to show the user a label that
is being filled via an HTTP call with "" or "Waiting for data..." or
something else, so it is presumptive to use up the code to assign "".

>
>I think it would be good idea to document all of these work arounds /
>fixes for common problems that Flex SDK or JS developers may run into.

Yep, we just need volunteers to help out.  We are also trying to remember
these things to add them to the Express components.  The goal is that
users of Express shouldn't hit these issues because that is where we add
more compensation code like folks are used to in Flex.  The premise is
that FlexJS won't be competitive if it has the overhead of Flex in JS.
FlexJS concepts like Beads, PAYG, etc in place to let someone get down to
the low-level if they need to.  And when you go low-level, you can't
assume much compensation code.

-Alex

Re: [FlexJS] Setting background colour at run time fails

[Justin Mclean]

Hi,

Looks good Peter, I'll give it a try in the next few days and come back with 
any feedback.

Thanks,
Justin

Re: [Flex JS] Padding not working as expected

[Justin Mclean]

Hi,

Anyone have thought on this?

It looks to be a serious bug to me and there’s no workaround except in the 
simplest cases.

One alternative is to wrap a component in 4 boxes to simulate the padding but 
that’s going to up your box/nest count really fast even for simple designs.

Thanks,
Justin

Re: [FlexJS] Text binding showing undefined

[Alex Harui]

On 2/16/17, 2:34 PM, "Harbs"  wrote:

>> Well, that's not PAYG (yes, I'm being picky).
>
>I disagree. For string it certainly is PAYG. There’s no extra cost. (and
>considering the three bytes of ‘=“”’ in the source code is getting petty
>IMO)

Pretty sure that uninitialized variables do not have any presence in
minified JS.  So every variable where you do this is adding

  foo.bar = "";

to the app.

> Adding an extra TextModelWithEmptyStringDefaults is totally unnecessary.
>
>> Again, what
>> percentage of the time in production will a label's text property not be
>> set to something other than “"?
>
>More than you’d think. We ran into this because we were using
>ImageAndTextButton without text. But it’s quite common to have components
>which get text or not at runtime.

Then use ImageButton.  Or swap in a different model with empty string
defaults for ImageAndTextButton.

For just one occurrence, you probably won't notice, But after we
initialize 100 or 1000 properties to "" you might notice.

My 2 cents,
-Alex

Re: [DISCUSS] Release Apache Flex SDK 4.16 RC2

[Alex Harui]

On 2/16/17, 12:32 AM, "Justin Mclean"  wrote:


>It looks like it hasn’t done a build yet and it still waiting on a
>pending slot. [1] 

OK, build finished and I ran the approval script on it and checked asdoc.
I'm good to go.

-Alex

[BlazeDS] landing in git version of BlazeDS

[Carlos Rovira]

Hi,

As I'm to start working on AMF library for FlexJS, I want to use apache
flex blazeds version and build with maven.
I use develop branch, and could build without problems
But see that in master there's an "apps" folder with some war examples. I
want to start from that in order to create examples that we could share in
the future with ease if we use the ones in the blazeds git folder and
people doesn't need to create additional things.

But don't understand

1.- why that folder is not in develop and only in master?

2.- snapshot from develop is 4.7.3, is the recomended version?

3.- could I build one of the apps? should I build from master all (blazeds
jars and examples) instead from develop? or maybe from a tag?

thanks


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

Re: [FlexJS] Text binding showing undefined

[Justin Mclean]

Hi,

> It is totally fine, however, to have a TextModelWithEmptyStringDefaults.
> And have Express use it and Harbs could use it in his app.  Again, what
> percentage of the time in production will a label's text property not be
> set to something other than “"?

It would be a reasonably common with binding I think. (I ran into the issue 
reasonably quickly multiple times in this app I making). But there are work 
arounds so it's not a big issue.

Basically between creating a component and setting the value, if the values 
that is need to be set to comes from a HTTP call then the time between those 
two events could be noticeable by the user.

I think it would be good idea to document all of these work arounds / fixes for 
common problems that Flex SDK or JS developers may run into.

Thanks,
Justin

Re: [Flex JS] Label's text gets trimmed

[Justin Mclean]

Hi,

> I think this is the normal way HTML works

No sure about that as if you do this:
Hi there

The space is displayed.

The generated HTML does include the space however so it does look like a HTML 
issue:
Hello, 
world

Thanks,
Justin

Re: [FlexJS][SpriteFlexJS][Maven] Integrating SprtiteFlexJS into Apache Flex problems

[Alex Harui]

On 2/16/17, 10:23 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:
>
>The big problem right now is that I can't get the project to find core
>html
>classes like "HTMLCanvasElement".

Did you verify that HTMLCanvasElement is in one of the SWCs?  SWCs are ZIP
files so unpack the ones you think have it and actually look.

HTH,
-Alex

Re: [FlexJS] Text binding showing undefined

[Alex Harui]

On 2/16/17, 12:00 PM, "Harbs"  wrote:

>I recently went this course in TextModel. By default, the text property
>was undefined which propagated to the view when it was never set. I
>changed it to 'private var _text:String = “”;' to set the default to an
>empty string.

Well, that's not PAYG (yes, I'm being picky).  It is probably ok for
String, but wouldn't be ok for an Array or Object.  The instnatiation and
assignment of non-scalar initial values happens on every instantiation.

It is totally fine, however, to have a TextModelWithEmptyStringDefaults.
And have Express use it and Harbs could use it in his app.  Again, what
percentage of the time in production will a label's text property not be
set to something other than ""?

It is also totally fine to create a version of Basic with lots of error
checking and other fault tolerance.  There is no one right answer.

IMO, in Justin's example, he is creating his own uninitialized variable
and assigning it via binding.  So default values in a TextModel won't
matter.

My 2 cents,
-Alex

Re: [FlexJS MDL] release build broken

[Alex Harui]

On 2/16/17, 12:34 PM, "Harbs"  wrote:

>When I’ve had these kinds of issues in my app, it’s because of minified
>renaming.

Yep, and there is code in one of the Binding classes that does some
trickery to look up a constant when minified.  That code might need to be
used in this scenario.

-Alex

[4.16.0] # Apache Flex SDK 4.16.0 nightly build 236: Fixed

[flex . ci . builds]

flex-sdk_release-candidate - Build #236 - Fixed

Changes since last build:
[Alex Harui] fix download cache


For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/236/.

[FlexJS]Routing

[Harbs]

The MDL demo app very nicely demonstrates something major missing from FlexJS: 
Routing.

The modern term for “deep linking” which we had in Flash is “routing”. The most 
common way to handle routing is by appending a has to a url and changing the 
address. That allows for navigating browser history, and can also load an app 
in a specific state.

I think we need a “RouterBead” to handle routing and correctly set hashtags 
when necessary and load an app into a specific state using the hashtags.

If you look at the NavigationLayoutContent in the example app, the hashes are 
actually being added (i.e. 
http://apacheflexbuild.cloudapp.net:8080/job/MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/bin/js-release/index.html#toggles_panel
 
).
 I assume that’s being added by the mdl js files. The hashes do not actually do 
anything, and clicking on the link actually loads the component without 
changing the address. Additionally, loading the app with the hash does not do 
anything other than start the app in the default state.

Thanks,
Harbs

Re: [FlexJS MDL] release build broken

[Harbs]

When I’ve had these kinds of issues in my app, it’s because of minified 
renaming.

Tangentially:
FWIW, I’m not sure how wise it is to use constants to specify the icon text. 
The minified version of just the definitions for the MaterialIconTypes is a 
full 77KB!

Until we have a way to stripped out unused constants during compilation, I 
think extra const definitions should be avoided.

Harbs

> On Feb 16, 2017, at 8:34 PM, Carlos Rovira  
> wrote:
> 
> Hi Harbs,
> 
> Thanks for seeing that.
> 
> @Pitor, I looked at the code and seems something related to binding,
> 
> 
>
>
> 
> 
>
>
>
>
> 
> The binding is not working and no text is retrieved. The output is:
> 
> 
> 
> So no text in the i element tag seems the binding not doing its work. Maybe
> some latest changes in binding caused this?
> 
> Thanks
> 
> 
> 2017-02-16 11:03 GMT+01:00 Harbs :
> 
>> 1. Go here: http://apacheflexbuild.cloudapp.net:8080/job/MDLExample/
>> lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/
>> bin/js-release/index.html > MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/
>> bin/js-release/index.html>
>> 
>> 2. Click on Toggles
>> 
>> You will see that the two IconToggles have no content. It seems like the
>> Material Design font is not beiing used for some reason in the release
>> build. The same thing works in the debug build.
>> 
>> Harbs
> 
> 
> 
> 
> -- 
> 
> 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] Text binding showing undefined

[Harbs]

I recently went this course in TextModel. By default, the text property was 
undefined which propagated to the view when it was never set. I changed it to 
'private var _text:String = “”;' to set the default to an empty string.

Harbs

> On Feb 16, 2017, at 8:58 PM, Carlos Rovira  
> wrote:
> 
> Hi, I was thinking the same as Om. Only setting a default would to the trick
> 
> thanks
> 
> 2017-02-16 19:56 GMT+01:00 OmPrakash Muppirala :
> 
>> On Thu, Feb 16, 2017 at 10:51 AM, Alex Harui  wrote:
>> 
>>> 
>>> 
>>> On 2/16/17, 10:37 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira"
>>> 
>>> wrote:
>>> 
 Hi Alex,
 
 IMHO, this is not PAYG, no body wants "undefined" as a possible output.
 In my way of thinking this could be very radical way and take PAYG to
>> the
 latest extreme.
 In that way almost all things are PAYG and should not be implemented in
 basic set ;) ... what do you think?
>>> 
>>> You are welcome to build in a test for null and undefined in your
>>> component sets.  The way I think of it is: in production, how often is
>>> null or undefined going to be assigned to a label?  I would think it
>> would
>>> be very rare, if at all, but I could be wrong.  If you use Model/View,
>>> have the model and its validators prevent null/undefined from being a
>>> value that the view is bound to.
>>> 
>> 
>> I don't think a test for null or undefined is required.  That implies code
>> running needlessly.
>> I am guessing that having a sensible default would solve this problem.
>> That does not run code needlessly.
>> 
>> Thanks,
>> Om
>> 
>> 
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
 
 2017-02-16 2:55 GMT+01:00 Alex Harui :
 
> The Basic components don't test for unexpected inputs.  It isn't PAYG.
> We
> should try to remember to add some defensive code for common cases to
> Express.
> 
> -Alex
> 
> On 2/15/17, 3:31 PM, "Justin Mclean" 
>> wrote:
> 
>> Hi,
>> 
>> This application when run displays “undefined” in text on the screen.
>> 
>> 
>> http://ns.adobe.com/mxml/2009;
>>   xmlns:js="library://ns.apache.org/flexjs/basic"
>>   xmlns:local="*">
>> 
>>   
>>   
>>   
>> 
>>   
>>   
>>   
>>   
>>   
>>   
>>   
>>   
>> 
>> 
>> 
>> The component code:
>> 
>> 
>> http://ns.adobe.com/mxml/2009;
>>   xmlns:js="library://ns.apache.org/flexjs/basic">
>> 
>>   
>> 
>>   
>>   
>>   
>> 
>>   
>> 
>> 
>> 
>> This can be worked around by doing this in the component:
>> 
>>   
>> 
>> But still looks like a bug / is unexpected behaviour to me. What do
> other
>> people think?
>> 
>> Thanks,
>> Justin
> 
> 
 
 
 --
 
 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 MDL] release build broken

[piotrz]

Hi Carlos,

I will look into that through the weekend. When I was doing Binding changes
I have to admit that I didn't check release version. But I think it's
something in the compiler.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-release-build-broken-tp59537p59564.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Text binding showing undefined

[Carlos Rovira]

Hi, I was thinking the same as Om. Only setting a default would to the trick

thanks

2017-02-16 19:56 GMT+01:00 OmPrakash Muppirala :

> On Thu, Feb 16, 2017 at 10:51 AM, Alex Harui  wrote:
>
> >
> >
> > On 2/16/17, 10:37 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> > 
> > wrote:
> >
> > >Hi Alex,
> > >
> > >IMHO, this is not PAYG, no body wants "undefined" as a possible output.
> > >In my way of thinking this could be very radical way and take PAYG to
> the
> > >latest extreme.
> > >In that way almost all things are PAYG and should not be implemented in
> > >basic set ;) ... what do you think?
> >
> > You are welcome to build in a test for null and undefined in your
> > component sets.  The way I think of it is: in production, how often is
> > null or undefined going to be assigned to a label?  I would think it
> would
> > be very rare, if at all, but I could be wrong.  If you use Model/View,
> > have the model and its validators prevent null/undefined from being a
> > value that the view is bound to.
> >
>
> I don't think a test for null or undefined is required.  That implies code
> running needlessly.
> I am guessing that having a sensible default would solve this problem.
> That does not run code needlessly.
>
> Thanks,
> Om
>
>
> >
> > My 2 cents,
> > -Alex
> >
> > >
> > >2017-02-16 2:55 GMT+01:00 Alex Harui :
> > >
> > >> The Basic components don't test for unexpected inputs.  It isn't PAYG.
> > >>We
> > >> should try to remember to add some defensive code for common cases to
> > >> Express.
> > >>
> > >> -Alex
> > >>
> > >> On 2/15/17, 3:31 PM, "Justin Mclean" 
> wrote:
> > >>
> > >> >Hi,
> > >> >
> > >> >This application when run displays “undefined” in text on the screen.
> > >> >
> > >> >
> > >> >http://ns.adobe.com/mxml/2009;
> > >> >xmlns:js="library://ns.apache.org/flexjs/basic"
> > >> >xmlns:local="*">
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >The component code:
> > >> >
> > >> >
> > >> >http://ns.adobe.com/mxml/2009;
> > >> >xmlns:js="library://ns.apache.org/flexjs/basic">
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >This can be worked around by doing this in the component:
> > >> >
> > >> >
> > >> >
> > >> >But still looks like a bug / is unexpected behaviour to me. What do
> > >>other
> > >> >people think?
> > >> >
> > >> >Thanks,
> > >> >Justin
> > >>
> > >>
> > >
> > >
> > >--
> > >
> > >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] Text binding showing undefined

[OmPrakash Muppirala]

On Thu, Feb 16, 2017 at 10:51 AM, Alex Harui  wrote:

>
>
> On 2/16/17, 10:37 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> 
> wrote:
>
> >Hi Alex,
> >
> >IMHO, this is not PAYG, no body wants "undefined" as a possible output.
> >In my way of thinking this could be very radical way and take PAYG to the
> >latest extreme.
> >In that way almost all things are PAYG and should not be implemented in
> >basic set ;) ... what do you think?
>
> You are welcome to build in a test for null and undefined in your
> component sets.  The way I think of it is: in production, how often is
> null or undefined going to be assigned to a label?  I would think it would
> be very rare, if at all, but I could be wrong.  If you use Model/View,
> have the model and its validators prevent null/undefined from being a
> value that the view is bound to.
>

I don't think a test for null or undefined is required.  That implies code
running needlessly.
I am guessing that having a sensible default would solve this problem.
That does not run code needlessly.

Thanks,
Om


>
> My 2 cents,
> -Alex
>
> >
> >2017-02-16 2:55 GMT+01:00 Alex Harui :
> >
> >> The Basic components don't test for unexpected inputs.  It isn't PAYG.
> >>We
> >> should try to remember to add some defensive code for common cases to
> >> Express.
> >>
> >> -Alex
> >>
> >> On 2/15/17, 3:31 PM, "Justin Mclean"  wrote:
> >>
> >> >Hi,
> >> >
> >> >This application when run displays “undefined” in text on the screen.
> >> >
> >> >
> >> >http://ns.adobe.com/mxml/2009;
> >> >xmlns:js="library://ns.apache.org/flexjs/basic"
> >> >xmlns:local="*">
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >The component code:
> >> >
> >> >
> >> >http://ns.adobe.com/mxml/2009;
> >> >xmlns:js="library://ns.apache.org/flexjs/basic">
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >This can be worked around by doing this in the component:
> >> >
> >> >
> >> >
> >> >But still looks like a bug / is unexpected behaviour to me. What do
> >>other
> >> >people think?
> >> >
> >> >Thanks,
> >> >Justin
> >>
> >>
> >
> >
> >--
> >
> >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 Summit] Preparing the schedule

[Carlos Rovira]

Hi,

this days I was looking how to manage a travel to Miami, I'm still looking
at it, but it seems near impossible to left all my duties (home, work) for
at least 3-4 days. So, I can prepare a talk but do it in remote from
Madrid? What do you think?

Let me know if that could be an option.

A part from that, love Om's idea about a hackathon, that would be great to
demonstrate the power of FlexJS and how easy could be to translate from a
pure JS world to a FlexJS world. I must say that talking with different
people doesn't see FlexJS an option since they think we lost all the JS
world out there. But if we make a session where someone make a FlexJS lib
from some JS known library, it could be really good to show to the world :)




2017-02-16 10:34 GMT+01:00 Harbs :

> I don’t know that I will able to be there on Friday either.
>
> I would prefer to either stay later on Thursday to do what we can, or do
> it on Wednesday. I doubt I will be attending too many presentations. The
> extent of my participation of ApacheCon besides for Flex will probably just
> be to meet the other Apache folks in person.
>
> Harbs
>
> > On Feb 16, 2017, at 10:30 AM, piotrz  wrote:
> >
> > Hi,
> >
> > If I manage to come to the conference probably I won't be able to stay on
> > friday due to flight back. Monday would be same.
> >
> > Piotr
> >
> >
> >
> > -
> > Apache Flex PMC
> > piotrzarzyck...@gmail.com
> > --
> > View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-Summit-Preparing-
> the-schedule-tp59477p59527.html
> > Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
>


-- 

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] Text binding showing undefined

[Alex Harui]

On 2/16/17, 10:37 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>IMHO, this is not PAYG, no body wants "undefined" as a possible output.
>In my way of thinking this could be very radical way and take PAYG to the
>latest extreme.
>In that way almost all things are PAYG and should not be implemented in
>basic set ;) ... what do you think?

You are welcome to build in a test for null and undefined in your
component sets.  The way I think of it is: in production, how often is
null or undefined going to be assigned to a label?  I would think it would
be very rare, if at all, but I could be wrong.  If you use Model/View,
have the model and its validators prevent null/undefined from being a
value that the view is bound to.

My 2 cents,
-Alex

>
>2017-02-16 2:55 GMT+01:00 Alex Harui :
>
>> The Basic components don't test for unexpected inputs.  It isn't PAYG.
>>We
>> should try to remember to add some defensive code for common cases to
>> Express.
>>
>> -Alex
>>
>> On 2/15/17, 3:31 PM, "Justin Mclean"  wrote:
>>
>> >Hi,
>> >
>> >This application when run displays “undefined” in text on the screen.
>> >
>> >
>> >http://ns.adobe.com/mxml/2009;
>> >xmlns:js="library://ns.apache.org/flexjs/basic"
>> >xmlns:local="*">
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >The component code:
>> >
>> >
>> >http://ns.adobe.com/mxml/2009;
>> >xmlns:js="library://ns.apache.org/flexjs/basic">
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >This can be worked around by doing this in the component:
>> >
>> >
>> >
>> >But still looks like a bug / is unexpected behaviour to me. What do
>>other
>> >people think?
>> >
>> >Thanks,
>> >Justin
>>
>>
>
>
>-- 
>
>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 JS] Label's text gets trimmed

[OmPrakash Muppirala]

Setting this style in CSS should fix this issue:

white-space: pre
or
white-space: pre-wrap

More options here: https://www.w3schools.com/cssref/pr_text_white-space.asp

Thanks,
Om

2017-02-16 10:39 GMT-08:00 Carlos Rovira :

> Hi Justing, I think this is the normal way HTML works.
> HTML removes whitespaces. If you put lots of whitespace, HTML will remove
> them.
> So I think no much to do there for this kind of trys
>
> 2017-02-16 7:15 GMT+01:00 Justin Mclean :
>
> > Hi,
> >
> > This:
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > Gives this: (removing the space)
> > Hello,world
> >
> > Rather than the expected:
> > Hello, world
> >
> > In this case you could of course do something like this (although it's
> not
> > quite the same):
> >
> >  > tools” />
> >
> > But there are other cases where this is not so easy to solve and spaces
> > are needed on either side.
> >
> > Is there any reason text labels are trimmed? Is this a bug?
> >
> > Thanks,
> > Justin
>
>
>
>
> --
>
> 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 JS] Label's text gets trimmed

[Carlos Rovira]

Hi Justing, I think this is the normal way HTML works.
HTML removes whitespaces. If you put lots of whitespace, HTML will remove
them.
So I think no much to do there for this kind of trys

2017-02-16 7:15 GMT+01:00 Justin Mclean :

> Hi,
>
> This:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> Gives this: (removing the space)
> Hello,world
>
> Rather than the expected:
> Hello, world
>
> In this case you could of course do something like this (although it's not
> quite the same):
>
>  tools” />
>
> But there are other cases where this is not so easy to solve and spaces
> are needed on either side.
>
> Is there any reason text labels are trimmed? Is this a bug?
>
> Thanks,
> Justin




-- 

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] Text binding showing undefined

[Carlos Rovira]

Hi Alex,

IMHO, this is not PAYG, no body wants "undefined" as a possible output.
In my way of thinking this could be very radical way and take PAYG to the
latest extreme.
In that way almost all things are PAYG and should not be implemented in
basic set ;) ... what do you think?

2017-02-16 2:55 GMT+01:00 Alex Harui :

> The Basic components don't test for unexpected inputs.  It isn't PAYG.  We
> should try to remember to add some defensive code for common cases to
> Express.
>
> -Alex
>
> On 2/15/17, 3:31 PM, "Justin Mclean"  wrote:
>
> >Hi,
> >
> >This application when run displays “undefined” in text on the screen.
> >
> >
> >http://ns.adobe.com/mxml/2009;
> >xmlns:js="library://ns.apache.org/flexjs/basic"
> >xmlns:local="*">
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >The component code:
> >
> >
> >http://ns.adobe.com/mxml/2009;
> >xmlns:js="library://ns.apache.org/flexjs/basic">
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >This can be worked around by doing this in the component:
> >
> >
> >
> >But still looks like a bug / is unexpected behaviour to me. What do other
> >people think?
> >
> >Thanks,
> >Justin
>
>


-- 

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.

[FlexJS][SpriteFlexJS][Maven] Integrating SprtiteFlexJS into Apache Flex problems

[Carlos Rovira]

Hi,

One of the efforts I'm doing is to get Lizhi's SpriteFlexJS *compliant*
with Apache FlexJS

To make that I put the current project inside "projects" folder with the
other libraries. I added license headers as well and then try to make it
building with Maven.

The big problem right now is that I can't get the project to find core html
classes like "HTMLCanvasElement".

So I created a branch "feature/spriteflexjs-refactor", with only the basic
project structure and 1 AS file that references some of the JS missing
classes.

Could someone take a look and see what's happening?

My bet is that there's some bug that make this impossible to accomplish at
the moment

Thanks

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

Re: [FlexJS] - Is FlexJS ready for production?

[Carlos Rovira]

Hi,

I will make a new thread for the current problem of spriteflexjs library
compilation since this is not in topic

2017-02-15 23:51 GMT+01:00 Christofer Dutz :

> Well the “type” is what we choose … also we can change the “classifier”s …
> the scope however is Maven-defined and we currently have to stick to that.
> But I’m happy to change naming, if that makes things easier.
>
> Chris
>
> Am 15.02.17, 23:48 schrieb "Alex Harui" :
>
>
>
> On 2/15/17, 1:09 PM, "Christofer Dutz" 
> wrote:
>
> >Ok … gee … think I still haven’t understood this completely ☹
>
> Yeah, it is a bit tricky.  I've been wondering whether the terms we
> currently use "typedefs", "externs", "runtime", "provided" are Maven
> standards or whether we can change some of them.
>
> In the dual branch, I am currently changing things so the Core.swc and
> CoreJS.swc are more like peers.  They both contain .JS files, but the
> library.swf in Core is for SWF and the library.swf in CoreJS is for
> JS.  I
> just want to get this working now, cut a release, then look into
> packing
> everything into one SWC.
>
> In light of that, my latest attempt to make categories for SWCs says
> that
> there are categories like:
>
> 1) External "Platform and JS Framework API" swcs.
> Playerglobal
> Airglobal
> Js
> Jquery
> Createjs
> Most of the flex-typedefs except for GCL.
>
> 2) External "JS Framework SWCs with SWF Mocks"
> We don't have any in the main repos but in flex-tourjs the
> BarcodeScanner
> makes a SWC like this.
>
> 3) Google Closure Library External SWCs
> GCL.swc
> Someday, some others.
>
> 4) SWF SWCs
> Core
> Binding
> Etc.
>
> 5) JS SWCs
> CoreJS
> BindingJS
> Etc.
>
> Bucket 1 always goes on the external-library-path for SWF and JS.
> Different ones are used for JS vs SWF.
> Bucket 2 goes on the external-library-path for JS, but on the
> library-path
> for SWF
> Bucket 3 goes on the library-path for JS and is not used for SWF
> unless it
> has a SWF Mock
> Bucket 4 goes on the external-library-path for SWC
> Bucket 4 goes on the library-path for SWF
> Bucket 5 goes on the library-path for cross-compiling to JS
> Bucket 5 goes on the external-library-path for building the library.swf
> for a JS.swc although it is probably ok if it is on the library-path.
>
> From another perspective, the JS within a SWC either uses goog.require
> or
> not.  GCL.swc uses goog.require, as will other GCL-compatible code,
> and as
> our JS files do.  That's why they go on the library-path for JS.  But
> when
> building a SWF, you either want the code from a SWC's library.swf in
> your
> application so you use library-path or you don't and you use
> -external-library-path.
>
> This makes me think we need an easier-to-understand way to mark what
> is in
> a SWC and have the Mojo figure it out from there.  I think we are
> currently using
> Typedefs + runtime to mean that it is meant for JS but doesn't use
> goog.require
> Typedefs by itself means that is meant for JS and uses goog.require
> Provided and Runtime seem to have the same meaning?
> If no typedefs it contains runnable ABC
> If no typedefs but provided it is bucket 1 for SWF.
>
> I think we just want to mark whether a SWC contains JS and/or runnable
> ABC
> and whether it contains goog.require or not.  I'm not sure we have a
> combination right now for bucket 2, and the keywords might not have
> enough
> meaning to others.  Can we use different keywords?  Classifiers like
> "JS",
> "ABC", "JS+ABC", Scope of "usesGoog"?
>
> 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.

[4.16.0] # Apache Flex SDK 4.16.0 nightly build 235: Failure

[flex . ci . builds]

flex-sdk_release-candidate - Build #235 - Failure

Changes since last build:
[jmclean] Hard code saxon jar name so ant scripts work


For more information, check the console output at 
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/235/.

Re: [VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[Alex Harui]

On 2/16/17, 7:34 AM, "Josh Tynjala"  wrote:
>
>One thing worth mentioning is that you cannot go to classes that come from
>SWC files (including framework classes in the SDK). Sometimes, SWC files
>include the original source path, but I've noticed that it's almost always
>missing, so I haven't added code to resolve that.

What is your plan to solve that?  FWIW, we have ways of generating DITA
and JSON information about the API surfaces.  These could be packages into
the SWCs like Fat-SWCs if that will help.  There is no guarantee the
source files for third-party libraries will be available.

-Alex 

Re: [VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[Josh Tynjala]

Any directories specified with the source-path compiler option, plus any
classes accessible from the root path (such as a "src" directory) of the
main class.

- Josh

On Thu, Feb 16, 2017 at 7:51 AM, OK  wrote:

> Hi Josh,
>
> >One thing worth mentioning is that you cannot go to classes that come from
> SWC files (including >framework classes in the SDK).
> Could you give me an example of such a framework class SWC?
>
> >If a class is on the source-path, it should resolve for goto definition.
> What is your understanding of 'source-path' in this case?
>
> Thank you!
>
> Olaf
>
>
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/VSCode-NextGenAS-Issues-
> with-IntelliSense-Goto-Definition-Ctrl-Click-and-
> auto-imports-tp59541p59547.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS, MDL] Layout Problems

[OK]

>If the Basic set has a component that MDL doesn't, MDL doesn't want you to
use
>that component.  Or am I wrong about that?

The problem is that MDL doesn't implement the complete Material Design spec.
There's a lack of e.g. DropDown, DatePicker and maybe something other...
If MDL would represent the complete spec I think there're would be no need
to mix components.

Olaf



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59550.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[Josh Tynjala]

> If the Basic set has a component that MDL doesn't, MDL doesn't want you
to use that component.  Or am I wrong about that?

MDL is a work in progress, much like FlexJS. Google hasn't necessarily
implemented every component that they want to add yet.

- Josh

Re: [DISCUSS] Release Apache Flex SDK 4.16 RC2

[Alex Harui]

On 2/16/17, 12:44 AM, "jus...@classsoftware.com"
 wrote:

>Hi,
>
>Looks like the issue is this, this has been running for 9+ hours and
>should probably be killed [1]
>
>May be a good idea to limit the time that job runs,it's usually fairly
>quick right?

Sure, go ahead and do it.  But some jobs do take a while on that server.

-Alex

Re: [VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[OK]

Hi Josh,

>One thing worth mentioning is that you cannot go to classes that come from
SWC files (including >framework classes in the SDK).
Could you give me an example of such a framework class SWC?

>If a class is on the source-path, it should resolve for goto definition.
What is your understanding of 'source-path' in this case?

Thank you!

Olaf





--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/VSCode-NextGenAS-Issues-with-IntelliSense-Goto-Definition-Ctrl-Click-and-auto-imports-tp59541p59547.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[Alex Harui]

On 2/16/17, 1:54 AM, "OK"  wrote:

>>I will try to create some beads which handle some mentioned cases above.
>
>From the FlexJS perspective folks of course could wondering why they can't
>remove this style but maybe from MDL perspective (including Material
>Design
>specs) this maybe makes sense [1].
>
>What I would like so say is that on the one hand we say "Use FlexJS MDL
>not
>the FlexJS way but the MDL way" and on the other hand we alyways want to
>mix
>components and different layout approaches.
>Don't know if this a bit inconsistent and confusing...

I've been wondering why folks want to mix MDL with other components.
AIUI, MDL is not just a theme, but an entire UX design and implementation.
 From the little I've read, there should not be any such thing as a
missing component or layout in MDL.  Every interaction and presentation
you want to make with your user has been specified and provided.  If the
Basic set has a component that MDL doesn't, MDL doesn't want you to use
that component.  Or am I wrong about that?

Now if you want to use the Basic set and just wished it looked better,
that's a different problem.  Trevor proposed some ideas for a better
default look.  I haven't had any time to try to implement that, although
I'd guess that there is a good chance it can't be done in Basic.  Basic is
mostly trying to have one element per component, which means that the
visuals that cannot be expressed in CSS probably can't be controlled
without a different component set with different views.  The Flat swc is
an example of where I boiled down the Flat Bootstrap theme into simpler
pieces.  Something like that may be what we do to support Trevor's
proposal.

My 2 cents,
-Alex

Re: [VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[Josh Tynjala]

Just like when you give a type to an ActionScript variable, MXML completion
includes every available class. You should be able to specify an XML
namespace to filter, though. Type  wrote:

> Hi Olaf,
>
> For me it also do not work enough well. When I hit intelli sence in mxml I
> always see much more results than I wanted to. It's being a bit messy. I
> see
> classes but it always takes me some time before I found it on the list.
>
> Piotr
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/VSCode-NextGenAS-Issues-
> with-IntelliSense-Goto-Definition-Ctrl-Click-and-
> auto-imports-tp59541p59542.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[Josh Tynjala]

> thought that it works similar to FlashBuilder regarding IntelliSense and
the auto additons of "imports".

That is exactly what this feature is supposed to do. An import for a class
should be added automatically when you complete it with IntelliSense. If
that's not working consistently, please file a bug report on Github with a
test case that will reproduce the issue.

> Goto does not work properly.

One thing worth mentioning is that you cannot go to classes that come from
SWC files (including framework classes in the SDK). Sometimes, SWC files
include the original source path, but I've noticed that it's almost always
missing, so I haven't added code to resolve that.

If a class is on the source-path, it should resolve for goto definition.

- Josh


On Feb 16, 2017 3:55 AM, "OK"  wrote:

Hi,
I wonder if I'm doing something wrong or if I'm gettting something wrong.
I've read the feature list and the ChangeLog [1] of the NextGenAS Extension
and thought that it works similar to FlashBuilder regarding IntelliSense and
the auto additons of "imports".

But for me it seems that IntelliSense and Goto does not work properly.
Sporadically sometimes it works and sometimes not... I have to test it a bit
more to get some more details.
Moreover it seems to me that it never adds the imports automatically.

I'm able to compile all the AS3/mxml stuff sucessfully and the compiled test
apps works like a charme but at the same time VSCode doesn't recognize some
classes or components.

Do I miss something?

Thanks,
Olaf

[1]
"IntelliSense completion of classes in ActionScript and  blocks
now automatically adds imports.
IntelliSense completion of classes in MXML now automatically adds xmlns
declarations."



--
View this message in context: http://apache-flex-
development.247.n4.nabble.com/VSCode-NextGenAS-Issues-
with-IntelliSense-Goto-Definition-Ctrl-Click-and-auto-imports-tp59541.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Setting background colour at run time fails

[Peter Ent]

Update:

I've pushed the following changes:

Core package: added StyleChangeNotifier and StyleChange event.
StyleChangeNotifier listens for ValueChangeEvents on its strand's style. I
decided to park this in Core because it seems listening for style changes
would be more universal than just HTML package. On the SWF side, the
StyleChangeNotifier simply detects a change in the style and dispatches a
new, StyleChangeEvent.STYLE_CHANGE event for anything that might be
interested. On the JS side, StyleChangeNotifier updates its strand's
wrapped element's style directly.

HTML package: I changed SolidBackgroundWithChangeListenerBead to be
SWF-only and to listen for STYLE_CHANGE events. When it sees such an
event, it causes the background of the strand to refresh.

I felt, after with Alex, that since SolidBackgroundBead is SWF-only, its
derivative, SolidBackgroundWithChangeListenerBead should also be SWF-only
which left few places for the JS side to actually change the style, so I
stuck that in the StyleChangeNotifier; it seems to work well.

To use this:


@namespace js "library://ns.apache.org/flexjs/basic";
@media -flex-flash {
   js|Container {
  iBackgroundBead:
ClassReference("org.apache.flex.html.beads.SolidBackgroundWithChangeListene
rBead");
   }
}





 
 

 


You can change the Container's background:  box.style.backgroundColor =
"red";

I will do the same for the border styles and then roll it into the Express
package Container element.

—peter

On 2/15/17, 2:48 PM, "Peter Ent"  wrote:

>This is what I have at the moment:
>
>SolidBackgroundWithChangeListenerBead (extends SolidBackgroundBead) grabs
>the style from its strand and sets up a listener for ValueChangeEvent. If
>the style dispatches it, SBWCLB then invokes its super class's methods,
>setupStyles and handleChange (both of which I made protected functions so
>the code could be reused with little effort.
>
>Changing the style involves: container.style.backgroundColor = 0xDD;
>
>This works fine for SWFs. It does not work for JS. There's no code on the
>JS side to transfer the container.style.backgroundColor to the
>container.element.style.backgroundColor. I think the SBWCLB needs a JS
>side to do that. Or, as you say, have BindableCSSStyle do it.
>
>However, what I read below was that my
>SolidBackgroundWithChangeListenerBead should really be StyleChangeNotifier
>that dispatches a more generic "styleChanged" event (which might be an
>extension of ValueChangeEvent). Then SolidBackgroundWithChangeListener
>would listen for that event and then trigger a refresh of its background.
>Then other beads, like SolidBoarderWithChangeListenerNotifierBead would do
>the same for borders.
>
>Then the application MXML becomes (you can't actually write this due to
>the fact that SolidBackgroundWithChangeListenerBead would only be
>available on SWF side so it would really go into a CSS with a media-query
>set for flash):
>
>
>
>
> 
> 
> 
> 
> 
>
>
>Does this sound more on the right track?
>
>‹peter
>
>On 2/15/17, 1:23 PM, "Alex Harui"  wrote:
>
>>
>>
>>On 2/15/17, 10:04 AM, "piotrz"  wrote:
>>
>>>Alex,
>>>
>>>Yes settings "style" wouldn't change some style property itself, but
>>>will
>>>register couple of times listener - shouldn't we avoid it ?
>>>
>>>What do you mean saying "IMO, styleChangeHandler should be removed from
>>>UIBase." - Where it should be placed exactly ?
>>
>>Maybe in a bead that looks for changes.  That's sort of how
>>LayoutChangeNotifier attempts to work.  Another possibility is that a
>>bead
>>could encapsulate the changing of the styles.
>>
>>The host strand in theory only contains code for convenience.  The beads
>>should be talking to each other.  In this case, the BindableCSSStyles
>>bead
>>and on the AS side a SolidBackgroundBead need to have a conversation.  On
>>the JS side, maybe BindableCSSStyles should just write to the element's
>>style object.
>>
>>We tried to purposefully leave out a lot of dynamic behavior in order to
>>see how small and fast Basic could be and if we can then add on dynamic
>>behavior some other way.  The Express package should bundle the dynamic
>>behavior.  So we are only now getting serious about how to implement this
>>dynamic behavior, so there is definitely room for improvement.
>>
>>My 2 cents,
>>-Alex
>>
>

Re: [VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[piotrz]

Hi Olaf,

For me it also do not work enough well. When I hit intelli sence in mxml I
always see much more results than I wanted to. It's being a bit messy. I see
classes but it always takes me some time before I found it on the list.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/VSCode-NextGenAS-Issues-with-IntelliSense-Goto-Definition-Ctrl-Click-and-auto-imports-tp59541p59542.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

[VSCode, NextGenAS] Issues with IntelliSense, Goto Definition (Ctrl+Click) and auto imports

[OK]

Hi,
I wonder if I'm doing something wrong or if I'm gettting something wrong.
I've read the feature list and the ChangeLog [1] of the NextGenAS Extension
and thought that it works similar to FlashBuilder regarding IntelliSense and
the auto additons of "imports".

But for me it seems that IntelliSense and Goto does not work properly.
Sporadically sometimes it works and sometimes not... I have to test it a bit
more to get some more details.
Moreover it seems to me that it never adds the imports automatically.

I'm able to compile all the AS3/mxml stuff sucessfully and the compiled test
apps works like a charme but at the same time VSCode doesn't recognize some
classes or components.

Do I miss something?

Thanks,
Olaf

[1]
"IntelliSense completion of classes in ActionScript and  blocks
now automatically adds imports.
IntelliSense completion of classes in MXML now automatically adds xmlns
declarations."



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/VSCode-NextGenAS-Issues-with-IntelliSense-Goto-Definition-Ctrl-Click-and-auto-imports-tp59541.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[piotrz]

No problem Olaf! :) Looking forward to see your try of MDL :)

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59540.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[OK]

>That's why I can provide some beads. If you wanted to use you will if not
the core implementation won't >be touched.

Yes sorry, this probably makes sens ;-)

Thanks for working on MDL!

Olaf





--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59539.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[piotrz]

That's why I can provide some beads. If you wanted to use you will if not the
core implementation won't be touched.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59538.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS MDL] release build broken

[Harbs]

1. Go here: 
http://apacheflexbuild.cloudapp.net:8080/job/MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/bin/js-release/index.html
 


2. Click on Toggles

You will see that the two IconToggles have no content. It seems like the 
Material Design font is not beiing used for some reason in the release build. 
The same thing works in the debug build.

Harbs

Re: [FlexJS, MDL] Layout Problems

[OK]

>I will try to create some beads which handle some mentioned cases above.

>From the FlexJS perspective folks of course could wondering why they can't
remove this style but maybe from MDL perspective (including Material Design
specs) this maybe makes sense [1].

What I would like so say is that on the one hand we say "Use FlexJS MDL not
the FlexJS way but the MDL way" and on the other hand we alyways want to mix
components and different layout approaches.
Don't know if this a bit inconsistent and confusing...

As Harbs said if the issues could be solved I would leave the origin margin
as it is and let the app developer decide what he would like to do.

Olaf




[1]
https://github.com/google/material-design-lite/blob/88872e672e41c56af0a78a35b34373b8c4a8c49d/src/slider/_slider.scss#L31







--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59536.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[Harbs]

To sum up the problems:

1. mdl applies a 20 px margin (I think it’s 30px for “flex” sliders)
2. This margin gets applied TWICE in FlexJS mdl. Once for the p element, and 
then again for the input element. This adds up to a 40px margin.
3. The slider gets wrapped in a mdl-slider__container element. This is done by 
the mdl js code. Because there are two mdl-slider elements, there are two 
containers created instead of one.
4. The outer container (which should not exist) pushes the slider down.

Problems 2,3 and 4 can be solved by only applying the classes to the input and 
not the p element.

Problem #1 seems to be by design for mdl, but can be overridden in css. I don’t 
think that should be done by the FlexJS mdl library. If the client wants to 
remove the margin, it should be done by them.

My $0.02.
Harbs

> On Feb 16, 2017, at 11:12 AM, OK  wrote:
> 
>> Can you exact specify what is the class of this container? 
> 
> There's a div that applies the class "mdl-slider__container" which sets the
> height to 18px [1].
> After removing this the vertical gap goes away.
> 
> The horizontal gap comes as Harbs said from MDL itself,  this is not nice
> but not a FlexJS issue.
> 
> Olaf
> 
> [1] https://snag.gy/x0gfpW.jpg
> 
> 
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59531.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[piotrz]

Hi Olaf,

I will try to create some beads which handle some mentioned cases above.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59534.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] maven faling (WeakMap)

[Christofer Dutz]

Hi Alex,

My current state is that the ASDoc generation uses the DITA output to generate 
the general data structures (It looked as DITA was a lot more complete than the 
others). But in contrast to your version it does two compilations … one for JS 
and one for SWF. Currently 

What I’m currently working on is to create a tree-walker that merges the two 
and marks elements as “available in both”, “available only in js” and 
“available in swf” and to output that as XML so we can easily output HTML and 
easily customize the output.

Chris


Am 16.02.17, 00:03 schrieb "Alex Harui" :



On 2/15/17, 2:46 PM, "Christofer Dutz"  wrote:

>Nope … not yet … I’ve got some uncommitted stuff in my local repo, but
>nothing globally usable yet … still thinking about how to do things
>nicely ☺

Then that's why it works for Maven.  The Ant build currently has to use
the old Flex SDK MXMLC compiler which doesn't allow "delete" as a function
name.  Once Falcon can generate DITA and you put in place the XSLT we'll
have the old ASDoc back.

Another option is that we invest a bit more in the FlexJS ASDoc app and
use that for ASDoc for now.

Thoughts?
-Alex

Re: [FlexJS Summit] Preparing the schedule

[Harbs]

I don’t know that I will able to be there on Friday either.

I would prefer to either stay later on Thursday to do what we can, or do it on 
Wednesday. I doubt I will be attending too many presentations. The extent of my 
participation of ApacheCon besides for Flex will probably just be to meet the 
other Apache folks in person.

Harbs

> On Feb 16, 2017, at 10:30 AM, piotrz  wrote:
> 
> Hi,
> 
> If I manage to come to the conference probably I won't be able to stay on
> friday due to flight back. Monday would be same. 
> 
> Piotr
> 
> 
> 
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: 
> http://apache-flex-development.247.n4.nabble.com/FlexJS-Summit-Preparing-the-schedule-tp59477p59527.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[OK]

>Can you exact specify what is the class of this container? 

There's a div that applies the class "mdl-slider__container" which sets the
height to 18px [1].
After removing this the vertical gap goes away.

The horizontal gap comes as Harbs said from MDL itself,  this is not nice
but not a FlexJS issue.

Olaf

[1] https://snag.gy/x0gfpW.jpg







--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59531.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] MDL: Add/Remove item(s) to TabBar

[sankar]

sankar wrote
> Also, I was thinking if there's a way possible to implement to
> programmatically 'active' certain section in 
*
> NavigationLayoutContent
*
>  (?)

Nevermind, I've created a method which does the job now.

Thanks!



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Add-Remove-item-s-to-TabBar-tp59508p59530.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Release Apache Flex SDK 4.16 RC2

[justin]

Hi,

Looks like the issue is this, this has been running for 9+ hours and should 
probably be killed [1]

May be a good idea to limit the time that job runs,it's usually fairly quick 
right?

Thanks,
Justin

1. http://apacheflexbuild.cloudapp.net:8080/job/MD5Checker/15255/

Re: [FlexJS Summit] Preparing the schedule

[Justin Mclean]

Hi,

> I think you misunderstood me … the day after the entire ApacheCon or the day 
> before … so it would be Monday or Firday … I would definitely favor Friday 
> too as it would sort of be a nice:
> - Thursday: Talking Day
> - Friday: Coding Day 

The BarCamp is also on Monday I think - that may be a consideration.

Thanks,
Justin

Re: [FlexJS Summit] Preparing the schedule

[piotrz]

Hi,

If I manage to come to the conference probably I won't be able to stay on
friday due to flight back. Monday would be same. 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Summit-Preparing-the-schedule-tp59477p59527.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: flexjs and flashdevelop

[flex capacitor]

Good job!

On Mon, Feb 13, 2017 at 10:21 PM, lizhi  wrote:

> https://github.com/matrix3d/spriteflexjs/wiki/flashdevelop
>
>
>
> -
> spriteflexjs.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/flexjs-and-flashdevelop-tp59364.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS, MDL] Layout Problems

[piotrz]

Harbs,

Can you exact specify what is the class of this container? 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59524.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS] Release Apache Flex SDK 4.16 RC2

[Justin Mclean]

Hi,

> Where did you look?

I compiled the SDK from the release branch (using the build/build_release.sh 
script)  on my local machine and looked at the artefacts it produced.

> I just looked at apacheflexbuilds and AFAICT it has
> not built a build with your changes.

It looks like it hasn’t done a build yet and it still waiting on a pending 
slot. [1] 

Thanks,
Justin

1. http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/

Re: [FlexJS] MDL: Add/Remove item(s) to TabBar

[sankar]

Also, I was thinking if there's a way possible to implement to
programmatically 'active' certain section in *NavigationLayoutContent* (?) I
was thinking to do a different component (i.e. breadcrumb) which should have
similar structure in use like NavigationLayoutContent, but I'm not sure how
to make certain section active in it.

Thanks!



--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Add-Remove-item-s-to-TabBar-tp59508p59523.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Layout Problems

[Harbs]

There are actually two problems with Slider. Besides the default 20px margins 
applied by the mdl css, there’s also an extra container/slider element in 
FlexJS which causes the margin to be doubled.

> On Feb 16, 2017, at 12:12 AM, piotrz  wrote:
> 
> Alex,
> 
> I like the idea! Maybe I should create two beads:
> 
> LayoutNotImportantBead
> SliderNoLeftMarginBead
> 
> What do the others thing ? 
> 
> Piotr
> 
> 
> 
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: 
> http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Layout-Problems-tp59423p59489.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.