377 reputation
513
bio website myagileadventures.blogspot.ca
location Shawinigan, Canada
age 38
visits member for 3 years, 11 months
seen Nov 28 at 17:10

Scrum Master, Software Architect/Analyst, and Analyst-Programmer.

I'm a passionate Software Development professional who strives to the best in every project. I consider every project a new challenge to take on, within which I deliver the best of myself.

I'm a strong believer of Agile Methodologies, and as such, I'm always studying, testing, reading, "googling", "StackOverflowing" in order to stay up to date and offer the best software architectures out there, based on the best practices: SOLID.

Lately, I have enlarged my knowledge over Dependancy Injection (DI) and Inversion of Control (IoC).

It's interesting to learn and share knowledge among the SO community!


Sep
30
awarded  Explainer
Sep
24
comment How should one handle a Parent-Child relationship using MVP?
So I could use an interface with a single property for which my form holds an implementation, and pass it upon a call to ShowView like so: Presenter.ShowView(myParentChildInterface). Is this what you're proposing, do I get it correctly?
Sep
24
comment How should one handle a Parent-Child relationship using MVP?
@BartvanIngenSchenau, In short, I can't say that I am sure. To the best of my knowledge, WPF, ASP.NET, and Silverlight don't have this concept. I might be mistaking, I perhaps only never needed such concept on other platforms than WinForms.
Sep
23
revised How should one handle a Parent-Child relationship using MVP?
deleted 6 characters in body
Sep
23
asked How should one handle a Parent-Child relationship using MVP?
Sep
10
comment Should the Presenter depend on the View or the vice versa?
Yes. I used to use the Observer Pattern as well, and this may become hard to debug and maintain due to the pattern's nature. Instead, I began to use interfaces so that the view has to fulfill the contract of having a property called Handler, and through this exposed property, the Presenter sets itself as the handler. Then, the view uses the Hollywood Principle and call upon the required method on its handler, which could be anything that implements IUiHandler.
Sep
10
comment Should the Presenter depend on the View or the vice versa?
This comforts me. In fact, I couldn't see much difference neither, so I wondered whether I missed something or I was right about it.
Sep
10
accepted Should the Presenter depend on the View or the vice versa?
Sep
9
comment Understanding C# Delegates Structure
What is it you want to know exactly about delegates, the way they're working, or how to work with them? It's unclear to me what you're asking.
Sep
9
comment Should the Presenter depend on the View or the vice versa?
I have often seen a Presenter being Setter Injected to the view, or else, before DI, instantiating a new presenter from within the view itself so that the code becomes testable. Even if the View depended on the Presenter, the Presenter still decouples the code from the UI and can be reused over and over again, and is easily testable.
Sep
9
asked Should the Presenter depend on the View or the vice versa?
Aug
17
revised Where should the “not empty field” validation code be written on a 3-layer application?
Provided a direct link to Martin's Fowler's MVC blog post.
Aug
17
revised Where should the “not empty field” validation code be written on a 3-layer application?
Linked the technologies brought forward in the discussion.
Aug
17
answered Where should the “not empty field” validation code be written on a 3-layer application?
Jun
5
awarded  Autobiographer
Apr
30
awarded  Notable Question
Jan
24
awarded  Yearling
Sep
29
awarded  Popular Question
Sep
26
awarded  Notable Question
Mar
14
awarded  Good Question