OK, so what's the entry point for your homepage? A controller with an
index method? Or a view?
On Feb 21, 12:02 pm, Baz <[EMAIL PROTECTED]> wrote:
> I usaully have a a different layout for my home page which consists of
> various "elements" and the elements call "requestAction"
>
> As Sam said, there's some docs out there about that and problems with
> efficiency. However, CakePHP has some beautiful caching which makes this
> livable....
>
> On Thu, Feb 21, 2008 at 10:46 AM, jim starboard <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > Sorry about getting off on the wrong foot.
>
> > I think my main question is: Should I create a controller for my
> > homepage? My homepage is not really specific to a single model, so it
> > would not be named as such. So is it OK to have something like
> > HomeController, with an index method? In general do you create
> > controllers that only have an index method?
>
> > All the tutorials have very tight relationships between a single
> > table, controller, view and model, I wish there were more examples of
> > multiple models being used, as well as controllers that were not tied
> > to as single model/table.
>
> > On Feb 20, 4:36 pm, "DJ Spark" <[EMAIL PROTECTED]> wrote:
> > > Your controller will get all the info you need from models, and
> > > using $this->set('varname', $yourinfo) will make it available for the
> > > view, where you make a loop (prabably) and show your information
> > > The basic blog example inhttp://manual.cakephp.orgwillshow it in
> > > a very easy way. just try it.
>
> > > Spark
>
> > > On Wed, Feb 20, 2008 at 5:43 PM, jim starboard <[EMAIL PROTECTED]>
> > wrote:
>
> > > > I'm trying to get a high-level understanding of how you would handle
> > a
> > > > site's homepage. Lets say it's a gaming site. Some of the items on
> > the
> > > > homepage would be:
>
> > > > -userlog in -- would show logged in state, if the user was logged in.
> > > > -highscores -- would show high scores in different games
> > > > - featured game -- admin tools select which game is featured.
>
> > > > I understand the basic MVC idea, and I can create models and
> > > > controllers for each of my *single* items, like user, game, etc.
> > Where
> > > > I get confused is how I combine information in a view. Is the
> > homepage
> > > > a single view or multiple views combined? Do I need a controller for
> > a
> > > > page like index? Basically looking for any help here, with a high
> > > > level explanation.
>
> > > > TIA
> > > > Jim
>
> > > --
> > > [livesets]http://djspark.com.br/
> > > [web]http://sydi.net
> > > [filmes]http://melhoresfilmes.com.br
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
