This project has moved and is read-only. For the latest updates, please go here.

Re-Organize HydroDesktop.Data?

Sep 9, 2010 at 9:23 PM

In previous discussion a re-organization of the code in HydroDesktop.Data has been suggested. The namespace names should correspond to the subfolder names. I suggest the following re-structuring of the namespaces:

HydroDesktop.Data (top-level namespace)

  • HydroDesktop.Data.ObjectModel
  • HydroDesktop.Data.Plugins
  • HydroDesktop.Data.ImportExport
  • HydroDesktop.Data.WebServices
  • HydroDesktop.Data.SQL
  • HydroDesktop.Data.NHibernate
  • HydroDesktop.Data.NHibernate.Mapping
  • HydroDesktop.Data.Configuration
  • HydroDesktop.Data.Themes 

I'd appreciate any comment, if this re-organization is more logical for the plugin developers using HydroDesktop.Data.dll.

Sep 9, 2010 at 10:15 PM

Almost all of this looks good to me.  When I think of data, I think of the database.  It seems like all of these are directly related except perhaps Plugins and WebServices.  However, these are also somewhat related because, for example, we map items such as series from web services directly into database constructs.  So, from a high level, my suggestion is to have

  • HydroDesktop.Plugins
  • HydroDesktop.WebServices

But those who are more familiar with the code in those namespaces can decide whether or not those two items can really be separated from the database stuff.

Sep 10, 2010 at 4:46 PM

What are the existing namespaces, and what are the exsting dependenices.

We if it's isolated to and main, then no problem

if plug-ins are dependent on the namepsaces, then reorganize the directories to


make the solution namespace Hydrodesktop. That is what it has really become

- add folders for the namespace

- Data

- database

- configuration

- HydroPlugIn (with the interfaces

- HydroPlugIn/Impl (code implementing Hydroplugin)