I think Yarko makes excellent points. I too am looking for the natural way to express components in Web2py and the code proposed by Massimo originally did not look general enough. The better job we do at abstracting this and generalizing it, the more capable the web2py platform will be.
One of the most interesting approches I have seen is "Seaside" -- the Smalltalk web app engine. Seaside relies on "continuations" in Smalltalk to keep state while the user interacts with different applets on a page. It is unclear to me if continuations are needed to make this work, or just an easier way to accomplish it. For one thing, it lets the developer keep objects in his state without needing to render them as strings and pass them through request and response vars. (I think.) Here is a description of Seaside. It did "ajax" before AJAX was invented. http://scg.unibe.ch/archive/papers/Duca04eSeaside.pdf As a postscript -- I'm not sure Python supports continuations in its native form. It is one of the features added in Stackless Python, however. It would be interesting to see Stackless with its tasklets put to use in a Pythonic one-upmanship of Seaside's concepts. Joe Barnhart P.S. Python and Smalltalk are very analogous languages. Other than syntax, it's almost like they were identical twins separated at birth... On Apr 3, 8:51 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > On Fri, Apr 3, 2009 at 10:33 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > Yarko most systems just use iframes. You can put anything you want > > into an iframe. > > I'm not sure that's so, but regardless I think that misses the point (iframe > is a dtd type, and can be the target of links on a page and so forth; > my.msn.com does not use any iframes anywhere, nor did dotnetnuke - although > an iframe type was one of the container types, as I recall). The point is > to have a surrounding structure to accomplish what you are trying to do in > controller code. I think doing what you're doing in controller is fine if > someone wants a quick solution to something they have to do "right now", but > I have issue that it's not sufficiently general nor appropriately decoupled > for more general use). Further, if the right structure were in place to do > this other ways, there would be no need to do it this way, and I think other > ways are better (and there is already evidence of others doing.... as I > pointed out). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
