1. Parsley is OSS, the repo is at github, so everyone can start working if there is need to do so (that hasn't been the case yet, because it works great out of the box). The original author moved on to other projects though, but that happens a lot and does not make Parsley any less valuable.
2. About complexity: complex != complicated and simple != easy. You can use every tool in a complex (possibly wrong) and easy (possibly correct) way. You can use a hammer wrong if you grab it on the wrong end, but it will get the job done eventually. So "Overkill" might not be the right word, better go for "wrong usage" or "over complicated usage". Parsley is simple if used properly. 3. Usage: Parsley basically comes down to IoC/DI (e.g. via [Inject] tags), Commands and Messages. Everything is wired together in (M)XML in the simples possible way. Once you've set it up it's absolutly simple in everyday work (read: efficant). There are some advanced features (Scopes, decoupled bindings, etc) which are optional. You don't have to use them if you don't need to, but if you do, it's great to have them available. The framework can also be manually improved in many ways (interceptors, etc). Another important part is documentation: Everything is well documented and explained(!). There could be more examples available though. So it might take some time to get things working, depending on your knowledge on AS3, Flex, software engineering, etc. Summed up, it's a stable, robust, extensible piece of software, that scales perfectly. Am 26.07.2013 14:21, schrieb Ajar: > In my opinion - overkill is indeed the right word to describe parsley in > most cases. > While I respect complexity and clockwork architecture, > I can really appreciate straight forward framework like RobotLegs which > reduces the complexity in my projects. > My projects are fairly complex and large scale, this is why RL was a treat, > since I didn't need to double (or triple) the complexity. > I'm not looking for extensive feature-set that I'll rarely get to, I'd > rather have 80% which covers most cases in an easy straight-forward way. > And while you argue the parsley is close to perfection, indeed try it out > and see for your self, while having a project to execute, will you prefer a > robust tool or a minimalist one. > In my opinion, you are bound to go astray while you go into a new > territory, that's why a community is essential to support and grow > according to real needs that are communicated within a live community, > rather then browsing through ghost-posts hoping it will stick. > RL approach to modules in particular was a relief after trying out plumbing > with pureMVC pipes... > simple, painless, and works like a charm. > good luck with it, any turn you take. > cheers > Ajar > > On Fri, Jul 26, 2013 at 2:06 PM, Maurice Amsellem < > [email protected]> wrote: > >> Fully agree with Thomas. >> Although Parsley will not evolve anymore from its creator, it's very >> mature and capable, almost bug free, and it's very extensible: >> - either from native documented extension points >> - with directly by modifying the source. >> >> So it may be overkill for small projects, but it really shines on complex >> or large projects. >> I also used it on Mobile Flex (using the FastInject feature) with little >> performance degradation. >> >> Regards, >> >> Maurice >> >> -----Message d'origine----- >> De : Frédéric Thomas [mailto:[email protected]] >> Envoyé : vendredi 26 juillet 2013 10:55 >> À : [email protected] >> Objet : Re: MVC framework >> >> Hi, >> >> Just to be clear even though Parsley is not maintain anymore by its >> original creator, it's up to individuals to add new feature as they like, >> it's the more complete and well design IOC / MVC framework I used out >> there, it has everything you need out of the box and probably more, that's >> the point, depending of your project complexity, you maybe won't need all >> its capabilities, in this case, a lighter and easier to learn framework >> will probably fit your needs as Swiz, Roboleg, Urania or even a custom one. >> >> -Fred >> >> -----Message d'origine----- >> From: Ajar >> Sent: Friday, July 26, 2013 10:23 AM >> To: [email protected] >> Subject: Re: MVC framework >> >> dude - Parsley is discontinued, you can checkout the news section on their >> site. >> RobotLegs on the other hand is alive and kicking! >> Great supportive community, and you'll pick it up on a weekend. >> well, i'm biased - it's my ultimate favorite :) >> >> >> On Fri, Jul 26, 2013 at 9:05 AM, Justin Mclean >> <[email protected]>wrote: >> >>> Hi, >>> >>>> How can I realize an MVC like architecture by using Flex/AS3 only. Are >>> there any examples out there? >>> >>> Basically AS classes for your model, loosely coupled MXML component >>> dispatching events for your views, data binding on the model to update >>> views and your application or an event bus as your application, add a but >>> of structure and discipline and it's a simple, easy to understand, >>> scalable >>> (to a reasonable size), flexible, non prescriptive MVC suitable for a lot >>> of jobs. >>> >>> Think I have a simple application lying about that does this (from my >>> frameworks are evil talk?), I'll see if I can find it. >>> >>> Thanks, >>> Justin >> >> >
