network profile
| bio | website | familyguestbook.com |
|---|---|---|
| location | Earth, TX | |
| age | 14 | |
| visits | member for | 2 years |
| seen | Jun 14 at 19:23 | |
| stats | profile views | 30 |
|
Jun 17 |
awarded | Student |
|
Jun 17 |
revised |
How does one manage an intern effectively? added 26 characters in body; deleted 2 characters in body; added 4 characters in body |
|
Jun 17 |
asked | How does one manage an intern effectively? |
|
Jun 17 |
awarded | Supporter |
|
Jun 16 |
awarded | Commentator |
|
Jun 16 |
awarded | Teacher |
|
Jun 15 |
comment |
What are the rules for coupling a ViewModel and a View in the MVVM pattern? @Rachel - fair enough. |
|
Jun 15 |
comment |
What are the rules for coupling a ViewModel and a View in the MVVM pattern? @Rachel - It is obvious you have way more experience in WPF than Silverlight. It is also apparent that you make up things as you go, such as "view-specific language" (please don't take offense). Look Silverlight is a subset of WPF and hence your value converters will not port so well, unless they are very basic. A property on the otherhand requires no porting, no extra class, no extra confusion, and no extra-maintenance. |
|
Jun 15 |
comment |
What are the rules for coupling a ViewModel and a View in the MVVM pattern? @Rachel - and a property in the viewmodel doesn't keep the view and view model separate? Please explain how that works. BTW - have you ever tried to port a WPF converter to a silverlight one? Good luck. |
|
Jun 15 |
comment |
What are the rules for coupling a ViewModel and a View in the MVVM pattern? @CodeNaked - I think you may have misunderstood my last comment. In any case, for the details he provided in his question a value converter is way overkill. If he follows your approach he is going to have a potential maintenance nightmare of value converters to have to deal with. |
|
Jun 15 |
comment |
What are the rules for coupling a ViewModel and a View in the MVVM pattern? @CodeNaked - I guess it depends on what he needs. The "cleanest" way is to use a simple property that matches the type of property he wants to bind too. Sure if he needs to take in a set of unique values and convert them to a valid Visibility value then a converter would be cleaner. |
|
Jun 15 |
comment |
What are the rules for coupling a ViewModel and a View in the MVVM pattern? Why does he need a converter? That's just creating more work for no benefit. |
