Comments on: A Proposal for Maemo 6 UI Framework MVC Model http://zchydem.enume.net/2009/11/19/proposal-for-maemo-6-ui-framework-mvc-model/ #Qt, #Linux, #Programming, #MeeGo... Sat, 07 Jan 2012 18:23:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: zchydem http://zchydem.enume.net/2009/11/19/proposal-for-maemo-6-ui-framework-mvc-model/comment-page-1/#comment-15 zchydem Fri, 20 Nov 2009 10:12:12 +0000 http://zchydem.enume.net/?p=195#comment-15 Thanks for the comment dubik. Nice to hear that this review has effected on something. I guess I haven't understood everything behind the Maemo 6 UI Framework's MVC model. Good that you also make things more clear, because I wasn't aware that widget can be just "inside" the controller. My model makes widget creation easier in that sense (in my opinion) that you don't need to have code that is generated in order to make this model work. If model data changes e.g. via style updates you can also make the controller to notify the view that it's time to update visualized data. I don't see any problems with this approach and therefore the model and style headers seem to be bit overengineered in my opinion. This is just my opinion. I believe there is a good rationale behind your design in anyway. Thanks for the comment dubik. Nice to hear that this review has effected on something.

I guess I haven’t understood everything behind the Maemo 6 UI Framework’s MVC model. Good that you also make things more clear, because I wasn’t aware that widget can be just “inside” the controller.

My model makes widget creation easier in that sense (in my opinion) that you don’t need to have code that is generated in order to make this model work. If model data changes e.g. via style updates you can also make the controller to notify the view that it’s time to update visualized data. I don’t see any problems with this approach and therefore the model and style headers seem to be bit overengineered in my opinion.

This is just my opinion. I believe there is a good rationale behind your design in anyway.

]]> By: dubik http://zchydem.enume.net/2009/11/19/proposal-for-maemo-6-ui-framework-mvc-model/comment-page-1/#comment-14 dubik Fri, 20 Nov 2009 06:11:33 +0000 http://zchydem.enume.net/?p=195#comment-14 Thanks for the review. I already saw that people changing their dynamic_cast into qobject_cast! You always can hack whole widget inside controller, since it inherits QGraphicsWidget. I don't think there is a way to make it more simplier. However when you need styling and models it can become a bit verbose. I didn't quite understand, how your proposal makes widget creation easier. I notice that you got rid of model, but thats just one header in Maemo6 UI. Model is quite handy, it's isolated from widget API (easy to change), you get notifications when values has changed, you can save state of widget easily. Thanks for the review. I already saw that people changing their dynamic_cast into qobject_cast!
You always can hack whole widget inside controller, since it inherits QGraphicsWidget. I don’t think there is a way to make it more simplier. However when you need styling and models it can become a bit verbose.
I didn’t quite understand, how your proposal makes widget creation easier. I notice that you got rid of model, but thats just one header in Maemo6 UI. Model is quite handy, it’s isolated from widget API (easy to change), you get notifications when values has changed, you can save state of widget easily.

]]>