Why Swiz?

[Julian]

Dear Swiz team and members,

I'm right now working with my development team and trying to decide on
a framework and a pattern. I've been looking at a number of different
frameworks (I'm at a talk on PureMVC right now) and I'm so far very
interested in Swiz.

As I meantioned Swiz, someone also mentioned Parsley - so I checked it
out. I haven't done any kind of POC on it yet, but I'm wondering -
why would I choose Swiz over Parsley?

So far I like Swiz much better, but if I need to convince my Snr.
Software Engineer that Swiz is the way to go, what arguments would I
use?

Any information would be awesome!

Cheers,
Julian

[Brian Kotek]

You can look at the Parsley documentation and get a feel for this yourself. Parsley is a much larger framework, with more potential coupling between your application code and the framework, and, in my opinion, is much more complex. Swiz is meant to be extremely simple.

[Julian Alexander]

That makes sense, and that's why I like it so much.  The only blocker I hve to using it right now is the lack of module support, but it might be worth waiting.  One thing that I am really opposed to is getting locked into a framework.

And I did look at the documentation - it seemed much more rich in functionality and features, but much more complicated and obfuscated as far as application, which has tons of disadvantages.

Any idea when the module support will be coming out for Swiz?

-Julian

2009/11/8 Brian Kotek <bria...@gmail.com>

--
- Julian

[Chris Scott]

Module support us coming in the next build. That is pretty much a matter if resolving some merge issues with my branch and development.

-chris 

Sent from my iPhone

[Ben Clinkinbeard]

I agree with what Brian said and would add that the Swiz community is
much larger and much more active than the Parsley community. It will
be easier to get assistance with Swiz questions than it will with
Parsley.

HTH,
Ben

On Nov 8, 2:07 pm, Julian Alexander <frool...@gmail.com> wrote:
> That makes sense, and that's why I like it so much.  The only blocker I hve
> to using it right now is the lack of module support, but it might be worth

> waiting.  One thing that I am *really* opposed to is getting locked into a

> framework.
>
> And I did look at the documentation - it seemed much more rich in
> functionality and features, but much more complicated and obfuscated as far
> as application, which has tons of disadvantages.
>
> Any idea when the module support will be coming out for Swiz?
>
> -Julian
>

> 2009/11/8 Brian Kotek <brian...@gmail.com>

>
>
>
> > You can look at the Parsley documentation and get a feel for this yourself.
> > Parsley is a much larger framework, with more potential coupling between
> > your application code and the framework, and, in my opinion, is much more
> > complex. Swiz is meant to be extremely simple.
>

[Bas Kamer]

Hello Chris,

I just saw this mail, thanks for this...

On 8 nov 2009, at 20:38, Chris Scott wrote:

> Module support us coming in the next build. That is pretty much a matter if resolving some merge issues with my branch and development.

<whispering> do u have an estimate on timing?

bas