I'm drafting a small essay about why I don't like XMLC (vs. WebMacro) for
Jason Hunter in a few minutes (I will CC the list, but I expect any
discussion to not go on the list because it is way offtopic). I'm going over
the Enhydra website and I just noticed that XMLC has been factored out of
the Enhydra framework into it's own standalone package. This is a good thing
because now we can go about integrating it into Turbine if anyone feels the
strong need to have it.
<http://xmlc.enhydra.org/>
Also, this is an excellent overview of MVC design:
<http://xmlc.enhydra.org/community/workingGroups/rocks_docs/rocks_presentati
on_framework.pdf>
It goes a bit to much into the theoretical than I like, but I guess that is
cause I never liked school that much. Regardless, it draws some pretty
pictures for people to get their head wrapped around.
One thing that I like about Turbine is that the Action modules essentially
are controllers and well defined in the framework as such. Most other
frameworks that I have seen do not have that abstraction and I really
appreciate that about Turbine. Thought has been put into not only dealing
with serving pages, but also dealing with accepting input (ie: <form
method=post>). Other web app frameworks tend to forget about that or
consider it secondary. :-(
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
