[Sugar-devel] M-V-C model for MusicBlocks

[b18050 b18050]

This is very helpful for beginner developers also if we maintain individual
directories for every widget. Different widgets work differently. So, there
must be some differences in them i.e. a change in one of the widget can
affect only that widget. If we want to add any facility to multiple
widgets, it will be just a matter of adding implemented code to that widget
, which can be done
easily.
Please provide any further suggestions .

On Wed, Mar 11, 2020 at 9:03 PM Walter Bender <walter.bender at gmail.com>
wrote:

> Sounds good to me. We should probably make an individual directory for
> each widget with its model and controller js files.
>
> On Wed, Mar 11, 2020 at 11:22 AM b18050 b18050 <
> b18050 at students.iitmandi.ac.in> wrote:
>
>> Hello everyone,
>> This is regarding model - view - controller model of Music Blocks. As
>> suggested by respected mentor , there is a need to separate controller and
>> model of widgets. I think it will be good if for every widget, we can have
>> two files controller.js  and model.js. In model.js , we can store the data
>> and the domain logic. In controller.js , various processes and response to
>> various events and invokes changes on the model and the view.
>>
>>
>>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> <http://www.sugarlabs.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200311/359a20bf/attachment.htm>