|
Also working on a MVVM app!
Though I won't call that its defining feature! 
modified 17-Jan-15 21:23pm.
|
|
|
|
|
This my first significant MVVM app. My head is spinning with Models, ViewModels and questions like: What is appropriate to put in code behind? For my smoking brain MVVM is the defining attribute of this app! 
|
|
|
|
|
Your first one!  Late to the game hey?!
Even web app do MVVM nowadays, allegedly with the popular AngularJS or, my favorite, KnockoutJS!
As an exercise try to put nothing in the code behind!
It can be sometimes hard, but it will challenge your thinking!
Even I made a recent progress and was able to close/open Window and Dialogs the MVVM way!  
|
|
|
|
|
Yeah, I'm a real Johnny-come-lately to the MVVM game. I just never had reason to learn it. Today I am retired and I am learning it just to keep my brain busy. After considerable research I also learnt how to use an attached property to close dialog windows from the ViewModel, but I was criticized for it here on CP, because it should be done from code behind. There is some conflicting opinions on the whole issue of what should be done from code behind. 
|
|
|
|
|
If some told you something SHOULD be done in the code behind when using MVVM pattern they got it wrong! 
You don't have to be a purist, and you COULD use code behind in MVVM app!
But ideally, the UI should just bind to property and have no code behind.
That said you might need lots of utility code! Such the famous DelegateCommand.
Here, just for you I shared my MVVM code top show/open dialog
Show/Hide Windows the MVVM way[^]
|
|
|
|
|
Thanks most sincerely! I have your article bookmarked so I can study it at leisure! There is not much on the web that I could find that covers the opening and closing of dialogs from the ViewModel.
|
|
|
|
|
Thanks!
|
|
|
|
|
Happy retirement!!
|
|
|
|
|
According to my screen, there are currently 64,808 members logged on at this moment for you to talk to. I've been here long enough to remember when having a dozen members online was something special. In fact, there was a time when having a couple hundred members online at once would crash the site. Chris and his minions have done an awesome job of keeping this place alive, and we don't show them near enough appreciation for their efforts.
Maybe you should get yourself a life, Cornelius. I encourage that, since I've never had one. Don't spend your Saturday evening sitting in front of a computer without a girl at your side. If you have to choose, take the girl part, not the computer part. In the long run, a warm, loving girl is a lot nicer to sleep with than a computer.
Will Rogers never met me.
|
|
|
|
|
Amen to what you say friend! But I am retired with a wife I have had for 47 years. Last night she went out to babysit our one grandson and that is how I happened to be alone at home on a Saturday night. 
|
|
|
|
|
How very cool! I won't live long enough to have a wife for 47 years, even if I managed to find one today, so I'm envious!
Will Rogers never met me.
|
|
|
|
|
Life? LIFE??? Where do you buy that?
My plan is to live forever ... so far so good
|
|
|
|
|
I installed SVN server 1.6.6 on my server in 2009. it is working.
Shall I upgrade to new version of SVN, currently 1.8?
please share some of your experience/lessons.
thanks a million.
diligent hands rule....
|
|
|
|
|
If it ain't broke, don't break it.
|
|
|
|
|
|
What are the changes in the newer versions?
Are there features in the new versions of the SVN Servers that you would like to have ?
Like others said, if it ain't broken...
I'd rather be phishing!
|
|
|
|
|
You should upgrade to a DVCS, e.g. Git.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
We work in Xcode and the svn. The update was fine: no problems and better performance.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
|
This reminded me of a issue I had a while back where our program started crashing (seemingly randomly) for certain customers, reporting a kernel32 error, and going through the whole gamut of reporting to MS, yada, yada... The behavior could not be reproduced on our end and plagued those users for many months until we were able to narrow it down to a rogue dll, not installed by us, but by another software vendor. Somehow, not always, and with no discernible pattern, this rogue library was being pulled into the stack. Replacing that dll with a newer version corrected the problem, until that vendor pushes another update, then we have to do it all over again! Sounds like job security to me!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Is "CommitStrip" the new "Usefriendly[^]" carton?
I'd rather be phishing!
|
|
|
|
|
For me, yes. Altough Commit Strip didn't make it to Antartica yet...
|
|
|
|
|
|
learn to program in/like Klingon - 'there are no bugs (weakling scum), there are only features'
|
|
|
|
|
if we cant reproduce a "bug" we call it "issue". And done.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
