Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Lately I have successfully implemented a desktop application using WPF technology with MVVM achtitecture and Prism. I am very happy with how the entire, quite large project emerged, and how it is easy to maintain the entire application now. No questions about the MVVM, I am already sold on that one, but how about the Prism, would you consider that a good choice when it comes to implementing the MVVM pattern? I am quite happy with the product, but I was wondering what is your opinion on it?
Short answer: No.
Longer answer: Prism is a Composite Application library, which provides features for creating composable applications, including MVVM patterns.
However, in my opinion, MVVM can be achieved using simpler frameworks like MVVMLight and Caliburn.Micro. If you don't need the extra features that Prism provides then I wouldn't use it. Extra functionality is just more code that can break, if you're not using it.
Is Prism a good product? Yes.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I decided to make an application that like statechart simulation tool or flowchart (such as yEd, MS visio etc.). It will be a diagram scene application. But, I have'nt decided to platform that I will use yet. Which one is suitable for this jobs?
Qt,
MS WPF,
Python
Others
well, I have only WPF platform experience but I'll share my experience in those area.
I worked almost 2 years for developing in desktop application using WPF(I know it was 1~3 millions $ project). and some portion of my job is developing and maintaining diagram based canvas with telerik libraries.
but the first, I want to recommend you to choose your program going to be a .net-based/cross-platform/web-based.
If you choose that you are going to make windows application and those diagram chart, then WPF and telerik may be a one of good choices.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
After reading the tutorials for both technologies AngularJS makes the HTML code much more easy to read.
My only concern is that AngularJS does not provide a Desktop Environment in terms of controls like ExtJS isn't that right?
Or is it these days ExtJS a technology becoming deprecated?
What exactly do you want to ask with the question?
The main difference between AngularJS and ExtJS in my opinion is, that AngularJS focuses mainly on being a MVC Framework, which doesn't offer any extended library-style functionality to design fancy user interfaces. ExtJS goes a step further, it also is a MVC framework at the core, but offers more than that lots of functionality, for example designing of a user interface (probably what you mean by "Desktop Environment" lookalike). Visit the sencha homepage to get a full overview of the built in functionality. Using ExtJS to build webapp, there shouldn't be much of a need to add any other libraries.
To answer your second question: I don't think that ExtJS becomes deprecated, it has an active development and this year version 5 of the framework was launched.
The question "Should I use AngularJS or ExtJS" depends on the style of the frameworks, whatever you prefer and on your requirements. There are lots of articles which you may view, they compare the two frameworks in a detailed way: http://www.techferry.com/articles/ExtJS-vs-AngularJS.html
If you want to create an application with an user interface that looks like a Desktop Environment, you could either user ExtJS or AngularJS + a library, which provides functionality to create such an user interface.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
How hard is it to transition from WPF to Silverlight?
Would you say that a developer who knows WPF can pick up Silverlight with ease?
It's fairly easy to pick up Silverlight if you know WPF. There are some subtle differences, but most of the concepts apply.
The largest stumbling block is dealing with things that are unsupported in Sliverlight. You often need convoluted workarounds for things that are easy in WPF but unsupported in Silverlight (such as IMultiValueConverter).
One of the most important things to get used to is the browser that sandboxes your Silverlight Application. Of course you can use the out-of-browser version and that opens quite a few options but it will still not be like WPF.
You might miss the full .NET functionality you are used to in WPF but the Silverlight runtime is pretty rich.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I have been looking at the Model-View-ViewModel pattern that is suggested by several people out there (especially John Gossman, take a look at this post and this podcast), but what other patterns (if any) have people used and liked ... and where do they add value?
I have also stumbled across:
Model-View-ViewModel
Presentation Model
DataModel-View-ViewModel
Patterns in Prism (now known as the Composite Application Guidance for WPF)
I would love an active discussion on these above and those I may not have discovered yet.
Another pattern that we have used and loved is the Attached Behavior pattern ... using the extensibility mechanism of attached properties in WPF. There are quite a few posts out there on this useful pattern as well.
http://blogs.msdn.com/johngossman/archive/2008/05/16/attachedbehavior-pattern-sample.aspx
http://blogs.msdn.com/johngossman/archive/2008/05/07/the-attached-behavior-pattern.aspx
http://blogs.msdn.com/dancre/archive/2006/03/04/543854.aspx
http://www.codeproject.com/KB/WPF/AttachedBehaviors.aspx
I have been using a variation of the Model-View-Presenter pattern. It has served our purposes pretty well developing various UIs. It is not perfect but it gets the job done well. One of the issues I've had is that I am never satisfied with multi-threaded scenarios. We've recently been making many of our presenters multi-threaded. Since these worker threads, in the end, update the UI, we have had to dispatch actions to the UI through the View's dispatcher. Code was becoming really verbose if every View property checked the dispatcher so because of time constraints, we ended up exposing the View's dispatcher to the Presenter. Not the greatest move if you ask me...
We are using a modular UI framework similar to CAB and Prism, so a lot of those patterns apply to us as well.
I am also a big fan of Commands in WPF. I haven't been able to play around with Prism's DelegateCommand and CompositeCommand yet, but they sound really nice.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am developing a mid-size application with VB2008. To better test my application I am following a MVP/Supervising Controller approach.
My question is: What are your recommendations to separate responsibilites? So far I've come up with a winform with an instance of a controller and with an instance of my class. The controls are updated via DataBinding
The problem is that I'm just not sure where to write the responsibilites (let's say Validation, Report creation, Queries and so on) Inside my class? in a separate class?
Is there any small example of a clean Winform class design that you could point me?
I would suggest you spend time reading Jeremy Millers 'Build your own CAB' series of posts to get a feel for what you might like/need to implement as your application becomes more complex.
Martin Fowler is a good source of information on all things design patterns including MVC. Fowler discusses Passive View and separation of responsibilities is demonstrated also
http://martinfowler.com/eaaDev/ModelViewPresenter.html