Comments on: crossing the mvc divide, kohana and zend style

By: dewaldbotha

dewaldbotha — Wed, 01 Jul 2009 06:07:45 +0000

@Aaron You can check for a logged in flag in the view, but now, say you want to add that form to one or more views, you have to copy that code in all relevant views.

So with the above solution, you can have that piece of code in one central place and then just call < ?php echo $this->template->partial = new View(‘log/generateform’);?>, which will allow for easy an easy reusable component that can be used in multiple views.

By: Aaron

Aaron — Tue, 30 Jun 2009 15:07:01 +0000

try that again:

[html]
[head]
[title] [?= $page->title ?] [/title]
[/head]
[body]
[?= $page->heading ?]

[!-- conditionally displayed content --]
[? if ( $user->is_logged_in() ): ?]
Hello, $user->name
[? else: ?]
[form]
username: [input name="username"]
password: [input name="password"]
[/form]
[? endif ?]

[!-- common content --]

[?= $page->footer ?]
[/body]
[/html]

By: Aaron

Aaron — Tue, 30 Jun 2009 15:04:31 +0000

I don’t see why you couldn’t determine if the user is logged in in your controller and then check the flag in your view?

title ?>

heading ?>

is_logged_in() ): ?>
Hello, $user->name

username:
password:

footer ?>

By: dewaldbotha

dewaldbotha — Mon, 26 Jan 2009 12:34:36 +0000

yip – i must admit that i’ve only started reading up on django this morning, but from what i’ve seen so far it seems like a pretty competent framework compared to others such as pylons.

as for the mvc and presentation/action logic issue, i guess i just needed that bit of reassurance -

but alas, for know, i’m looking deep into the chapters of my ‘dive into python’ book

By: Stii

Stii — Mon, 26 Jan 2009 12:00:12 +0000

Rails are heavy action driven (i.e. the view dictates the presentation logic, AFAIK), so it is quite different from Kohana/Django in that respect. Yet Rails are the acme of mvc frameworks in many people’s eye! I think the issue are not being pressed since it is not really that big a deal. As long as the basic principles are being followed, its okay.

Keep in mind that Django is considered an MVT (Model-View-Template) framework and not MVC, which does make it different.

By: dewaldbotha

dewaldbotha — Sun, 25 Jan 2009 18:10:42 +0000

thanks for the syntax check and feedback – (i’ll blame it on the wordpress devils) –

i agree with your point of keeping within a framework – especially if you have to make changes to some core functions for it to work for you – then you are most probably using it wrong.

i’m just contemplating the fact that i’ve never really found too much write-up on the whole issue of using the view in a framework to decide on the actual presentation logic, and i must say i quite agree with the django approach of not setting variables within a template, since it kind of defies the point of mvc -

but who knows, maybe i’ll start a whole drive and convice people otherwise in the whole action/view debacle of january 2009

By: Stii

Stii — Sun, 25 Jan 2009 17:30:58 +0000

Personally, I’m not one to get all anal about so called principals. IMHO, that’s okay! I cannot see it overstepping mvc principals in principal.

On a different note, a framework like Django don’t even allow you to set variables in templates, never mind calling actions in templates! See: http://code.djangoproject.com/ticket/1322 where someone requested a feature to set variables in a template. It was outright closed with a “won’t fix” reason. Yet, I consider Django one of the best frameworks around.

The important factor is that you can get it to work for you within the boundaries of the framework. As soon as you need to make changes to the core of the framework (i.e. the source maintained by the community) it hampers future upgrades and defeats the purpose of using a framework of any kind (i.e. have a community of developers maintain some of the code of your project).

$dispatch->method(generateForm’); You forgot an ‘ before generateForm. (me being anal )