> Overly complicated? Come on More simple and organized in a way that
> everyone comprehends ?
I don't know your framework but I have experience with several
intrusive frameworks that brutally impose MVC (PureMVC, Aconcagua) and
I really find them too restrictive. I don't like boilerplate code
Ouch. Flex is already a bit bloated. Why would we need to have it
connected with some MVC framework in ANY way? I had no issues with
'integrating' Flex with PureMVC or Aconcagua (oohh I HATE that
name!!!) and one custom built framework! Moreover, developing more and
more with Flex I came to a concl
What about test reports? If there are two test frameworks used then I
guess one either have to somehow merge the results or live with a set
of two reports?
ke idea of having more frameworks allowed as it results in tests
suites which are harder to maintain and more complicated build. But
that's of course only my two cents, I'm not even commiter so feel free
to ignore me ;)
2012/2/9 Martin Heidegger :
> On 10/02/2012 03:25, Piotr Kawiak wr
I really wouldn't recommend choosing two unit test frameworks. Much
harder to maintain.
2012/2/9 Piotr Kawiak :
> Magic string methods are not cool. Much better to have code completion
> / refactoring support. Mockito works great for me. What do you mean by
> 'checks if there
Magic string methods are not cool. Much better to have code completion
/ refactoring support. Mockito works great for me. What do you mean by
'checks if there was _any_ execution of this method call' ?
2012/2/9 Jonathan Campos :
> Just dropping in 2 cents.
>
> While I too use FlexUnit and think th
I totally agree with Alex. I am working in a large company on
enterprise scale project with Flex GUI and I'd love 'new' Flex to be
backwards compatible, but this sure looks like an enormous effort. In
my company we keep using Flex 3, we didn't even switch to 4, cause it
isn't really worth the effor
