1

I have this idea of generating an array of user-links that will depend on user-roles.

The user can be a student or an admin.

What I have in mind is use a foreach loop to generate a list of links that is only available for certain users.

My problem is, I created a helper class called Navigation, but I am so certain that I MUST NOT hard-code the links in there, instead I want that helper class to just read an object sent from somewhere, and then will return the desired navigation array to a page.

Follow up questions, where do you think should i keep the links that will only be available for students, for admins. Should i just keep them in a text-file?

or if it is possible to create a controller that passes an array of links, for example a method in nav_controller class -> studentLinks(){} that will send an array of links to the helper class, the the helper class will then send it to the view..

Sorry if I'm quite crazy at explaining. Do you have any related resources?

Joey Hipolito
  • 3,108
  • 11
  • 44
  • 83

2 Answers2

1

From your description it seems that you are building some education-related system. It would make sense to create implementation in such way, that you can later expand the project. Seems reasonable to expect addition of "lectors" as a role later.

Then again .. I am not sure how extensive your knowledge about MVC design pattern is.

That said, in this situation I would consider two ways to solve this:

  1. View requests current user's status from model layer and, based on the response, requests additional data. Then view uses either admin or user templates and creates the response.

    You can either hardcode the specific navigation items in the templates, from which you build the response, or the lit of available navigation items can be a part of the additional information that you requested from model layer.

    The downside for this method is, that every time you need, when you need to add another group, you will have to rewrite some (if not all) view classes.

  2. Wrap the structures from model layer in a containment object (the basis of implementation available in this post), which would let you restrict, what data is returned.

    When using this approach, the views aways request all the available information from model layer, but some of it will return null, in which case the template would not be applied. To implement this, the list of available navigation items would have to be provided by model layer.

P.S. As you might have noticed from this description, view is not a template and model is not a class.

Community
  • 1
  • 1
tereško
  • 58,060
  • 25
  • 98
  • 150
  • I super like your post in there, and you sure have a deep understanding on mvc. thanks a lot, i think i really need a teacher for this one, coz I think I'm in the wrong path. please guide me. – Joey Hipolito Aug 04 '12 at 03:51
  • I would recommend for you to start with some advanced studies in OOP. Try watching the lectures that were listed in [this post](http://stackoverflow.com/a/9855170/727208). As for MVC itself, you could start by reading [this article](http://r.je/views-are-not-templates.html) and maybe [this post](http://stackoverflow.com/a/5864000/727208). Also consulting with people from [php chat room](http://chat.stackoverflow.com/rooms/11/php). – tereško Aug 04 '12 at 04:02
0

It really depends on what you're already using and the scale of your project. If you're using a db - stick it there. If you're using xml/json/yaml/whatever - store it in a file with corresponding format. If you have neither - hardcode it. What I mean - avoid using multiple technologies to store data. Also, if the links won't be updated frequently and the users won't be able to customize them I'd hardcode them. There's no point in creating something very complex for the sake of dynamics if the app will be mostly static.

Note that this question doesn't quite fit in stackoverflow. programmers.stackexchange.com would probably be a better fit

karka91
  • 733
  • 1
  • 6
  • 20