On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira carlosrov...@apache.orgwrote:
Hi,
I want to propose the donation of Swiz Framework to Apache Flex.
This would be awesome in my opinion :-) Just remember that the donation
process could get complicated if Chris doesn't hold the copyright to all
* Swiz stopped development in 2.0.0 beta that brings AOP to Flex Framework.
The problem with this implementation is that is not ready for producction
since it needs changes in Flex Compiler and in AS3 Commons ByteCode to get
it work properly.
Hi there,
I'm the author of as3commons-bytecode.
Good luck, but I'd rather see Parsley integrated into Apache Flex.
Am 28.05.2013 16:52, schrieb Carlos Rovira:
Hi,
I want to propose the donation of Swiz Framework to Apache Flex.
https://github.com/swiz/swiz-framework/
https://swizframework.jira.com/wiki/display/SWIZ/Home
The reasons
On Tue, May 28, 2013 at 10:33 AM, dude d...@atheist.com wrote:
Good luck, but I'd rather see Parsley integrated into Apache Flex.
That's the only concern I'd have about the donation. I know Swiz is one
framework among several. So we'd have to manage it carefully to keep from
alienating part of
On 28 May 2013 17:33, dude d...@atheist.com wrote:
Good luck, but I'd rather see Parsley integrated into Apache Flex.
Personally, the above response shows exactly the reason why I think there
shouldn't be any
application framework integrated into Apache Flex. Too many opinions on
the
On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga rol...@stackandheap.comwrote:
On 28 May 2013 17:33, dude d...@atheist.com wrote:
Good luck, but I'd rather see Parsley integrated into Apache Flex.
Personally, the above response shows exactly the reason why I think there
shouldn't be any
Hi Greg,
other people behind the project are Ben and Brian (maybe more other
contributions), but all files are behind Apache License 2.0 and seems
there's no authors specifications so maybe they already agreed with the
Apache License 2.0, but I'll ask them on the swiz list to get it clear
I don't know the actual state of RobotLegs, Parsley or others... Swiz is
without maintenance and needs attention and 2.0 could bring a great
improvment not reached for any other framework. This doesn't mean any base
sdk integration and dependency. We could make the same with other projects
that
Adding a top level applicaction framework to the APACHE FLEX project
suitcase will somehow set is as the facto standard accepted framework to
build applications using the FLEX SDK, or at least will create that
understanding between developers.
So I think top level application frameworks must not
I don't use swiz but it seems silly to reject a donation because of a fear
of what might happen. It's easy enough to keep it separate, and if it's
not supported anywhere projects using it will likely ditch the flex
framework completely
On 28 May 2013 18:49, Carlos Velasco
On 5/28/13 8:39 AM, Greg Reddin gred...@gmail.com wrote:
On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga
rol...@stackandheap.comwrote:
On 28 May 2013 17:33, dude d...@atheist.com wrote:
Good luck, but I'd rather see Parsley integrated into Apache Flex.
Personally, the above response
Top level application flex frameworks should be incubated at Apache as
independent projects to Apache FLEX to avoid missunderstandings and be
politically correct.
2013/5/28 Avi Kessner akess...@gmail.com
I don't use swiz but it seems silly to reject a donation because of a fear
of what might
None of these frameworks should be integrated into Apache Flex, I guess
everyone agrees with that.
FYI: Parsley has been abandoned by its creator as well and there is no
further development atm (afaik). It is licenced under Apache License 2.0
and available here https://github.com/spicefactory
Am
I agree
On 28 May 2013 17:28, dude d...@atheist.com wrote:
None of these frameworks should be integrated into Apache Flex, I guess
everyone agrees with that.
FYI: Parsley has been abandoned by its creator as well and there is no
further development atm (afaik). It is licenced under Apache
I like the idea of a vote. I don't think the community is divided
about 'having' Swiz, it seems the division is more 'what to do with
it'. Please let the VOTE be clear about this.
EdB
On Tue, May 28, 2013 at 6:49 PM, Carlos Rovira
carlos.rov...@codeoscopic.com wrote:
I think this would require
On Tue, May 28, 2013 at 11:18 AM, Alex Harui aha...@adobe.com wrote:
Greg, do you think donations like these need to have a goal of being
integrated with Apache Flex or becoming its own project? Personally, I'd
be ok with Apache Flex being a warehouse of all kinds of Flex-related code
even
Greg,
I see why you might be worried about future additional projects, but
the sub-projects you mention (Falcon, SDK, FlexJS) are very much part
of one and the same project. Other sub-projects are purely for
supporting the community and various workflows (Installer, Maven) and
are too small to
I like the donation of the Swiz framework. I use both swiz(for work) and
parsley(personal projects) and I am ambivalent at this point. What I would
really like to see the best part of these frameworks (and maeby others like
spring-actionscript, robotlegs, etc.) integrated into Flex.
I am
I would prefer JIRA activity to be on another list. I've heard from quite
a few people in my User Group that they dropped off dev@ people of the
noise of JIRA. I think those of us who want to know what is committed
will subscribe to those (plus, it makes filtering those messages into a
separate
+1 on the JIRA on another list, do we need a vote on that, or can we
just ask INFRA for it?
Maybe this discussion should be in a separate thread, however...
EdB
On Tue, May 28, 2013 at 7:57 PM, Nicholas Kwiatkowski nicho...@spoon.as wrote:
I would prefer JIRA activity to be on another list.
I do not agree to you. There are a lot of ways to approach an application
development, some may be of your liking others will not be. But there is no
need to force one of them as the Flex sdk one.
I would rather prefer to maintain all those as separate libraries for anyone to
choose the one he
Om is pointing my main concern with Swiz donation. The main point here is
that Swiz 2.0.0 Beta has many good and beautiful ideas about AOP that are
very new to web client technologies. Something that people are using from
long time in java could be first citizen in Flex making an huge difference.
22 matches
Mail list logo