Shop OBEX P1 Docs P2 Docs Learn Events
MVC approach to software — Parallax Forums

MVC approach to software

Larry C.Larry C. Posts: 48
edited 2013-04-05 08:43 in Propeller 1
Just finished reading an article about Model-View-Controller (MVC) approach to developing software. It seems this might be a good fit to multi-cores like the Propeller chip. Before I get too far into my next project, I was wondering if anyone has used this architecture for Propeller software and what has been your experience? Worth it, or not?

Thanks,

Larry C.

Comments

  • Mike GreenMike Green Posts: 23,101
    edited 2013-04-05 08:41
    The MVC approach to software was fundamental to object-oriented systems like Smalltalk and benefitted markedly from the tools (objects) available including various database structures. While you could use this approach with the Propeller, it doesn't have the richness of tools to support it. The amount of memory available is a limitation and object pointers are not primitive values (they don't really exist in Spin). You can certainly conceptualize your system in terms of MVC and that provides a useful conceptual paradigm, but only that.
  • Mike GMike G Posts: 2,702
    edited 2013-04-05 08:43
    IMO, any well written multicog Propeller application will be akin to the MVC architecture. For example, you have DAT and VAR block to hold types, There are object to write to a terminal or LCD, and generally COG processes look to HUB memory to listen for events or triggers. But you're not going to get a true MVC app.
Sign In or Register to comment.