What Comes After MVC

Re:What Comes After MVC by colinramsay on Monday May 25, 2015 @02:29PM (#9601099)

I did some research into MVC a few months ago for a book [1] and my understanding is that this is how it worked when the concept was first devised in those first few Smalltalk releases: something like a textbox would still have the M and the V and the C. React just feels like a simplified version of that to me.

https://www.packtpub.com/web-development/ext-js-application-...

[ Parent | on HN ]

Re:What Comes After MVC by derefr on Wednesday May 27, 2015 @11:56AM (#9612246)

Seaside (http://www.seaside.st/), the Smalltalk web-application framework, does exactly what you're talking about—each component on the page has its own server-side view-controller, much like if you were using a controls library in a native GUI app.

One should also note that Seaside is likely the direct inspiration for Arc's (i.e. HN's) use of links that reference stored server-side closures by ID.

[ Parent | on HN ]

Re:What Comes After MVC by muraiki on Wednesday May 27, 2015 @08:45PM (#9615414)

The free Seaside book and also the free Pharo by Example book are great ways to learn MVC. The only downside is that after using Seaside and a Smalltalk environment, you will probably be dissatisfied with not having such awesome features available in modern tools. :)

Edit: It looks like there is a new Pharo book that covers more advanced topics! http://deepintopharo.com/

[ Parent | on HN ]