Re: [Phpgroupware-developers] Autorefresh feature in Mail app

[Dan Kuykendall (Seek3r)]

Why does this need to go into the header.inc.php?
I would think this could be an option for the users preferences. This
way each user can decide if they want to be bothered with having the
page auto-refresh on them.

Seek3r

Tony (Angles) Puglisi wrote:
> 
> I coded this a while ago but it seemed to incite controversy.
> 
> I experimented with various refresh methods and decided on one that would not
> re-request the images, i.e. it used the browser's cached images. Note that 
> some
> refresh methods will ask for the images all over again, not accepting the 
> cached files.
> 
> Then, I had the mail email page (email/index.php) autorefresh, then someone
> suggested it would be better to have the user's "welcome" page (home.php)
> autorefresh, since this page also may have calendar, weather, etc. portals on 
> it.
> 
> Then I was told there was a notify window to accomplish the email checking 
> (which
> works fine) and in the future the calendar notifies as well, so that 
> autorefreshing
> any page was unnecessary.
> 
> In the end, I decided to use the notify window, and I archived the code and 
> never
> committed it, although it worked great on my personal install when it was 
> there.
> 
> If there is demand, I can simply un-archive the code and commit. Note that it
> involves the header.inc.php (? hard to remember) file, and the autorefresh is
> conditional upon it being the "welcome page" home.php or the email/index.php 
> page.
> 
> You say the word, it's in.