[horde] Alarms in Portal view

Jan Schneider jan at horde.org
Wed Nov 7 12:47:19 UTC 2007


Zitat von Bill Graham <grahamcw at hurleybulldogs.com>:

> I have modified the message area on the portal screen to use  
> xmlhttpd  when the portal is in that mode. It works fine and by  
> activating   turba summary to be a xmlhttpd block - I can sit on the  
> portal page -  have alarms fire correctly and then watch the turba  
> items roll off the  schedule as their times expire. This was my  
> objective - but I am

Great, though I guess you mean Kronolith, not Turba.

> not  having any luck getting imp to fire sounds or to invoke the  
> popup  message. Does imp use a different message mechanism ? I am  
> pulling  messages and sounds using this.

Yes, IMP is using the notification API directly IIRC, while Kronolith  
uses the Alarm API.

> $html = $GLOBALS['notification']->notify(array('listeners' => 'status'));
> if (isset($GLOBALS['notification'])) $html .=   
> $GLOBALS['notification']->notify(array('listeners' => array('audio',  
>  'javascript')));
> echo $html;

notify() doesn't return the HTML code necessary for notifications but  
echoes it. You probably need to use something like Util::bufferOutput().

> Any insights would be appreciated.
> I am trying to migrate all the portal blocks to use xmlhttpd when it  
>  is available and justified.
>
> thx
> Bill
> -- 
> Bill Graham
> Systems Administrator
> Hurley Public Schools
> Hurley,SD 57036
> USA
> http://www.hurleybulldogs.com
> grahamcw at hurleybulldogs.com
>
>
>
> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Bill Graham <grahamcw at hurleybulldogs.com>:
>>
>>> My observation is that the alarm trigger only goes off then the
>>> entire  portal page is refreshed -
>>> there is no portal block that that causes the alarm to sound or popup -
>>> so - the result is the alarms won't notify the user if sits on their
>>> portal page with an xmlhttpd capable browser.
>>
>> Correct.
>>
>>> Most of my users want to use their Horde world via their portal page.
>>> Either the calendar portal block will have to handle the alarms for
>>> calendar events or the whole page has to refresh -
>>
>> Neither. If we have an xmlhttprpc capable browser, we should use this
>> feature to show alarms.
>> A patch would be great.
>>
>>> I am not trying to make a fuss -
>>> But my users are not going to understand why they can sit on the
>>> portal and get alarms.
>>>
>>> I was thinking the alarm code might better go into the left menu -
>>> since it refreshes regularly. But then - it they turn that off -
>>> same  problem.
>>
>> Calendar alarms are already displayed in the left menu.
>>
>>> I think a xmlhttpd alarm block that is always present on the portal
>>> page may be necessary.
>>
>> Not necessarily a dedicated block. It would sit there most of the time
>> doing nothing and wasting space.
>>
>>> Quoting Jan Schneider <jan at horde.org>:
>>>
>>>> Zitat von Bill Graham <grahamcw at hurleybulldogs.com>:
>>>>
>>>>> Using last nights snapshot 10/23/07 - php 5.2.4
>>>>>
>>>>> I am seeing strange behavior using kronolith alarms in portal view.
>>>>> It appears that the alarms will not "fire" - no sounds or alerts
>>>>> occur in normal pportal view. If I am in imp - the alarms will fire.
>>>>> What I surmized is that the alarm notification was tied to the
>>>>> portal frame refresh - and this was not being done - only the
>>>>> xmlhttpd refreshes were occuring in portal view.
>>>>> In horde/services/portal/index.php
>>>>> a decision is made if the browser supports xmlhttpdreq - and if it
>>>>> does - then do not refresh the portal frame.
>>>>>
>>>>> // Get refresh interval.
>>>>> if (($r_time = $prefs->getValue('summary_refresh_time'))
>>>>> && !$browser->hasFeature('xmlhttpreq')) {
>>>>> $refresh_time = $r_time;
>>>>> $refresh_url = Horde::applicationUrl('services/portal/');
>>>>> }
>>>>>
>>>>> By removing the not condition on the xmlhttpreq test -
>>>>> ie6/ie7/firefox all start refreshing the portal frame and the alarms
>>>>> fire.
>>>>>
>>>>> As an adjunct to this xmlhttpdreq test - other portal objects that
>>>>> depend on full frame updates do not get updated.
>>>>>
>>>>> I couldn't find anything in bugs on this -
>>>>> Any assistance or insights would be appreciated.
>>>>
>>>> It's not a bug. The idea is that only blocks that make sense being
>>>> refreshed are actually refreshed. And each block can specify its own
>>>> refresh interval.
>>
>> Jan.
>>
>> --
>> Do you need professional PHP or Horde consulting?
>> http://horde.org/consulting/
>>
>> --
>> Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>



Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/



More information about the horde mailing list