Re: [FlexJS] Some things still missing ni FlexJS

[Christofer Dutz]

Well from my point of view it was the whole “write once run everywhere” thing. 
I was totally annoyed of having to write UI things once and then patch and 
bugfix things for all the other Browsers.

But in general I think you (Alex) and I have one great difference in our 
assumption of who will probably be our generation 1 users.

You assume it’s mainly the people wanting to create new applications. That’s 
why you see 1.0 the way you do it. 

I, on the other side, think that our generation 1 users would probably be 
people migrating legacy Flex applications to FlexJS.

The reason, why I think that way, is that no matter what bank or insurance 
company I have worked for in the last 4 years. I always encounter Flashplayer 
maintenance updates. I usually ask why Flash? And always get the answer: “We 
still got some legacy applications that need that”. A little more investigation 
usually shows that there are loads of applications still in production 
internally which are built in Flex. There are plans to migrate to JavaScript, 
but there just isn’t enough budget to simply rewrite something with the only 
benefit in the end being no longer to require the Flashplayer. For me “Flex” is 
stigmatized. Even if it’s not deserved, it’s still a reality. I doubt that 
someone wanting to try out the latest cool stuff will tend to go directly 
towards a stigmatized technology, not if there’s all the cool React, Angular2, 
Typescript and similar stuff out there that does “the same we promise to 
provide”. 

If we get FlexJS to a point where it’s easy to migrate we sort of offer the 
only option the people stuck in a dead-end with Flash have to migrate to 
JavaScript at a fraction of the costs. That’s why I’m continuing to argue to 
add the most essential Flex features to FlexJS. It doesn’t matter if AMF 
support is slower than JSON or than AMF was on Flash. It just have to be there 
to ease the migration path. Same with skinning. It’s been used quite a lot and 
this I one concept where migrating isn’t just a matter of replacing some 
classes. If there is no skinning support all the Components have to be 
completely rewritten. Eventually we could do without modules, even if I think 
they are essential, but for me it’s:

- AMF Support
- Skinning
- Modules
- ResourceBundles and I18N

Which we need in order to ease the migration path.

Chris


Am 13.01.17, 00:24 schrieb "Alex Harui" :



On 1/12/17, 12:46 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>We need some strategy, and we must think about what others are giving in
>comparison with us.
>In LTE I think our solution win, but right now is complicate convince
>business to choose us over Angular/React, since is world trending.
>
>So I'm with Chris that we need to give things others doesn't have, for me
>maven is one of that things, but is something in the backstage.
>We need more things on that make us different. One of those things is AMF,
>and since many Flex apps out there have it is a key point to make them
>move
>to FlexJS.

I guess I'm wondering why folks chose Flex in the first place.  Was it
some cool feature?  If so, what was it?  My assumption has been that the
real reason folks chose Flex (or maybe the reason they stayed) was about
Developer Productivity.  A feature fight will be very difficult for us to
win without more contributors.  Any feature we can produce as an advantage
would likely be short-lived:  the other frameworks will simply produce the
same feature.

But we can win or at least compare more favorably on helping you get your
app into production faster and having fewer maintenance issues because we
are a single-source provider of both a declarative language and an
object-oriented language and have a tool chain in our workflow.  And, I
still believe that having a SWF version of your app will be very valuable.
 For those who are interested in modules, without the runtime verification
that Flash has, you will be at the mercy of any synchronization issues
between the code that loads the module and the code in the module.  Flash
will tell you right when the module loads that it doesn't meet the
interface contract.  When will you find out when running just in JS?

My 2 cents,
-Alex

Re: [FalconJX] Output path

[Christofer Dutz]

Well the Maven build shouldn’t care at all as the output path is always set in 
the build and it’s never built using the CWD as for a maven multi-module build 
is always the directory where the build was started (so in case of a 
multi-module build it could be some directory other than the current modules 
directory)

Chris

Am 11.01.17, 20:51 schrieb "Josh Tynjala" :

MXMLFlexJSPublisher contains the following code that is run when no output
path is specified in the compiler options:

//begin code
String mainClassFolder = configuration.getTargetFileDirectory();
if (mainClassFolder.endsWith("src"))
outputParentFolder = new
File(configuration.getTargetFileDirectory()).getParentFile();
else if (mainClassFolder.endsWith("src/main/flex") ||
mainClassFolder.endsWith("src\\main\\flex"))
outputParentFolder = new

File(configuration.getTargetFileDirectory()).getParentFile().getParentFile().getParentFile();
else
outputParentFolder = new File(configuration.getTargetFileDirectory());
//end code

In plain English:

1. If the main class is in a src directory, bin will be created in the
parent directory of src.

2. If the main class is in a src/main/flex directory (in other words, if
it's a Maven project), bin will be created in ../../..

3. Otherwise, bin will be created in the same directory as the main class.

I often use "source" rather than "src", so I was getting source/bin as my
output directory, which was unexpected.

Rather than hardcoding a couple of special paths, maybe we should create
bin relative to the current working directory instead. I think that's a
common behavior for command line tools.

With this change, both of these commands should continue to work exactly
the same way:

mxmlc src/Main.mxml
mxmlc src/main/flex/Main.mxml

I assume that Maven sets the CWD to the correct location before it runs the
compiler too.

This would also allow other build tools with different project structures
to work without modifying the compiler.

Thoughts?

- Josh

Re: Apache Flex Twitter Account Changes

[Carlos Rovira]

Yeah! just see it! :)



2017-01-13 1:08 GMT+01:00 OmPrakash Muppirala :

> Looks very nice, Carlos!
>
> Great idea, adding the appropriate tags.  Looks like we already have a hit
> :-)
>
> Thanks,
> Om
>
> On Thu, Jan 12, 2017 at 3:01 PM, Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > just make some adjustment to our twitter account:
> >
> > https://twitter.com/apacheflex
> >
> > Mainly:
> >
> > * Changed Main Picture (still hope to have more time in the future to
> make
> > more of this blender 3d art)
> > * Adjust Logo account size (to have more white borders and let "breath" a
> > bit)
> > * Insert a text description of our project
> >
> > And finaly tweeted about the UX/UI seek with hashtags so people looking
> for
> > #UX #UI #Design could see us...
> >
> > Still If someone nows a good place where we could ask for help in design
> > (some place with lots of good UX/UI designers) please let me know :)
> >
> > --
> > 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.

[FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Christofer Dutz]

Hi,

I am currently writing some unit-tests for the Examples and encountered 
something I would like to discuss with you.
For example, in FlexJSStore the search field doesn’t have an id so it is not 
very simple to select the field. I could simply give the field an id, but I 
remembered in the old Flex there were “automationName” attributes which 
elements could have. These names helped identifying elements during tests. What 
do you think if we should start supporting some attributes that help writing 
tests (This would also be something that other frameworks don’t have and that 
could be treated as quite handy).

Chris

Re: [FlexJS] Some things still missing ni FlexJS

[Harbs]

I agree with Chris that target #1 is developers migrating from Flash.

But, #2 is a very close second with JS developers looking for better 
productivity.

#2 is where we can have a real win in terms of adoption. I think the reason js 
developers seem to always flutter from framework to framework is that they’re 
looking for better efficiency and not really finding it.

I’m not sure what the minimal feature set for version 1 is, but I’m not sure 
what percentage of enterprise apps use AMF modules and resource bundles. It 
would be interesting to know if there’s any indicators on that.

On Jan 13, 2017, at 10:44 AM, Christofer Dutz  wrote:

> Well from my point of view it was the whole “write once run everywhere” 
> thing. 
> I was totally annoyed of having to write UI things once and then patch and 
> bugfix things for all the other Browsers.
> 
> But in general I think you (Alex) and I have one great difference in our 
> assumption of who will probably be our generation 1 users.
> 
> You assume it’s mainly the people wanting to create new applications. That’s 
> why you see 1.0 the way you do it. 
> 
> I, on the other side, think that our generation 1 users would probably be 
> people migrating legacy Flex applications to FlexJS.
> 
> The reason, why I think that way, is that no matter what bank or insurance 
> company I have worked for in the last 4 years. I always encounter Flashplayer 
> maintenance updates. I usually ask why Flash? And always get the answer: “We 
> still got some legacy applications that need that”. A little more 
> investigation usually shows that there are loads of applications still in 
> production internally which are built in Flex. There are plans to migrate to 
> JavaScript, but there just isn’t enough budget to simply rewrite something 
> with the only benefit in the end being no longer to require the Flashplayer. 
> For me “Flex” is stigmatized. Even if it’s not deserved, it’s still a 
> reality. I doubt that someone wanting to try out the latest cool stuff will 
> tend to go directly towards a stigmatized technology, not if there’s all the 
> cool React, Angular2, Typescript and similar stuff out there that does “the 
> same we promise to provide”. 
> 
> If we get FlexJS to a point where it’s easy to migrate we sort of offer the 
> only option the people stuck in a dead-end with Flash have to migrate to 
> JavaScript at a fraction of the costs. That’s why I’m continuing to argue to 
> add the most essential Flex features to FlexJS. It doesn’t matter if AMF 
> support is slower than JSON or than AMF was on Flash. It just have to be 
> there to ease the migration path. Same with skinning. It’s been used quite a 
> lot and this I one concept where migrating isn’t just a matter of replacing 
> some classes. If there is no skinning support all the Components have to be 
> completely rewritten. Eventually we could do without modules, even if I think 
> they are essential, but for me it’s:
> 
> - AMF Support
> - Skinning
> - Modules
> - ResourceBundles and I18N
> 
> Which we need in order to ease the migration path.
> 
> Chris
> 
> 
> Am 13.01.17, 00:24 schrieb "Alex Harui" :
> 
> 
> 
>On 1/12/17, 12:46 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> wrote:
> 
>> We need some strategy, and we must think about what others are giving in
>> comparison with us.
>> In LTE I think our solution win, but right now is complicate convince
>> business to choose us over Angular/React, since is world trending.
>> 
>> So I'm with Chris that we need to give things others doesn't have, for me
>> maven is one of that things, but is something in the backstage.
>> We need more things on that make us different. One of those things is AMF,
>> and since many Flex apps out there have it is a key point to make them
>> move
>> to FlexJS.
> 
>I guess I'm wondering why folks chose Flex in the first place.  Was it
>some cool feature?  If so, what was it?  My assumption has been that the
>real reason folks chose Flex (or maybe the reason they stayed) was about
>Developer Productivity.  A feature fight will be very difficult for us to
>win without more contributors.  Any feature we can produce as an advantage
>would likely be short-lived:  the other frameworks will simply produce the
>same feature.
> 
>But we can win or at least compare more favorably on helping you get your
>app into production faster and having fewer maintenance issues because we
>are a single-source provider of both a declarative language and an
>object-oriented language and have a tool chain in our workflow.  And, I
>still believe that having a SWF version of your app will be very valuable.
> For those who are interested in modules, without the runtime verification
>that Flash has, you will be at the mercy of any synchronization issues
>between the code that loads the module and the code in the module.  Flash
>will tell you right when the module loads that it

[FlexJS] Problem in FlexJSStore

[Christofer Dutz]

Hi,

I am currently investigating a problem in FlexJSStore which is preventing any 
of the top navigation-buttons from doing anything.
It turns out that the problem can be solved by commenting out the line:


The problem I can see in the console log is: that binding is unable to get the 
value of price from a null attribute. Could it be that this only occurs if the 
binding contains some further processing? In this case the result of 
“product.price” binding would be processed by “cf.format(…)” … well whatever is 
causing this, I guess we need to fix it.

Chris

Re: [FlexJS] Some things still missing ni FlexJS

[Dev LFM]

Hi all,

For me, as I since 8 years constantly developed content editors for
printing labs (basically I would use a Canvas on FlexJS), it was the no
crossbrowsing differences, one player that behaves the same on all targets
(This is the key). My company currently relies on Flash to sell.. and
html/js fails on this hard... so in the end I will probably deploy a Air
release..

Then it was the IDE with good tools for productivity and debug. It is a
waste of time patching to solve some IE/Firefox/Chrome issue..

Thats why, and listen to this pls, the most valuable thing that FlexJS can
sell, is the Stage3D/WebGL targets as replacement to flashplayer. Then with
Cordova for mobile, and Electron for desktop, we would target everywhere
and win marketshare like in flex/flash did.

We should get that flexjsstage3d from
http://matrix3d.github.io/assets/html5/flexjsstage3d/bin/js-release/ and
help him finish all compatibility with flash stage3d, then port the
starling/feathers and we would be on top again.

AMF and ResourcesBundles / I18N are a must, modules could wait..

This is my vision for the future.


2017-01-13 13:58 GMT+00:00 Harbs :

> I agree with Chris that target #1 is developers migrating from Flash.
>
> But, #2 is a very close second with JS developers looking for better
> productivity.
>
> #2 is where we can have a real win in terms of adoption. I think the
> reason js developers seem to always flutter from framework to framework is
> that they’re looking for better efficiency and not really finding it.
>
> I’m not sure what the minimal feature set for version 1 is, but I’m not
> sure what percentage of enterprise apps use AMF modules and resource
> bundles. It would be interesting to know if there’s any indicators on that.
>
> On Jan 13, 2017, at 10:44 AM, Christofer Dutz 
> wrote:
>
> > Well from my point of view it was the whole “write once run everywhere”
> thing.
> > I was totally annoyed of having to write UI things once and then patch
> and bugfix things for all the other Browsers.
> >
> > But in general I think you (Alex) and I have one great difference in our
> assumption of who will probably be our generation 1 users.
> >
> > You assume it’s mainly the people wanting to create new applications.
> That’s why you see 1.0 the way you do it.
> >
> > I, on the other side, think that our generation 1 users would probably
> be people migrating legacy Flex applications to FlexJS.
> >
> > The reason, why I think that way, is that no matter what bank or
> insurance company I have worked for in the last 4 years. I always encounter
> Flashplayer maintenance updates. I usually ask why Flash? And always get
> the answer: “We still got some legacy applications that need that”. A
> little more investigation usually shows that there are loads of
> applications still in production internally which are built in Flex. There
> are plans to migrate to JavaScript, but there just isn’t enough budget to
> simply rewrite something with the only benefit in the end being no longer
> to require the Flashplayer. For me “Flex” is stigmatized. Even if it’s not
> deserved, it’s still a reality. I doubt that someone wanting to try out the
> latest cool stuff will tend to go directly towards a stigmatized
> technology, not if there’s all the cool React, Angular2, Typescript and
> similar stuff out there that does “the same we promise to provide”.
> >
> > If we get FlexJS to a point where it’s easy to migrate we sort of offer
> the only option the people stuck in a dead-end with Flash have to migrate
> to JavaScript at a fraction of the costs. That’s why I’m continuing to
> argue to add the most essential Flex features to FlexJS. It doesn’t matter
> if AMF support is slower than JSON or than AMF was on Flash. It just have
> to be there to ease the migration path. Same with skinning. It’s been used
> quite a lot and this I one concept where migrating isn’t just a matter of
> replacing some classes. If there is no skinning support all the Components
> have to be completely rewritten. Eventually we could do without modules,
> even if I think they are essential, but for me it’s:
> >
> > - AMF Support
> > - Skinning
> > - Modules
> > - ResourceBundles and I18N
> >
> > Which we need in order to ease the migration path.
> >
> > Chris
> >
> >
> > Am 13.01.17, 00:24 schrieb "Alex Harui" :
> >
> >
> >
> >On 1/12/17, 12:46 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> >
> wrote:
> >
> >> We need some strategy, and we must think about what others are giving in
> >> comparison with us.
> >> In LTE I think our solution win, but right now is complicate convince
> >> business to choose us over Angular/React, since is world trending.
> >>
> >> So I'm with Chris that we need to give things others doesn't have, for
> me
> >> maven is one of that things, but is something in the backstage.
> >> We need more things on that make us different. One of those things is
> AMF,
> >> and since many Flex apps out there have it is a key 

Re: [FlexJS] Some things still missing ni FlexJS

[Dev LFM]

Actually it would be more easy, if adobe just convert their flashplayer to
render on webgl and that would work for all...

2017-01-13 15:15 GMT+00:00 Dev LFM :

> Hi all,
>
> For me, as I since 8 years constantly developed content editors for
> printing labs (basically I would use a Canvas on FlexJS), it was the no
> crossbrowsing differences, one player that behaves the same on all targets
> (This is the key). My company currently relies on Flash to sell.. and
> html/js fails on this hard... so in the end I will probably deploy a Air
> release..
>
> Then it was the IDE with good tools for productivity and debug. It is a
> waste of time patching to solve some IE/Firefox/Chrome issue..
>
> Thats why, and listen to this pls, the most valuable thing that FlexJS can
> sell, is the Stage3D/WebGL targets as replacement to flashplayer. Then with
> Cordova for mobile, and Electron for desktop, we would target everywhere
> and win marketshare like in flex/flash did.
>
> We should get that flexjsstage3d from http://matrix3d.github.io/assets/
> html5/flexjsstage3d/bin/js-release/ and help him finish all compatibility
> with flash stage3d, then port the starling/feathers and we would be on top
> again.
>
> AMF and ResourcesBundles / I18N are a must, modules could wait..
>
> This is my vision for the future.
>
>
> 2017-01-13 13:58 GMT+00:00 Harbs :
>
>> I agree with Chris that target #1 is developers migrating from Flash.
>>
>> But, #2 is a very close second with JS developers looking for better
>> productivity.
>>
>> #2 is where we can have a real win in terms of adoption. I think the
>> reason js developers seem to always flutter from framework to framework is
>> that they’re looking for better efficiency and not really finding it.
>>
>> I’m not sure what the minimal feature set for version 1 is, but I’m not
>> sure what percentage of enterprise apps use AMF modules and resource
>> bundles. It would be interesting to know if there’s any indicators on that.
>>
>> On Jan 13, 2017, at 10:44 AM, Christofer Dutz 
>> wrote:
>>
>> > Well from my point of view it was the whole “write once run everywhere”
>> thing.
>> > I was totally annoyed of having to write UI things once and then patch
>> and bugfix things for all the other Browsers.
>> >
>> > But in general I think you (Alex) and I have one great difference in
>> our assumption of who will probably be our generation 1 users.
>> >
>> > You assume it’s mainly the people wanting to create new applications.
>> That’s why you see 1.0 the way you do it.
>> >
>> > I, on the other side, think that our generation 1 users would probably
>> be people migrating legacy Flex applications to FlexJS.
>> >
>> > The reason, why I think that way, is that no matter what bank or
>> insurance company I have worked for in the last 4 years. I always encounter
>> Flashplayer maintenance updates. I usually ask why Flash? And always get
>> the answer: “We still got some legacy applications that need that”. A
>> little more investigation usually shows that there are loads of
>> applications still in production internally which are built in Flex. There
>> are plans to migrate to JavaScript, but there just isn’t enough budget to
>> simply rewrite something with the only benefit in the end being no longer
>> to require the Flashplayer. For me “Flex” is stigmatized. Even if it’s not
>> deserved, it’s still a reality. I doubt that someone wanting to try out the
>> latest cool stuff will tend to go directly towards a stigmatized
>> technology, not if there’s all the cool React, Angular2, Typescript and
>> similar stuff out there that does “the same we promise to provide”.
>> >
>> > If we get FlexJS to a point where it’s easy to migrate we sort of offer
>> the only option the people stuck in a dead-end with Flash have to migrate
>> to JavaScript at a fraction of the costs. That’s why I’m continuing to
>> argue to add the most essential Flex features to FlexJS. It doesn’t matter
>> if AMF support is slower than JSON or than AMF was on Flash. It just have
>> to be there to ease the migration path. Same with skinning. It’s been used
>> quite a lot and this I one concept where migrating isn’t just a matter of
>> replacing some classes. If there is no skinning support all the Components
>> have to be completely rewritten. Eventually we could do without modules,
>> even if I think they are essential, but for me it’s:
>> >
>> > - AMF Support
>> > - Skinning
>> > - Modules
>> > - ResourceBundles and I18N
>> >
>> > Which we need in order to ease the migration path.
>> >
>> > Chris
>> >
>> >
>> > Am 13.01.17, 00:24 schrieb "Alex Harui" :
>> >
>> >
>> >
>> >On 1/12/17, 12:46 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira"
>> >
>> wrote:
>> >
>> >> We need some strategy, and we must think about what others are giving
>> in
>> >> comparison with us.
>> >> In LTE I think our solution win, but right now is complicate convince
>> >> business to choose us over Angular/React, since is world trending.
>>

Re: [FlexJS] Problem in FlexJSStore

[piotrz]

Hi Chris,

I just dig into that and have some solution, but not sure whether it is
correct.

In PropertyWatcher class we have function updateProperty. 
If "source" is available we are trying to apply value from source, but if I
correct understand sometimes the "getterFunction" is our source. 
If getter function for some reason is throwing an error we should set null
to value. Code with fix -> [1]

[1] https://paste.apache.org/pxDj

Piotr





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

Re: AW: [FALCONJX] Combining SWF and JS compilers (was Re: AW: [FalconJX][FlexJS] COMPJSC and Build order)

[Alex Harui]

Back to working on this again...

Currently, there are "clients" like MXMLJSC, COMPJSC, and ASDOCJSC.  You
launch one of these clients.  Then you specify (via -js-output-type) what
"backend" you want the client to use.  A backend supplies an "emitter"
that walks the AST and generates some sort of output.   These "backends"
also currently supply a "publisher" that packages up the output.

I think going forward, there may be a need to have different publishers
for the same backend/emitter.  For example, it might turn out to be
beneficial to specify a Cordova publisher that knows how to place the
output and add Cordova plugins to a Cordova project structure.  Right now
we have an Ant script and it doesn't have an extensible way of adding
Cordova plugins.  A Cordova-specific publisher could examine the JS output
and detect directives to add certain plugins to the Cordova project.
That could be a significant time-saver for folks building Cordova apps
with FlexJS.

Then there is the main goal of this thread which is to allow the developer
(especially the developer using an IDE) to launch a single client and run
both a SWF compile and a JS compile.  SWF compilation is currently done
with a different set of clients (MXMLC and COMPC).

If I understand Chris's suggestion below, it might be better to have a new
client for each backend.  So, instead of MXMLJSC with js-output-type=NODE
and MXMLJSC with js-output-type=FLEXJS, we'd have MXMLNODEJSC and
MXMLFLEXJSC clients and no -js-output-type parameter.

Now having an additional switch for the publisher makes this a bit more
complex.  We might then have an MXMLFLEXJSCCORDOVA as well that knows how
to output to Cordova projects.  What do folks think of this idea?

The backend would no longer be responsible for a publisher.  They would be
separate entities integrated by a client.

Then for Flash Builder, the flex-compiler-oem jar would simply launch more
than one of these clients and aggregate the output.

Thoughts?
-Alex

On 12/5/16, 8:52 AM, "Christofer Dutz"  wrote:

>Yes I do ... I did a lot of „networking“ with the maven guys in Seville.
>It seems that I managed to get the point I didn’t seem to manage via
>emails. 
>Currently I am using different sets of libaries based upon classifiers,
>but that’s just a temporary hack. I am hoping that I will be able to make
>Maven more polyglot in the near future and then we will probably have a
>complete new world of possibilities ;-)
>
>Chris
>
>Am 05.12.16, 17:07 schrieb "Alex Harui" :
>
>Thanks Chris, that's helpful.  Do you have any thoughts on how to
>manage
>two different sets of libraries, one for SWF compile, one for JS
>compile?
>
>Thanks,
>-Alex
>
>On 12/5/16, 12:44 AM, "Christofer Dutz" 
>wrote:
>
>>Hi Alex,
>>
>>sorry for not responding on that last email ☹... must have missed
>that
>>one ☹
>>
>>For the general functionality of the flex-tool-groups, I simply use
>the
>>basic Java service registry functionality.
>>This allows to lookup a list of instances with a symbolic name. You
>can
>>add more implementations to the list, by providing a jar with a
>simple
>>text file named:
>“META-INF/services/org.apache.flex.tools.FlexToolGroup”.
>>This file only contains class names. Each row will be treated as an
>>alternate implementation.
>>So if I want to get all “tool-groups”, all I have to do, is to ask
>the
>>Service registry to give me all
>“org.apache.flex.tools.FlexToolGroup”.
>>In my case I made sure I defined a universal interface that all
>>implementations would implement, so I know that I can simply cast
>each
>>instance I get back to that base interface.
>>In my case in order to add a new compiler called “foo”, all I would
>do,
>>is to add a jar with a class implementing FlexToolGroup and to make
>>“getName” return “foo”.
>>
>>Currently I would have to extend the Enum JSOutputType to support
>“foo”,
>>which doesn’t make it that extensible.
>>
>>Right now I have a template for each type of compilation and a
>matching
>>“Mojo”. All compiler options go into the configuration file for that
>>particular Mojo. Additionally, the Mojo is able to customize the
>default
>>values used to generate the template. For example, the getDefines
>method
>>returns different values for CompileASMojo and for CompileJSMojo.
>>
>>All I have to do then, is to provide the template path to the
>compiler
>>using the default “execute” method of any of the “FlexTool”
>>implementations and simply provide an array of Strings which equals
>the
>>normal array of Strings the compiler gets in the Ant world.
>>
>>Hope that explains things a little more.
>>
>>Chris
>>
>>
>>Am 02.12.16, 19:13 schrieb "Alex Harui" :
>>
>>I'm about to start working on this.  I haven't actually tried
>anything
>>yet, but my thinking is that there are some inte

Re: [FlexJS] Problem in FlexJSStore

[Alex Harui]

Sounds reasonable.  Binding should have try/catch blocks in the right
places and expect to handle null.
Now when you get null, the watcher chain has to know to watch for the
value becoming non-null so it can attach watchers to the new object to
watch.  Not sure if we have the right code for that or not.

Thanks for digging into it.
-Alex

On 1/13/17, 8:29 AM, "piotrz"  wrote:

>Hi Chris,
>
>I just dig into that and have some solution, but not sure whether it is
>correct.
>
>In PropertyWatcher class we have function updateProperty.
>If "source" is available we are trying to apply value from source, but if
>I
>correct understand sometimes the "getterFunction" is our source.
>If getter function for some reason is throwing an error we should set null
>to value. Code with fix -> [1]
>
>[1] https://paste.apache.org/pxDj
>
>Piotr
>
>
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Problem-in-Fle
>xJSStore-tp58232p58235.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [Jenkins] All build is down

[Alex Harui]

OK, I brought it back up.  All PMC members should be able to get the
credentials from the private@ list and Remote Desktop and launch the slave
agent and not have to wait for me.  I'll re-send instructions to private@.

-Alex

On 1/12/17, 11:41 PM, "piotrz"  wrote:

>Hi All,
>
>I noticed that from yesterday all builds are stuck. [1] Probably cause
>both
>slaves are down.
>
>[1] http://apacheflexbuild.cloudapp.net:8080/
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/Jenkins-All-build-is-
>down-tp58226.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Problem in FlexJSStore

[piotrz]

Place where it blow up cause of these PropertyWatcher is in wrapUpdate
(WatcherBase):

 try
{
wrappedFunction.apply(this);
}
catch(error:Error)
{
we are logging on console here error
}

Searching no-null object, but how and where ? If I do not have such code
once this property get back from null to not null during work of application
we won't notice it ? 

Piotr





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

Re: [Jenkins] All build is down

[piotrz]

Thank you Alex. I just saved your email and will try to do this next time.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/Jenkins-All-build-is-down-tp58226p58240.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Some things still missing ni FlexJS

[Alex Harui]

On 1/13/17, 12:44 AM, "Christofer Dutz"  wrote:

>Well from my point of view it was the whole “write once run everywhere”
>thing. 
>I was totally annoyed of having to write UI things once and then patch
>and bugfix things for all the other Browsers.

I would say that fits under the "Developer Productivity" umbrella.

>
>But in general I think you (Alex) and I have one great difference in our
>assumption of who will probably be our generation 1 users.
>
>You assume it’s mainly the people wanting to create new applications.
>That’s why you see 1.0 the way you do it.

That is an incorrect assumption.

IMO, there are at least some existing Flex apps that don't use AMF.  Now
it may turn out that we will have AMF shortly, but until it is done, those
who don't need it can start migrating their apps today.  Some folks are
already migrating.  I will believe that AMF is used by the vast majority
of Flex apps, but as I said upthread, we simply need to attract more
committers/contributors to really get FlexJS off the ground.  Some folks
believe that declaring something as 1.0 will invite more folks to try it
and thus get involved.  I don't have a strong opinion, but that sounds
like a reasonable approach, and better than telling folks not to try
FlexJS for another year or two and wait for the few of us who are active
committers to reproduce all of these killer features that a much larger
team of full-timers did at Adobe over many more years.

Flex 4 had many more features than Flex 3, which had more features than
Flex 2 which had more features than Flex 1.0.  FlexJS 1.0 may only allow a
small percentage of Flex customers to migrate, but again, if that brings
in new contributors we can handle more Flex customers with FlexJS 2.0 and
so on.

There may also be a way to get traction with new customers and new apps as
well by trying to get attention from Cordova developers, CreateJS
developers, etc.  I don't care who gets to production first, whether it is
a new app or migrated app, but mainly, I think a testimonial is what we
really need since we don't have a budget for marketing.  So when folks
show up with a need in order to get to production, I will try to help them
out.

-Alex

Re: [FlexJS] Some things still missing ni FlexJS

[Carlos Rovira]

The last time I saw webgl working was testing Unity 3D webgl.
Unity invest much effort and they got it working, but mainly on desktop,
and without great performance.
In mobile devices, was not supported (that was about 6 month ago), and when
playing on iPhone (for example) was really bad experience.

I think webgl is not here yet...at least for what I see.

If it could be I think Adobe smart people would make it




2017-01-13 16:18 GMT+01:00 Dev LFM :

> Actually it would be more easy, if adobe just convert their flashplayer to
> render on webgl and that would work for all...
>
> 2017-01-13 15:15 GMT+00:00 Dev LFM :
>
> > Hi all,
> >
> > For me, as I since 8 years constantly developed content editors for
> > printing labs (basically I would use a Canvas on FlexJS), it was the no
> > crossbrowsing differences, one player that behaves the same on all
> targets
> > (This is the key). My company currently relies on Flash to sell.. and
> > html/js fails on this hard... so in the end I will probably deploy a Air
> > release..
> >
> > Then it was the IDE with good tools for productivity and debug. It is a
> > waste of time patching to solve some IE/Firefox/Chrome issue..
> >
> > Thats why, and listen to this pls, the most valuable thing that FlexJS
> can
> > sell, is the Stage3D/WebGL targets as replacement to flashplayer. Then
> with
> > Cordova for mobile, and Electron for desktop, we would target everywhere
> > and win marketshare like in flex/flash did.
> >
> > We should get that flexjsstage3d from http://matrix3d.github.io/assets/
> > html5/flexjsstage3d/bin/js-release/ and help him finish all
> compatibility
> > with flash stage3d, then port the starling/feathers and we would be on
> top
> > again.
> >
> > AMF and ResourcesBundles / I18N are a must, modules could wait..
> >
> > This is my vision for the future.
> >
> >
> > 2017-01-13 13:58 GMT+00:00 Harbs :
> >
> >> I agree with Chris that target #1 is developers migrating from Flash.
> >>
> >> But, #2 is a very close second with JS developers looking for better
> >> productivity.
> >>
> >> #2 is where we can have a real win in terms of adoption. I think the
> >> reason js developers seem to always flutter from framework to framework
> is
> >> that they’re looking for better efficiency and not really finding it.
> >>
> >> I’m not sure what the minimal feature set for version 1 is, but I’m not
> >> sure what percentage of enterprise apps use AMF modules and resource
> >> bundles. It would be interesting to know if there’s any indicators on
> that.
> >>
> >> On Jan 13, 2017, at 10:44 AM, Christofer Dutz <
> christofer.d...@c-ware.de>
> >> wrote:
> >>
> >> > Well from my point of view it was the whole “write once run
> everywhere”
> >> thing.
> >> > I was totally annoyed of having to write UI things once and then patch
> >> and bugfix things for all the other Browsers.
> >> >
> >> > But in general I think you (Alex) and I have one great difference in
> >> our assumption of who will probably be our generation 1 users.
> >> >
> >> > You assume it’s mainly the people wanting to create new applications.
> >> That’s why you see 1.0 the way you do it.
> >> >
> >> > I, on the other side, think that our generation 1 users would probably
> >> be people migrating legacy Flex applications to FlexJS.
> >> >
> >> > The reason, why I think that way, is that no matter what bank or
> >> insurance company I have worked for in the last 4 years. I always
> encounter
> >> Flashplayer maintenance updates. I usually ask why Flash? And always get
> >> the answer: “We still got some legacy applications that need that”. A
> >> little more investigation usually shows that there are loads of
> >> applications still in production internally which are built in Flex.
> There
> >> are plans to migrate to JavaScript, but there just isn’t enough budget
> to
> >> simply rewrite something with the only benefit in the end being no
> longer
> >> to require the Flashplayer. For me “Flex” is stigmatized. Even if it’s
> not
> >> deserved, it’s still a reality. I doubt that someone wanting to try out
> the
> >> latest cool stuff will tend to go directly towards a stigmatized
> >> technology, not if there’s all the cool React, Angular2, Typescript and
> >> similar stuff out there that does “the same we promise to provide”.
> >> >
> >> > If we get FlexJS to a point where it’s easy to migrate we sort of
> offer
> >> the only option the people stuck in a dead-end with Flash have to
> migrate
> >> to JavaScript at a fraction of the costs. That’s why I’m continuing to
> >> argue to add the most essential Flex features to FlexJS. It doesn’t
> matter
> >> if AMF support is slower than JSON or than AMF was on Flash. It just
> have
> >> to be there to ease the migration path. Same with skinning. It’s been
> used
> >> quite a lot and this I one concept where migrating isn’t just a matter
> of
> >> replacing some classes. If there is no skinning support all the
> Components
> >> have to be completely rewritten.

Re: [FlexJS] Some things still missing ni FlexJS

[Peter Ent]

I was speaking to a friend that has some JavaScript developers working for
him. They use React and React/Native for their mobile apps. His feeling is
that web-centric apps (e.g. Amazon.com) are going to be replaced with
mobile apps since mobile devices are cheaper than laptops. They are
concentrating their app development to server-side services with native
apps delivered via React/Native.

IMO then, what FlexJS needs is the ability to go native. This isn't
necessary for a 1.0 launch, but having FlexJS/Native with applications
constructed in ActionScript and MXML and then cross-compiled into Swift or
Java could go a long way to make FlexJS the platform for cross-device
development.

‹peter

On 1/13/17, 8:58 AM, "Harbs"  wrote:

>I agree with Chris that target #1 is developers migrating from Flash.
>
>But, #2 is a very close second with JS developers looking for better
>productivity.
>
>#2 is where we can have a real win in terms of adoption. I think the
>reason js developers seem to always flutter from framework to framework
>is that they¹re looking for better efficiency and not really finding it.
>
>I¹m not sure what the minimal feature set for version 1 is, but I¹m not
>sure what percentage of enterprise apps use AMF modules and resource
>bundles. It would be interesting to know if there¹s any indicators on
>that.
>
>On Jan 13, 2017, at 10:44 AM, Christofer Dutz 
>wrote:
>
>> Well from my point of view it was the whole ³write once run everywhere²
>>thing. 
>> I was totally annoyed of having to write UI things once and then patch
>>and bugfix things for all the other Browsers.
>> 
>> But in general I think you (Alex) and I have one great difference in
>>our assumption of who will probably be our generation 1 users.
>> 
>> You assume it¹s mainly the people wanting to create new applications.
>>That¹s why you see 1.0 the way you do it.
>> 
>> I, on the other side, think that our generation 1 users would probably
>>be people migrating legacy Flex applications to FlexJS.
>> 
>> The reason, why I think that way, is that no matter what bank or
>>insurance company I have worked for in the last 4 years. I always
>>encounter Flashplayer maintenance updates. I usually ask why Flash? And
>>always get the answer: ³We still got some legacy applications that need
>>that². A little more investigation usually shows that there are loads of
>>applications still in production internally which are built in Flex.
>>There are plans to migrate to JavaScript, but there just isn¹t enough
>>budget to simply rewrite something with the only benefit in the end
>>being no longer to require the Flashplayer. For me ³Flex² is
>>stigmatized. Even if it¹s not deserved, it¹s still a reality. I doubt
>>that someone wanting to try out the latest cool stuff will tend to go
>>directly towards a stigmatized technology, not if there¹s all the cool
>>React, Angular2, Typescript and similar stuff out there that does ³the
>>same we promise to provide².
>> 
>> If we get FlexJS to a point where it¹s easy to migrate we sort of offer
>>the only option the people stuck in a dead-end with Flash have to
>>migrate to JavaScript at a fraction of the costs. That¹s why I¹m
>>continuing to argue to add the most essential Flex features to FlexJS.
>>It doesn¹t matter if AMF support is slower than JSON or than AMF was on
>>Flash. It just have to be there to ease the migration path. Same with
>>skinning. It¹s been used quite a lot and this I one concept where
>>migrating isn¹t just a matter of replacing some classes. If there is no
>>skinning support all the Components have to be completely rewritten.
>>Eventually we could do without modules, even if I think they are
>>essential, but for me it¹s:
>> 
>> - AMF Support
>> - Skinning
>> - Modules
>> - ResourceBundles and I18N
>> 
>> Which we need in order to ease the migration path.
>> 
>> Chris
>> 
>> 
>> Am 13.01.17, 00:24 schrieb "Alex Harui" :
>> 
>> 
>> 
>>On 1/12/17, 12:46 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>Rovira"
>>
>>wrote:
>> 
>>> We need some strategy, and we must think about what others are giving
>>>in
>>> comparison with us.
>>> In LTE I think our solution win, but right now is complicate convince
>>> business to choose us over Angular/React, since is world trending.
>>> 
>>> So I'm with Chris that we need to give things others doesn't have, for
>>>me
>>> maven is one of that things, but is something in the backstage.
>>> We need more things on that make us different. One of those things is
>>>AMF,
>>> and since many Flex apps out there have it is a key point to make them
>>> move
>>> to FlexJS.
>> 
>>I guess I'm wondering why folks chose Flex in the first place.  Was
>>it
>>some cool feature?  If so, what was it?  My assumption has been that
>>the
>>real reason folks chose Flex (or maybe the reason they stayed) was
>>about
>>Developer Productivity.  A feature fight will be very difficult for
>>us to
>>win without more contributors.  Any feature we can produce 

Re: [FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Alex Harui]

My thought was that automated testing properties would be a separate bead.
 That way you can more easily rip it out before going to production.

My 2 cents,
-Alex

On 1/13/17, 5:53 AM, "Christofer Dutz"  wrote:

>Hi,
>
>I am currently writing some unit-tests for the Examples and encountered
>something I would like to discuss with you.
>For example, in FlexJSStore the search field doesn’t have an id so it is
>not very simple to select the field. I could simply give the field an id,
>but I remembered in the old Flex there were “automationName” attributes
>which elements could have. These names helped identifying elements during
>tests. What do you think if we should start supporting some attributes
>that help writing tests (This would also be something that other
>frameworks don’t have and that could be treated as quite handy).
>
>Chris

Re: [FlexJS] Some things still missing ni FlexJS

[Carlos Rovira]

2017-01-13 19:11 GMT+01:00 Alex Harui :

>
>
> IMO, there are at least some existing Flex apps that don't use AMF.  Now
> it may turn out that we will have AMF shortly, but until it is done, those
> who don't need it can start migrating their apps today.  Some folks are
> already migrating.


I don't think so. For me flow data comes first and then other things.
Without server connection I think almost no people will start migrating.
People even can start a wireframe ugly project, but seeing data is coming
and they can sent data. Then will come themes, and other eye candy things...



> I will believe that AMF is used by the vast majority
> of Flex apps, but as I said upthread, we simply need to attract more
> committers/contributors to really get FlexJS off the ground.  Some folks
> believe that declaring something as 1.0 will invite more folks to try it
> and thus get involved.


I don't think so. React and others are in 0.15?...and they attract all devs.
If we put some groundbreaking examples and say "hey! this is Flex and we
have a cool component set, modules, AMF..."
People will start then to think in us seriously. Until then we don't have
to much to captivate people coming...



> I don't have a strong opinion, but that sounds
> like a reasonable approach, and better than telling folks not to try
> FlexJS for another year or two and wait for the few of us who are active
> committers to reproduce all of these killer features that a much larger
> team of full-timers did at Adobe over many more years.
>

I think that people will start to join as they can work with flexJS. we
need a set of capabilities that make people could use us in their Apps
We are near, but not still there. and the people that we can't attract more
are the people that has old flex apps as Chris said.


>
> Flex 4 had many more features than Flex 3, which had more features than
> Flex 2 which had more features than Flex 1.0.  FlexJS 1.0 may only allow a
> small percentage of Flex customers to migrate, but again, if that brings
> in new contributors we can handle more Flex customers with FlexJS 2.0 and
> so on.
>

Flex was popular in 2005 when Adobe bought Macromedia and invest money to
make Flex 2.0. That was for me the vortex that make people change from
crappy html/js to Flex/swf


>
> There may also be a way to get traction with new customers and new apps as
> well by trying to get attention from Cordova developers, CreateJS
> developers, etc.


All people I hear talking about Cordoba says "it's crap" and CreateJS is
not very popular...I think we should not see in that direction since is not
the excellence we can reach to be "the top" tech out there.


> I don't care who gets to production first, whether it is
> a new app or migrated app, but mainly, I think a testimonial is what we
> really need since we don't have a budget for marketing.  So when folks
> show up with a need in order to get to production, I will try to help them
> out.
>

For me get the 1.0 state is not related to see a guy or a team that say us
"hey! I made a FlexJS app and I have in pro"...mmm...definitely no.
I see that we are not 1.0...we all see that. We see that we are getting
great advances to that path, but for 1.0 means "the minimum set of things
that allows me to make a FlexJS app" and that means crafting an interface
with controls and layouts (buttons, text inputs, lists, ...), break into
parts (modules) and communicate with server (AMF). That marks a round
circle come from the user browser and go to the server and come back with
something to the user again... and all of that with great "flex"
productivity :)



>
> -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.

Re: [FlexJS] Some things still missing ni FlexJS

[Carlos Rovira]

Hi Peter,

2017-01-13 19:22 GMT+01:00 Peter Ent :

> I was speaking to a friend that has some JavaScript developers working for
> him. They use React and React/Native for their mobile apps. His feeling is
> that web-centric apps (e.g. Amazon.com) are going to be replaced with
> mobile apps since mobile devices are cheaper than laptops. They are
> concentrating their app development to server-side services with native
> apps delivered via React/Native.
>
> IMO then, what FlexJS needs is the ability to go native. This isn't
> necessary for a 1.0 launch, but having FlexJS/Native with applications
> constructed in ActionScript and MXML and then cross-compiled into Swift or
> Java could go a long way to make FlexJS the platform for cross-device
> development.
>


I already see that. but for 2.0, as you said native (swift or java) seems
huge work.
But...what about SWF *native* ?
I mean, SWF Stage3D mode is very performant (I think even native) right?
I think FeathersUI is Stage3D powered and is performant on Native. someone
correct me If I'm wrong.
So maybe SWF should be not display object ready but stage3d ready to allow
us to have the same performance as native

That's is for me the main reason for SWF existence. Alex said that actual
SWF FlexJS framework based on display list could be very performant...I
don't know since we didn't make any benchmark here and that it had the
advantage of have accessibility implemented...

Re: [FlexJS] Problem in FlexJSStore

[piotrz]

Once I add above code something additional has been exposed.
JSONItemConverter crashed in function convertItem.

If data = "" function is adding to one "}". In the results JSON.parse("}")
is taking which cause an error. I think I it should be JSON.parse("{}");

I think this fix issue -> https://paste.apache.org/zHum - Let me know what
do you think.

Piotr



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

Re: [FlexJS] Some things still missing ni FlexJS

[Peter Ent]

See in-line.
‹peter

On 1/13/17, 1:35 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Peter,
>
>2017-01-13 19:22 GMT+01:00 Peter Ent :
>
>> I was speaking to a friend that has some JavaScript developers working
>>for
>> him. They use React and React/Native for their mobile apps. His feeling
>>is
>> that web-centric apps (e.g. Amazon.com) are going to be replaced with
>> mobile apps since mobile devices are cheaper than laptops. They are
>> concentrating their app development to server-side services with native
>> apps delivered via React/Native.
>>
>> IMO then, what FlexJS needs is the ability to go native. This isn't
>> necessary for a 1.0 launch, but having FlexJS/Native with applications
>> constructed in ActionScript and MXML and then cross-compiled into Swift
>>or
>> Java could go a long way to make FlexJS the platform for cross-device
>> development.
>>
>
>
>I already see that. but for 2.0, as you said native (swift or java) seems
>huge work.
>But...what about SWF *native* ?
>I mean, SWF Stage3D mode is very performant (I think even native) right?
>I think FeathersUI is Stage3D powered and is performant on Native. someone
>correct me If I'm wrong.
>So maybe SWF should be not display object ready but stage3d ready to allow
>us to have the same performance as native
>
>That's is for me the main reason for SWF existence. Alex said that actual
>SWF FlexJS framework based on display list could be very performant...I
>don't know since we didn't make any benchmark here and that it had the
>advantage of have accessibility implemented...

I wasn't thinking of FlexJS/Native as desire to dump SWF and JS-xcompile,
but FlexJS/Native as a new addition and option for folks who want to work
in ActionScript and layout their apps in MXML but want a native
application as the end result, rather than going through Cordova.

>

Re: [FlexJS] Problem in FlexJSStore

[Alex Harui]

We should probably build out some test cases for this.  It looks like
PropertyWatcher.parentChanged should be called with the parent object goes
from null to non-null, but maybe that code doesn't exist.

-Alex

On 1/13/17, 10:03 AM, "piotrz"  wrote:

>Place where it blow up cause of these PropertyWatcher is in wrapUpdate
>(WatcherBase):
>
> try
>{
>wrappedFunction.apply(this);
>}
>catch(error:Error)
>{
>we are logging on console here error
>}
>
>Searching no-null object, but how and where ? If I do not have such code
>once this property get back from null to not null during work of
>application
>we won't notice it ?
>
>Piotr
>
>
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Problem-in-Fle
>xJSStore-tp58232p58239.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Problem in FlexJSStore

[piotrz]

Basically we should build example where object with similar structure as in
case from FlexJSStore at start is null, but later it turns out to non-null -
Maybe it will be working without any additional changes.

Piotr



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

Re: [FlexJS] Some things still missing ni FlexJS

[Carlos Rovira]

2017-01-13 19:46 GMT+01:00 Peter Ent :

>
>
> I wasn't thinking of FlexJS/Native as desire to dump SWF and JS-xcompile,
> but FlexJS/Native as a new addition and option for folks who want to work
> in ActionScript and layout their apps in MXML but want a native
> application as the end result, rather than going through Cordova.
>
>
Right! I understand. I want to said that I see as you the benefits to go
native and Swift for iOS and Java for Android. But my point was that
the effort is huge and we could get easily to a v2.0 and one? two years?

I was saying that SWF Stage 3D could give as the performant benefits of
native and could be much easier and doable in less time..but without change
one thing for the other, I still would want iOS and Android Native! :)

Think that others like haxe finaly take the same path, and we should do the
same in the end


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

Re: [FlexJS] Some things still missing ni FlexJS

[Alex Harui]

On 1/13/17, 10:28 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>2017-01-13 19:11 GMT+01:00 Alex Harui :
>
>>
>>
>> IMO, there are at least some existing Flex apps that don't use AMF.  Now
>> it may turn out that we will have AMF shortly, but until it is done,
>>those
>> who don't need it can start migrating their apps today.  Some folks are
>> already migrating.
>
>
>I don't think so. For me flow data comes first and then other things.
>Without server connection I think almost no people will start migrating.
>People even can start a wireframe ugly project, but seeing data is coming
>and they can sent data. Then will come themes, and other eye candy
>things...

Some Flex apps I've seen used SOAP/XML.  I definitely know there is at
least one app under migration now and AIUI, it is using XML not AMF.  I
completely understand that with AMF we will become more attractive to more
Flex customers, but if we can make migration possible for folks using XML
or even JSON, why can't we call that our 1.0?  What would be wrong with
calling that 1.0?

-Alex

Re: [FlexJS] Problem in FlexJSStore

[Alex Harui]

On 1/13/17, 10:44 AM, "piotrz"  wrote:

>Once I add above code something additional has been exposed.
>JSONItemConverter crashed in function convertItem.
>
>If data = "" function is adding to one "}". In the results JSON.parse("}")
>is taking which cause an error. I think I it should be JSON.parse("{}");
>
>I think this fix issue -> https://paste.apache.org/zHum - Let me know what
>do you think.

Seems reasonable.

-Alex

Re: [FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Carlos Rovira]

Hi great to think in it as a bead. But this makes me thing about a way to
"inject the beads" so we doesn't need to touch code, but some config that
remove the inject of automation beads in all components...(the manual way
of write the bead and remove would be not usable in the real world)

2017-01-13 19:25 GMT+01:00 Alex Harui :

> My thought was that automated testing properties would be a separate bead.
>  That way you can more easily rip it out before going to production.
>
> My 2 cents,
> -Alex
>
> On 1/13/17, 5:53 AM, "Christofer Dutz"  wrote:
>
> >Hi,
> >
> >I am currently writing some unit-tests for the Examples and encountered
> >something I would like to discuss with you.
> >For example, in FlexJSStore the search field doesn’t have an id so it is
> >not very simple to select the field. I could simply give the field an id,
> >but I remembered in the old Flex there were “automationName” attributes
> >which elements could have. These names helped identifying elements during
> >tests. What do you think if we should start supporting some attributes
> >that help writing tests (This would also be something that other
> >frameworks don’t have and that could be treated as quite handy).
> >
> >Chris
>
>


-- 

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] [Discuss] Add support for "automationName" for making unit-tests simpler

[piotrz]

Hi Guys,

In my opinion injecting Beads by some configuration will confuse people. As
I understand such Bead which adding automation name will take same parameter
with this name. 

Once you have Beads in your view it's giving really nice and clean
information, what actually is happening with component.

Piotr





-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Discuss-Add-support-for-automationName-for-making-unit-tests-simpler-tp58230p58255.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Alex Harui]

On 1/13/17, 11:03 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi great to think in it as a bead. But this makes me thing about a way to
>"inject the beads" so we doesn't need to touch code, but some config that
>remove the inject of automation beads in all components...(the manual way
>of write the bead and remove would be not usable in the real world)

The compiler could probably be taught to filter certain tags out of the
MXML.

If we don't like that idea, some configuration could swap in a "null"
implementation behind those tags so they have lower cost and don't do
anything.

-Alex

Re: [FlexJS] Some things still missing ni FlexJS

[piotrz]

I was working on Big Flex app where we were using SOAP/XML. - I think now we
can consume XML in FlexJS.

Another thing which came up to my mind - Did we ever write any WIKI page to
show people what actually option of data consuming we have ? 

I think if it will be pointed on WIKI and in Release notes somewhere it gets
an attention - What do you think ?

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Some-things-still-missing-ni-FlexJS-tp57985p58257.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Alex Harui]

On 1/13/17, 11:09 AM, "piotrz"  wrote:

>Hi Guys,
>
>In my opinion injecting Beads by some configuration will confuse people.
>As
>I understand such Bead which adding automation name will take same
>parameter
>with this name. 
>
>Once you have Beads in your view it's giving really nice and clean
>information, what actually is happening with component.

I think both Carlos and I are thinking of ejecting instead of injecting.
IOW, you would declare beads in MXML but compiler options would filter
those tags out of the output.  Sort of like conditional compilation.
Maybe like:


   
  

And then run with:

mxmlc -ignore-tag=js:AutomationData

My 2 cents.  Other ideas welcome.
-Alex

Re: [FlexJS] Some things still missing ni FlexJS

[Alex Harui]

On 1/13/17, 11:13 AM, "piotrz"  wrote:

>I was working on Big Flex app where we were using SOAP/XML. - I think now
>we
>can consume XML in FlexJS.

Yes.  You can migrate today if you are using XML, only need to support one
language and don't use modules.  Regarding skinning, in theory your
company already has CSS for branding other web-pages and hopefully a lot
of that can be used in FlexJS assuming the only skinning you need is to
brand the app as opposed to offering lots of different skins for your
customers to choose.

We don't have support for WSDL handling or decoding SOAP to ValueObjects
yet, but instead of us having to write that code before we get more
customers, I keep hoping that one customer will show up and say "I can't
wait to migrate anymore and I think it will be cheaper to have one of my
developers help build out this missing feature than to have my team port
the whole app to some other JS framework."  What I think we need is
"credibility" via a testimonial.  I think folks who have to migrate now
just pass up FlexJS for React or Angular because they aren't sure that
FlexJS is ready.  FlexJS isn't a "safe" choice yet.  That's why if one
person can attest that it was safe enough for them, that could cause one
more person to not pass on us and get the ball rolling faster.


>
>Another thing which came up to my mind - Did we ever write any WIKI page
>to
>show people what actually option of data consuming we have ?
>
>I think if it will be pointed on WIKI and in Release notes somewhere it
>gets
>an attention - What do you think ?

It should be documented somewhere, but that opens the whole debate about
where to document.  Some folks don't want to add more stuff to the wiki.
IMO, as Peter gets going on Tour De FlexJS, that where we should document
the ways to get data.

My 2 cents,
-Alex

Re: git commit: [flex-asjs] [refs/heads/develop] - MDL Table component and example initial implementation

[Piotr Zarzycki]

Love this commit :)

On Fri, Jan 13, 2017, 20:34  wrote:

> Repository: flex-asjs
> Updated Branches:
>   refs/heads/develop 2e52060f3 -> b0b41aefe
>
>
> MDL Table component and example initial implementation
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/b0b41aef
> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/b0b41aef
> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/b0b41aef
>
> Branch: refs/heads/develop
> Commit: b0b41aefe2a419d310c010299430ba56bf87d974
> Parents: 2e52060
> Author: Carlos Rovira 
> Authored: Fri Jan 13 20:34:17 2017 +0100
> Committer: Carlos Rovira 
> Committed: Fri Jan 13 20:34:17 2017 +0100
>
> --
>  .../src/main/flex/MainNavigation.mxml   |   1 +
>  .../flexjs/MDLExample/src/main/flex/Tables.mxml |  41 ++
>  .../src/main/flex/models/MainNavigationModel.as |   1 +
>  .../src/main/flex/models/TablesModel.as |  41 ++
>  .../MDLExample/src/main/flex/vos/MaterialVO.as  |  35 +
>  .../main/flex/org/apache/flex/mdl/Navigation.as |   2 +-
>  .../src/main/flex/org/apache/flex/mdl/Table.as  |  30 ++--
>  .../flex/mdl/itemRenderers/TableItemRenderer.as | 145 +++
>  .../src/main/resources/defaults.css |  10 ++
>  .../src/main/resources/mdl-manifest.xml |   2 +
>  10 files changed, 293 insertions(+), 15 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/b0b41aef/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> --
> diff --git a/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> b/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> index f056f18..a2414b8 100644
> --- a/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> +++ b/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> @@ -74,6 +74,7 @@ limitations under the License.
>  
>  
>  
> +
>  
>  
>  
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/b0b41aef/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> --
> diff --git a/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> b/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> new file mode 100644
> index 000..a5591d7
> --- /dev/null
> +++ b/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> @@ -0,0 +1,41 @@
> +
> +
> +http://ns.adobe.com/mxml/2009";
> + xmlns:js="library://ns.apache.org/flexjs/basic"
> + xmlns:mdl="library://ns.apache.org/flexjs/mdl"
> + xmlns="http://www.w3.org/1999/xhtml";
> + xmlns:models="models.*">
> +
> +
> +
> +   
> +
> +
> +
> +
> + +sourceID="model"
> +sourcePropertyName="materials"
> +destinationPropertyName="dataProvider" />
> +
> +
> +
> +
> +
> \ No newline at end of file
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/b0b41aef/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> --
> diff --git
> a/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> b/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> index 5330ae4..12fbbf3 100644
> ---
> a/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> +++
> b/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> @@ -63,6 +63,7 @@ package models
>  new NavigationLinkVO("Snackbar", "snackbar_panel"),
>  new NavigationLinkVO("Toggles", "toggles_panel"),
>  new NavigationLinkVO("Lists", "lists_panel"),
> +new NavigationLinkVO("Tables", "tables_panel"),
>  new NavigationLinkVO("Loading", "loading_panel"),
>  new NavigationLinkVO("Menu", "menus_panel"),
>  new NavigationLinkVO("Badges", "badges_panel"),
>
>
> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/b0b41aef/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.as
> --
> diff --git
> a/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.as
> b/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.as
> new file mode 100644
> index 000..19e355e
> --- /dev/null
> +++ b/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.as
> @@ -0,0 +1,41 @@
>
> +
> +//
> +//  Licensed to the Apache Software Foundation (ASF) under o

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

OK. I pushed changes that should generate the code code for [Bindable] on
getter/setters.

HTH,
-Alex

On 1/10/17, 2:38 PM, "piotrz"  wrote:

>No problem - "patient" - will be my second name :)
>
>I just did small clarification for code in ViewDataBinding. I will commit
>it
>along with this first fix for this jira.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58136.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

I just tested it and it's working fine. Now we have clean VO object without
dispatching anything inside and in view. :)

Multiple reference binding is still not working. I will take a look now to
this closer.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58262.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

Alex,

I see the problem it's probably again in the compiler. I have two classes
A[1] and B[2]. Class B is being created in A, but after compilation I have
null there. Generated Class A [3] - Doesn't contain B at all.

[1] https://paste.apache.org/t5pH
[2] https://paste.apache.org/ji8J
[3] https://paste.apache.org/ln6f

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58263.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

OK.  There should be an array of 3 properties in the data binding
structure.  It shouldn't give up and create a getter function.  Then,
ViewDataBinding may need to detect that and use a ChainBinding.  It could
borrow code from ContainerDataBinding.

-Alex

On 1/13/17, 12:04 PM, "piotrz"  wrote:

>I just tested it and it's working fine. Now we have clean VO object
>without
>dispatching anything inside and in view. :)
>
>Multiple reference binding is still not working. I will take a look now to
>this closer.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58262.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

OK.  I will take a look.

But if you workaround it by using getter/setter and not a [Bindable] var,
does that allow the chain to work?

-Alex

On 1/13/17, 12:13 PM, "piotrz"  wrote:

>Alex,
>
>I see the problem it's probably again in the compiler. I have two classes
>A[1] and B[2]. Class B is being created in A, but after compilation I have
>null there. Generated Class A [3] - Doesn't contain B at all.
>
>[1] https://paste.apache.org/t5pH
>[2] https://paste.apache.org/ji8J
>[3] https://paste.apache.org/ln6f
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58263.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

With getter and setter class B has been created, but Binding doesn't work. I
will take a look in that scenario what is happening with binding. 
Generated binding array [1]

[1] https://paste.apache.org/LodF

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58266.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

Please post the source as well.

On 1/13/17, 12:25 PM, "piotrz"  wrote:

>With getter and setter class B has been created, but Binding doesn't
>work. I
>will take a look in that scenario what is happening with binding.
>Generated binding array [1]
>
>[1] https://paste.apache.org/LodF
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58266.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

I'm looking for the MXML file with the {} expression.

Thanks,
-Alex

On 1/13/17, 12:46 PM, "piotrz"  wrote:

>Source for A [1], B [2] and InitView [3]
>
>[1] https://paste.apache.org/6YzL
>[2] https://paste.apache.org/hMCA
>[3] https://paste.apache.org/QfK3
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58268.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

Source for A [1], B [2] and InitView [3]

[1] https://paste.apache.org/6YzL
[2] https://paste.apache.org/hMCA
[3] https://paste.apache.org/QfK3

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58268.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

Alex,

Do not understand - You need MXML code? 

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58270.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

Yeah, I wanted to see what the original data binding expression looks like.

Thanks,
-Alex

On 1/13/17, 12:59 PM, "piotrz"  wrote:

>Alex,
>
>Do not understand - You need MXML code?
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58270.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

In AS class A [1], B [2], InitView [3] and A [4] before I change subClass to
getter/setter/

[1] https://paste.apache.org/YRqm
[2] https://paste.apache.org/Gwsl
[3] https://paste.apache.org/6q5m
[4] https://paste.apache.org/DlLs



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58272.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

I just tested your last commit and it's working, so multiple ref binding is
still which I need to investigate.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58273.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

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

[flex . ci . builds]

flex-sdk_release-candidate - Build #201 - Successful

Changes since last build:
[Mihai Chira] FLEX-27509

[Mihai Chira] FLEX-35149 updating release notes with fix for FLEX-27509


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

Re: [FlexJS] Data-binding fails when following multiple references

[piotrz]

Alex,

I think in case of subClass again _bindings [1] array is wrong. Cause
sourceID is being searched in View - Take a look:

 

I think in case of subClass it should look or something like that:
["anyClass.subClass", "fieldC"]

[1] https://paste.apache.org/WAYT

Piotr





-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58275.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Data-binding fails when following multiple references

[Alex Harui]

IMO, the output should be:
["anyClass", "subClass", "fieldC"]



I will look into it.

-Alex

On 1/13/17, 1:42 PM, "piotrz"  wrote:

>Alex,
>
>I think in case of subClass again _bindings [1] array is wrong. Cause
>sourceID is being searched in View - Take a look:
>
>.png> 
>
>I think in case of subClass it should look or something like that:
>["anyClass.subClass", "fieldC"]
>
>[1] https://paste.apache.org/WAYT
>
>Piotr
>
>
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Data-binding-f
>ails-when-following-multiple-references-tp58022p58275.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] static method with arguments failing

[Carlos Rovira]

Hi, I'm trying to create a ObjectUtil.as Core class with the following
method borrowed from Flex SDK:

/**
 * Convert the object to a string of form: PROP: VAL&PROP: VAL
where: PROP is a property VAL is its corresponding value & is the specified
optional delimiter
 * @param obj Object to convert
 * @param delimiter (optional) Delimiter of property/value pairs
 * @return An string of all property/value pairs delimited by the
given string or null if the input object or delimiter is null.
 */
public static function toString( obj:Object=null, delimiter:String
= "\n" ):String
{
if ( obj == null || delimiter == null )
{
return "";
}
else
{
var ret:Array = [];

for ( var s:Object in obj )
{
ret.push( s + ": " + obj[s] );
}

return ret.join( delimiter );
}
}


when I try to use it in a SWC library it fails with this error:

Incorrect number of arguments.  Expected no more than 0
   var str:String = ObjectUtil.toString(value);
^

I'm trying to see where is the problem without luck

Some idea of what is going wrong here?

Thanks


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

Re: [FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Carlos Rovira]

mmm I was thinink on Injecting, but inject could be problematic since
mainly *all* components would get the automation bead and maybe that's not
what we want. Ejecting? mmm don't like the idea of "writing" it down to the
component...don't know right now

I like the spring framework philosophy for this cases where some
configuration makes what you want without *blurring* the code.

In such philosophy you don't put nothing in the code, and instead you
configure in some external resources what you want to put or quit at your
discretion, so in this case, you could have a list of controls that will
have automation bead in a config file, and that list would be used to
inject automation bead in the listed controls (maybe even the relation of
control and its corresponding automation bead





2017-01-13 20:16 GMT+01:00 Alex Harui :

>
>
> On 1/13/17, 11:09 AM, "piotrz"  wrote:
>
> >Hi Guys,
> >
> >In my opinion injecting Beads by some configuration will confuse people.
> >As
> >I understand such Bead which adding automation name will take same
> >parameter
> >with this name.
> >
> >Once you have Beads in your view it's giving really nice and clean
> >information, what actually is happening with component.
>
> I think both Carlos and I are thinking of ejecting instead of injecting.
> IOW, you would declare beads in MXML but compiler options would filter
> those tags out of the output.  Sort of like conditional compilation.
> Maybe like:
>
> 
>
>   
>
> And then run with:
>
> mxmlc -ignore-tag=js:AutomationData
>
> My 2 cents.  Other ideas welcome.
> -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.

Re: git commit: [flex-asjs] [refs/heads/develop] - MDL Table component and example initial implementation

[Carlos Rovira]

Yeah! :)

2017-01-13 20:43 GMT+01:00 Piotr Zarzycki :

> Love this commit :)
>
> On Fri, Jan 13, 2017, 20:34  wrote:
>
> > Repository: flex-asjs
> > Updated Branches:
> >   refs/heads/develop 2e52060f3 -> b0b41aefe
> >
> >
> > MDL Table component and example initial implementation
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/b0b41aef
> > Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/b0b41aef
> > Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/b0b41aef
> >
> > Branch: refs/heads/develop
> > Commit: b0b41aefe2a419d310c010299430ba56bf87d974
> > Parents: 2e52060
> > Author: Carlos Rovira 
> > Authored: Fri Jan 13 20:34:17 2017 +0100
> > Committer: Carlos Rovira 
> > Committed: Fri Jan 13 20:34:17 2017 +0100
> >
> > --
> >  .../src/main/flex/MainNavigation.mxml   |   1 +
> >  .../flexjs/MDLExample/src/main/flex/Tables.mxml |  41 ++
> >  .../src/main/flex/models/MainNavigationModel.as |   1 +
> >  .../src/main/flex/models/TablesModel.as |  41 ++
> >  .../MDLExample/src/main/flex/vos/MaterialVO.as  |  35 +
> >  .../main/flex/org/apache/flex/mdl/Navigation.as |   2 +-
> >  .../src/main/flex/org/apache/flex/mdl/Table.as  |  30 ++--
> >  .../flex/mdl/itemRenderers/TableItemRenderer.as | 145
> +++
> >  .../src/main/resources/defaults.css |  10 ++
> >  .../src/main/resources/mdl-manifest.xml |   2 +
> >  10 files changed, 293 insertions(+), 15 deletions(-)
> > --
> >
> >
> >
> > http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> b0b41aef/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> > --
> > diff --git a/examples/flexjs/MDLExample/src/main/flex/MainNavigation.
> mxml
> > b/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> > index f056f18..a2414b8 100644
> > --- a/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> > +++ b/examples/flexjs/MDLExample/src/main/flex/MainNavigation.mxml
> > @@ -74,6 +74,7 @@ limitations under the License.
> >  
> >  
> >  
> > +
> >  
> >  
> >  
> >
> >
> > http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> b0b41aef/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> > --
> > diff --git a/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> > b/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> > new file mode 100644
> > index 000..a5591d7
> > --- /dev/null
> > +++ b/examples/flexjs/MDLExample/src/main/flex/Tables.mxml
> > @@ -0,0 +1,41 @@
> > +
> > +
> > +http://ns.adobe.com/mxml/2009";
> > + xmlns:js="library://ns.apache.org/flexjs/basic"
> > + xmlns:mdl="library://ns.apache.org/flexjs/mdl"
> > + xmlns="http://www.w3.org/1999/xhtml";
> > + xmlns:models="models.*">
> > +
> > +
> > +
> > +   
> > +
> > +
> > +
> > +
> > + > +sourceID="model"
> > +sourcePropertyName="materials"
> > +destinationPropertyName="dataProvider" />
> > +
> > +
> > +
> > +
> > +
> > \ No newline at end of file
> >
> >
> > http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> b0b41aef/examples/flexjs/MDLExample/src/main/flex/
> models/MainNavigationModel.as
> > --
> > diff --git
> > a/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> > b/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> > index 5330ae4..12fbbf3 100644
> > ---
> > a/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> > +++
> > b/examples/flexjs/MDLExample/src/main/flex/models/MainNavigationModel.as
> > @@ -63,6 +63,7 @@ package models
> >  new NavigationLinkVO("Snackbar", "snackbar_panel"),
> >  new NavigationLinkVO("Toggles", "toggles_panel"),
> >  new NavigationLinkVO("Lists", "lists_panel"),
> > +new NavigationLinkVO("Tables", "tables_panel"),
> >  new NavigationLinkVO("Loading", "loading_panel"),
> >  new NavigationLinkVO("Menu", "menus_panel"),
> >  new NavigationLinkVO("Badges", "badges_panel"),
> >
> >
> > http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
> b0b41aef/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.as
> > --
> > diff --git
> > a/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.as
> > b/examples/flexjs/MDLExample/src/main/flex/models/TablesModel.a

Re: [FlexJS] Some things still missing ni FlexJS

[Carlos Rovira]

2017-01-13 20:01 GMT+01:00 Alex Harui :

>
>
>  why can't we call that our 1.0?  What would be wrong with
> calling that 1.0?
>
>
As I said, for me 0.8, 1.0, 0.15 or 2.1 is not a problem. Things out there
taught us that number version not really matters
I'm more with the internal thinking that make us think "we're not ready yet
for prime time", and my position is that we should try to
cover the few holes we have as soon as we can (i.e: for me, IMHO, modules
and AMF), and then as you said let people come and
help we others (i.e: for example WS/WSDL, and others that seems less
crucial or adopted out there).

just my 2cnts

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

Re: [FlexJS] static method with arguments failing

[Carlos Rovira]

The problem seems related to the method name "toString" already in use...

But the object doesn't extend nothing, so there's no super.toString()

This seems a bug right?

I workaround changing the name to _toString(...)



2017-01-14 0:26 GMT+01:00 Carlos Rovira :

> Hi, I'm trying to create a ObjectUtil.as Core class with the following
> method borrowed from Flex SDK:
>
> /**
>  * Convert the object to a string of form: PROP: VAL&PROP: VAL
> where: PROP is a property VAL is its corresponding value & is the specified
> optional delimiter
>  * @param obj Object to convert
>  * @param delimiter (optional) Delimiter of property/value pairs
>  * @return An string of all property/value pairs delimited by the
> given string or null if the input object or delimiter is null.
>  */
> public static function toString( obj:Object=null, delimiter:String
> = "\n" ):String
> {
> if ( obj == null || delimiter == null )
> {
> return "";
> }
> else
> {
> var ret:Array = [];
>
> for ( var s:Object in obj )
> {
> ret.push( s + ": " + obj[s] );
> }
>
> return ret.join( delimiter );
> }
> }
>
>
> when I try to use it in a SWC library it fails with this error:
>
> Incorrect number of arguments.  Expected no more than 0
>var str:String = ObjectUtil.toString(value);
> ^
>
> I'm trying to see where is the problem without luck
>
> Some idea of what is going wrong here?
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


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

[FlexJS] Reflection API - How to Use

[Carlos Rovira]

Hi,

where I can learn to use the Reflection API?

I want to introspect a object an get the properties and its corresponding
values

If I make a for loop as normal I get lots of functions and see

FLEXJS_REFLECTION_INFO

I assume that's the work done by the reflection API, but can't find any
documentation or example on how to use

Thanks

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

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

[flex . ci . builds]

flex-sdk_release-candidate - Build #202 - 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/202/.

[FlexJS] className problem with MDL properties that modifies component className

[Carlos Rovira]

Hi,

found an issue with MDL and custom class.

If you declare a component that has some new custom additional class (lets
call "someClass"), and has some property that modifies the className (in
our case always through classList API), let's say is a button, and this is
the example:



the result is the colored className is remove from the list of applied
classes, since is not part of "typeNames" and className implementation
overrides all

We must say that properties that modifies className in MDL like "ripple",
"colored", etc... are by definition "behaviors" that use CSS (classNames)
to modify some visual aspect of the component or control, so me want don't
be affected if we apply a custom className like "someClass" right?

So If we set "colored" to true, we want the component maintains the
className that is applied and if we set to false we want to be remove from
classNames, and in no other way,

so the solution I have is to add a line in *each* property of each
component in MDL just behind the classList.add or classList.toggle
instruction that should be:

typeNames = element.className;

So, in this way we make the property part of typeNames while is activated
and if removed, we remove as well from typeNames, giving the control of
that visual aspect only to the setter of the property

I'll make that change tomorrow (it's very late here), if no body finds any
problem.

After much testing I don't see other way

Thanks

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

Re: [FlexJS] className problem with MDL properties that modifies component className

[OmPrakash Muppirala]

On Jan 13, 2017 6:30 PM, "Carlos Rovira"  wrote:

Hi,

found an issue with MDL and custom class.

If you declare a component that has some new custom additional class (lets
call "someClass"), and has some property that modifies the className (in
our case always through classList API), let's say is a button, and this is
the example:



the result is the colored className is remove from the list of applied
classes, since is not part of "typeNames" and className implementation
overrides all

We must say that properties that modifies className in MDL like "ripple",
"colored", etc... are by definition "behaviors" that use CSS (classNames)
to modify some visual aspect of the component or control, so me want don't
be affected if we apply a custom className like "someClass" right?

So If we set "colored" to true, we want the component maintains the
className that is applied and if we set to false we want to be remove from
classNames, and in no other way,

so the solution I have is to add a line in *each* property of each
component in MDL just behind the classList.add or classList.toggle
instruction that should be:

typeNames = element.className;

So, in this way we make the property part of typeNames while is activated
and if removed, we remove as well from typeNames, giving the control of
that visual aspect only to the setter of the property

I'll make that change tomorrow (it's very late here), if no body finds any
problem.

After much testing I don't see other way

Thanks


I ran into a similar problem with FontAwesome.  I think this is a good way
to fix this.

Can we override the classname setter to do

typeNames = element.className;

 after calling super?

Then maybe we dont need to do this in the future?

Thanks,
Om



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

Re: [FlexJS] Reflection API - How to Use

[Greg Dove]

Hi  Carlos,

If you look inside manualtests/GenericTests and in particular at the
reflection unit tests it should give you some (hopefully) good examples.

e.g. ReflectionTesterTest [1]

1.
https://git-wip-us.apache.org/repos/asf?p=flex-asjs.git;a=blob_plain;f=manualtests/GenericTests/src/flexUnitTests/reflection/ReflectionTesterTest.as;hb=refs/heads/develop




On Sat, Jan 14, 2017 at 2:00 PM, Carlos Rovira 
wrote:

> Hi,
>
> where I can learn to use the Reflection API?
>
> I want to introspect a object an get the properties and its corresponding
> values
>
> If I make a for loop as normal I get lots of functions and see
>
> FLEXJS_REFLECTION_INFO
>
> I assume that's the work done by the reflection API, but can't find any
> documentation or example on how to use
>
> Thanks
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: [FlexJS] static method with arguments failing

[Alex Harui]

On 1/13/17, 4:18 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>The problem seems related to the method name "toString" already in use...
>
>But the object doesn't extend nothing, so there's no super.toString()
>
>This seems a bug right?

Yes, please file a bug.

Thanks,
-Alex

Re: [FlexJS] [Discuss] Add support for "automationName" for making unit-tests simpler

[Alex Harui]

On 1/13/17, 3:35 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>mmm I was thinink on Injecting, but inject could be problematic since
>mainly *all* components would get the automation bead and maybe that's not
>what we want. Ejecting? mmm don't like the idea of "writing" it down to
>the
>component...don't know right now
>
>I like the spring framework philosophy for this cases where some
>configuration makes what you want without *blurring* the code.
>
>In such philosophy you don't put nothing in the code, and instead you
>configure in some external resources what you want to put or quit at your
>discretion, so in this case, you could have a list of controls that will
>have automation bead in a config file, and that list would be used to
>inject automation bead in the listed controls (maybe even the relation of
>control and its corresponding automation bead

That sounds good to me as well.

-Alex

Re: [FlexJS] className problem with MDL properties that modifies component className

[Alex Harui]

typeNames are classSelectors meant to act like TypeSelectors.  Like
DataGrid or DropDownList.  If the customer sets className it shouldn't
affect typeNames.

Can the customer also use the classList API?  If so, then you may need yet
another thing like typeNames like "internalClassNames" which is the list
controlled by the component developer and different from the classNames
specified by the customer.

Or maybe the way you are currently using classNames inside MDL should
actually be changing typeNames.

My 2 cents,
-Alex

On 1/13/17, 6:44 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>On Jan 13, 2017 6:30 PM, "Carlos Rovira"  wrote:
>
>Hi,
>
>found an issue with MDL and custom class.
>
>If you declare a component that has some new custom additional class (lets
>call "someClass"), and has some property that modifies the className (in
>our case always through classList API), let's say is a button, and this is
>the example:
>
>
>
>the result is the colored className is remove from the list of applied
>classes, since is not part of "typeNames" and className implementation
>overrides all
>
>We must say that properties that modifies className in MDL like "ripple",
>"colored", etc... are by definition "behaviors" that use CSS (classNames)
>to modify some visual aspect of the component or control, so me want don't
>be affected if we apply a custom className like "someClass" right?
>
>So If we set "colored" to true, we want the component maintains the
>className that is applied and if we set to false we want to be remove from
>classNames, and in no other way,
>
>so the solution I have is to add a line in *each* property of each
>component in MDL just behind the classList.add or classList.toggle
>instruction that should be:
>
>typeNames = element.className;
>
>So, in this way we make the property part of typeNames while is activated
>and if removed, we remove as well from typeNames, giving the control of
>that visual aspect only to the setter of the property
>
>I'll make that change tomorrow (it's very late here), if no body finds any
>problem.
>
>After much testing I don't see other way
>
>Thanks
>
>
>I ran into a similar problem with FontAwesome.  I think this is a good way
>to fix this.
>
>Can we override the classname setter to do
>
>typeNames = element.className;
>
> after calling super?
>
>Then maybe we dont need to do this in the future?
>
>Thanks,
>Om
>
>
>
>--
>Carlos Rovira
>http://about.me/carlosrovira