|
Thank God for you are alive and no serious injuries! 
wishing you a speedy recovery... n hope for good news for your wife's results!
.:>GSN<:.
|
|
|
|
|
Thanks, I appreciate that.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
got the report?
and what about the Porsche driver?
.:>GSN<:.
|
|
|
|
|
Nope, no news yet. It is 9 PM Sunday evening here. We should get the results back Monday.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
|
hey! what about the reports?
Were they normal??
P.S. any update about the driver?
.:>GSN<:.
|
|
|
|
|
Thank you for asking. Yes, the results were good news - there is no cancer. We are very relieved. :phew:
I have not heard if they caught the driver, but Tuesday they declared my car a total loss. It would cost $10,000 to fix it. So I have been to the bank and checked out a few cars, but I have not found one yet.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
phew!  for the result!
too bad about the car.. though it's a good thing that you were ok..
has your bodyache lessened?
.:>GSN<:.
|
|
|
|
|
I hope the news from your wife's biopsy is good and they catch the SOB in the Porsche.
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
|
|
|
|
|
Thanks Mike. That pretty much sums up my thoughts as well. 
And welcome back from your trip
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
Soren, Congratulations on being alive, and my condolences on your terrible experience !
“I speak in a poem of the ancient food of heroes: humiliation, unhappiness, discord. Those things are given to us to transform, so that we may make from the miserable circumstances of our lives things that are eternal, or aspire to be so.” Jorge Luis Borges
|
|
|
|
|
Thanks Bill, I appreciate that.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
SoMad wrote: the driver of a Porsche made an insanely illegal move ... I was trying to figure out where the sunshine had come to rest, but several witnesses told me he stopped for a few seconds and then took off
The one saving grace is that the f***er should be easy to find.SoMad wrote: my wife had a biopsy on a number of lumps in her knee
Best of luck to you and your wife.
I've had these sorts of "it's raining sh*t and no umbrella" periods in my life, so I know what it feels like.
Software Zen: delete this;
|
|
|
|
|
Thanks Gary,
Yes, it seems like they should be able to find the driver. Even in a city as big as San Diego.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
"A rose by any other name would smell just as sweet."
No doubt.
But what you call things does matter. Abe Lincoln trumps the bard this time (paraphrased): "If you call a tail a leg, how many legs does a dog have? ... Four! It doesn't matter what you *call* a tail, it's still a tail, not a leg."
The "View" in Model-View-Controller (MVC) should be called "Sensory," not "View" because, quoting "Programming Android" by Mednieks, Dornin, Meike, and Nakamura (the "Droidians of 4"):
"...a view is the portion of the application responsible for rendering the display, sending audio to the speakers, generating tactile feedback, and so on."
IOW, it's not just about visuals; it's also about audibles and "tactibles."
Who comes up with this nomenclature? Calling stuff by non-optimal names makes it harder to perceive just what is what. Maybe the software development profession should have a body, like the Académie française[^]to keep stuff like this in check.
|
|
|
|
|
I guess it was a View when the only aspects of the sensory that were relevant was what the user could see on the screen.
The name that totally annoys me is MVVM. Whoever thought that was a good way of naming the pattern needs spanking.
|
|
|
|
|
And what would you have named MVVM?
|
|
|
|
|
Perhaps VVVVVV instead[^]
.-.
|o,o|
,| _\=/_ .-""-.
||/_/_\_\ /[] _ _\
|_/|(_)|\\ _|_o_LII|_
\._. |\_/|"` |_| ==== |_|
|_|_| ||" || ||
|-|-| ||LI o ||
|_|_| ||'----'||
/_/ \_\ /__| |__\
|
|
|
|
|
I actually did come up with an alternate name for it, and blogged about it on posterous, but posterous has gone the way of the cuckoo bird, and I don't recall just what I came up with. I liked it way better than MVVM, though, I remember that.
|
|
|
|
|
Good question.
The M for model is fine - although requirements for WPF binding may mean legacy models need an adapter layer for notification events.
The V for view is fine - although the idea that the view could be replaced entirely with text to speech and speech to text (or DTMF) means we could look for something more generic. (Presentation, Manifestation?)
The VM seems convoluted to me. It's reusing the word Model with a different meaning. To my mind, Controller (or Manager) is a good word, but that's already used. It also implies a superior role between the V and VM, and one of the key principles is the disassociation between them.
Thinking it through, perhaps it should be:
DMVVM - Data Model, View, View Model or
MMM - Model, Manifestation, Manager.
|
|
|
|
|
Ah, it looks like you're falling into the common mistake of viewing MVVM as a Presentation Pattern. It's not, it's an Architectural Pattern, so the Model isn't necessarily a data model - it's actually the services (including data models) that is needed to be presented to the View via the ViewModel.
|
|
|
|
|
Fair point.
I've spent some time trying to convince myself that services can simply be perceived as data.
In some cases, it can - a web service that gives the current fx rate for two currencies. Equivalent to a data table containing the same.
The case where I decided services are different is 'Request this Credit Card Payment' . Could still be a web service, but it doesn't make sense to see it as a CRUD data operation.
But couldn't the same point be made against MVC, MVP, MV*? Where would services fit in those 'models'?.
|
|
|
|
|
NeverJustHere wrote: But couldn't the same point be made against MVC, MVP, MV*?
Indeed it could.
|
|
|
|
|
MVC. The view model in MVVM is doing exactly the same job as a controller in a traditional MVC scenario, or controllers in ASP.net MVC for that matter.
|
|
|
|
|
Err, no it's not. MVC and MVVM are separate entities - in spirit, MVVM is closest to the MVSC pattern than to MVC. I posed my question to see who was aware of the architectural heritage that led up to MVVM (this was a term independently coined by John Gossman at roughly the same time as the GOF retired MVP and split it into MVPP and MVSC).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
