I'm working on some multi-touch Surface computers for my workplace (mainly for meetings and presentation), and not being wholly familiar with WPF, I was wondering if I might be able to put some Windows Forms in a Surface project so that several users could ostensibly use programs at the same time.
Is this possible?
I don't understand the reason why you want to include windows forms into a WPF project, but if that's all you want to do, check out this. WindowsFormsHost Class is used to manage WinForms things in WPF.
Please mark my reply as answer if it solves your problem.
Thanks,
Related
I was using windows form to create a game but I concluded that the performance is just too bad. So I decided to work with Monogame.
The thing is that I can't use the tools(picturebox, bitmaps, menus etc..) with monogame so my question is : Can I draw all the things that are normally drawn in monogame in a picturebox in Windows Forms to get the drawing performance of Monogame but still being able to use everything Windows Forms has to offer?
I can't find any information about this topic on the Internet, so I would really appreciate if someone can help me out!
Take a look at embedding in a winform.
http://jaquadro.com/2013/03/embedding-your-monogame-game-in-a-winforms-control/
This might be a stupid question, but there are soo many combinations of approach (wpf, silverlight, winforms, html5) with incompatibility at mscorlib level, that I got completely lost.
I would like to be able to have a few windows mainly displaying realtime charts.
Probably with interaction among the windows (click in one, pop and display a new windows)
If it can be viewed on the web, perfect.
But I dont want to have to deal with another layer of nasty stuff for those features (like having to setup some "WCF" on a "IIS", kill me first)
In the end I was thinking of using FSharpChart on Silverlight.
Is that possible and/ or the best option ?
Thanks for your suggestions
update
I see that system.drawing which fsharpchart relies on is not silverlight supported..
Try Dynamic Data Display instead of FSharpChart. It runs on Silverlight: http://research.microsoft.com/en-us/um/cambridge/groups/science/tools/d3/dynamicdatadisplay.htm
It's not as F# Interactive friendly as FSharpChart, but you can easily wrap it in a handful of functions to make it more usable
I've seen the beautiful MetroTwit interface http://www.metrotwit.com/ ; I would like to know which WPF components have been used for trying to reproduce it.
MetroTwit designer here :)
All of the controls and animations were designed from scratch.
Obviously I drew a lot of inspiration from Zune, Windows Phone 7 but everything was re-templated from the default base styles. Most of the icons were made in Photoshop then converted into Expression Design to be output in XAML.
Since much of our design was with a Twitter client in mind, it's not universal for all applications. What you should really do is read up on the User Experience Design Guidelines for Windows Phone for a much broader understanding of Metro.
After you have a solid grasp of what you believe Metro to be, it's much easier to style the controls to the way that suits your application.
Look at http://metrotheme.codeplex.com/ and http://www.silverlight.net/content/samples/sl4/themes/cosmopolitan.html those are silverlight but you can use it in WPF with some changes
I'm trying to figure out how to make a customizable stock trading platform with Prism and MVVM.
Trading platforms normally look something like this:
http://www.shareupdate.net/wp-content/uploads/2010/11/Best-online-share-trading-software..jpeg
This kind of layout allows you to select which windows to display in MDI region. I'm not sure how to build this with Prism and Silverlight. I suppose I have to use childwindows, but Prism seems kinda rigid for this kind of design. Correct me if I'm wrong :)
Any help is greatly appreciated
I'm not sure how well MDI would work in terms of usability in a Sivlerlight app. You might find that the blacklight dragdrop panel dashboard (under interactive controls) would be much more suitable for a silverlight app. It should give you some MDI style features, you could also have multiple tabs with the dashboards in.
I think this link might provide some help here.
Telerik provide the mechanism for a dockable window system in Silverlight.
I apologize for my newbie question by why do WPF apps look like web pages?
I am new to gui and still shopping for a book to learn gui programming. The push seems to be in the direction of WPF but all the screenshots of WPF applications that I've seen look like cheap web pages. Frankly I'd be ashamed to sell an app that looked like a web page.
I realize that WPF is built on XML technology but can you not build normal looking WPF apps in Visual Studio (via button("widget")) drag-n-drop? In other words an app that does not look like a web page?
How can WPF be a replacement for WinForms or the like when it doesn't provide the same standard application look?
The default look of WPF applications is admittedly rather simple, but WPF allows unprecedented control over how your application looks.
Here are some examples, all of them WPF applications.
If you are to deveop an application under .net and are able to target .net 3.5 or above, you will want to use wpf. If you don't know much about ui technology and want to work with .net, understanding windows forms is useful but not necessary. You should learn wpf regardless.
2 perks that I have found while using the framework:
- it is very easy to inject branding and custom interactivity into your app. It is then very easy to change these when your sales guy decides the want it blue, not red.
- the way components are organized on screen is relational like a webpage, not coordinate based like windows forms. This is ideal for scenarios when translated strings will change length (English to German for example). Under usual circumstances the ui will resize itself automatically at runtime to make it all fit.
If you just throw in controls and don't change the style of anything, your first wpf applications will look almost identical to native win32 applications. It is very easy to change this, but you will achieve great results regardless of the "look" you choose. Microsoft also provide the tools to create new ui components that look like native buttons. There are a host of other features that will make you grin while learning!
This is not a technical note, but at the moment wpf is a highly sellable skill and looks great on a cv! Companies want great branding in their apps. Wpf helps that happen.
WPF does provide the same appication look wich is the default look. When you drag and drop your controls onto the design surface (just like in windows forms, MFC ...) the controls look as you would expect them to look under the current theme. Chances are that you have seen quite some WPF applications without noticing. Just because they look like any other app.
The reason you might see more WPF based applications that have some sort of custom look and feel to them is simple because it is so much easier to do what ever you like to your GUI than in any other GUI framework on any platform. This is both blessing and curse. While you being absolutely flexible it is easy to do absolutely horrible stuff.
user440267, I believe that the most application in WPF are built using normal Windows. But there is an option which we don't create a window, instead we create a page, which behave like you think.