Re: [OT] The end of the SpiceFactory
Wow, so much arrogance and ignorance in one single post. Am 15.01.2013 19:57, schrieb David Coleman: > Having used (and DESPISED) Parsley, I can say with pleasure "Good Riddance". > For me it was overkill and added little to no value to the quality of the > code. All the ppl I know who used Parsley said "oh but you have dependency > injection" "oh but you have encapsulation of this" "oh but you have > decoupled code"... I say "ever hear of a singleton? flex doesn't need > dependency injection if you are smart" "why encapsulate? don't your > developers know how to use the Flex SDK?, what are you afraid of writing your > own code" and to the ppl who blather on about decoupled code... I laugh in > their faces and ask them "ever hear of Events?" > > Ok so maybe there were some benefits, and of course my opinions are > admittedly acid, draconian and intentionally dismissive... But I believe > that Flex is a great framework all by itself, and if you need an extra > package to do MVC, you don't understand what MVC is in the first place, and > no matter what you do, it won't be good. > >> From: tang...@usa.net >> To: dev@flex.apache.org >> Subject: RE: [OT] The end of the SpiceFactory >> Date: Tue, 15 Jan 2013 13:44:31 -0500 >> >> I am glad I have skipped Parsley and looked into RobotLegs, which is about >> to release RobotLegs 2. >> >> As for HTML 5, I still don't get all the frenzy around the technologies >> where they are built on old JavaScript that is not strongly typed, and >> pretty much every features HTML 5 has to offer are "I am catching up with >> Flash." But all the decision makers who have zero understanding of Flash >> and just a few whitepaper on HTML 5 would go frenzy with the latest stuff, >> most stemmed from the hatred of Flash because of those annoying Flash >> advertisements that incompetent designers have come up with. >> >> -Original Message- >> From: Michael Schmalle [mailto:apa...@teotigraphix.com] >> Sent: Monday, January 14, 2013 6:09 PM >> To: dev@flex.apache.org >> Subject: Re: [OT] The end of the SpiceFactory >> >> Right, the eating and beating was a visual for the hedonism of the >> HTML5 community and there reckless JavaScript development. >> >> I agree, if I can use ActionScript to make WebAudio applications in 1 >> year, this will be a success. :) >> >> Mike >> >> Quoting Alex Harui : >> >>> >>> >>> >>> On 1/14/13 2:22 PM, "Michael Schmalle" wrote: >>> >>> JavaScript unfortunately is the only road left. >>> Native (mobile) apps is also a possible road. >>> This decade of my life will be fulfilled if the tortoise can walk passed the hare stuffing his face with jQuery muffins. >>> Thanks for making me laugh. I wish I were an artist because I would >> sketch >>> a political cartoon of that. But remember, the hare got beat by snoozing, >>> not by overeating. And really, I don't think we have to beat the hare to >> be >>> successful. >>> >>> -- >>> Alex Harui >>> Flex SDK Team >>> Adobe Systems, Inc. >>> http://blogs.adobe.com/aharui >>> >>> >> >> -- >> Michael Schmalle - Teoti Graphix, LLC >> http://www.teotigraphix.com >> http://blog.teotigraphix.com >> > >
Re: [PR] Flex != Flash
Nice read. There is a minor typo in the 7th paragraph "But Flex was always open source!": [...]before it was donated to *Adobe* was by Adobe employees[...] ... should be Apache/ASF. :) Am 27.01.2013 23:58, schrieb Harbs: > You guys might enjoy my blog post: > http://printui.com/blog/2013/01/flex-flash/ > > If you do, feel free to pass it on… ;-) > > Harbs >
Re: Flex-Spring Integration
FYI: Carlos Rovira forked spring-flex a few months ago to integrate Hibernate 4.1 support. https://github.com/codeoscopic/spring-flex
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
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 behind the propossal are: > > * Swiz Framework is a mature microarquitecure for Apache Flex that > complements it to build applications with MVC, DI and other commodities > needed today to be productive. (There's other frameworks out there that > could be used along Flex like RobotLegs, Parsley, ) > > * Swiz is not updated anymore since people behind it migrated from Flex > platform to HTML5 technologies and does not want to invest more time. > > * 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. > > Chris Scott, the creator of swiz respond on the list some minutes ago and > he approved the Swiz Framework Donation to Apache Flex. > > If people doesn't have any issues with this donation I'll go through the > steps that, will require for actual production version. Taking into account > that * Swiz Framework already has Apache License 2.0, the steps to get > donation done should be only: > > * Get Chris Scott email accepting the donation of the swiz source code and > wiki content. > * I'll request a "flex-swiz-framework" git repo where we can migrate the > source code. > > In a second round, Chris will want to donate 2.0.0 Beta and we can disscuss > changes to Flex compiler and talk with as3commons to know enhancements to > bytecode project and see if it's viable or not. > > Let me know what do you think about it and If I need to take into account > something else. > > Thanks. > > Carlos Rovira >
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
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 28.05.2013 17:44, schrieb Carlos Rovira: > 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 need a home. This should be driven by community necessity and should > have people behind the effort. > > 2013/5/28 Greg Reddin > >> On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga >> wrote: >> >>> On 28 May 2013 17:33, dude 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 matter... >>> >> >> But, there's no reason we can't integrate it as a sub-project or incubate >> it. If it develops a community it can become its own TLP. >> > > >
Re: BlazeDS
Looking forward to that. Am 30.05.2013 12:36, schrieb christofer.d...@c-ware.de: > As far as I know there are a lot of tutorials about creating NIO adapters for > BlazeDS ... > The ones out there make use of properitary Jetty features and I have not yet > come across one generic servlet 3.0 spec endpoint. I would much more prefer > to start working on such an endpoint. It's something I have on my todo list > for quite some time now ;-) > > Chris > > -Ursprüngliche Nachricht- > Von: Nick Collins [mailto:ndcoll...@gmail.com] > Gesendet: Mittwoch, 29. Mai 2013 23:58 > An: dev@flex.apache.org > Betreff: Re: BlazeDS > > I may or may not have missed it, but does anyone know if there is any chance > of the guys at Farata donating their extensions along with BlazeDS that add > NIO support and such? That would make the Apache BlazeDS even more > competitive against ADEP DS. > > Nick > > > On Tue, May 28, 2013 at 10:47 PM, Alex Harui wrote: > >> I keep seeing signs that they are making slow progress toward getting >> it donated. >> >> On 5/28/13 7:48 PM, "Justin Mclean" wrote: >> >>> HI, >>> >>> A question just come up on the user list about BlazeDS. Alex do you >>> know if it still likely to be donated? >>> >>> Thanks, >>> Justin >> >>
Re: BlazeDS
I know about GraniteDS and it's awesome (we already use Gas3). Unfort. it's not possible to migrate our current project to GraniteDS entirely within a reasonable amount of time, because we use technologies like Spring-Flex and Parsley which do not work combined with GraniteDS (or do they?). Am 30.05.2013 14:50, schrieb Franck Wolff: > If you are looking for an efficient realtime messaging stack, you could > have a look at GraniteDS <http://www.graniteds.org/>. > > Franck. > > > 2013/5/30 dude > >> Looking forward to that. >> >> Am 30.05.2013 12:36, schrieb christofer.d...@c-ware.de: >>> As far as I know there are a lot of tutorials about creating NIO >> adapters for BlazeDS ... >>> The ones out there make use of properitary Jetty features and I have not >> yet come across one generic servlet 3.0 spec endpoint. I would much more >> prefer to start working on such an endpoint. It's something I have on my >> todo list for quite some time now ;-) >>> >>> Chris >>> >>> -Ursprüngliche Nachricht- >>> Von: Nick Collins [mailto:ndcoll...@gmail.com] >>> Gesendet: Mittwoch, 29. Mai 2013 23:58 >>> An: dev@flex.apache.org >>> Betreff: Re: BlazeDS >>> >>> I may or may not have missed it, but does anyone know if there is any >> chance of the guys at Farata donating their extensions along with BlazeDS >> that add NIO support and such? That would make the Apache BlazeDS even more >> competitive against ADEP DS. >>> >>> Nick >>> >>> >>> On Tue, May 28, 2013 at 10:47 PM, Alex Harui wrote: >>> >>>> I keep seeing signs that they are making slow progress toward getting >>>> it donated. >>>> >>>> On 5/28/13 7:48 PM, "Justin Mclean" wrote: >>>> >>>>> HI, >>>>> >>>>> A question just come up on the user list about BlazeDS. Alex do you >>>>> know if it still likely to be donated? >>>>> >>>>> Thanks, >>>>> Justin >>>> >>>> >> >
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
Same concerns here. Reviving Swiz would be a good thing to do, but if that happens under the Apache Flex flag it could be recognized as 'the best' or 'supported' IoC framework, even if explicitely stated otherwise. It might be better to keep the Status Quo (none of those frameworks in Apache Flex) - or get them all under one roof (not sure if that is possible at all). AOP: It has also been pointed out in this thread that implementing AOP compile time weaving into Falcon might be a better approach (by Roland Zwaga). Am 31.05.2013 18:30, schrieb Alex Harui: > I'd like to vote in favor, but I'm not liking the quantity of -1's we're > seeing. > Can we cancel this vote and draft a more detailed proposal, maybe after > some discussing with those voting -1? > > I think the new proposal should be explicit about the name of the repo. > I think the new proposal should state that Swiz would have its own > releases and not be part of an SDK release. > > One thing I'm not quite understanding is how the future would look if a > committer did try to add AOP into the SDK. Would that conflict with the > implementations in Swiz or other frameworks? Or is the expectation that > some set of committers will update Swiz to use that implementation of AOP? > Committers are free to do whatever they want, but if Swiz gets more love > than the other frameworks it could appear to be the "endorsed" framework, > which is what I think we are trying to avoid. > > -Alex > > > On 5/29/13 6:16 PM, "Jeff Tapper" wrote: > >> -1 Binding, unless there are assurances that this will not be part of the >> main branch, but instead live in a separate repo. >> >> -Original Message- >> From: Greg Reddin [mailto:gred...@gmail.com] >> Sent: Wednesday, May 29, 2013 12:12 PM >> To: dev@flex.apache.org >> Subject: Re: [VOTE] Swiz Framework Donation to Apache Flex >> >> +1 (binding) >> >> >> On Wed, May 29, 2013 at 4:43 AM, Carlos Rovira >> wrote: >> >>> After proposal thread >>> (http://markmail.org/message/jtedmmx5djqen52l),comes >>> the vote thread. >>> >>> This thread is to decide if we finally adopt Swiz Framework under >>> Apache Flex, since there is multiple opinions in the Apache Flex >> community. >>> >>> points to take into account: >>> >>> * 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). >>> >>> Points that some people argument to not accept the donation: >>> * There is other frameworks like Swiz out there in the same situation >>> and this donation could make Swiz the preferred/recommended IOC >>> framework of use. >>> >>> Points to take into account: >>> * Erik de bruin stated that maybe the problem is "what to do with it" >>> under Apache Flex umbrella. >>> >>> >>> Please make your vote. >>> >>> Thanks >>> >>> Carlos Rovira >>> >> >
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
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 only option. People get to chose what they > want to use - the SDK isn't and won't be tied to any framework - and > if they chose to use Swiz, they can find it at Apache Flex. That's it. > > EdB > > > > On Sat, Jun 1, 2013 at 6:31 PM, Igor Costa wrote: >> 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 Sat, Jun 1, 2013 at 12:46 PM, Erik de Bruin wrote: >> >>> 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, like 'flex-swiz', we need to discuss that a bit more, >>> I think. >>> >>> Thank you Carlos for managing the vote and keeping track of this donation. >>> >>> EdB >>> > > >
Re: [DISCUSS] Swiz Framework Donation to Apache Flex
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://github.com/spicefactory . And there is a JIRA: http://opensource.powerflasher.com/jira/secure/Dashboard.jspa Am 01.06.2013 22:14, schrieb Carlos Rovira: > 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 requeriment here is to have people interested in donate > time and effort in the donation and subsequent maintenance of the source > code... > > > 2013/6/1 dude > >> 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 only option. People get to chose what they >>> want to use - the SDK isn't and won't be tied to any framework - and >>> if they chose to use Swiz, they can find it at Apache Flex. That's it. >>> >>> EdB >>> >>> >>> >>> On Sat, Jun 1, 2013 at 6:31 PM, Igor Costa wrote: >>>> 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 Sat, Jun 1, 2013 at 12:46 PM, Erik de Bruin >> wrote: >>>> >>>>> 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, like 'flex-swiz', we need to discuss that a bit more, >>>>> I think. >>>>> >>>>> Thank you Carlos for managing the vote and keeping track of this >> donation. >>>>> >>>>> EdB >>>>> >>> >>> >>> >> > > >
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: BlazeDS Software Grant was sent to Apache today.
Good news. Besides NIO and alike, I'd love to see lazy loading implemented into BlazeDS. I remember there was a project called dphibernate or something that tried to do that, but it was a PITA to setup iirc. How much efford would it take to get lazy loading into BlazeDS? Am 02.08.2013 07:16, schrieb Alex Harui: > Once the grant is recorded, we'll start in on moving the code over. I think > we're just going to take it without SVN history. Extracting SVN history from > opensource.adobe.com is quite painful. Let me know if you disagree. > > That should mean one less option and download in the installer and build > scripts in releases after 4.10.0. > > Many thanks to the BlazeDS team at Adobe for slogging through a difficult IP > clearance process. > > -Alex >
