RE: [FlexJS] Spacers and positioning

[Yishay Weiss]

CenterElement (name can change) takes the RightAlignBead approach. It deals 
with conflicts by listening to the layoutComplete event and making the changes 
then. Maybe a bit expensive but it works.



From: Alex Harui
Sent: Sunday, February 12, 2017 8:56 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Spacers and positioning



In the current layouts, %width works the way it does in the browser and
not the way it did in Flex.  Where should we document that so folks find
it easily?

If someone wants to port the Flex layouts that's fine with me.  They will
be at least twice as slow, if not more, but that's PAYG for you.

I think you might be able to use Spacer as the FlexibleChild in
OneFlexibleChildHorizontalLayout

And we want the recommended JS patterns to work.  Nice to know that you
got position:absolute;right:0px; to work.  Supposedly "float: right" will
work as well, but I don’t think the SWF side supports that.

We are in the business of finding common patterns and encapsulating them.
So, it is totally within the FlexJS philosophy to have a bead called a
RightAlignBead that injects position:absolute;right:0px; into the styles
block.  There is probably some trickiness to dealing with conflicts if the
styles are also being set in some other way, but then you could do:



  

  


I'm not sure I understand the last code snippet, but there is no reason
not to create a 4ColumnLayout.  We have a VerticalColumnLayout already.
Find the pattern and encapsulate it so others can use it.  Try to keep it
small and loosely coupled.

My 2 cents,
-Alex

On 2/11/17, 10:07 PM, "Harbs"  wrote:

>Currently, the best you can do to spread elements in FlexJS is by using
>OneFlexibleChildVerticalLayout and OneFlexibleChildHorizontalLayout.
>
>The more we use FlexJS, the more we’re coming to the conclusion that we
>really need a ConstrainedLayout which has the features of the classic
>Flex layout…
>
>Harbs
>
>> On Feb 12, 2017, at 4:46 AM, Justin Mclean 
>>wrote:
>>
>> Hi,
>>
>> An old trick to get things to be pined to the RHS was to use a 100%
>>spacer in MXML.
>>
>> However code like this doesn’t work in FlexJS:
>>
>> 
>>
>>
>>
>> 
>>
>> But in FlexJS the spacer is 100% of the containers width and the button
>>wraps onto the next line.
>>
>> You can do this but is seems bit cumbersome:
>>
>> 
>>
>>
>> 
>>
>> And a little more cumbersome once you have several items you want to
>>evenly space.
>>
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>>
>> Is there a better way of doing this?
>>
>> Thanks,
>> Justin
>>
>

Re: [FlexJS] Uncaught type exception

[Alex Harui]

On 2/11/17, 10:18 PM, "Justin Mclean"  wrote:

>Hi,
>
>I trying something perhaps a little too complex fro FlexJS. First off
>does FlexJS support binding on setters/getters yet?

Binding works mostly.  It looks like the generated code might need a
try/catch.  File a bug.

>
>I think that the setter is being called before bigBox exists. Debugging
>the code I can see that this.numElements is 0 inside the colour method.

Yes, that is probably the case.  If your properties are being applied to
objects being created later you may have to defer the application of those
properties.  That was true in regular Flex as well.

Properties get applied early, children are created later.  Most of our
other components have a model so properties applied early are set in the
model and children pull their data from the model when created.

-Alex

Re: [FlexJS] Spacers and positioning

[Alex Harui]

In the current layouts, %width works the way it does in the browser and
not the way it did in Flex.  Where should we document that so folks find
it easily?

If someone wants to port the Flex layouts that's fine with me.  They will
be at least twice as slow, if not more, but that's PAYG for you.

I think you might be able to use Spacer as the FlexibleChild in
OneFlexibleChildHorizontalLayout

And we want the recommended JS patterns to work.  Nice to know that you
got position:absolute;right:0px; to work.  Supposedly "float: right" will
work as well, but I don’t think the SWF side supports that.

We are in the business of finding common patterns and encapsulating them.
So, it is totally within the FlexJS philosophy to have a bead called a
RightAlignBead that injects position:absolute;right:0px; into the styles
block.  There is probably some trickiness to dealing with conflicts if the
styles are also being set in some other way, but then you could do:



  

  


I'm not sure I understand the last code snippet, but there is no reason
not to create a 4ColumnLayout.  We have a VerticalColumnLayout already.
Find the pattern and encapsulate it so others can use it.  Try to keep it
small and loosely coupled.

My 2 cents,
-Alex

On 2/11/17, 10:07 PM, "Harbs"  wrote:

>Currently, the best you can do to spread elements in FlexJS is by using
>OneFlexibleChildVerticalLayout and OneFlexibleChildHorizontalLayout.
>
>The more we use FlexJS, the more we’re coming to the conclusion that we
>really need a ConstrainedLayout which has the features of the classic
>Flex layout…
>
>Harbs
>
>> On Feb 12, 2017, at 4:46 AM, Justin Mclean 
>>wrote:
>> 
>> Hi,
>> 
>> An old trick to get things to be pined to the RHS was to use a 100%
>>spacer in MXML.
>> 
>> However code like this doesn’t work in FlexJS:
>> 
>> 
>>
>>
>>
>> 
>> 
>> But in FlexJS the spacer is 100% of the containers width and the button
>>wraps onto the next line.
>> 
>> You can do this but is seems bit cumbersome:
>> 
>> 
>>
>>
>> 
>> 
>> And a little more cumbersome once you have several items you want to
>>evenly space.
>> 
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>> 
>> Is there a better way of doing this?
>> 
>> Thanks,
>> Justin
>> 
>

Re: [FlexJS] background colour bug

[Justin Mclean]

Hi,

I've raised a JIRA for this:
https://issues.apache.org/jira/browse/FLEX-35261 


Thanks,
Justin

Re: source forge downloads failing

[Alex Harui]

On 2/11/17, 11:22 AM, "Josh Tynjala"  wrote:

>This is also an issue for the Feathers SDK. I agree with Chris. If Adobe
>could move these files somewhere else, that would help the community a
>lot.
>The current workaround really seems like it's too cumbersome. Since the
>files are currently on SourceForge, maybe a repository on Github would be
>just as acceptable to Adobe.

I haven't tested the installer.  Has anyone?  It is using Adobe AIR.
Saxon is bundled so it isn't an issue.  The font kit is optional.

Apparently, it is very difficult for Adobe to change where the font kit
files are.  We could switch back to downloading the entire Adobe Flex 4.6
and unpacking the font kit jars.  I believe that is on a CDN and not
source forge.

-Alex

Re: [FlexJS] background colour bug

[Harbs]

Confirmed.

It looks like it parses the color into an integer value, and it never gets 
saved as a hex value in the styles.

> On Feb 12, 2017, at 5:57 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> Looks like this works (ie you get a big red square):
> 
> 
> http://ns.adobe.com/mxml/2009;
>xmlns:js="library://ns.apache.org/flexjs/basic">
>
>
>
> 
>
> style="background-color:red;">
>
>
> 
> 
> However using HTML RGB value like this doesn’t seem to work:
> 
> 
> style="background-color:#FF;">
>
> 
> 
> Anyone confirm and do you want me to raise a JIRA? I’m using a nightly from a 
> few days ago.
> 
> Thanks,
> Justin
> 
> 
> 

[FlexJS] Uncaught type exception

[Justin Mclean]

Hi,

I trying something perhaps a little too complex fro FlexJS. First off does 
FlexJS support binding on setters/getters yet?

I have this code:

http://ns.adobe.com/mxml/2009;
   xmlns:js="library://ns.apache.org/flexjs/basic"
   xmlns:comp="components.*">

   
   
   
   
   

   
   


And this component:


http://ns.adobe.com/mxml/2009; 
xmlns:js="library://ns.apache.org/flexjs/basic">

   
 
   

   

   
   
   


When I run the application I get this exception.

Box.js:88 Uncaught TypeError: Cannot set property 'style' of undefined
   at components.Box.__bindingWrappedSetter__colour (Box.js:88)
   at components.Box.bindable__set__colour (Box.js:124)
   at components.Box.set__colour (Box.js:135)
   at 
Function.org.apache.flex.utils.MXMLDataInterpreter.initializeStrandBasedObject 
(MXMLDataInterpreter.js:158)
   at Function.org.apache.flex.utils.MXMLDataInterpreter.generateMXMLArray 
(MXMLDataInterpreter.js:95)
   at Function.org.apache.flex.utils.MXMLDataInterpreter.generateMXMLInstances 
(MXMLDataInterpreter.js:218)
   at 
org.apache.flex.core.View.org.apache.flex.core.ContainerBase.addedToParent 
(ContainerBase.js:149)
   at Main.org.apache.flex.core.Application.addElement (Application.js:116)
   at Main.org.apache.flex.core.Application.initialize (Application.js:55)
   at Main.org.apache.flex.core.Application.start (Application.js:212)
components.Box.__bindingWrappedSetter__colour @ Box.js:88
components.Box.bindable__set__colour @ Box.js:124
components.Box.set__colour @ Box.js:135
org.apache.flex.utils.MXMLDataInterpreter.initializeStrandBasedObject @ 
MXMLDataInterpreter.js:158
org.apache.flex.utils.MXMLDataInterpreter.generateMXMLArray @ 
MXMLDataInterpreter.js:95
org.apache.flex.utils.MXMLDataInterpreter.generateMXMLInstances @ 
MXMLDataInterpreter.js:218
org.apache.flex.core.ContainerBase.addedToParent @ ContainerBase.js:149
org.apache.flex.core.Application.addElement @ Application.js:116
org.apache.flex.core.Application.initialize @ Application.js:55
org.apache.flex.core.Application.start @ Application.js:212
(anonymous) @ index.html:108

I think that the setter is being called before bigBox exists. Debugging the 
code I can see that this.numElements is 0 inside the colour method.

Thanks,
Justin

Re: [FlexJS] Spacers and positioning

[Harbs]

Currently, the best you can do to spread elements in FlexJS is by using 
OneFlexibleChildVerticalLayout and OneFlexibleChildHorizontalLayout.

The more we use FlexJS, the more we’re coming to the conclusion that we really 
need a ConstrainedLayout which has the features of the classic Flex layout…

Harbs

> On Feb 12, 2017, at 4:46 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> An old trick to get things to be pined to the RHS was to use a 100% spacer in 
> MXML.
> 
> However code like this doesn’t work in FlexJS:
> 
> 
>
>
>
> 
> 
> But in FlexJS the spacer is 100% of the containers width and the button wraps 
> onto the next line.
> 
> You can do this but is seems bit cumbersome:
> 
> 
>
>
> 
> 
> And a little more cumbersome once you have several items you want to evenly 
> space.
> 
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 
> 
> Is there a better way of doing this?
> 
> Thanks,
> Justin
> 

[FlexJS] background colour bug

[Justin Mclean]

Hi,

Looks like this works (ie you get a big red square):


http://ns.adobe.com/mxml/2009;
xmlns:js="library://ns.apache.org/flexjs/basic">










However using HTML RGB value like this doesn’t seem to work:






Anyone confirm and do you want me to raise a JIRA? I’m using a nightly from a 
few days ago.

Thanks,
Justin

[FlexJS] Spacers and positioning

[Justin Mclean]

Hi,

An old trick to get things to be pined to the RHS was to use a 100% spacer in 
MXML.

However code like this doesn’t work in FlexJS:







But in FlexJS the spacer is 100% of the containers width and the button wraps 
onto the next line.

You can do this but is seems bit cumbersome:






And a little more cumbersome once you have several items you want to evenly 
space.




















Is there a better way of doing this?

Thanks,
Justin

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

[flex . ci . builds]

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

draft announcement for 4.16.0

[Justin Mclean]

The Apache Flex community is pleased to announce the release of Apache
Flex SDK 4.16.0

The Apache Flex SDK is a highly productive, open source application
framework for building and maintaining expressive applications that deploy
consistently on all major browsers, desktops and devices (including
smartphones, tablets and tv).

The Apache Flex SDK 4.16.0 is an update to Apache Flex SDK 4.15.0 that
adds support for the latest Flash Player and AIR runtimes and many bug fixes.

For more details, see the release notes at:
http://www.apache.org/dist/flex/4.16.0/RELEASE_NOTES 



The Apache Flex SDK is available in source form from the following
download page:
http://flex.apache.org/download-source.html 


It's recommended you install the Apache Flex SDK by using the Apache Flex
IDE installer:
http://flex.apache.org/installer.html 

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

For more information on Apache Flex, visit the project home page:
http://flex.apache.org 

Thank you for using Apache Flex,
The Apache Flex Community

Re: [ApacheCon] Let's make it happen :-)

[Justin Mclean]

Hi,

As the CFP is “over” I’ve updated the us.apacheflexjs. 
org site. As always pull requests welcome.

We need to announce the speakers/schedule on March 9th but we could put it up 
sooner if need be and that’s OK with the LF. Chris what do you want to do here?

To update the site with the speakers I need:
- 100x100 jpeg of speaker (head and shoulders)
- title of talk
- description of talk

For the schedule we need times of talks and breaks.

Re sponsors logos at the bottom of the page. Chris you said your company would 
make some t-shirts I think that deserves a logo there. What do other PMC 
members think?

I also know there’s at least one other potential sponsor, has that been sorted 
with LF Chris?

Thanks,
Justin

[DISCUSS] Release Apache Flex SDK 4.16 RC2

[Justin Mclean]

Hi,

Please discuss the release candidate here and not in the vote thread.

Thanks,
Justin

[VOTE] Release Apache Flex SDK 4.16 RC2

[Justin Mclean]

Hi,

This is a  Apache Flex 4.16 release candidate 2. Please see the
RELEASE_NOTES and the README.

The release candidate can be found here;
https://dist.apache.org/repos/dist/dev/flex/sdk/4.16.0/rc2/ 


Before voting please review the section,"What are the ASF requirements on
approving a release?", at:
http://www.apache.org/dev/release.html#approving-a-release 


At a minimum you would be expected to check that:
- MD5 and signed packages are correct
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
- That you can compile from source package
- That the SDK can be used in your IDE of choice
- That the SDK can be used to make a mobile, desktop and browser
application

Please vote to approve this release:
+1 Approve the release
-1 Don’t approve the release (please provide specific comments to why)

This vote will be open for 72 hours or until a result can be called.

The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes

If you find an issue with the release that's a "show stopper" please don't
hold off voting -1. If someone votes -1 please continue testing we want to
try and catch as many issues as we can and cut down on the number of
release candidates. Remember existing voters can change their vote during
the voting process.

People who are not in PMC are also encouraged to test out the release and
vote, although their votes will not be binding, they can influence how the
PMC votes.

When voting please indicate what OS, IDE, Flash Player version and AIR
version you tested the SDK with.

Please put all discussion about this release in the DISCUSSION thread not
this VOTE thread.

Thanks,
Justin

Re: source forge downloads failing

[Josh Tynjala]

This is also an issue for the Feathers SDK. I agree with Chris. If Adobe
could move these files somewhere else, that would help the community a lot.
The current workaround really seems like it's too cumbersome. Since the
files are currently on SourceForge, maybe a repository on Github would be
just as acceptable to Adobe.

- Josh

On Sat, Feb 11, 2017 at 7:47 AM, Christofer Dutz 
wrote:

> Well I have to make the mavenizer not stop if it’s not able to download.
> I think this sucks … isn’t there a way for Adobe to host these files
> somewhere else?
> From my experience, if something doesn’t work out of the box and you have
> people manually patch things, they lose interest. I doubt the Flex
> installer or the mavenizer will be able to reliably work on normal machines.
>
> Chris
>
>
> Am 10.02.17, 23:09 schrieb "Alex Harui" :
>
> The font kit is optional.  Maybe some folks will have to go through
> more
> steps to get it.
>
> Saxon is available on Maven.  Bundle the NOTICEs in our repo and call
> it
> done.
>
> My 2 cents,
> -Alex
>
> On 2/10/17, 2:00 PM, "Justin Mclean"  wrote:
>
> >Hi,
> >
> >>  so we need our users to update the JCE, but this is not available
> >>outside of the US.
> >
> >How do we get around this bit? (For context about 20% of our web site
> >audience is from the US). I’m not sure it's all countries however.
> >
> >There seems to be serval countries where it can’t be used due to US
> >export laws/there import laws [1].
> >
> >Does this cause an issue with distribution of our source/binaries vs
> the
> >Apache license as we’re basically putting in a restriction of use???
> (I
> >don't know the answer to this.)
> >
> >Justin
> >
> >1.
> >http://crypto.stackexchange.com/questions/20524/why-there-
> are-limitations-
> >on-using-encryption-with-keys-beyond-certain-length
>
>
>
>

Re: source forge downloads failing

[Christofer Dutz]

Well I have to make the mavenizer not stop if it’s not able to download.
I think this sucks … isn’t there a way for Adobe to host these files somewhere 
else?
From my experience, if something doesn’t work out of the box and you have 
people manually patch things, they lose interest. I doubt the Flex installer or 
the mavenizer will be able to reliably work on normal machines. 

Chris


Am 10.02.17, 23:09 schrieb "Alex Harui" :

The font kit is optional.  Maybe some folks will have to go through more
steps to get it.

Saxon is available on Maven.  Bundle the NOTICEs in our repo and call it
done.

My 2 cents,
-Alex

On 2/10/17, 2:00 PM, "Justin Mclean"  wrote:

>Hi,
>
>>  so we need our users to update the JCE, but this is not available
>>outside of the US.
>
>How do we get around this bit? (For context about 20% of our web site
>audience is from the US). I’m not sure it's all countries however.
>
>There seems to be serval countries where it can’t be used due to US
>export laws/there import laws [1].
>
>Does this cause an issue with distribution of our source/binaries vs the
>Apache license as we’re basically putting in a restriction of use??? (I
>don't know the answer to this.)
>
>Justin
>
>1. 
>http://crypto.stackexchange.com/questions/20524/why-there-are-limitations-
>on-using-encryption-with-keys-beyond-certain-length

Re: Donating to Apache Flex

[Christofer Dutz]

Ok … responding to this part first:

3) I don’t see the need of this. I think our CI servers are now setup nicely. 
We have build-times of about 8-10 minutes. I don’t see a need to jump through 
all the hoops of having to maintain our own infrastructure. Yes, the Ant build 
doesn’t run on Infra, but I don’t see this as a problem of Infra, but more of 
the Ant build. The Maven build works nicely and I currently can’t think of 
anything that’s not possible at the moment. We now even have automated UI tests 
in Browsers and whenever I needed anything, I got it in the end. Yes it did 
usually take some time and convincing, but in the end things turned out exactly 
as we needed them. 

4) I don’t see this as a valid argument towards requiring our own Jira … ok … 
it is somewhat sluggish every now and then, but for example, being a TAC judge 
I like the option to search for a user’s Jira activity over several projects. 
If TLPs started having their own JIRAs, things would get a lot harder.

So now to some general thoughts:
- If we started this, probably a lot of the big projects would start getting a 
lot of funds. Funds that no longer go to the foundation, reducing the funds 
shared upon projects without their own funds. We have 3xx TLPs, but I doubt 
most of them would receive the funding they would need. So, we would have a 
hand full of rich projects and a lot of poor ones. I don’t think that’s the 
spirit of the Foundation. What about Apache Commons? Probably one of the 
most-used project, but probably also not one of the sexiest ones for getting 
funds? What about the Incubator? It’s one of the most important Projects of 
Apache, but it doesn’t have that outside marketing value.
- Having companies pay for individual Projects sort of produces a bad feeling 
in my gut. Even if they don’t say so, they still could and probably would 
expect something for their generous founds. I don’t want to be in the situation 
of having to implement something a company wants, because otherwise they 
threaten to cut funding.
- I think we suck at running infrastructure … at least compared to having a 
team of skilled people watching for Infra 24/7. What happens in the time lights 
are out in the US, if a service goes down just before Christmas? I don’t want 
to rely on volunteers to run our systems. That’s also the reason why Infra 
people are the only paid contractors at the ASF.
- There is a huge number of things you must deal with when running your own 
infrastructure. A lot of the things are quite restrictive on Apache Infra, but 
it’s not because they want to make our life harder, it’s because of damage that 
had been done in the past. We would have to re-learn all those lessons already 
learnt by Infra. Setting up a server is super-easy. Setting one up that’s not 
hackable in a handful of minutes by a Script-Kiddie is super-hard. 

So, if it’s just that one VM you are looking for, I don’t have any objections 
as I don’t see any difference to what we are doing now. But I don’t want to 
have an essential part of our Projects infrastructure outside of Infra. 

Chris



Am 10.02.17, 22:46 schrieb "Alex Harui" :

My reasons for spending time on this are several.
1) The ASF is growing and so are expenses.  Expenses rarely change based
on the economy, but donations can.  If a time ever comes to discuss
cutting expenses, I want to protect Flex by being able to make a case that
we don't cost the ASF any money and in fact, help.
2) We should be donating money to the ASF, but how many of you do?  I
don't myself.  And would it be easier to justify if the money went
directly to Flex?  It would for me.
3) I am currently paying for one of our CI servers.  If we could get
directed donations to pay for it, we might be able to upgrade to a faster
server.  I would personally donate more since I would get a tax break on
the donation.  And anyone who wants to pitch in can help and at least in
the US, get a tax break.
4) There are certain resources we share in the ASF like JIRA that are not,
IMO, optimally set up for us.  We can't create custom JIRA fields, for
example.  And more than one person has tripped over the Infra-centric
buttons on each JIRA issue.
5) I, and I think several board members, want to understand if handing off
more server responsibilities to the project would scale to other projects
and help the bottom line or hurt it.

Re: [ApacheCon] Let's make it happen :-)

[Christofer Dutz]

Hi,

Yesterday I got my hands on the first prints of our company newspaper (It’s 
actually more a little book) with my article on FlexJS ;-)
It’s free and there’s also a digital subscription: 
https://www.codecentric.de/wissen/softwerker/ (Just if anyone is interested in 
it)
Our companies Blog is also one of the most read tech-blogs in Germany and I’ll 
plan some follow up articles. 

But it does seem as if we are getting more and more traction (Just judging from 
the retweets I got after posting our FlexJS summit at some JavaScript topics ;-)

Chris


Am 11.02.17, 01:42 schrieb "Justin Mclean" :

Hi,

FYI we’ve had  more people than I expect look at the FlexJS site. Most of 
traffic is via direct links, but there’s a decent amount from twitter and a few 
referrers.

Thanks goes to Andisia Labs for this blog post: 
http://ardisialabsblog.blogspot.com.au

Once the CPF is over perhaps we can make more noise and get more people 
looking at it and hopefully that will turn into attendance.

Thanks,
Justin