Hi,
here's my +1 (I think I should state it although is clear since I was who
open the vote)
2013/6/1 Carlos Rovira carlos.rov...@codeoscopic.com
Hi,
seems like all has been said yet. I don't think we should stop the vote
since as others commented two -1 votes was left in the cold with
The vote was open for more than 72 hours. I'm closing it.
Here are results:
+1 (binding)
Erik de Bruin
Greg Reddin
Justin Mclean
Fréderic Thomas
-1 (binding)
Igor Costa (no explanation)
Jeff Tapper (he stated unless there are assurances that this will not be
part of the
main branch, but
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.
Alex wrote on the FlexJS wiki page,
*States were used often but had a limitation once the set of
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
Usually I solve this by just overriding the getCurrentState method and a
having all the posible options in the states group.
J
On Sat, Jun 1, 2013 at 6:41 AM, John Cunliffe mahn...@gmail.com wrote:
How is that different from the already existing
stateGroups
When I find myself pondering such a situation, I usually come to the
conclusion it's time to split up my component into smaller ones: most of
the times it's a signal that there's too much going in one view and I'm
breaking separation of concerns.
Of course that's not true for *every* situation,
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
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
The way we voted to include Swiz will be applied to any other
framework if/when those are donated as well.
The fact that Swiz gets a home at Apache Flex doesn't mean it will be
endorsed as the one and only option. People get to chose what they
want to use - the SDK isn't and won't be tied to any
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
really looking forward about this, i have being missing swiz for mobile app
development lot so once the donation took place hope there will be new
development towards swiz mobile application support
Thanks
Sumudu
On Sat, Jun 1, 2013 at 10:36 PM, Carlos Rovira
carlos.rov...@codeoscopic.com
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
You hid your vote well... you did +1 and -1 in two short sentences.
Re-reading helped a bit, but - at least for non-native speakers - it
was very ambivalent.
I think most of your concerns have been addressed in one way or
another, or will (must) be addressed during the coming process of
donation.
Sorry Om,
your mail was confusing since it had -1 and +1 votes in the same mail, so
the external lecture was that it was only an opinion and want to express
something but not state a final vote.
Regarding the contrib folder, I'm not a supporter of this idea in the
Swiz case, since in my case we
So Parsley could find a new home here as well?
Am 01.06.2013 18:54, schrieb Erik de Bruin:
The way we voted to include Swiz will be applied to any other
framework if/when those are donated as well.
The fact that Swiz gets a home at Apache Flex doesn't mean it will be
endorsed as the one and
It certainly could, in my opinion. I think these frameworks enhance
Flex and therefor enhance the Apache Flex project. I think there is
synergy to be had, both for 'users' and contributors.
EdB
On Sat, Jun 1, 2013 at 7:43 PM, dude d...@atheist.com wrote:
So Parsley could find a new home here
My bad for not voting clearly.
If you two are confident that we can make a release of Swiz in a reasonable
timeframe, I am cool with it.
It would bode well for us if we make a blog post making it clear that we
support all other frameworks as well. Can someone come up with such a post
and put it
[
https://issues.apache.org/jira/browse/FLEX-33052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672200#comment-13672200
]
Jan Durian commented on FLEX-33052:
---
I mean, this one is still actual. Copying styles
Hi Om,
I can make the blog post, but we should wait until Chris Scott write the
email with his intention of donation. Then we can make the official blog
post to make the announcement to the world. And we will put special wording
in make clear that this donation should not be seen as giving any
Right! why not? :)
I don't know too much about parsely but seems it's in the same state that
Swiz. If AOP efforts progress all frameworks like swiz and parsley could
benefit from the hooks in the compiler to implement it and will need people
behind it to make this evolution.
I think the only
What steps are required from the author to make the donation? Since he
has moved on to other things, I'd like to bother him as less as possible.
Parsley3/Spicelib3 are release under Apache License 2.0. The framework
consists of several libraries which can be found here
[
https://issues.apache.org/jira/browse/FLEX-33052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672288#comment-13672288
]
Justin Mclean commented on FLEX-33052:
--
Can you supply a simple project that
[
https://issues.apache.org/jira/browse/FLEX-33547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672294#comment-13672294
]
Justin Mclean commented on FLEX-33547:
--
Perhaps also
FLEX-33052
Hi,
What steps are required from the author to make the donation?
Having them mailing the mailing list would probably be enough. A vote would
also need to be taken but I don't see any major reason why we would allow one
framework and not the other.
Parsley3/Spicelib3 are release under
Hi,
Alex, since that was the controversial part of the proposal, perhaps it is
better to have a separate vote for it.
No need for a vote IMO. Committers can unsubscribe just like they can
unsubscribe to the dev list. Although I'd hope that all committer would stay
subscribed to both lists
On 6/1/13 7:58 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Alex, since that was the controversial part of the proposal, perhaps it
is
better to have a separate vote for it.
No need for a vote IMO. Committers can unsubscribe just like they can
unsubscribe to the dev list. Although
On 6/1/13 7:54 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
What steps are required from the author to make the donation?
Having them mailing the mailing list would probably be enough. A vote
would also need to be taken but I don't see any major reason why we would
allow one
See http://localhost:8080/job/flex-sdk_mustella/120/
--
[...truncated 79775 lines...]
[java] spark/validators/NumberValidator/Methods/NV_validate_tester
NV_validate_default_invalid_trigger_test16 Passed
[java]
28 matches
Mail list logo
