Making a Diagram Application [closed] - wpf

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.

Related

reactjs dashboards vs BI reporting tools || which one has the edge? [closed]

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 2 months ago.
Improve this question
I see react also has support for the dashboard programming libraries.. will it be used as a replacement for bi report tools?
Need to know when we can go for react dashboard libraries.
You are trying to mix two completely different tools here. BI report tools are used by business directly. I mean, there is a platform where they can go and work with the tool. Charting libraries in Javascript is used when you are developing a custom report inside a web application. So, unless the business is going to use your custom web app for reporting, there is no need of javascript libraries.

Separate mobile site [closed]

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 7 years ago.
Improve this question
So, I have a desktop site that has lots of features and design specific contents which are not really suitable for mobile view (loading speed etc).
So, I want to have a separate mobile site, such as m.example.com.
I am thinking of somehow detecting that it is in either mobile or tablet view.
What would be the most appropriate tutorial that is up to date?
As for a good overview of what you might want (to do further research), you might want to take a look at this question: How to make Mobile website like m.yahoo.com (Mobile Version)?
For a good tutorial, I'm not sure if you're asking for a text tutorial or a video tutorial. I find that text tutorials give you options to go at your own pace and dive deeper in the subject. Therefore, I would suggest this tutorial: http://www.html5rocks.com/en/mobile/responsivedesign/
Wish you best of luck with your developing

Transitioning from WPF to Silverlight [closed]

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.

How do you offer Silverlight to clients? [closed]

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 3 years ago.
Improve this question
We know that Silverlight currently in 3.0.x version - very fast transition from Silverlight 2.0.x. For those using Windows and Mac, it will not be an issue since the runtime supports those platform. The problem is with Linux users. I know that Mono guys (through Moonlight project) are doing their best to keep it up to date with Silverlight, but unfortunately they are too much behind.
How do you offer Silverlight to clients considering that facts?
If your client base has "full support for Linux on the desktop" as a pre-req, you're really in an interesting niche -- one I'd love to learn more about, btw, but not one I've ever encountered. If you're REALLY in such a situation, I guess your only viable silverlight strategy is to limit your silverlight use to not much more than is currently available via moonlight, clearly document to your Linux-rabid clients what's missing on Moonlight for them to be able to use your latest release, and endeavor (via clients involvement, involvement of your tech people, bounties for developers that add each missing features, etc) to get Moonlight up to the level you absolutely need it to be!-)

Any recommendation for a good enough Winforms GUI design? [closed]

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

Resources