Re: Annoucement. PureMVC4GWT RC is available
Hello Thomas, you right. Regards On 25 sep, 14:29, Thomas Broyer [EMAIL PROTECTED] wrote: On 25 sep, 00:12, marcelo melo [EMAIL PROTECTED] wrote: While I understand that it must be done because GWT does not let one use reflection, I think that a small change could remove the necessity of such Provider. If, at the Controller and MacroCommand classes, instead of receiving references to Class? extends ICommand , the parameter becomes an instance of ICommand, and when invoking the registerCommand or subCommand we pass a new Instance of the desired Command, it could be achieved. The only difference I see is that there would be always the same reference to the Commands, instead of creating a new instance each time. I don't know if that would be a problem. If you follow the principles of PureMVC that a command must be state-less, then it won't be a problem, but it allows you to write stateful commands, whereas the pattern used in PureMVC prevents this with throwaway instances. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
On 25 sep, 00:12, marcelo melo [EMAIL PROTECTED] wrote: While I understand that it must be done because GWT does not let one use reflection, I think that a small change could remove the necessity of such Provider. If, at the Controller and MacroCommand classes, instead of receiving references to Class? extends ICommand , the parameter becomes an instance of ICommand, and when invoking the registerCommand or subCommand we pass a new Instance of the desired Command, it could be achieved. The only difference I see is that there would be always the same reference to the Commands, instead of creating a new instance each time. I don't know if that would be a problem. If you follow the principles of PureMVC that a command must be state-less, then it won't be a problem, but it allows you to write stateful commands, whereas the pattern used in PureMVC prevents this with throwaway instances. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hi, This is the solution we use in pureMvc MultiCore Edition. But Cliff is not satisfied with it. He doesn't want that users can manage the life cicle of a command. We search a solution on the generator side. Thanks for your interest. Matthieu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
I'm agree with you, the pureMvc MultiCore edition use instance instead of factory. The probleme is to allow people to write non State-less command. All the principles will not guarantee that it will not happen. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hi Srini, Here you have a simple sample http://code.google.com/p/purevmc4gwt/downloads/list Login Sample HTH On 25 sep, 16:42, Srini Marreddy [EMAIL PROTECTED] wrote: Hi Luciano, It is good to know that we have a Framework for GWT. I am not familiar with Pure MVC framework,but I would like to play with it. A simple hello world example on how to use the framework will be very helpful for those interested in trying this framework. Best Regards, Srini On Sep 17, 5:34 am, Luciano Broussal [EMAIL PROTECTED] wrote: Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. This offer an opportunity to have the same design patterns what ever you code in Java, .Net, Pythom, PHP ... Find all necessary documention on PureMVC on the offcial sitehttp://puremvc.org/ PureMVC4GWT is hosted on Google Code at http://code.google.com/p/purevmc4gwt/ Feel free to try it and join me to help me to leverage it. Regards. Luciano Broussal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
I see there is a LoginDemo sample in the project home page downloads section. I will play with it and send my feedback. Best, Srini On Sep 25, 9:42 am, Srini Marreddy [EMAIL PROTECTED] wrote: Hi Luciano, It is good to know that we have a Framework for GWT. I am not familiar with Pure MVC framework,but I would like to play with it. A simple hello world example on how to use the framework will be very helpful for those interested in trying this framework. Best Regards, Srini On Sep 17, 5:34 am, Luciano Broussal [EMAIL PROTECTED] wrote: Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. This offer an opportunity to have the same design patterns what ever you code in Java, .Net, Pythom, PHP ... Find all necessary documention on PureMVC on the offcial sitehttp://puremvc.org/ PureMVC4GWT is hosted on Google Code at http://code.google.com/p/purevmc4gwt/ Feel free to try it and join me to help me to leverage it. Regards. Luciano Broussal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hi, I've been working on a project with PureMVC for Flex for some time and I really like it. When looking at the example I've noticed a small difference from the GWT implementation, that is the necessity of creating a Provider for executing the Commands. While I understand that it must be done because GWT does not let one use reflection, I think that a small change could remove the necessity of such Provider. If, at the Controller and MacroCommand classes, instead of receiving references to Class? extends ICommand , the parameter becomes an instance of ICommand, and when invoking the registerCommand or subCommand we pass a new Instance of the desired Command, it could be achieved. The only difference I see is that there would be always the same reference to the Commands, instead of creating a new instance each time. I don't know if that would be a problem. I have the modified code, and it runs fine with the login example, and I could send it to you (Luciano). By the way, are you brazilian? Thanks On Sat, Sep 20, 2008 at 5:44 PM, Luciano Broussal [EMAIL PROTECTED] wrote: Thomas, Thanks for your interesting point of view. Feel free to checkout the project and you can help me to get it better. Currently is a port of the java version of PureMVC but i didn't want to change it to not loose people who already know and use PureMVC with other languages. Regards. On 20 sep, 21:31, Thomas Broyer [EMAIL PROTECTED] wrote: Hi Luciano, On 19 sep, 19:27, Luciano Broussal [EMAIL PROTECTED] wrote: Here is the documentationhttp://puremvc.org/component/option,com_wrapper/Itemid,174/. It is available on the PureMVC Home page. Thanks (so it was the thing called best practices ;-) ) Maybe you don't like but i'm not sure you can do more simple than the 15 classes which compose PureMvc and help the developper to separate layers and the main design patterns it use : Proxy Facade. Medialor Commands View Controller Don't get me wrong, I didn't say I dislike PureMVC or its approach, quite the contrary actually! Two things though: - I'm not a fan of frameworks, I prefer libraries/toolkits and a set of patterns - given that the PureMVC framework preferred usage is through the patterns (Façade, Proxy, Mediator, Command), why not making it lighter with mostly those classes and a few helper classes? (e.g. Model Controller and View are masked behind Facade, just get rid of the singletons and Anyway, thank you for had a look to the project. Some thoughts: - PureMVC best practices, page 28, reads: Because of its readability, and the ease of which one may refactor to add or remove Notifications handled, the 'switch / case' construct is preferred over the 'if / else if' expression style inside the handleNotifications method. Given that you cannot do switch/case on strings in Java, I'd replace the Notification names with integer identifiers. An Enum could be used but that would mean making the classes generics: FacadeE extends Enum, etc. (to be implemented as ApplicationFacade extends FacadeApplicationConstants). - AFAIK, a Flex application must inherit mx.core.Application, so it can't inherit Facade at the same time; hence the dichotomy; but in GWT we implement EntryPoint, so the Facade could be the EntryPoint, with appropriate abstract methods to avoid the need for explicitly calling a startup method. This might lead to bad uses of the framework though, where the façade would have direct access to - I haven't yet read the best practices 'til the end but couldn't a Mediator be a Composite? - I'm concerned that there's no notion of relevant mediators at a given time (e.g. in a tabbed app, the components outside the active tab are irrelevant, so handling of notifications could just be mark as dirty and when the components become relevant again, they can re- build or update their UI subcomponents); or should it be handled on the visual component side and have the mediator handle notifications independently of this relevant/irrelevant state) The EntryPoint as Facade and Mediator as Composite would drastically reduce the sample's code... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hi Luciano, On 19 sep, 19:27, Luciano Broussal [EMAIL PROTECTED] wrote: Here is the documentationhttp://puremvc.org/component/option,com_wrapper/Itemid,174/. It is available on the PureMVC Home page. Thanks (so it was the thing called best practices ;-) ) Maybe you don't like but i'm not sure you can do more simple than the 15 classes which compose PureMvc and help the developper to separate layers and the main design patterns it use : Proxy Facade. Medialor Commands View Controller Don't get me wrong, I didn't say I dislike PureMVC or its approach, quite the contrary actually! Two things though: - I'm not a fan of frameworks, I prefer libraries/toolkits and a set of patterns - given that the PureMVC framework preferred usage is through the patterns (Façade, Proxy, Mediator, Command), why not making it lighter with mostly those classes and a few helper classes? (e.g. Model Controller and View are masked behind Facade, just get rid of the singletons and Anyway, thank you for had a look to the project. Some thoughts: - PureMVC best practices, page 28, reads: Because of its readability, and the ease of which one may refactor to add or remove Notifications handled, the ‘switch / case’ construct is preferred over the ‘if / else if’ expression style inside the handleNotifications method. Given that you cannot do switch/case on strings in Java, I'd replace the Notification names with integer identifiers. An Enum could be used but that would mean making the classes generics: FacadeE extends Enum, etc. (to be implemented as ApplicationFacade extends FacadeApplicationConstants). - AFAIK, a Flex application must inherit mx.core.Application, so it can't inherit Facade at the same time; hence the dichotomy; but in GWT we implement EntryPoint, so the Facade could be the EntryPoint, with appropriate abstract methods to avoid the need for explicitly calling a startup method. This might lead to bad uses of the framework though, where the façade would have direct access to - I haven't yet read the best practices 'til the end but couldn't a Mediator be a Composite? - I'm concerned that there's no notion of relevant mediators at a given time (e.g. in a tabbed app, the components outside the active tab are irrelevant, so handling of notifications could just be mark as dirty and when the components become relevant again, they can re- build or update their UI subcomponents); or should it be handled on the visual component side and have the mediator handle notifications independently of this relevant/irrelevant state) The EntryPoint as Facade and Mediator as Composite would drastically reduce the sample's code... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Thomas, Thanks for your interesting point of view. Feel free to checkout the project and you can help me to get it better. Currently is a port of the java version of PureMVC but i didn't want to change it to not loose people who already know and use PureMVC with other languages. Regards. On 20 sep, 21:31, Thomas Broyer [EMAIL PROTECTED] wrote: Hi Luciano, On 19 sep, 19:27, Luciano Broussal [EMAIL PROTECTED] wrote: Here is the documentationhttp://puremvc.org/component/option,com_wrapper/Itemid,174/. It is available on the PureMVC Home page. Thanks (so it was the thing called best practices ;-) ) Maybe you don't like but i'm not sure you can do more simple than the 15 classes which compose PureMvc and help the developper to separate layers and the main design patterns it use : Proxy Facade. Medialor Commands View Controller Don't get me wrong, I didn't say I dislike PureMVC or its approach, quite the contrary actually! Two things though: - I'm not a fan of frameworks, I prefer libraries/toolkits and a set of patterns - given that the PureMVC framework preferred usage is through the patterns (Façade, Proxy, Mediator, Command), why not making it lighter with mostly those classes and a few helper classes? (e.g. Model Controller and View are masked behind Facade, just get rid of the singletons and Anyway, thank you for had a look to the project. Some thoughts: - PureMVC best practices, page 28, reads: Because of its readability, and the ease of which one may refactor to add or remove Notifications handled, the ‘switch / case’ construct is preferred over the ‘if / else if’ expression style inside the handleNotifications method. Given that you cannot do switch/case on strings in Java, I'd replace the Notification names with integer identifiers. An Enum could be used but that would mean making the classes generics: FacadeE extends Enum, etc. (to be implemented as ApplicationFacade extends FacadeApplicationConstants). - AFAIK, a Flex application must inherit mx.core.Application, so it can't inherit Facade at the same time; hence the dichotomy; but in GWT we implement EntryPoint, so the Facade could be the EntryPoint, with appropriate abstract methods to avoid the need for explicitly calling a startup method. This might lead to bad uses of the framework though, where the façade would have direct access to - I haven't yet read the best practices 'til the end but couldn't a Mediator be a Composite? - I'm concerned that there's no notion of relevant mediators at a given time (e.g. in a tabbed app, the components outside the active tab are irrelevant, so handling of notifications could just be mark as dirty and when the components become relevant again, they can re- build or update their UI subcomponents); or should it be handled on the visual component side and have the mediator handle notifications independently of this relevant/irrelevant state) The EntryPoint as Facade and Mediator as Composite would drastically reduce the sample's code... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
On 17 sep, 12:34, Luciano Broussal [EMAIL PROTECTED] wrote: Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. I didn't know PureMVC, and I'm not very familiar with MVC either (well, I know the basics but I'm far from being used to MVC), but after throwing an eye at the puremvc overview docs and at your code (loginsample and then some of the framework's classes), it seems like I was having a similar idea for the next big rewrite of our GWT app: mainly having a single object to publish/subscribe to (Facade). However, I was rather thinking about using integers (or maybe a big Enum, not the best choice as far as SoC is concerned, but easier to maintain in order to prevent conflicts) rather than strings to identify notifications (allows switch/case in Java and probably leads to faster code than String comparisons; as was done with com.google.gwt.user.client.Event's constants). All in all, PureMVC seems a little bit over-engineered, bringing too much overhead to the constrained environment that a web browser is... Looks like a good and clean pattern, but I'd rather build my own specific implementation from a template project than use this generic impl... (for example: why having a Notification class and INotification interface if you don't ever subclass/implement them? why not just have onHandleNotification(String name, Object body, String type) methods all over the place?) Actually, I didn't spend much more than half an our reading PureMVC docs and your code, so I probably missed a lot of things (btw, where's the userguide you talked about? I couldn't find it on puremvc.org, or is what's called best practices?) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hi, Here is the documentation http://puremvc.org/component/option,com_wrapper/Itemid,174/. It is available on the PureMVC Home page. Maybe you don't like but i'm not sure you can do more simple than the 15 classes which compose PureMvc and help the developper to separate layers and the main design patterns it use : Proxy Facade. Medialor Commands View Controller Anyway, thank you for had a look to the project. Regards FYI a little hello would have been welcome at the beginning of your post ;) Luciano On 19 sep, 12:11, Thomas Broyer [EMAIL PROTECTED] wrote: On 17 sep, 12:34, Luciano Broussal [EMAIL PROTECTED] wrote: Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. I didn't know PureMVC, and I'm not very familiar with MVC either (well, I know the basics but I'm far from being used to MVC), but after throwing an eye at the puremvc overview docs and at your code (loginsample and then some of the framework's classes), it seems like I was having a similar idea for the next big rewrite of our GWT app: mainly having a single object to publish/subscribe to (Facade). However, I was rather thinking about using integers (or maybe a big Enum, not the best choice as far as SoC is concerned, but easier to maintain in order to prevent conflicts) rather than strings to identify notifications (allows switch/case in Java and probably leads to faster code than String comparisons; as was done with com.google.gwt.user.client.Event's constants). All in all, PureMVC seems a little bit over-engineered, bringing too much overhead to the constrained environment that a web browser is... Looks like a good and clean pattern, but I'd rather build my own specific implementation from a template project than use this generic impl... (for example: why having a Notification class and INotification interface if you don't ever subclass/implement them? why not just have onHandleNotification(String name, Object body, String type) methods all over the place?) Actually, I didn't spend much more than half an our reading PureMVC docs and your code, so I probably missed a lot of things (btw, where's the userguide you talked about? I couldn't find it on puremvc.org, or is what's called best practices?) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hope this help eggsy84. PureMVC userguide is very well documented i think and explain also so obvious design errors. Thanks. Luciano On 17 sep, 16:27, eggsy84 [EMAIL PROTECTED] wrote: Hi there I have never encountered PureMVC but have been developing using GWT for around 10 months now. We have come up with various methods of attempting to implement the MVC approach through GWT none of which we have been that happy with to be honest. I'll read up on PureMVC and how it works first then it looks like your implementation should be very useful! Thank you for bringing this to my attention if I understand the concept I would definately be interested in helping the development of puremvc4gwt! Eggsy --- On Sep 17, 11:34 am, Luciano Broussal [EMAIL PROTECTED] wrote: Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. This offer an opportunity to have the same design patterns what ever you code in Java, .Net, Pythom, PHP ... Find all necessary documention on PureMVC on the offcial sitehttp://puremvc.org/ PureMVC4GWT is hosted on Google Code at http://code.google.com/p/purevmc4gwt/ Feel free to try it and join me to help me to leverage it. Regards. Luciano Broussal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Annoucement. PureMVC4GWT RC is available
Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. This offer an opportunity to have the same design patterns what ever you code in Java, .Net, Pythom, PHP ... Find all necessary documention on PureMVC on the offcial site http://puremvc.org/ PureMVC4GWT is hosted on Google Code at http://code.google.com/p/purevmc4gwt/ Feel free to try it and join me to help me to leverage it. Regards. Luciano Broussal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoucement. PureMVC4GWT RC is available
Hi there I have never encountered PureMVC but have been developing using GWT for around 10 months now. We have come up with various methods of attempting to implement the MVC approach through GWT none of which we have been that happy with to be honest. I'll read up on PureMVC and how it works first then it looks like your implementation should be very useful! Thank you for bringing this to my attention if I understand the concept I would definately be interested in helping the development of puremvc4gwt! Eggsy --- On Sep 17, 11:34 am, Luciano Broussal [EMAIL PROTECTED] wrote: Hi All, I've created a tiny but powerful gwt project The Goal is to provide a MVC framework based on the simple, well designed and powerful PureMVC framework. This offer an opportunity to have the same design patterns what ever you code in Java, .Net, Pythom, PHP ... Find all necessary documention on PureMVC on the offcial sitehttp://puremvc.org/ PureMVC4GWT is hosted on Google Code at http://code.google.com/p/purevmc4gwt/ Feel free to try it and join me to help me to leverage it. Regards. Luciano Broussal --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
