8 added 16 characters in body
source | link

NO. Here I agree with you that the UI shouldn't know the domain objects exist. It should only know how to request things through controller logic and how to display responses from presenter logic. The UI shouldn't be able to directly touch those domain objects. If the UI can touch them then the domain isn't properly encapsulated.

NO. Here I agree with you that the UI shouldn't know the domain objects exist. It should only know how to request things through controller logic and how to display responses from presenter logic. The UI shouldn't be able to directly touch those domain objects. If the UI can the domain isn't properly encapsulated.

NO. Here I agree with you that the UI shouldn't know the domain objects exist. It should only know how to request things through controller logic and how to display responses from presenter logic. The UI shouldn't be able to directly touch those domain objects. If the UI can touch them then the domain isn't properly encapsulated.

7 added 55 characters in body
source | link

By moving the logic into an isolated object you're free to define an interface/API for talking to it that makes sense in your domain. Something simple and, readable, and free of details like understanding what a textbox is. So much so that you can get your DDD ubiquitous language going and write business rules that a domain expert, who's never written code before, could actually read and tell you if you have it wrong.

By moving the logic into an isolated object you're free to define an interface/API for talking to it that makes sense in your domain. Something simple and readable. So much so that you can get your DDD ubiquitous language going and write business rules that a domain expert, who's never written code before, could actually read and tell you if you have it wrong.

By moving the logic into an isolated object you're free to define an interface/API for talking to it that makes sense in your domain. Something simple, readable, and free of details like understanding what a textbox is. So much so that you can get your DDD ubiquitous language going and write business rules that a domain expert, who's never written code before, could actually read and tell you if you have it wrong.

6 deleted 3 characters in body
source | link

By moving the logic into an isolated object you're free to define an interface/API for talking to it that makes sense in your domain. Something simple and readable. So much so that you can get your DDD ubiquitous language going and write business rules that a domain expert, who's never written code before, could actually read it and tell you if you have it wrong.

Now if the worst happens and they just wont work with you don't give in and shove logic ininto the UI. Make your own layer between the UI and their stuff to handle their shenanigans. Don't package this layer with the UI. Do that and you can ensure the UI has a clean API that you can test quickly when fingers start pointing.

By moving the logic into an isolated object you're free to define an interface/API for talking to it that makes sense in your domain. Something simple and readable. So much so that you can get your DDD ubiquitous language going and write business rules that a domain expert, who's never written code before, could actually read it and tell you if you have it wrong.

Now if the worst happens and they just wont work with you don't give in and shove logic in the UI. Make your own layer between the UI and their stuff to handle their shenanigans. Don't package this layer with the UI. Do that and you can ensure the UI has a clean API that you can test quickly when fingers start pointing.

By moving the logic into an isolated object you're free to define an interface/API for talking to it that makes sense in your domain. Something simple and readable. So much so that you can get your DDD ubiquitous language going and write business rules that a domain expert, who's never written code before, could actually read and tell you if you have it wrong.

Now if the worst happens and they just wont work with you don't give in and shove logic into the UI. Make your own layer between the UI and their stuff to handle their shenanigans. Don't package this layer with the UI. Do that and you can ensure the UI has a clean API that you can test quickly when fingers start pointing.

5 added 67 characters in body
source | link
4 added 67 characters in body
source | link
3 added 28 characters in body
source | link
2 added 41 characters in body
source | link
1
source | link