[Chandler-dev] Proposal/Call for volunteers/Brain dump: Showing reminders when Chandler isn't running

[Grant Baillie]

On 5 Jul, 2006, at 22:07, Mike Taylor wrote:

> If the reminder/event information is dumped to a flat file then any  
> low-impact program could sit in the task-tray/status-bar of each OS  
> and run thru a check-for-file, check-for-reminder-hit, go-to-sleep  
> cycle every minute.
>
> The actual notification process could be tailored for each OS:  
> Growl for OS X, pop-up dialog for Windows, etc
>
> The program could even check to see if chandler is running and if  
> so open a simple connection to give more value-added services.
>
> As for how to start the program, each OS provides an area that if a  
> program is listed it will be started when the user logs into the  
> system.

More specifically, "an area" == ?

- Mac OS X: An entry in ~/Library/Preferences/loginwindow.plist

- Windows: A "startup items" folder/registry entry?

- Linux: ?

--Grant


> On Jul 5, 2006, at 9:08 PM, Grant Baillie wrote:
>
>> One commonly found Calendar feature that we'd like to implement is  
>> the ability to have reminder dialogs for events be displayed even  
>> when the Chandler GUI isn't visible (see https:// 
>> bugzilla.osafoundation.org/show_bug.cgi?id=5407).
>>
>> Presumably, this would be something users could turn on and off,  
>> lest we be accused of propagating some kind of CPU-hogging  
>> virus :). It's unlikely we'll have time to do this in the α4 time  
>> frame, but I'd like to request comments and/or propose some ideas  
>> for how we could get this done.
>>
>> Also, since I'm somewhat of a Mac guy, and solving the issue will  
>> probably require different behaviours on Windows & Linux, it would  
>> be good to enlist the help of people who know the other platforms  
>> well. For instance, there may be OS-specific services that I'm not  
>> aware of that could be helpful here. The main technical stumbling  
>> block that I see is one that probably has a platform-specific answer:
>>
>> +++ How do we make sure that some kind of background process or  
>> app runs whenever the user is logged in?
>> ...