1

Closed

Refactor Domain namespace

description

Concepts from the Domain namespace should be place in right namespace (Model, View or ViewModel)
  • the BindSupport class is rather a ViewModel type class
  • the EntriesProviderType class is more of a model
  • the FilterParams class is more a model
Closed Apr 30, 2013 at 10:22 PM by dirkster

comments

dirkster wrote Apr 24, 2013 at 4:24 PM

I moved the BindSupport class but I'd like to leave the other two classes where they are right now (on second thought).

Therefore, this resolved on master as of:

https://yalvlib.codeplex.com/SourceControl/changeset/7f61b5fc9adda3de7d79b270c2ac08014de6aa8e

tongbong wrote Apr 25, 2013 at 10:12 PM

EntriesProviderType and FilterParams are used only in Providers namespace. These types should be at first relocated in Providers namespace.

Agreed?

If yes, this will be the end of the Providers namespace and will therefore reduce project complexity.

dirkster wrote Apr 30, 2013 at 10:21 PM

Yes agreed and this is indeed the end of the Domain namespace:

https://yalvlib.codeplex.com/SourceControl/changeset/8bab6b4b2879b480a79784985a396f6803c7b4da

tongbong wrote May 2, 2013 at 5:55 PM

Nice, no more domain namespace.
Next should be Behaviour which seams to be pure UI and therefore could be placed into View namespace.

dirkster wrote May 2, 2013 at 11:43 PM

Yes behavior is purely view related thats right. Its mostly used in XAML - so refactoring it requires searching for string occurrences in the XAML of both MainWindow demo apps and the control

(there are most likely no other references). Would you or Gwen be able to do this? This workitem is already closed.... :)

gwentreb wrote May 3, 2013 at 7:54 AM

Behaviour namespace has been moved to view namespace.