Comments on: Using the Abstract Factory pattern with Flex http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/ avoid mickey mouse programming Tue, 06 Jul 2010 18:20:46 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Giorgio Natili http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/comment-page-1/#comment-786 Giorgio Natili Tue, 17 Feb 2009 07:51:54 +0000 http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/#comment-786 Hi Emanuele, Thanks for your comment, I believe that your idea is good, the only concern that I have is if you encounter in your development a server side team that is not so smart, but it's trough, sending a value object and handling it on the server is a smarter solution... Hi Emanuele,

Thanks for your comment, I believe that your idea is good, the only concern that I have is if you encounter in your development a server side team that is not so smart, but it’s trough, sending a value object and handling it on the server is a smarter solution…

]]> By: Emanuele Spinella http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/comment-page-1/#comment-780 Emanuele Spinella Mon, 16 Feb 2009 01:04:29 +0000 http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/#comment-780 Very good job! I think that you should write other articles related to the design patterns, because your approach is very easy to understand and implement following the examples. Very good job! I think that you should write other articles related to the design patterns, because your approach is very easy to understand and implement following the examples.

]]> By: Emanuele Spinella http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/comment-page-1/#comment-779 Emanuele Spinella Mon, 16 Feb 2009 00:50:29 +0000 http://www.mxml.it/index.php/2009/02/13/using-the-abstract-factory-pattern-with-flex/#comment-779 I would like to extend your work with some considerations: The credit card presenters have a duplicated submit method, because all the credit cards have the same fields, regardless of the type (Visa, American Express, etc). Maybe it would be better to write a CreditCardPresenter super-class, that implements the submit() public method and from which AmericanExpressCreditCard e VisaCreditCard derive. We can do also another thing: CreditCardPresenter, ECheck and PayPal classes have to create their own VO (Value Objects), in order to communicate, for example, with a server. VO are of three different types because, for each of those payment types, there are different informations to provide. However, you can think to unify the submit method with an empty interface (e.g. IPayment) that all the VO have to implement. Following this approach, the submit method can send an IPayment object and can be shared by all the presenters. So we can have a super-presenter that implements the submit method and we can reach a more abstract, modular and flexible structure. I've send you a class diagram that should explain better what I mean. I would like to extend your work with some considerations:
The credit card presenters have a duplicated submit method, because all the credit cards have the same fields, regardless of the type (Visa, American Express, etc).
Maybe it would be better to write a CreditCardPresenter super-class, that implements the submit() public method and from which AmericanExpressCreditCard e VisaCreditCard derive.
We can do also another thing: CreditCardPresenter, ECheck and PayPal classes have to create their own VO (Value Objects), in order to communicate, for example, with a server. VO are of three different types because, for each of those payment types, there are different informations to provide.
However, you can think to unify the submit method with an empty interface (e.g. IPayment) that all the VO have to implement.
Following this approach, the submit method can send an IPayment object and can be shared by all the presenters.
So we can have a super-presenter that implements the submit method and we can reach a more abstract, modular and flexible structure.
I’ve send you a class diagram that should explain better what I mean.

]]>