Background

• #17 and #18 support configurations by directories, but it forces to put same configuration file to multiple directories if shortcuts in most directories need the same configurations

Acceptance criteria

• Support global-wide (over directories) configurations which will be put into common parent directory of all shortcuts directories

• Name of shortcut can be changed easily on Explorer
• If fllow keeps to launch as alphabetical order of shortcuts' name, user can control launch order by Explorer
  • Name shortcuts like as "00_TaskManager.lnk", "01_Chrome.lnk", "02_Outlook.lnk", ...

• 1 - 1 / num_of_logical_cores seems better default CPU usage threshold than fixed 0.5
  • It can mean "At least 1 logical core ore more are free"

Background

• Organize much shortcuts by user
• Apply specific configurations only to specific shortcuts

Acceptance criteria

• Support multiple directories which include shortcuts
• Configurations file only affect to shortcuts in the same directory

Background

• Enable to configurate
  • CPU usage threshold
  • Timeout duration
• Configurations can be affect to each directory (for future multiple shortcuts directories support)
• Balance of ease for implementations and usability is focus point of configuration format

Acceptance criteria

• Support JSON based configurations file, which includes CPU usage threshold and timeout duration configurations
• It also works as default configurations if there are no configurations

Minimum launch interval seems not enough, log appears only twice.

• Currently, threshold(%) to launch next app is 100 * (num_of_logical_cores - 1) / num_of_locical_cores (%)
• That threshold can be very close to 100% (cores are fully working) on environments which have 8 or more cores
  • 8 cores: 87.5%
  • 16 cores: 93.75%
• It is necessary to reconsider algorithm for threshold which can be support both a few cores and many cores

Class and sequence diagrams by #3 are supposed with multiple context (main event loop, watcher by another context, and timeout will managed by more another context). It may not be suitable for PowerShell, so consider design which has only single context.

• Enumerate shortcuts in a specific directory
• Default CPU usage threshold and timeout

• Pulse of CPU usage can be unstable, so averaging should be necessary
  • But it needs major changes
• But also minimum interval to launch apps should be configurable