using Pithos.Client.WPF.Properties;
using Pithos.Client.WPF.SelectiveSynch;
using Pithos.Client.WPF.Services;
++using Pithos.Client.WPF.Shell;
using Pithos.Core;
using Pithos.Interfaces;
using System;
private IStatusChecker _statusChecker;
private IEventAggregator _events;
-
- public PithosSettings Settings { get; private set; }
-
- public IScreen Parent { get; set; }
+ public PithosSettings Settings { get; private set; }
-
+
private Dictionary<string, PithosMonitor> _monitors = new Dictionary<string, PithosMonitor>();
+ ///<summary>
+ /// Dictionary of account monitors, keyed by account
+ ///</summary>
+ ///<remarks>
+ /// One monitor class is created for each account. The Shell needs access to the monitors to execute start/stop/pause commands,
+ /// retrieve account and boject info
+ ///</remarks>
+ // TODO: Does the Shell REALLY need access to the monitors? Could we achieve the same results with a better design?
+ // TODO: The monitors should be internal to Pithos.Core, even though exposing them makes coding of the Object and Container windows easier
public Dictionary<string, PithosMonitor> Monitors
{
get { return _monitors; }
}
++ public void AboutPithos()
++ {
++ var about = new AboutView();
++ _windowManager.ShowWindow(about);
++ }
++
++ public void SendFeedback()
++ {
++ var feedBack = new FeedbackView();
++ _windowManager.ShowWindow(feedBack);
++ }
- public PithosCommand OpenPithosFolderCommand { get; private set; }
+ //public PithosCommand OpenPithosFolderCommand { get; private set; }
public void OpenPithosFolder()
{