on 5/30/01 3:41 PM, "Sky Torch" <[EMAIL PROTECTED]> wrote:
>
>> Abstraction of the Modules is important because it gives you full control
>> over the look and feel of your web application.
>
> i don't get that. in this approach, you have to cut you web page
> into modules. beside management overhead and some re-usability, i don't see
> other benefits over using one template for the page.
Uh...how about having a standard header/footer for all pages. Seems like a
pretty simple request doesn't it? How are you going to solve that problem
with one template for the page? Let me guess, you are going to copy/paste
the same header footer into every page or use a #include? Talk about
backwards...lets try to be a bit more innovative than that.
Also, there is nothing in Turbine that forces you to use the Module
approach. You can implement things however you want. That is part of the
beauty of Turbine. We come up with a set of recommended ways of doing things
and if you don't like it, you can implement something differently.
> agree. this is exactly what i modeled in "surbine" system which you don't
> think necessary writing.
When did I say that? You can go implement whatever the heck you want to
implement.
p.s. It is very difficult to read what you write. Please try a little harder
to use proper English.
p.p.s. I don't have any more time to explain this stuff to you and
constantly answer your basic questions that you could figure out on your
own. I also don't appreciate you putting words into my mouth. If you think
Turbine doesn't solve your needs you are welcome to go find or create
something else that does.
Good luck.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
