Difference between revisions of "WinCalendarTime"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
Line 12: Line 12:
  
 
<pre>%ProgramFiles%\WinCalendarTime\WinCalendarTime.exe</pre>
 
<pre>%ProgramFiles%\WinCalendarTime\WinCalendarTime.exe</pre>
 +
 +
=== Package definition ===
 +
 +
<package
 +
    id="wincalendartime"
 +
    name="WinCalendarTime"
 +
    revision="100"
 +
    reboot="false"
 +
    priority="0">
 +
    <check type="file" condition="exists" path="%ProgramFiles%\WinCalendarTime\WinCalendarTime.exe" />
 +
    <install cmd='%SOFTWARE%\WinCalendarTimeSetup-1.0.exe /sp- /silent /norestart'>
 +
    <exit code="0" />
 +
    </install>
 +
    <remove cmd='"%PROGRAMFILES%\WinCalendarTime\unins000.exe" /Silent'>
 +
        <exit code="0"/>
 +
    </remove>
 +
</package>
  
 
=== Open Questions ===
 
=== Open Questions ===

Revision as of 19:09, 26 April 2007

WinCalendarTime

WinCalendarTime "replaces the standard Windows clock with an enhanced clock, if you click on it a calendar is displayed." (It's like the nice GNOME clock!)

Installer

Apparently, WinCalendarTime uses InnoSetup because the following works.

WinCalendarTimeSetup-1.0.exe /silent

Since this doesn't start the program yet, you should also try

%ProgramFiles%\WinCalendarTime\WinCalendarTime.exe

Package definition

<package

   id="wincalendartime"
   name="WinCalendarTime"
   revision="100"
   reboot="false"
   priority="0">
   <check type="file" condition="exists" path="%ProgramFiles%\WinCalendarTime\WinCalendarTime.exe" />
   <install cmd='%SOFTWARE%\WinCalendarTimeSetup-1.0.exe /sp- /silent /norestart'>
   <exit code="0" />
   </install>
   <remove cmd='"%PROGRAMFILES%\WinCalendarTime\unins000.exe" /Silent'>
       <exit code="0"/>
   </remove>

</package>

Open Questions

Does the above start WinCalendarTime on every login?