Re: Parallel Mustella runs
I have an Azure VM sitting idle. Theoretically, we could add it as a second slave and divvy up the Mustella run into two halves. We should be able to have a single run in half the time. The more slaves we can add, the faster the run would get. Do you want me to give this idea a shot? You may want to wait until we get mustella running clean on Erik's Azure VM. In the meantime, we can discuss details. I think the simplest implementation is to add to each script some way to hide a bunch of folders and un-hide them after. I'm pretty sure mustella -all simply runs down the set of folders it finds in mustella/tests. There are other ways to subset, but I think that happens after compilation, so hiding folders is probably better. I don't think it is worth trying to implement some sort of email/failure consolidation subsystem. If we get 20 Vms running and you get 20 failure emails if you bust UIComponent, too bad ;-)
Re: Build failed in Jenkins: flex-sdk_mustella #119
OK, got what I needed. On 6/2/13 10:55 PM, Alex Harui aha...@adobe.com wrote: Hey, can I log in again? It looks like there are some tests that didn't have a win-specific bitmap and I want to see if there is a bad.png.xml for them. -Alex On 6/2/13 10:32 PM, Erik de Bruin e...@ixsoftware.nl wrote: So, the metric for success may require that script that checks for failures.txt and runs with the -failures options. Ok, that script is ready to go in 'jenkins.sh', it's commented out on the bottom of the file. But the interesting thing for me once we get this Jenkins thing running is: if several committers also set up this same Jenkins job, could we have them each run a subset of the mustella tests and report much sooner? I think it was you who suggested we could create a massively parallel mustella system. If only I was such a creative thinker. I won't take credit for that idea as I don't have a clue where to start, even ;-) EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Parallel Mustella runs
On Jun 2, 2013 11:01 PM, Alex Harui aha...@adobe.com wrote: I have an Azure VM sitting idle. Theoretically, we could add it as a second slave and divvy up the Mustella run into two halves. We should be able to have a single run in half the time. The more slaves we can add, the faster the run would get. Do you want me to give this idea a shot? You may want to wait until we get mustella running clean on Erik's Azure VM. In the meantime, we can discuss details. I think the simplest implementation is to add to each script some way to hide a bunch of folders and un-hide them after. I'm pretty sure mustella -all simply runs down the set of folders it finds in mustella/tests. There are other ways to subset, but I think that happens after compilation, so hiding folders is probably better. I was thinking more on the lines of creating shell scripts with explicit mustella calls with individual test directories as params. Or run a script on the master that walks through the tests directory and divvies them passes them to the slaves. This way is a bit more cleaner IMHO. I don't think it is worth trying to implement some sort of email/failure consolidation subsystem. If we get 20 Vms running and you get 20 failure emails if you bust UIComponent, too bad ;-) You don't? Although, I am hoping that Jenkins has some functionality like this. Thanks, Om
Re: Parallel Mustella runs
The VM I run is a 2 core, 3,5GB memory 'medium' instance. A full run takes 9 hours. I remember your VM was a bit lighter? EdB On Mon, Jun 3, 2013 at 7:44 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Jun 2, 2013 10:33 PM, Erik de Bruin e...@ixsoftware.nl wrote: So, the metric for success may require that script that checks for failures.txt and runs with the -failures options. Ok, that script is ready to go in 'jenkins.sh', it's commented out on the bottom of the file. But the interesting thing for me once we get this Jenkins thing running is: if several committers also set up this same Jenkins job, could we have them each run a subset of the mustella tests and report much sooner? I think it was you who suggested we could create a massively parallel mustella system. If only I was such a creative thinker. I won't take credit for that idea as I don't have a clue where to start, even ;-) EdB I have an Azure VM sitting idle. Theoretically, we could add it as a second slave and divvy up the Mustella run into two halves. We should be able to have a single run in half the time. The more slaves we can add, the faster the run would get. Do you want me to give this idea a shot? Thanks, Om -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Multidimensional States
Just trying to throw a quick thinking at it, in particular about the MXML
declaration mess - to avoid cartesian multiplication of states, couldn't we
just normalize them? I mean, grouping them in mutually exclusive groups,
which is the typical scenario:
s:states
s:ExclusiveStateGruop
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGruop
s:ExclusiveStateGruop
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGruop
s:ExclusiveStateGruop
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGruop
/s:states
This is different from the current freely assignable state groups, in that
they define the mixing rules of the various base states - thus we
implicitly expressed all the possible (and valid) combinations of the
various base state (in this case, 3*2*2 = 12 possible valid states),
instead of manually declaring a lot of states with long and unreadable
names (like overAndFocusedAndDefault).
The API should let specify multiple current states, as long as two mutually
exclusive state are not specified, for example with a sintax like this:
myComp.currentState = up-focused-nonDefault // VALID
myComp.currentState = up-down-nonDefault // INVALID
(to avoid confusion with current syntax, I think we should pick another
separator different from , to express these state trails) We may also
agree that the first state declared of each exclusive group is the default
value of its group, so that we can write:
myComp.currentState = up // same as up-nonFocused-nonDefault
Then, current state groups and MXML syntax would kick in, it should just
recognize the state trails:
s:Rect includeIn=focused alpha=0.5 alpha.default=0.7
...
s:Rect includeIn=focused-nonDefault
Or, we could also supports additional MXML like:
s:Rect alpha.up=0 alpha.over=0.5 alpha.over-focused=1.0 ...
In which more specific value assignment should win over more generic ones
(something like that is already implemented, when you write alpha=0
alpha.over=1).
Finally, from a compatibility point of view, a component using an
old-style states set could be just translated to a single mutually
exclusive state group (in fact, it is one) - the compiler should just
prevent mixing the two approaches.
2013/6/3 Alex Harui aha...@adobe.com
Hi Max,
Thanks for detailing it out.
In the relatively few minutes I've spent thinking about the problem, I
pondered whether the answer is to expand on how s:State is used, or simply
allow you to have conditional attributes based on things other than
States. IMO, along with this set of States is code you have to write to
set currentState appropriately, and in many cases, it seems like you're
just going to wire it to some other property. For this Button example, we
don't really have a isFocused property, but we certainly could add one,
and the Default states are all tied to what is currently called the
'emphasized' property. So why not some syntax that just lets you set a
property based on some other property? For sure there can be collisions,
or maybe it won't handle complex situations, but it seems like when I look
at the AS that we write when we give up on States, they are generally
simple expressions. So, while property.state implies the value of that
property when currentState is that State, maybe some other delimiter
besides '.' can be used to dictate the value of a property when some other
property is true or false or some simple expression. I'm going to use (
in this example, which may not be legal XML, but should give you an idea)
Then the states are simply:
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
And some widgets in the skin look like:
s:Rect id=focusBorder includeIn(isFocused)=
left(emphasized)=-2 left=-1 /
s:Rect id=background color.up=... color.down=...
color(currentState==upemphasized)
Now, when I look at that, I wonder: why not just use binding?
s:Rect id=focusBorder includeIn={isFocused}
left={emphasized ? -1 : -2} /
s:Rect id=background color.up=... color.down=...
color={(currentState==upemphasized) ? red : blue}
Yes, I know we told you not to use binding in skins for performance
reasons, but I am hoping to find ways to make databinding much faster in
FlexJS.
And one final thought: In FlexJS, we may end up saying that you shouldn't
specify these visual aspects in the skin. Instead, you might want to
use more CSS, and then we could implement attribute selectors on the AS
side since that CSS is going to work on the JS side.
Then you just have:
s:Rect id=focusBorder className=buttonFocusBorder
s:Rect id=background className=buttonBackground
And CSS like:
.buttonFocusBorder#focusBorder[emphasized] {
left: -2;
}
.buttonFocusBorder#focusBorder {
left: -1;
}
.buttonBackground#background[emphasize] {
[jira] [Commented] (FLEX-33500) XMLEncoder fails to encode WSDL simpleType union
[
https://issues.apache.org/jira/browse/FLEX-33500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672887#comment-13672887
]
Maurits Lourens commented on FLEX-33500:
We need this fix very urgently, so I'm wondering if it's possible to get a
pre-release of the 4.10.0 SDK. Can I access Jenkins to download an compiled
version of the SDK? I have no time to set I an environment to compile the SDK
myself...
XMLEncoder fails to encode WSDL simpleType union
Key: FLEX-33500
URL: https://issues.apache.org/jira/browse/FLEX-33500
Project: Apache Flex
Issue Type: Bug
Components: RPC: General, RPC: WebService
Affects Versions: Adobe Flex SDK 3.3 (Release)
Reporter: Maurits Lourens
Assignee: Justin Mclean
Labels: easyfix
The XMLEncoder can not encode simpleTypes with a definitionChild Union.
Steps to reproduce:
1. Create a WSDL with a request containing a simpleType, with a union child,
like this:
simpleType name=dateTimeOrEmpty
union memberTypes=dateTime tns:emptyString/
/simpleType
2. Create a sample project which uses this call to do send a date to the
server.
Expected behavior: the dateTime should be send to the server.
Actual behavior: the dateTime object is always empty (not nill).
The cause of this bug can be found inside the XMLEncoder. Around line 1340
you will find the function encodeSimpleType:
public function encodeSimpleType(definition:XML, parent:XML, name:QName,
value:*, restriction:XML = null):void
{
var definitionChild:XML = getSingleElementFromNode(definition,
constants.restrictionQName,
constants.listQName,
constants.unionQName);
if (definitionChild.name() == constants.restrictionQName)
{
// restriction
encodeSimpleRestriction(definitionChild, parent, name, value);
}
else if (definitionChild.name() == constants.listQName)
{
// list
encodeSimpleList(definitionChild, parent, name, value,
restriction);
}
else if (definitionChild.name() == constants.listQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value,
restriction);
}
}
If you look at this function, you see that the last else if statement is
exactly the same as the previous, so you will never execute the code inside
this statement, which is needed to encode union simpleTypes. To fix this, you
should change it to something like this:
else if (definitionChild.name() == constants.unionQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value, restriction);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
SDK Nightly builds?
Hi, Question just came up on JIRA. Do we want to publish nightly builds? We have Jenkins already creating a release build so it wouldn't be much work - only having Jenkins copying the compile release somewhere and documenting where it is. Thanks, Justin
[jira] [Commented] (FLEX-33500) XMLEncoder fails to encode WSDL simpleType union
[
https://issues.apache.org/jira/browse/FLEX-33500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672898#comment-13672898
]
Erik de Bruin commented on FLEX-33500:
--
The artefacts created by the Jenkins 'release' build
(https://builds.apache.org/job/flex-sdk_release/ws/out/) are for testing
purposes only and are in no way supported for other uses. They are not official
releases of the Apache Flex project.
XMLEncoder fails to encode WSDL simpleType union
Key: FLEX-33500
URL: https://issues.apache.org/jira/browse/FLEX-33500
Project: Apache Flex
Issue Type: Bug
Components: RPC: General, RPC: WebService
Affects Versions: Adobe Flex SDK 3.3 (Release)
Reporter: Maurits Lourens
Assignee: Justin Mclean
Labels: easyfix
The XMLEncoder can not encode simpleTypes with a definitionChild Union.
Steps to reproduce:
1. Create a WSDL with a request containing a simpleType, with a union child,
like this:
simpleType name=dateTimeOrEmpty
union memberTypes=dateTime tns:emptyString/
/simpleType
2. Create a sample project which uses this call to do send a date to the
server.
Expected behavior: the dateTime should be send to the server.
Actual behavior: the dateTime object is always empty (not nill).
The cause of this bug can be found inside the XMLEncoder. Around line 1340
you will find the function encodeSimpleType:
public function encodeSimpleType(definition:XML, parent:XML, name:QName,
value:*, restriction:XML = null):void
{
var definitionChild:XML = getSingleElementFromNode(definition,
constants.restrictionQName,
constants.listQName,
constants.unionQName);
if (definitionChild.name() == constants.restrictionQName)
{
// restriction
encodeSimpleRestriction(definitionChild, parent, name, value);
}
else if (definitionChild.name() == constants.listQName)
{
// list
encodeSimpleList(definitionChild, parent, name, value,
restriction);
}
else if (definitionChild.name() == constants.listQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value,
restriction);
}
}
If you look at this function, you see that the last else if statement is
exactly the same as the previous, so you will never execute the code inside
this statement, which is needed to encode union simpleTypes. To fix this, you
should change it to something like this:
else if (definitionChild.name() == constants.unionQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value, restriction);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33500) XMLEncoder fails to encode WSDL simpleType union
[
https://issues.apache.org/jira/browse/FLEX-33500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672901#comment-13672901
]
Maurits Lourens commented on FLEX-33500:
Thanks for the link, I can now at least test our software before the release of
4.10.0. Do you now when the release is planned?
XMLEncoder fails to encode WSDL simpleType union
Key: FLEX-33500
URL: https://issues.apache.org/jira/browse/FLEX-33500
Project: Apache Flex
Issue Type: Bug
Components: RPC: General, RPC: WebService
Affects Versions: Adobe Flex SDK 3.3 (Release)
Reporter: Maurits Lourens
Assignee: Justin Mclean
Labels: easyfix
The XMLEncoder can not encode simpleTypes with a definitionChild Union.
Steps to reproduce:
1. Create a WSDL with a request containing a simpleType, with a union child,
like this:
simpleType name=dateTimeOrEmpty
union memberTypes=dateTime tns:emptyString/
/simpleType
2. Create a sample project which uses this call to do send a date to the
server.
Expected behavior: the dateTime should be send to the server.
Actual behavior: the dateTime object is always empty (not nill).
The cause of this bug can be found inside the XMLEncoder. Around line 1340
you will find the function encodeSimpleType:
public function encodeSimpleType(definition:XML, parent:XML, name:QName,
value:*, restriction:XML = null):void
{
var definitionChild:XML = getSingleElementFromNode(definition,
constants.restrictionQName,
constants.listQName,
constants.unionQName);
if (definitionChild.name() == constants.restrictionQName)
{
// restriction
encodeSimpleRestriction(definitionChild, parent, name, value);
}
else if (definitionChild.name() == constants.listQName)
{
// list
encodeSimpleList(definitionChild, parent, name, value,
restriction);
}
else if (definitionChild.name() == constants.listQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value,
restriction);
}
}
If you look at this function, you see that the last else if statement is
exactly the same as the previous, so you will never execute the code inside
this statement, which is needed to encode union simpleTypes. To fix this, you
should change it to something like this:
else if (definitionChild.name() == constants.unionQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value, restriction);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: SDK Nightly builds?
Hi, My thinking was the more people that use it the more likely we are to pick up any issues before making an official release. Justin
Change Request In IVisualElementContainer
Hi, Is there any problem if IVisualElementContainer extends IVisualElement Interface. I feels it will be helpful if it does so. -- * Regards, S. Jagan Langa*
Re: SDK Nightly builds?
I can do that, where would we want to 'publish' the nightly builds and what would we include in them? EdB On Mon, Jun 3, 2013 at 10:47 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, My thinking was the more people that use it the more likely we are to pick up any issues before making an official release. Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
[jira] [Commented] (FLEX-33500) XMLEncoder fails to encode WSDL simpleType union
[
https://issues.apache.org/jira/browse/FLEX-33500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672947#comment-13672947
]
Erik de Bruin commented on FLEX-33500:
--
Please direct general project related questions (or really anything not
directly to do with this bug) to 'dev@flex.apache.org'...
XMLEncoder fails to encode WSDL simpleType union
Key: FLEX-33500
URL: https://issues.apache.org/jira/browse/FLEX-33500
Project: Apache Flex
Issue Type: Bug
Components: RPC: General, RPC: WebService
Affects Versions: Adobe Flex SDK 3.3 (Release)
Reporter: Maurits Lourens
Assignee: Justin Mclean
Labels: easyfix
The XMLEncoder can not encode simpleTypes with a definitionChild Union.
Steps to reproduce:
1. Create a WSDL with a request containing a simpleType, with a union child,
like this:
simpleType name=dateTimeOrEmpty
union memberTypes=dateTime tns:emptyString/
/simpleType
2. Create a sample project which uses this call to do send a date to the
server.
Expected behavior: the dateTime should be send to the server.
Actual behavior: the dateTime object is always empty (not nill).
The cause of this bug can be found inside the XMLEncoder. Around line 1340
you will find the function encodeSimpleType:
public function encodeSimpleType(definition:XML, parent:XML, name:QName,
value:*, restriction:XML = null):void
{
var definitionChild:XML = getSingleElementFromNode(definition,
constants.restrictionQName,
constants.listQName,
constants.unionQName);
if (definitionChild.name() == constants.restrictionQName)
{
// restriction
encodeSimpleRestriction(definitionChild, parent, name, value);
}
else if (definitionChild.name() == constants.listQName)
{
// list
encodeSimpleList(definitionChild, parent, name, value,
restriction);
}
else if (definitionChild.name() == constants.listQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value,
restriction);
}
}
If you look at this function, you see that the last else if statement is
exactly the same as the previous, so you will never execute the code inside
this statement, which is needed to encode union simpleTypes. To fix this, you
should change it to something like this:
else if (definitionChild.name() == constants.unionQName)
{
// union
encodeSimpleUnion(definitionChild, parent, name, value, restriction);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
+1 (non binding) I like the new verbiage better. -Mark -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, June 02, 2013 5:58 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote.
[jira] [Updated] (FLEX-33529) Change build scripts to create Linux source and release packages
[ https://issues.apache.org/jira/browse/FLEX-33529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33529: - Attachment: pizelbender.gz gzip of required PB files to compile on linux Change build scripts to create Linux source and release packages Key: FLEX-33529 URL: https://issues.apache.org/jira/browse/FLEX-33529 Project: Apache Flex Issue Type: Sub-task Reporter: Justin Mclean Attachments: pizelbender.gz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
+1 2013/6/3 Kessler CTR Mark J mark.kessler@usmc.mil +1 (non binding) I like the new verbiage better. -Mark -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, June 02, 2013 5:58 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote.
[RESULT][VOTE] move JIRA emails to a new list
The results are in: +1 (binding): aharui bigosmallm erikdebruin fthomas jhouser jmclean jonbcampos quetwo +1: a...@binitie.com carlos.velasco.bla...@gmail.com christofer.d...@c-ware.de cyrill.za...@gmail.com harbs.li...@gmail.com mark.kessler@usmc.mil mick.pow...@veeops.com That's it, a unanimous vote! I'll ask INFRA to set up 'iss...@flex.apache.org' and redirect all primary JIRA emails to that address. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
-1 (Binding) Igor Costa www.igorcosta.com www.igorcosta.org On Mon, Jun 3, 2013 at 8:17 AM, Carlos Velasco carlos.velasco.bla...@gmail.com wrote: +1 2013/6/3 Kessler CTR Mark J mark.kessler@usmc.mil +1 (non binding) I like the new verbiage better. -Mark -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, June 02, 2013 5:58 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote.
Re: [RESULT][VOTE] move JIRA emails to a new list
I spoke too soon :-( Only the PMC chair (Alex) can request a new list at: https://infra.apache.org/officers/mlreq Alex, would you be so kind? Here's what I wrote in the 'Notes' box before I realised the 'ok' button was greyed out: Notes We would like to use this list as the receiver for all JIRA emails generated by https://issues.apache.org/jira/browse/FLEX. Can you set that up directly, or do I need to file a separate JIRA ticket for that? Just to be sure: I unchecked the Reply-To box above. Did I understand correctly that doing so causes all responses to emails from the new list to be (also) directed to 'dev@flex.apache.org'? If not, how can I make that happen? /Notes Thanks, EdB On Mon, Jun 3, 2013 at 1:33 PM, Erik de Bruin e...@ixsoftware.nl wrote: The results are in: +1 (binding): aharui bigosmallm erikdebruin fthomas jhouser jmclean jonbcampos quetwo +1: a...@binitie.com carlos.velasco.bla...@gmail.com christofer.d...@c-ware.de cyrill.za...@gmail.com harbs.li...@gmail.com mark.kessler@usmc.mil mick.pow...@veeops.com That's it, a unanimous vote! I'll ask INFRA to set up 'iss...@flex.apache.org' and redirect all primary JIRA emails to that address. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Build failed in Jenkins: flex-sdk #44
See https://builds.apache.org/job/flex-sdk/44/ -- Started by timer Building remotely on windows1 in workspace https://builds.apache.org/job/flex-sdk/ws/ Checkout:flex-sdk / https://builds.apache.org/job/flex-sdk/ws/ - hudson.remoting.Channel@175e63ef:windows1 Using strategy: Default Last Built Revision: Revision aef1d4556c9bd66901e48b87b6162059dafa0af4 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/flex-sdk.git Commencing build of Revision aef1d4556c9bd66901e48b87b6162059dafa0af4 (origin/develop) Checking out Revision aef1d4556c9bd66901e48b87b6162059dafa0af4 (origin/develop) [flex-sdk] $ cmd.exe /C 'f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\bin\ant.bat -file build.xml super-clean exit %%ERRORLEVEL%%' Buildfile: https://builds.apache.org/job/flex-sdk/ws/build.xml thirdparty-clean: thirdparty-clean: batik-jars-clean: velocity-jars-clean: clean: thirdparty-clean: swfobject-clean: swfobject-fabridge-clean: clean-adobe-flex-sdk: clean: [delete] Deleting directory https://builds.apache.org/job/flex-sdk/ws/lib\external\optional [delete] Deleting directory https://builds.apache.org/job/flex-sdk/ws/in [delete] Deleting directory https://builds.apache.org/job/flex-sdk/ws/lib BUILD FAILED https://builds.apache.org/job/flex-sdk/ws/build.xml:311: Unable to delete file https://builds.apache.org/job/flex-sdk/ws/lib\player\11.1\playerglobal.swc Total time: 4 seconds Build step 'Invoke Ant' marked build as failure
Build failed in Jenkins: flex-sdk #45
See https://builds.apache.org/job/flex-sdk/45/ -- Started by user erikdebruin Building remotely on windows1 in workspace https://builds.apache.org/job/flex-sdk/ws/ Checkout:flex-sdk / https://builds.apache.org/job/flex-sdk/ws/ - hudson.remoting.Channel@175e63ef:windows1 Using strategy: Default Last Built Revision: Revision aef1d4556c9bd66901e48b87b6162059dafa0af4 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/flex-sdk.git Commencing build of Revision aef1d4556c9bd66901e48b87b6162059dafa0af4 (origin/develop) Checking out Revision aef1d4556c9bd66901e48b87b6162059dafa0af4 (origin/develop) [flex-sdk] $ cmd.exe /C 'f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\bin\ant.bat -file build.xml super-clean exit %%ERRORLEVEL%%' Buildfile: https://builds.apache.org/job/flex-sdk/ws/build.xml thirdparty-clean: thirdparty-clean: batik-jars-clean: velocity-jars-clean: clean: thirdparty-clean: swfobject-clean: swfobject-fabridge-clean: clean-adobe-flex-sdk: clean: [delete] Deleting directory https://builds.apache.org/job/flex-sdk/ws/lib BUILD FAILED https://builds.apache.org/job/flex-sdk/ws/build.xml:311: Unable to delete file https://builds.apache.org/job/flex-sdk/ws/lib\player\11.1\playerglobal.swc Total time: 1 second Build step 'Invoke Ant' marked build as failure
Jenkins build is back to normal : flex-sdk #46
See https://builds.apache.org/job/flex-sdk/46/
RE: SDK Nightly builds?
I used to test against Adobe nightly builds all the time when they still did that Think it would be a good idea as long as it wasn't causing someone a real headache -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Monday, June 03, 2013 10:29 AM To: dev@flex.apache.org Subject: Re: SDK Nightly builds? I can do that, where would we want to 'publish' the nightly builds and what would we include in them? EdB On Mon, Jun 3, 2013 at 10:47 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, My thinking was the more people that use it the more likely we are to pick up any issues before making an official release. Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: SDK Nightly builds?
See [1] [1] http://www.apache.org/dev/release.html#host-rc I wonder if we should add some functionality to the installer to make it find nightly and rc builds. -Alex On 6/3/13 6:09 AM, Erik de Bruin e...@ixsoftware.nl wrote: Ah, it seems Jenkins can archive build 'artifacts' with the proper after build task. I've change the config to have it do that for the 'release' task. The nightly build (== last successful build) of that job should be available from: https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifac t/out/ when the current run finishes (about 45 min.) This was what we're looking for, correct? EdB On Mon, Jun 3, 2013 at 11:28 AM, Erik de Bruin e...@ixsoftware.nl wrote: I can do that, where would we want to 'publish' the nightly builds and what would we include in them? EdB On Mon, Jun 3, 2013 at 10:47 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, My thinking was the more people that use it the more likely we are to pick up any issues before making an official release. Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
Igor, again, why are you against the proposal? We clearly need to understand why you are voting -1 so we can address the issue. On 3 June 2013 13:12, Igor Costa igorco...@gmail.com wrote: -1 (Binding) Igor Costa www.igorcosta.com www.igorcosta.org On Mon, Jun 3, 2013 at 8:17 AM, Carlos Velasco carlos.velasco.bla...@gmail.com wrote: +1 2013/6/3 Kessler CTR Mark J mark.kessler@usmc.mil +1 (non binding) I like the new verbiage better. -Mark -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, June 02, 2013 5:58 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote. -- João Fernandes
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
+1 (non binding)
Re: [RESULT][VOTE] move JIRA emails to a new list
OK, sent request. On 6/3/13 5:40 AM, Erik de Bruin e...@ixsoftware.nl wrote: I spoke too soon :-( Only the PMC chair (Alex) can request a new list at: https://infra.apache.org/officers/mlreq Alex, would you be so kind? Here's what I wrote in the 'Notes' box before I realised the 'ok' button was greyed out: Notes We would like to use this list as the receiver for all JIRA emails generated by https://issues.apache.org/jira/browse/FLEX. Can you set that up directly, or do I need to file a separate JIRA ticket for that? Just to be sure: I unchecked the Reply-To box above. Did I understand correctly that doing so causes all responses to emails from the new list to be (also) directed to 'dev@flex.apache.org'? If not, how can I make that happen? /Notes Thanks, EdB On Mon, Jun 3, 2013 at 1:33 PM, Erik de Bruin e...@ixsoftware.nl wrote: The results are in: +1 (binding): aharui bigosmallm erikdebruin fthomas jhouser jmclean jonbcampos quetwo +1: a...@binitie.com carlos.velasco.bla...@gmail.com christofer.d...@c-ware.de cyrill.za...@gmail.com harbs.li...@gmail.com mark.kessler@usmc.mil mick.pow...@veeops.com That's it, a unanimous vote! I'll ask INFRA to set up 'iss...@flex.apache.org' and redirect all primary JIRA emails to that address. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Change Request In IVisualElementContainer
Hi, Hopefully I will get a patch tester up and running this week and then you can try it yourself and see if anything breaks. -Alex On 6/3/13 2:07 AM, Jagan Langa Sami Durai jaga...@sybrant.com wrote: Hi, Is there any problem if IVisualElementContainer extends IVisualElement Interface. I feels it will be helpful if it does so. -- * Regards, S. Jagan Langa*
RE: Multidimensional States
State groups are pretty much the question in reverse - they allow you to group
related states together, but you still have to set the currentState as the
combination.
I've seen this myself mostly when trying to deal with mobile apps and the
rotation capabilities of a view. If you want to use the orientation and
another state set, it's not as easy as it could be.
Ultimately, I ended up doing something like Jude mentions, setting the current
state to a combination of the substates:
private var _orientation:String;// landscape or portrait
private var _displayAs:String: // the real state
public function set orientation(value:String):void {
_orientation = value;
super.setCurrentState(_orientation + '_' + _displayAs);
}
It would be nice if there was some way to combine the substates. In
particular, in this case the built-in orientation management of the mobile
doesn't combine automatically, as it's checking if landscape and portrait
are states, so there's some workaround that's required anyway...
I had wondered about something like what Cosma suggested on the declaration -
but the setting of the combined states still is cumbersome and requires the app
to manage the sub-states itself rather than having the framework help.
Maybe something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
currentState.mouse = up // Change just the mouse group state
I agree that having too many substates says there's something wrong, but this
could help with some meaningful state combinations like orientation and an
app-specific state.
Bill Turner
Enterprise Software Engineer
First Pacific Corporation
(503) 588-1411 ext. 2303
bi...@firstpac.com
-Original Message-
From: John Cunliffe [mailto:mahn...@gmail.com]
Sent: Saturday, June 01, 2013 4:41 AM
To: dev@flex.apache.org
Subject: Re: Multidimensional States
How is that different from the already existing
stateGroupshttp://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf63611-7ffa.htmlproperty?
On Sat, Jun 1, 2013 at 12:28 PM, jude flexcapaci...@gmail.com wrote:
I've been coming across more and more cases where it would be great to have
support for multidimensional states. What this looks like and how it's used
I'm not sure. Maybe we can discuss ideas.
snip
Confidentiality Notice: This page and any accompanying documents contain
information that is confidential, privileged, or exempt from disclosure under
applicable law and is intended for the exclusive use of the addressee. This
information is private and protected by law. If you are not the intended
recipient, you are hereby notified that any disclosure, copying, distribution,
or use of the contents of this information in any manner is strictly prohibited.
Re: Multidimensional States
Hi Cosma,
Thanks for presenting this possible approach.
-Alex
On 6/3/13 12:45 AM, Cosma Colanicchia cosma...@gmail.com wrote:
Just trying to throw a quick thinking at it, in particular about the MXML
declaration mess - to avoid cartesian multiplication of states, couldn't
we
just normalize them? I mean, grouping them in mutually exclusive groups,
which is the typical scenario:
s:states
s:ExclusiveStateGruop
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGruop
s:ExclusiveStateGruop
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGruop
s:ExclusiveStateGruop
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGruop
/s:states
This is different from the current freely assignable state groups, in that
they define the mixing rules of the various base states - thus we
implicitly expressed all the possible (and valid) combinations of the
various base state (in this case, 3*2*2 = 12 possible valid states),
instead of manually declaring a lot of states with long and unreadable
names (like overAndFocusedAndDefault).
The API should let specify multiple current states, as long as two
mutually
exclusive state are not specified, for example with a sintax like this:
myComp.currentState = up-focused-nonDefault // VALID
myComp.currentState = up-down-nonDefault // INVALID
(to avoid confusion with current syntax, I think we should pick another
separator different from , to express these state trails) We may also
agree that the first state declared of each exclusive group is the default
value of its group, so that we can write:
myComp.currentState = up // same as up-nonFocused-nonDefault
Then, current state groups and MXML syntax would kick in, it should just
recognize the state trails:
s:Rect includeIn=focused alpha=0.5 alpha.default=0.7
...
s:Rect includeIn=focused-nonDefault
Or, we could also supports additional MXML like:
s:Rect alpha.up=0 alpha.over=0.5 alpha.over-focused=1.0 ...
In which more specific value assignment should win over more generic ones
(something like that is already implemented, when you write alpha=0
alpha.over=1).
Finally, from a compatibility point of view, a component using an
old-style states set could be just translated to a single mutually
exclusive state group (in fact, it is one) - the compiler should just
prevent mixing the two approaches.
2013/6/3 Alex Harui aha...@adobe.com
Hi Max,
Thanks for detailing it out.
In the relatively few minutes I've spent thinking about the problem, I
pondered whether the answer is to expand on how s:State is used, or
simply
allow you to have conditional attributes based on things other than
States. IMO, along with this set of States is code you have to write to
set currentState appropriately, and in many cases, it seems like you're
just going to wire it to some other property. For this Button example,
we
don't really have a isFocused property, but we certainly could add
one,
and the Default states are all tied to what is currently called the
'emphasized' property. So why not some syntax that just lets you set a
property based on some other property? For sure there can be
collisions,
or maybe it won't handle complex situations, but it seems like when I
look
at the AS that we write when we give up on States, they are generally
simple expressions. So, while property.state implies the value of that
property when currentState is that State, maybe some other delimiter
besides '.' can be used to dictate the value of a property when some
other
property is true or false or some simple expression. I'm going to use
(
in this example, which may not be legal XML, but should give you an
idea)
Then the states are simply:
s:states
s:State name=up/
s:State name=down/
s:State name=over/
/s:states
And some widgets in the skin look like:
s:Rect id=focusBorder includeIn(isFocused)=
left(emphasized)=-2 left=-1 /
s:Rect id=background color.up=... color.down=...
color(currentState==upemphasized)
Now, when I look at that, I wonder: why not just use binding?
s:Rect id=focusBorder includeIn={isFocused}
left={emphasized ? -1 : -2} /
s:Rect id=background color.up=... color.down=...
color={(currentState==upemphasized) ? red : blue}
Yes, I know we told you not to use binding in skins for performance
reasons, but I am hoping to find ways to make databinding much faster in
FlexJS.
And one final thought: In FlexJS, we may end up saying that you
shouldn't
specify these visual aspects in the skin. Instead, you might want to
use more CSS, and then we could implement attribute selectors on the AS
side since that CSS is going to work on the JS side.
Then you just have:
s:Rect id=focusBorder className=buttonFocusBorder
s:Rect id=background className=buttonBackground
And CSS like:
Re: Multidimensional States
Good input.
If I understand your scenario (and maybe you or someone can post a small
but real-world scenario), it supports my thinking that, instead of more
ways to use State, that the currentState property should just be thought
of as another organizing property, and the conditional setting of values
should be somehow determined by any property on a component, not just
currentState. Then if you had an orientation property or maybe
isLandscape then you would create conditional expressions to determine
what to do.
-Alex
On 6/3/13 8:22 AM, Bill Turner bi...@firstpac.com wrote:
State groups are pretty much the question in reverse - they allow you to
group related states together, but you still have to set the currentState
as the combination.
I've seen this myself mostly when trying to deal with mobile apps and the
rotation capabilities of a view. If you want to use the orientation and
another state set, it's not as easy as it could be.
Ultimately, I ended up doing something like Jude mentions, setting the
current state to a combination of the substates:
private var _orientation:String;// landscape or portrait
private var _displayAs:String: // the real state
public function set orientation(value:String):void {
_orientation = value;
super.setCurrentState(_orientation + '_' + _displayAs);
}
It would be nice if there was some way to combine the substates. In
particular, in this case the built-in orientation management of the
mobile doesn't combine automatically, as it's checking if landscape and
portrait are states, so there's some workaround that's required
anyway...
I had wondered about something like what Cosma suggested on the
declaration - but the setting of the combined states still is cumbersome
and requires the app to manage the sub-states itself rather than having
the framework help.
Maybe something like:
s:states
s:ExclusiveStateGroup id=mouse
s:State name=up/
s:State name=down/
s:State name=over/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=focus
s:State name=nonFocused/
s:State name=focused/
/s:ExclusiveStateGroup
s:ExclusiveStateGroup id=selection
s:State name=nonDefault/
s:State name=default/
/s:ExclusiveStateGroup
/s:states
currentState.mouse = up // Change just the mouse group
state
I agree that having too many substates says there's something wrong, but
this could help with some meaningful state combinations like orientation
and an app-specific state.
Bill Turner
Enterprise Software Engineer
First Pacific Corporation
(503) 588-1411 ext. 2303
bi...@firstpac.com
-Original Message-
From: John Cunliffe [mailto:mahn...@gmail.com]
Sent: Saturday, June 01, 2013 4:41 AM
To: dev@flex.apache.org
Subject: Re: Multidimensional States
How is that different from the already existing
stateGroupshttp://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e
3d11c0bf63611-7ffa.htmlproperty?
On Sat, Jun 1, 2013 at 12:28 PM, jude flexcapaci...@gmail.com wrote:
I've been coming across more and more cases where it would be great to
have
support for multidimensional states. What this looks like and how it's
used
I'm not sure. Maybe we can discuss ideas.
snip
Confidentiality Notice: This page and any accompanying documents contain
information that is confidential, privileged, or exempt from disclosure
under applicable law and is intended for the exclusive use of the
addressee. This information is private and protected by law. If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution, or use of the contents of this information in any
manner is strictly prohibited.
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
I've explained in my previous e-mail, why I vote -1 (binding). Maybe you missed the e-mail on previous thread. But here's the mention. A year back, someone at Flex Brazil group asked me why we couldn't simple have a MVC approach into the SDK. My short answer was We prefer you decide which way you want to code, rather than force you on our perspective way. For mature and freedom of choice we should not have such only a way of coding, like explicit someone to code on that specific way. We have a plethora of Flex frameworks out there, if we include one, we should include all of it. For the freedom of choice that's why I voted -1. Igor Costa www.igorcosta.com www.igorcosta.org On Mon, Jun 3, 2013 at 12:07 PM, Dasa Paddock dpadd...@esri.com wrote: +1 (non binding)
Rendering mathematical equations in TLF
Is it possible to render mathematical equations in the Text Layout Framework? Specifically fractions (with a horizontal bar between numerator and denominator) and square roots (a square root of an equation). Is this possible? Does anyone have expertise that can advise on these issues? Thanks. Kenny -- Kenny Nova Prep Games 917-731-6253
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
+1 (binding) -Message d'origine- From: Carlos Rovira Sent: Sunday, June 02, 2013 11:57 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote.
Re: SDK Nightly builds?
The nightly build is available through this URL: https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/ The files at that URL always represent the last successful build using the 'release' target. If someone can figure out a way to either upload these files somewhere using FTP or submit them to SVN for inclusion on the 'dev' tree of the dist repository, I will add that to the build script. EdB On Mon, Jun 3, 2013 at 5:03 PM, Alex Harui aha...@adobe.com wrote: See [1] [1] http://www.apache.org/dev/release.html#host-rc I wonder if we should add some functionality to the installer to make it find nightly and rc builds. -Alex On 6/3/13 6:09 AM, Erik de Bruin e...@ixsoftware.nl wrote: Ah, it seems Jenkins can archive build 'artifacts' with the proper after build task. I've change the config to have it do that for the 'release' task. The nightly build (== last successful build) of that job should be available from: https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifac t/out/ when the current run finishes (about 45 min.) This was what we're looking for, correct? EdB On Mon, Jun 3, 2013 at 11:28 AM, Erik de Bruin e...@ixsoftware.nl wrote: I can do that, where would we want to 'publish' the nightly builds and what would we include in them? EdB On Mon, Jun 3, 2013 at 10:47 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, My thinking was the more people that use it the more likely we are to pick up any issues before making an official release. Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
Igor, have you read the proposal? it's stated that it will not be part of the SDK and will be totally optional. On 3 June 2013 16:51, Frédéric THOMAS webdoubl...@hotmail.com wrote: +1 (binding) -Message d'origine- From: Carlos Rovira Sent: Sunday, June 02, 2013 11:57 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/**o6zjmorfh4lxuygohttp://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote. -- João Fernandes
Re: [VOTE] {DISCUSS} Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
Igor, you are free to vote however you want, but nowhere in the proposal does it say that Flex SDK users will be forced to use Swiz. Thanks, Om On Jun 3, 2013 8:30 AM, Igor Costa igorco...@gmail.com wrote: I've explained in my previous e-mail, why I vote -1 (binding). Maybe you missed the e-mail on previous thread. But here's the mention. A year back, someone at Flex Brazil group asked me why we couldn't simple have a MVC approach into the SDK. My short answer was We prefer you decide which way you want to code, rather than force you on our perspective way. For mature and freedom of choice we should not have such only a way of coding, like explicit someone to code on that specific way. We have a plethora of Flex frameworks out there, if we include one, we should include all of it. For the freedom of choice that's why I voted -1. Igor Costa www.igorcosta.com www.igorcosta.org On Mon, Jun 3, 2013 at 12:07 PM, Dasa Paddock dpadd...@esri.com wrote: +1 (non binding)
TLF - How to render line spacing for image in block of text
Is there a proper technique in the TLF to render line spacing to accommodate for an image in a block of text. Specifically, maintaining single line spacing before and after the image, but appropriately accommodating for the larger image size. Is this possible? Does anyone have expertise that can advise on these issues? Thanks. Kenny -- Kenny Nova Prep Games 917-731-6253
[DRAFT] Flex June Report
Hi Folks, Looks like we nee to report in June. Here's a draft. Can we get latest web-site visitor activity? Thanks, -Alex - Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES Apache Flex SDK 4.9.1 was released on 2/28/13. Apache Flex Installer 2.5.4 was released on 4/11/13. The community is currently preparing its next release of both the SDK and Installer. ACTIVITY Activity in Apache Flex continues to be in two main areas: improvements to the existing Adobe Flash Platform-dependent code base, including the releases listed above, and prototyping ways to create a version of Flex that is independent from the Adobe Flash Platform. There is another group working on Maven-related tools for the existing code base. Just in the past 30 days, 130 JIRA issues were resolved. JIRA activity is so high, a vote is underway to split JIRA notifications off to its own mailing list (issues@flex.a.o) Getting used to Git was still a frequent topic in April and May. Because Git does not support partial checkouts, the community prototyped using GitHub for the whiteboards. GitHub notifications are sent to the commits@ list just like any other Apache Git commit. The PMC then voted to approve this workflow. And because we do our work in a branch and have trunk only have released sources, we had to ask Infra to update the mirrors to work from that branch. The owner of a popular application-framework that leverages the Flex SDK has offered to donate the code to the project. This has met with some opposition from those who use competing application-frameworks. The ensuing dicussion indicated that the PMC is in favor of accepting donations from the these other frameworks should they choose to donate, so we believe we are not endorsing or showing favoritism. COMMUNITY No new committers in the last 90 days. A vote is underway to promote a committer to the PMC. Latest analytics are: _ INFRASTRUCTURE * Infra attempted to resolve INFRA-4380 but ran into problems. I have approval to try to use the SOAP interface to pull the current state of JIRA issues, merge them with the original attachments and provide a new import file for INFRA. That task has been delayed by other issues like getting new releases out, but we will get to it eventually. BRANDING We have noted that Apache projects are forming that use code module names that are used in Apache Flex. Namely 'Falcon' and now 'Spark'. These two words are used often on the mailing lists when discussing the related code which then finds its way into the search engines. Is this an issue? --
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. It would make me much happier to have a vote thread with just +1's or -1's without qualifications. -Alex On 6/1/13 10:19 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I am sorry, but I voted a -1 binding as well and my concerns have not been addressed. If we are going to go ahead, can we at least bring it into a contrib folder and make at least one release out of it before promoting it to a main repo? Thanks, Om On Jun 1, 2013 10:07 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: Ok Erik, I see it ok as well. As you said there's only one -1 binding vote (Igor Costa) and one -1 non binding vote (Carlos Velasco), and it was already explained the motivations behind the donation and the intention to maintain swiz out of main flex-sdk cycle and not promote it as the preferred mvc-ioc microarquitecture. So for me it's ok, if it's ok for the rest of people here. Hope Chris could send us that email soon regarding it's intention of donate the source code and wiki Thanks to you Erik as well for clearing things here. Carlos 2013/6/1 Erik de Bruin e...@ixsoftware.nl I think this is a valid vote and there is no need to declare it invalid. There is only one definite, binding -1 (Igor) and he declined to explain his motivation, something that is customary when casting a negative vote. Once Chris Scott 'officially' donates Swiz - there are some hoops he has to jump through, but we'll get to those when he contacts us- we can create a new repo for it: either a general 'flex-contrib/swiz' or a specific one,
Re: [VOTE] {DISCUSS} Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
Igor,
Indeed and Om pointed out, you're free with your vote, the point is the
arguments you gave to justify your negative vote doesn't seem to exist
anymore, I mean, even your last one:
We have a plethora of Flex frameworks out there, if we include one, we
should include all of it.
It would mean this plethora of Flex frameworks owners should decide to
donate their framework before we can accept one, how do you think it can
possible to do so ?
How the number or the order of the donations is important now it is well
stated those framework will not be included in the SDK or forced to be used
but only taken under the Apache Flex umbrella given an easier way for
contributors to make it evolved which will be the same for all other
frameworks as soon as they will be donated if the owners want to.
Have you got more argument to discuss ?
-Fred
-Message d'origine-
From: OmPrakash Muppirala
Sent: Monday, June 03, 2013 6:01 PM
To: dev@flex.apache.org
Subject: Re: [VOTE] {DISCUSS} Oprtional MVC/IOC Frameworks Donation: Swiz
Framework Donation
Igor, you are free to vote however you want, but nowhere in the proposal
does it say that Flex SDK users will be forced to use Swiz.
Thanks,
Om
On Jun 3, 2013 8:30 AM, Igor Costa igorco...@gmail.com wrote:
I've explained in my previous e-mail, why I vote -1 (binding).
Maybe you missed the e-mail on previous thread. But here's the mention.
A year back, someone at Flex Brazil group asked me why we couldn't simple
have a MVC approach into the SDK.
My short answer was We prefer you decide which way you want to code,
rather than force you on our perspective way.
For mature and freedom of choice we should not have such only a way of
coding, like explicit someone to code on that specific way.
We have a plethora of Flex frameworks out there, if we include one, we
should include all of it.
For the freedom of choice that's why I voted -1.
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Mon, Jun 3, 2013 at 12:07 PM, Dasa Paddock dpadd...@esri.com wrote:
+1 (non binding)
Re: Example apps for new components
@Om ... is there a compiled version of this SDK around? If so, where can I grab it? -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Tue, May 28, 2013 at 7:20 PM, Nicholas Kwiatkowski nicho...@spoon.aswrote: The ultimate hope is that we will have proper docs sometime in the future -- and those will include some samples. The Tour de Flex source code will be googleable as well, since it write out HTML pages for each MXML source it uses. -Nick On Tue, May 28, 2013 at 4:02 AM, Tom Chiverton t...@extravision.com wrote: On 24/05/2013 18:12, OmPrakash Muppirala wrote: On May 24, 2013 2:16 AM, Tom Chiverton t...@extravision.com wrote: Well, there's no point putting it on the wiki if a few days later someone is going to have to scrape it off into an application is there ? Tom The advantage of having it as a web resource is that people can google for them, and in general would be easier to share. Isn't the idea to bake the docs into the code and let asdoc write a web site with working examples though ? That solves the Google problem. Tom
Re: SDK Nightly builds?
I'll ask Infra if that location is sufficient. On 6/3/13 8:53 AM, Erik de Bruin e...@ixsoftware.nl wrote: The nightly build is available through this URL: https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifac t/out/ The files at that URL always represent the last successful build using the 'release' target. If someone can figure out a way to either upload these files somewhere using FTP or submit them to SVN for inclusion on the 'dev' tree of the dist repository, I will add that to the build script. EdB On Mon, Jun 3, 2013 at 5:03 PM, Alex Harui aha...@adobe.com wrote: See [1] [1] http://www.apache.org/dev/release.html#host-rc I wonder if we should add some functionality to the installer to make it find nightly and rc builds. -Alex On 6/3/13 6:09 AM, Erik de Bruin e...@ixsoftware.nl wrote: Ah, it seems Jenkins can archive build 'artifacts' with the proper after build task. I've change the config to have it do that for the 'release' task. The nightly build (== last successful build) of that job should be available from: https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artif ac t/out/ when the current run finishes (about 45 min.) This was what we're looking for, correct? EdB On Mon, Jun 3, 2013 at 11:28 AM, Erik de Bruin e...@ixsoftware.nl wrote: I can do that, where would we want to 'publish' the nightly builds and what would we include in them? EdB On Mon, Jun 3, 2013 at 10:47 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, My thinking was the more people that use it the more likely we are to pick up any issues before making an official release. Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
Sebastian, you should open a new thread :) On 3 June 2013 17:22, Sebastian Mohr flex.masul...@gmail.com wrote: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. It would make me much happier to have a vote thread with just +1's or -1's without qualifications. -Alex On 6/1/13 10:19 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I am sorry, but I voted a -1 binding as well and my concerns have not been addressed. If we are going to go ahead, can we at least bring it into a contrib folder and make at least one release out of it before promoting it to a main repo? Thanks, Om On Jun 1, 2013 10:07 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: Ok Erik, I see it ok as well. As you said there's only one -1 binding vote (Igor Costa) and one -1 non binding vote (Carlos Velasco), and it was already explained the motivations behind the donation and the intention to maintain swiz out of main flex-sdk cycle and not promote it as the preferred mvc-ioc microarquitecture. So for me it's ok, if it's ok for the rest of people here. Hope Chris could send us that email soon regarding it's intention of donate the source code and wiki Thanks to you Erik as well for clearing things here. Carlos 2013/6/1 Erik de Bruin e...@ixsoftware.nl I think this is a valid vote and there is no need to declare it invalid. There is only one definite, binding -1 (Igor) and he declined to explain his motivation, something that is customary when
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
Interesting..., to me, some are light weight, some full featured, some complex, some simple, I guess the choice of a framework very depends on the project needs (and probably at time, the knowledge of the team on the framework). -Fred -Message d'origine- From: Sebastian Mohr Sent: Monday, June 03, 2013 6:22 PM To: dev@flex.apache.org Subject: Re: [DISCUSS] Swiz Framework Donation to Apache Flex IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. It would make me much happier to have a vote thread with just +1's or -1's without qualifications. -Alex On 6/1/13 10:19 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I am sorry, but I voted a -1 binding as well and my concerns have not been addressed. If we are going to go ahead, can we at least bring it into a contrib folder and make at least one release out of it before promoting it to a main repo? Thanks, Om On Jun 1, 2013 10:07 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: Ok Erik, I see it ok as well. As you said there's only one -1 binding vote (Igor Costa) and one -1 non binding vote (Carlos Velasco), and it was already explained the motivations behind the donation and the intention to maintain swiz out of main flex-sdk cycle and not promote it as the preferred mvc-ioc microarquitecture. So for me it's ok, if it's ok for the rest of people here. Hope Chris could send us that email soon regarding it's intention of donate the source code and wiki Thanks to you Erik as well for clearing things here. Carlos 2013/6/1 Erik de Bruin e...@ixsoftware.nl I think this is a valid vote and there is no need to declare it invalid. There is only one definite, binding -1 (Igor) and he declined to explain his motivation, something that is
Re: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation
+1 (binding) On Mon, Jun 3, 2013 at 5:59 PM, João Fernandes joaopedromartinsfernan...@gmail.com wrote: Igor, have you read the proposal? it's stated that it will not be part of the SDK and will be totally optional. On 3 June 2013 16:51, Frédéric THOMAS webdoubl...@hotmail.com wrote: +1 (binding) -Message d'origine- From: Carlos Rovira Sent: Sunday, June 02, 2013 11:57 AM To: dev@flex.apache.org Subject: [VOTE] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation This vote comes from an original vote thread declared as null (see original thread for info about motivations): http://markmail.org/message/**o6zjmorfh4lxuygo http://markmail.org/message/o6zjmorfh4lxuygo The new vote thread is considering the donation of the optional MVC/IOC Swiz Framework. Points taken from the original vote thread: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Here's the new points from Alex Harui to make clear what it implies: 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. This vote thread will be open for the next 72 hours Please make your vote. -- João Fernandes -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
Apache Flex needs an MVC framework out of the box IMHO no, that is not needed, because Flex can be used to create an MVC/MVVC/MVP/you-name-it architecture out of the box without any framework. And wouldn't that be like integrating Spring into Java? Having that would bring more stability to the our Flex market. How? Am 03.06.2013 18:22, schrieb Sebastian Mohr: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex
Re: [DRAFT] Flex June Report
With the risc of sounding biased aint Flash4j something community related ? 2013/6/3 Alex Harui aha...@adobe.com Hi Folks, Looks like we nee to report in June. Here's a draft. Can we get latest web-site visitor activity? Thanks, -Alex - Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES Apache Flex SDK 4.9.1 was released on 2/28/13. Apache Flex Installer 2.5.4 was released on 4/11/13. The community is currently preparing its next release of both the SDK and Installer. ACTIVITY Activity in Apache Flex continues to be in two main areas: improvements to the existing Adobe Flash Platform-dependent code base, including the releases listed above, and prototyping ways to create a version of Flex that is independent from the Adobe Flash Platform. There is another group working on Maven-related tools for the existing code base. Just in the past 30 days, 130 JIRA issues were resolved. JIRA activity is so high, a vote is underway to split JIRA notifications off to its own mailing list (issues@flex.a.o) Getting used to Git was still a frequent topic in April and May. Because Git does not support partial checkouts, the community prototyped using GitHub for the whiteboards. GitHub notifications are sent to the commits@ list just like any other Apache Git commit. The PMC then voted to approve this workflow. And because we do our work in a branch and have trunk only have released sources, we had to ask Infra to update the mirrors to work from that branch. The owner of a popular application-framework that leverages the Flex SDK has offered to donate the code to the project. This has met with some opposition from those who use competing application-frameworks. The ensuing dicussion indicated that the PMC is in favor of accepting donations from the these other frameworks should they choose to donate, so we believe we are not endorsing or showing favoritism. COMMUNITY No new committers in the last 90 days. A vote is underway to promote a committer to the PMC. Latest analytics are: _ INFRASTRUCTURE * Infra attempted to resolve INFRA-4380 but ran into problems. I have approval to try to use the SOAP interface to pull the current state of JIRA issues, merge them with the original attachments and provide a new import file for INFRA. That task has been delayed by other issues like getting new releases out, but we will get to it eventually. BRANDING We have noted that Apache projects are forming that use code module names that are used in Apache Flex. Namely 'Falcon' and now 'Spark'. These two words are used often on the mailing lists when discussing the related code which then finds its way into the search engines. Is this an issue? --
Re: [DRAFT] Flex June Report
Looks good to me. Most stats are available here and is current to the date[1] Significantly, the Flex SDK has been downloaded 4676 times since April 11th (the date we started tracking it) Thanks, Om [1] http://www.seethestats.com/site/flex.apache.org On Mon, Jun 3, 2013 at 9:18 AM, Alex Harui aha...@adobe.com wrote: Hi Folks, Looks like we nee to report in June. Here's a draft. Can we get latest web-site visitor activity? Thanks, -Alex - Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES Apache Flex SDK 4.9.1 was released on 2/28/13. Apache Flex Installer 2.5.4 was released on 4/11/13. The community is currently preparing its next release of both the SDK and Installer. ACTIVITY Activity in Apache Flex continues to be in two main areas: improvements to the existing Adobe Flash Platform-dependent code base, including the releases listed above, and prototyping ways to create a version of Flex that is independent from the Adobe Flash Platform. There is another group working on Maven-related tools for the existing code base. Just in the past 30 days, 130 JIRA issues were resolved. JIRA activity is so high, a vote is underway to split JIRA notifications off to its own mailing list (issues@flex.a.o) Getting used to Git was still a frequent topic in April and May. Because Git does not support partial checkouts, the community prototyped using GitHub for the whiteboards. GitHub notifications are sent to the commits@ list just like any other Apache Git commit. The PMC then voted to approve this workflow. And because we do our work in a branch and have trunk only have released sources, we had to ask Infra to update the mirrors to work from that branch. The owner of a popular application-framework that leverages the Flex SDK has offered to donate the code to the project. This has met with some opposition from those who use competing application-frameworks. The ensuing dicussion indicated that the PMC is in favor of accepting donations from the these other frameworks should they choose to donate, so we believe we are not endorsing or showing favoritism. COMMUNITY No new committers in the last 90 days. A vote is underway to promote a committer to the PMC. Latest analytics are: _ INFRASTRUCTURE * Infra attempted to resolve INFRA-4380 but ran into problems. I have approval to try to use the SOAP interface to pull the current state of JIRA issues, merge them with the original attachments and provide a new import file for INFRA. That task has been delayed by other issues like getting new releases out, but we will get to it eventually. BRANDING We have noted that Apache projects are forming that use code module names that are used in Apache Flex. Namely 'Falcon' and now 'Spark'. These two words are used often on the mailing lists when discussing the related code which then finds its way into the search engines. Is this an issue? --
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
@Sebastian: I could not disagree more. In my opinion Flex *is* an MVC framework. It doesn't need an additional layer that requires me to write a whole lot of boilerplate, unnecessarily complicates project structure and forces me to adhere to some rules I often find questionable. I believe Flex has all the tools for creating well-architectured, cleanly separated code (at least since Flex 4). The one thing I miss is an IoC container (even though I could get things done without it, but an IoC sure makes life easier - as opposed to most MVC frameworks). For this I usually use SwiftSuspenders because it is the only library that is *only* an IoC and nothing else (except perhaps for Spring-AS, which I find too complex for most situations). Anyway, I'm not saying you shouldn't adopt frameworks like Swiz under the Apache Flex umbrella (that's why I didn't vote: I don't like Swiz or any other MVC framework, but other people should be able to use it if they like). I'm saying that you really should not force people into such frameworks. For me that would be a reason to drop Flex. Max On Mon, Jun 3, 2013 at 6:22 PM, Sebastian Mohr flex.masul...@gmail.comwrote: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. It would make me much happier to have a vote thread with just +1's or -1's without qualifications. -Alex On 6/1/13 10:19 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I am sorry, but I voted a -1 binding as well and my concerns have not been addressed. If we are going to go ahead, can we at least bring it into a contrib folder and make at least one release out of
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
Hi guys, How can i unsubscribe this list !? tks, Marcelo 2013/6/3 Maxime Cowez maxime.co...@gmail.com @Sebastian: I could not disagree more. In my opinion Flex *is* an MVC framework. It doesn't need an additional layer that requires me to write a whole lot of boilerplate, unnecessarily complicates project structure and forces me to adhere to some rules I often find questionable. I believe Flex has all the tools for creating well-architectured, cleanly separated code (at least since Flex 4). The one thing I miss is an IoC container (even though I could get things done without it, but an IoC sure makes life easier - as opposed to most MVC frameworks). For this I usually use SwiftSuspenders because it is the only library that is *only* an IoC and nothing else (except perhaps for Spring-AS, which I find too complex for most situations). Anyway, I'm not saying you shouldn't adopt frameworks like Swiz under the Apache Flex umbrella (that's why I didn't vote: I don't like Swiz or any other MVC framework, but other people should be able to use it if they like). I'm saying that you really should not force people into such frameworks. For me that would be a reason to drop Flex. Max On Mon, Jun 3, 2013 at 6:22 PM, Sebastian Mohr flex.masul...@gmail.com wrote: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. It would make me much happier to have a vote thread with just +1's or -1's without qualifications. -Alex On 6/1/13 10:19 AM, OmPrakash Muppirala
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
Send an email to flex-unsubscr...@flex.apache.org Sad to see you go :-( Can you maybe tell us why you are leaving? EdB On Mon, Jun 3, 2013 at 7:26 PM, Marcelo Fabricio de Mello marcelofme...@gmail.com wrote: Hi guys, How can i unsubscribe this list !? tks, Marcelo 2013/6/3 Maxime Cowez maxime.co...@gmail.com @Sebastian: I could not disagree more. In my opinion Flex *is* an MVC framework. It doesn't need an additional layer that requires me to write a whole lot of boilerplate, unnecessarily complicates project structure and forces me to adhere to some rules I often find questionable. I believe Flex has all the tools for creating well-architectured, cleanly separated code (at least since Flex 4). The one thing I miss is an IoC container (even though I could get things done without it, but an IoC sure makes life easier - as opposed to most MVC frameworks). For this I usually use SwiftSuspenders because it is the only library that is *only* an IoC and nothing else (except perhaps for Spring-AS, which I find too complex for most situations). Anyway, I'm not saying you shouldn't adopt frameworks like Swiz under the Apache Flex umbrella (that's why I didn't vote: I don't like Swiz or any other MVC framework, but other people should be able to use it if they like). I'm saying that you really should not force people into such frameworks. For me that would be a reason to drop Flex. Max On Mon, Jun 3, 2013 at 6:22 PM, Sebastian Mohr flex.masul...@gmail.com wrote: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be
Re: [DRAFT] Flex June Report
Hi Alain, I'm not sure if external projects should be mentioned in an Apache Report. If Flash4j was part of Apache Flex, it would probably be a very valid observation, but I'm no Committer or PPMC so I'm not the right person to answer. On 3 June 2013 18:17, Alain Ekambi jazzmatad...@gmail.com wrote: With the risc of sounding biased aint Flash4j something community related ? 2013/6/3 Alex Harui aha...@adobe.com Hi Folks, Looks like we nee to report in June. Here's a draft. Can we get latest web-site visitor activity? Thanks, -Alex - Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES Apache Flex SDK 4.9.1 was released on 2/28/13. Apache Flex Installer 2.5.4 was released on 4/11/13. The community is currently preparing its next release of both the SDK and Installer. ACTIVITY Activity in Apache Flex continues to be in two main areas: improvements to the existing Adobe Flash Platform-dependent code base, including the releases listed above, and prototyping ways to create a version of Flex that is independent from the Adobe Flash Platform. There is another group working on Maven-related tools for the existing code base. Just in the past 30 days, 130 JIRA issues were resolved. JIRA activity is so high, a vote is underway to split JIRA notifications off to its own mailing list (issues@flex.a.o) Getting used to Git was still a frequent topic in April and May. Because Git does not support partial checkouts, the community prototyped using GitHub for the whiteboards. GitHub notifications are sent to the commits@ list just like any other Apache Git commit. The PMC then voted to approve this workflow. And because we do our work in a branch and have trunk only have released sources, we had to ask Infra to update the mirrors to work from that branch. The owner of a popular application-framework that leverages the Flex SDK has offered to donate the code to the project. This has met with some opposition from those who use competing application-frameworks. The ensuing dicussion indicated that the PMC is in favor of accepting donations from the these other frameworks should they choose to donate, so we believe we are not endorsing or showing favoritism. COMMUNITY No new committers in the last 90 days. A vote is underway to promote a committer to the PMC. Latest analytics are: _ INFRASTRUCTURE * Infra attempted to resolve INFRA-4380 but ran into problems. I have approval to try to use the SOAP interface to pull the current state of JIRA issues, merge them with the original attachments and provide a new import file for INFRA. That task has been delayed by other issues like getting new releases out, but we will get to it eventually. BRANDING We have noted that Apache projects are forming that use code module names that are used in Apache Flex. Namely 'Falcon' and now 'Spark'. These two words are used often on the mailing lists when discussing the related code which then finds its way into the search engines. Is this an issue? -- -- João Fernandes
Re: [DRAFT] Flex June Report
On 6/3/13 10:17 AM, Alain Ekambi jazzmatad...@gmail.com wrote: With the risc of sounding biased aint Flash4j something community related ? Yes, Flash4j is community related, but I don't think Flash4j activity deserves specific mention in a report to the Apache board which is reviewing dozens of reports from a wide variety of communities. But if others feel like it should be mentioned, I'll be happy to add it. -Alex
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
I have to admit to being a bit confused as to why this discussion is even occuring. This project is called Apache Flex after all, so why are other projects, such as Swiz and FlexUnit, to be included. Where does it end? Do we include AS3CoreLib, Starling or any of the 100s of github projects if the owner offers them? Swiz and FlexUnit are great projects - but they are not part of the Flex framework, and therefore don't belong here. Its as simple as that imho. On 03/06/2013 18:24, Maxime Cowez wrote: @Sebastian: I could not disagree more. In my opinion Flex *is* an MVC framework. It doesn't need an additional layer that requires me to write a whole lot of boilerplate, unnecessarily complicates project structure and forces me to adhere to some rules I often find questionable. I believe Flex has all the tools for creating well-architectured, cleanly separated code (at least since Flex 4). The one thing I miss is an IoC container (even though I could get things done without it, but an IoC sure makes life easier - as opposed to most MVC frameworks). For this I usually use SwiftSuspenders because it is the only library that is *only* an IoC and nothing else (except perhaps for Spring-AS, which I find too complex for most situations). Anyway, I'm not saying you shouldn't adopt frameworks like Swiz under the Apache Flex umbrella (that's why I didn't vote: I don't like Swiz or any other MVC framework, but other people should be able to use it if they like). I'm saying that you really should not force people into such frameworks. For me that would be a reason to drop Flex. Max On Mon, Jun 3, 2013 at 6:22 PM, Sebastian Mohr flex.masul...@gmail.comwrote: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote didn't have to really count since it came late, but without a [VOTE][RESULT] tag on a vote summary email it wasn't clear it was officially closed. Thanks again, -Alex On 6/2/13 2:44 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: I'm fine with a second reound of votes. So we can close here this thread and I open a new one just now. 2013/6/2 Erik de Bruin e...@ixsoftware.nl Ok, if that's what it takes to avoid further confusion, I'll second (or third) a new vote, but all the points you raise have been discussed and the resulting consensus conforms with the points you want to add/amend in the new vote. Note also that Parsley also seems to be on the point of being donated, so all the 'endorsment' worries seem premature and unnecessary. A point of procedure: can you add a 'binding' vote AFTER the result has been called? EdB On Sun, Jun 2, 2013 at 8:05 AM, Alex Harui aha...@adobe.com wrote: My count is now three binding -1's. Igor Costa, Jeff Tapper, and Om. I guess I'll add a fourth. Jeff qualified his vote, but it still reads as -1 because it isn't right to assume he accepts your interpretation of the proposal. Jeff should change his vote if he is convinced. The amount of discussion and confusion by others that we are not picking Swiz as the favorite and that Parsley and other app frameworks are welcome, makes me make another plea to re-do this vote. Reading some of these posts make it clear to me that folks have different ideas of what is going to happen in the future. I'm still unclear whether Swiz AOP code is going to be moved into the framework or not. I thought we were going to warehouse Swiz, but instead, it appears that Carlos wants to make a set of significant improvements to Swiz, which is fine, but might be what makes people think we're endorsing or playing favorites. Yes, you have the numbers to forge ahead, but we are told to consider the number of -1's. I would recommend a proposal that states clearly that 1) Swiz goes in its own repo. The original proposal says it could go into a folder under utilities, but I think flexunit is a better model. 2) Swiz will have active development but release separately from the SDK. The activity level isn't quite clear from the original proposal. People need to be comfortable that this activity isn't an endorsement or favoritism. 3) Acceptance of Swiz is not an endorsement or favoritism. 4) Any other app framework is welcomed to be donated via the same process. It would make me much happier to have a vote thread with just +1's or -1's without qualifications. -Alex On
Re: [DRAFT] Flex June Report
Looking at it to from that angle it does make sense to include Flash4j in that report. Just ignore the question. Cheers, Alain 2013/6/3 Alex Harui aha...@adobe.com On 6/3/13 10:17 AM, Alain Ekambi jazzmatad...@gmail.com wrote: With the risc of sounding biased aint Flash4j something community related ? Yes, Flash4j is community related, but I don't think Flash4j activity deserves specific mention in a report to the Apache board which is reviewing dozens of reports from a wide variety of communities. But if others feel like it should be mentioned, I'll be happy to add it. -Alex
Re: SDK Nightly builds?
Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin
Re: SDK Nightly builds?
Hi, I can do that, where would we want to 'publish' the nightly builds and what would we include in them? The projects I found link directly to the builds machine. http://directory.apache.org/studio/nightly-builds.html http://nutch.apache.org/nightly.html http://ant.apache.org/nightlies.html http://wiki.apache.org/solr/NightlyBuilds So that's likly good enough for us. Justin
Re: Example apps for new components
On Mon, Jun 3, 2013 at 9:28 AM, Sebastian Mohr flex.masul...@gmail.com wrote: @Om ... is there a compiled version of this SDK around? If so, where can I grab it? There is nothing as of today. But we are trying to make nightly builds available soon. Hang tight :-) Thanks, Om -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Tue, May 28, 2013 at 7:20 PM, Nicholas Kwiatkowski nicho...@spoon.aswrote: The ultimate hope is that we will have proper docs sometime in the future -- and those will include some samples. The Tour de Flex source code will be googleable as well, since it write out HTML pages for each MXML source it uses. -Nick On Tue, May 28, 2013 at 4:02 AM, Tom Chiverton t...@extravision.com wrote: On 24/05/2013 18:12, OmPrakash Muppirala wrote: On May 24, 2013 2:16 AM, Tom Chiverton t...@extravision.com wrote: Well, there's no point putting it on the wiki if a few days later someone is going to have to scrape it off into an application is there ? Tom The advantage of having it as a web resource is that people can google for them, and in general would be easier to share. Isn't the idea to bake the docs into the code and let asdoc write a web site with working examples though ? That solves the Google problem. Tom
Re: SDK Nightly builds?
On Mon, Jun 3, 2013 at 12:47 PM, Erik de Bruin e...@ixsoftware.nl wrote: I took those links as examples and I spied on their settings to come to the URL I posted earlier. That URL doesn't simple point to the 'out' directories, it provides a permanent link to a continually update (on every build) archived version of the last successful build. A minor setting in the post build actions takes care of this archiving and makes the 'artifact' part of the URL available. Yes, I am using https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/apache-flex-sdk-4.10.0-bin for the installer config. Did you just enable this? :-) Thanks, Om EdB On Mon, Jun 3, 2013 at 9:28 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 3:38 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. Apache JMeter provides nightly builds by just pointing to the Jenkins out directories [1] Thanks, Om [1] http://jmeter.apache.org/nightly.html and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: SDK Nightly builds?
I am playing around with the installer to see how best we can support nightlies. Is there any way to generate a .MD5 hash of the artifacts after the release build is done? Or should we have a switch in the installer to disable MD5 checks for nightlies? Is that even a safe option? Thanks, Om On Mon, Jun 3, 2013 at 12:28 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 3:38 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. Apache JMeter provides nightly builds by just pointing to the Jenkins out directories [1] Thanks, Om [1] http://jmeter.apache.org/nightly.html and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin
My next check in may break the build
Hi, Just about to check in some changes that might break the build on Mac/Windows - that should be a clue to what the check in is :-). If it does break I'll fix it quickly. Thanks, Justin
Re: SDK Nightly builds?
I can't tell if you're kidding or not... As far as I can tell I just enabled that URL by adding the Archive the artifact Post-build Action this afternoon. EdB On Mon, Jun 3, 2013 at 9:49 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 12:47 PM, Erik de Bruin e...@ixsoftware.nl wrote: I took those links as examples and I spied on their settings to come to the URL I posted earlier. That URL doesn't simple point to the 'out' directories, it provides a permanent link to a continually update (on every build) archived version of the last successful build. A minor setting in the post build actions takes care of this archiving and makes the 'artifact' part of the URL available. Yes, I am using https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/apache-flex-sdk-4.10.0-bin for the installer config. Did you just enable this? :-) Thanks, Om EdB On Mon, Jun 3, 2013 at 9:28 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 3:38 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. Apache JMeter provides nightly builds by just pointing to the Jenkins out directories [1] Thanks, Om [1] http://jmeter.apache.org/nightly.html and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: My next check in may break the build
Go ahead, make my day ;-) EdB On Mon, Jun 3, 2013 at 10:18 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Just about to check in some changes that might break the build on Mac/Windows - that should be a clue to what the check in is :-). If it does break I'll fix it quickly. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: SDK Nightly builds?
No I am not kidding. I used the url for build 27 in the Installer at which point I thought hmm... it would be good if I dint have to hardcode the build number and had a canonical url for the last build I started typing that in an email and I thought I would check if Jenkins indeed had a feature like that. That's when I saw the url for the last successful build. I dint realize that you had enabled it a few minutes back :-) On Mon, Jun 3, 2013 at 1:27 PM, Erik de Bruin e...@ixsoftware.nl wrote: I can't tell if you're kidding or not... As far as I can tell I just enabled that URL by adding the Archive the artifact Post-build Action this afternoon. EdB On Mon, Jun 3, 2013 at 9:49 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 12:47 PM, Erik de Bruin e...@ixsoftware.nl wrote: I took those links as examples and I spied on their settings to come to the URL I posted earlier. That URL doesn't simple point to the 'out' directories, it provides a permanent link to a continually update (on every build) archived version of the last successful build. A minor setting in the post build actions takes care of this archiving and makes the 'artifact' part of the URL available. Yes, I am using https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/apache-flex-sdk-4.10.0-bin for the installer config. Did you just enable this? :-) Thanks, Om EdB On Mon, Jun 3, 2013 at 9:28 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 3:38 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. Apache JMeter provides nightly builds by just pointing to the Jenkins out directories [1] Thanks, Om [1] http://jmeter.apache.org/nightly.html and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: SDK Nightly builds?
I love it when a plan comes together ;-) EdB On Mon, Jun 3, 2013 at 10:32 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: No I am not kidding. I used the url for build 27 in the Installer at which point I thought hmm... it would be good if I dint have to hardcode the build number and had a canonical url for the last build I started typing that in an email and I thought I would check if Jenkins indeed had a feature like that. That's when I saw the url for the last successful build. I dint realize that you had enabled it a few minutes back :-) On Mon, Jun 3, 2013 at 1:27 PM, Erik de Bruin e...@ixsoftware.nl wrote: I can't tell if you're kidding or not... As far as I can tell I just enabled that URL by adding the Archive the artifact Post-build Action this afternoon. EdB On Mon, Jun 3, 2013 at 9:49 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 12:47 PM, Erik de Bruin e...@ixsoftware.nl wrote: I took those links as examples and I spied on their settings to come to the URL I posted earlier. That URL doesn't simple point to the 'out' directories, it provides a permanent link to a continually update (on every build) archived version of the last successful build. A minor setting in the post build actions takes care of this archiving and makes the 'artifact' part of the URL available. Yes, I am using https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/apache-flex-sdk-4.10.0-bin for the installer config. Did you just enable this? :-) Thanks, Om EdB On Mon, Jun 3, 2013 at 9:28 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, Jun 3, 2013 at 3:38 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I can do that, where would we want to 'publish' the nightly builds That I'm not sure about I'll see what other Apache projects do. Apache JMeter provides nightly builds by just pointing to the Jenkins out directories [1] Thanks, Om [1] http://jmeter.apache.org/nightly.html and what would we include in them? IMO The 2 source and 2 binary releases and a huge warning that these are untested, not official releases, use at own risk, not suitable for production etc etc Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: FlexUnit Wiki Status
.. you could add those files to https://issues.apache.org/jira/browse/FLEX-33490. If possible also html web content as a zip archive. So that we have got everything collected here at apache. All- I would love to attach the jira issue. Unfortunately, the actual content and all of the code samples are _significantly_ larger than one can attach to the Jira issue. I can send you a link on dropbox or something similar. I did some cleanup already, removing copyrights and headers/footers but there is more to do. Tell me how you want this content, Mike
Re: My next check in may break the build
HI, Go ahead, make my day Checked in - any major issues feel free to revert. The SDK should now compile (via ant main) under Linux if you have a pb.tar.gz file contains the 20 odd pixel bender files you need - open to suggestions of any other way of doing it. There still a minor issue with checkintests which is stopping ant binary-release from working, but ant source-release works. Thanks, Justin
Re: My next check in may break the build
Hi Justin, Thanks for slogging through this. I was unable to tell from scanning the diffs how the pg.tar.gz file ends up where it does. Can you provide more details? Thanks, -Alex On 6/3/13 3:49 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Go ahead, make my day Checked in - any major issues feel free to revert. The SDK should now compile (via ant main) under Linux if you have a pb.tar.gz file contains the 20 odd pixel bender files you need - open to suggestions of any other way of doing it. There still a minor issue with checkintests which is stopping ant binary-release from working, but ant source-release works. Thanks, Justin
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
With the greatest of respect, I have to disagree - i dont think it is reasonable to accept donations for the reasons you suggest. while they could continue to exist in GitHub or Google Code, it isn't clear that anyone is really around to handle questions or bugs - That would still be true if the projects were part of Apache Flex, and Apache is not an historical archive. in a few cases, the code owners have indicated that they no longer wish to support a separate community around those bodies of code - If nobody is willing to take ownership of a project (or at least put it on a free github account), how useful a project is it? we know we have active folks here who have used or developed these libraries and can contribute if needed - They would would still help out if project were hosted elsewhere, wouldn't they? Your argument seems to be 'if we dont save them, they will die'. I think we need to let evolution run its course - if a project is useful/important enough to the community, it will survive without Apache Flex's help. having one-stop shopping for Flex SDK and related libraries seems like a good thing to me - Its only one-stop shopping it you use Swiz. I'm all for publicising the fact that there are great libraries for extending Flex, but wouldn't a page on the wiki be more appropriate? That way, everyone gets a mention. Anyway, this is a democracy, so i'll accept the majority decision - but i really dont like it. On 03/06/2013 22:21, Alex Harui wrote: Apache is about communities and open source software. Creating new communities and projects is quite a bit of work, having just gone through it for Flex. There are some popular libraries like Swiz, Parsley, FlexUnit, TLF, and more that, while they could continue to exist in GitHub or Google Code, it isn't clear that anyone is really around to handle questions or bugs, and in a few cases, the code owners have indicated that they no longer wish to support a separate community around those bodies of code. So, while I agree these libraries are not part of the Flex Framework, it seems reasonable to accept these donations because we know we have active folks here who have used or developed these libraries and can contribute if needed. And if we see a separate community form around some of these libraries we can spin them off into their own projects. As the proposal stated, these libraries aren't destined to be integrated into the Flex SDK. But having one-stop shopping for Flex SDK and related libraries seems like a good thing to me. -Alex On 6/3/13 10:53 AM, Lee Burrows subscripti...@leeburrows.com wrote: I have to admit to being a bit confused as to why this discussion is even occuring. This project is called Apache Flex after all, so why are other projects, such as Swiz and FlexUnit, to be included. Where does it end? Do we include AS3CoreLib, Starling or any of the 100s of github projects if the owner offers them? Swiz and FlexUnit are great projects - but they are not part of the Flex framework, and therefore don't belong here. Its as simple as that imho. On 03/06/2013 18:24, Maxime Cowez wrote: @Sebastian: I could not disagree more. In my opinion Flex *is* an MVC framework. It doesn't need an additional layer that requires me to write a whole lot of boilerplate, unnecessarily complicates project structure and forces me to adhere to some rules I often find questionable. I believe Flex has all the tools for creating well-architectured, cleanly separated code (at least since Flex 4). The one thing I miss is an IoC container (even though I could get things done without it, but an IoC sure makes life easier - as opposed to most MVC frameworks). For this I usually use SwiftSuspenders because it is the only library that is *only* an IoC and nothing else (except perhaps for Spring-AS, which I find too complex for most situations). Anyway, I'm not saying you shouldn't adopt frameworks like Swiz under the Apache Flex umbrella (that's why I didn't vote: I don't like Swiz or any other MVC framework, but other people should be able to use it if they like). I'm saying that you really should not force people into such frameworks. For me that would be a reason to drop Flex. Max On Mon, Jun 3, 2013 at 6:22 PM, Sebastian Mohr flex.masul...@gmail.comwrote: IMO ... Apache Flex needs an MVC framework out of the box ... may it be Parsley, Spring AS or Swiz. I'd call it then Apache Flex MVC framework. Having that would bring more stability to the our Flex market. More information can be found here [1]. [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Sun, Jun 2, 2013 at 5:02 PM, Alex Harui aha...@adobe.com wrote: Thanks Carlos. When the 72 hours pass, please use a [VOTE][RESULT] tag to officially close the vote. @Erik. My vote
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
On 6/3/13 6:49 PM, Jeffry Houser jef...@dot-com-it.com wrote: On 6/3/2013 7:44 PM, Lee Burrows wrote: while they could continue to exist in GitHub or Google Code, it isn't clear that anyone is really around to handle questions or bugs - That would still be true if the projects were part of Apache Flex, and Apache is not an historical archive. in a few cases, the code owners have indicated that they no longer wish to support a separate community around those bodies of code - If nobody is willing to take ownership of a project (or at least put it on a free github account), how useful a project is it? I have had similar thoughts; but Lee stated them much more elegantly than I. ( Thanks Lee). Yup, and your reasoning is well-considered. I'm not sure there is a 'right' answer, but IMO, we're all here to change the expected 'evolution' of Adobe's move away from in-house development of Flex. But we do have to keep an eye out for spreading ourselves too thin, showing favoritism for one framework vs another, etc. It is the primary reason I have been voting '0'. I, personally don't see the mutual benefit to either project to get donated; but do not see any benefit in trying to block the donation from others who seem to care about it a lot more than I. When I last commented on Swiz; one response was there are a few contributors that never got their improvements / bug fixes merged to the project so anyone using swiz is missing those. http://markmail.org/search/+list:org.apache.incubator.flex-dev#query:list% 3Aorg.apache.incubator.flex-dev%20from%3A%22Jeffry%20Houser%22+page:1+mid: wsd6vm6tjp6mba6z+state:results I have no idea how moving the project to Apache Flex will address that issue. Because we have a process, any Apache Flex committer can make those changes to the code base and create a release candidate. And if anyone is that motivated, I will take the time to review the candidate, and I hope the others voting for donation will as well. And that's a better chance than I think the situation would be otherwise. -Alex
[jira] [Updated] (FLEX-33529) Change build scripts to create Linux source and release packages
[ https://issues.apache.org/jira/browse/FLEX-33529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33529: - Attachment: (was: pizelbender.gz) Change build scripts to create Linux source and release packages Key: FLEX-33529 URL: https://issues.apache.org/jira/browse/FLEX-33529 Project: Apache Flex Issue Type: Sub-task Reporter: Justin Mclean -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33529) Change build scripts to create Linux source and release packages
[ https://issues.apache.org/jira/browse/FLEX-33529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33529: - Attachment: pb.tar.gz Gziped archive of all compiled pixel bender files. Change build scripts to create Linux source and release packages Key: FLEX-33529 URL: https://issues.apache.org/jira/browse/FLEX-33529 Project: Apache Flex Issue Type: Sub-task Reporter: Justin Mclean Attachments: pb.tar.gz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Build failed in Jenkins: flex-falcon #22
The server at jflex.de isn't responding, so the download fails. I'm going to wait a day or so to see if the server comes up again... What would Plan B be? EdB On Tue, Jun 4, 2013 at 7:30 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/flex-falcon/22/ -- Started by user erikdebruin Building remotely on windows1 in workspace https://builds.apache.org/job/flex-falcon/ws/ Checkout:flex-falcon / https://builds.apache.org/job/flex-falcon/ws/ - hudson.remoting.Channel@175e63ef:windows1 Using strategy: Default Last Built Revision: Revision 0d5171cabfa556b90ca007c0b91234b26ba66514 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/flex-falcon.git Commencing build of Revision 0d5171cabfa556b90ca007c0b91234b26ba66514 (origin/develop) Checking out Revision 0d5171cabfa556b90ca007c0b91234b26ba66514 (origin/develop) [flex-falcon] $ cmd.exe /C 'f:\hudson\hudson-slave\tools\hudson.tasks.Ant_AntInstallation\ant-1.8.2\bin\ant.bat -file jenkins.xml main exit %%ERRORLEVEL%%' Buildfile: https://builds.apache.org/job/flex-falcon/ws/jenkins.xml clean: [delete] Deleting directory https://builds.apache.org/job/flex-falcon/ws/jenkins\temp [delete] Deleting directory https://builds.apache.org/job/flex-falcon/ws/jenkins\JFlex init: [mkdir] Created dir: https://builds.apache.org/job/flex-falcon/ws/jenkins\temp [mkdir] Created dir: https://builds.apache.org/job/flex-falcon/ws/jenkins\JFlex jflex-download: [echo] Be patient. This takes a few minutes... [get] Getting: http://jflex.de/jflex-1.4.3.zip [get] To: https://builds.apache.org/job/flex-falcon/ws/jenkins\temp\JFlex.zip [get] Error getting http://jflex.de/jflex-1.4.3.zip to https://builds.apache.org/job/flex-falcon/ws/jenkins\temp\JFlex.zip BUILD FAILED https://builds.apache.org/job/flex-falcon/ws/jenkins.xml:39: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:395) at sun.net.www.http.HttpClient.openServer(HttpClient.java:530) at sun.net.www.http.HttpClient.init(HttpClient.java:234) at sun.net.www.http.HttpClient.New(HttpClient.java:307) at sun.net.www.http.HttpClient.New(HttpClient.java:324) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) at org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:660) at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:579) at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:569) Total time: 22 seconds Build step 'Invoke Ant' marked build as failure Recording test results -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: My next check in may break the build
On 6/3/13 10:19 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Thanks for slogging through this. I was unable to tell from scanning the diffs how the pg.tar.gz file ends up where it does. Can you provide more details? It needs to be obtained from somewhere. On Linux we can't compile the files, and having the compiled files in version control is not an option as that's against Apache policy. I guess we could host it somewhere but I'm not sure if that could be at Apache or would need to be somewhere else. I've added the zip to the JIRA issue for now. https://issues.apache.org/jira/browse/FLEX-33529 Justin OK, but does it get automatically downloaded? Or do folks have to download manually? One thought I had was to pull them from a recent Apache Flex binary kit. We already pull certain binaries from the Adobe Flex SDK in downloads.xml, although some day we will hopefully not have to pull stuff from Adobe. -Alex
Re: My next check in may break the build
We can have Jenkins automate this. We can have the Linux build download the artifact(s) from the nightly build (which we discussed yesterday) and use those, right? Does a Linux build have any dependencies on specific software on the build machine? EdB On Tue, Jun 4, 2013 at 7:47 AM, Alex Harui aha...@adobe.com wrote: On 6/3/13 10:19 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Thanks for slogging through this. I was unable to tell from scanning the diffs how the pg.tar.gz file ends up where it does. Can you provide more details? It needs to be obtained from somewhere. On Linux we can't compile the files, and having the compiled files in version control is not an option as that's against Apache policy. I guess we could host it somewhere but I'm not sure if that could be at Apache or would need to be somewhere else. I've added the zip to the JIRA issue for now. https://issues.apache.org/jira/browse/FLEX-33529 Justin OK, but does it get automatically downloaded? Or do folks have to download manually? One thought I had was to pull them from a recent Apache Flex binary kit. We already pull certain binaries from the Adobe Flex SDK in downloads.xml, although some day we will hopefully not have to pull stuff from Adobe. -Alex -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
