Yeah. But none of this is really necessary as long as we can live with
the quote being changed only once per hour. Makes things a lot simpler
:-) (we're doing this already with the surveys, comments, news etc etc)
//Magnus
> -----Original Message-----
>
> The other side of that is, there should be a default one
> incase the user has javascript disabled. Then the javascript
> would replace the innerHTML of the div that contains it with
> a random quote. I can provide code if needed.
>
> Gavin
>
> On Aug 17, 2005, at 7:13 PM, Marc G. Fournier wrote:
>
> > On Wed, 17 Aug 2005, Gavin M. Roy wrote:
> >
> >
> >> Could use javascript to fill an array of quotes and
> randomly pic one.
> >>
> >
> > That works ...
> >
> >>
> >> On Aug 17, 2005, at 12:56 PM, Marc G. Fournier wrote:
> >>
> >>
> >>> Ummm, how are you planning on handling the web servers,
> which are
> >>> all static pages generated by the master site?
> >>> On Wed, 17 Aug 2005, Robert Treat wrote:
> >>>
> >>>> Hey guys,
> >>>> I'm thinking about making the user quotes on the main website
> >>>> database
> >>>> driven . Two goals behind this would be to allow for a page
> >>>> where we could
> >>>> display all user quotes, and also to allow the quotes on the
> >>>> main page to be
> >>>> randomly generated for each site build, making the front page a
> >>>> little less
> >>>> static. The one tricky part seems to be how best to handle
> >>>> translations. I
> >>>> had a thought to make the database table something simple like
> >>>> quote,
> >>>> tagline, & lang, which would be fine for storing the content,
> >>>> however I'm not
> >>>> sure the best way for extracting it. I was thinking the calls
> >>>> to func_lang
> >>>> could be replaced with a get_quote, and then use $_LANGUAGE for
> >>>> system/handler.php as an argument to get the appropriate
> quote.
> >>>> I figure
> >>>> this will also mean we need an addition to the admin
> screens for
> >>>> inputing
> >>>> quotes. Does this sound reasonable?