WPF
-
I guessed as much. :) I likely will add bindings for that, but I also will add bindings for other game frameworks, so games can be built for Win8 (I actually like Win8, and XNA is not (officially) supported there). I might add bindings for ANX.Framework[^], which is a clone of XNA. It also (is supposed to) work on Win8 as well. I will likely use Axiom3D[^] as the built-in game GUI framework, with the ability to use either DirectX (through SlimDX), or OpenGL (through OpenTK) with it. I am deciding on which Physics engine to use, but will likely use Jitter Physics[^].
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a
-
You'll have to keep re-reading my initial post until you understand it. When you post a reponse that shows you comprehend what I wrote I'll respond. If you never get there, we're done.
I got it fine. You basically suggested Silverlight over WPF, and my point to you is that Silverlight won't be around, and WPF will be. Not sure where the disconnect is here.
If it's not broken, fix it until it is
-
Yeah, the new designer is a huge improvement.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
True that.
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a
-
I guessed as much. :) I likely will add bindings for that, but I also will add bindings for other game frameworks, so games can be built for Win8 (I actually like Win8, and XNA is not (officially) supported there). I might add bindings for ANX.Framework[^], which is a clone of XNA. It also (is supposed to) work on Win8 as well. I will likely use Axiom3D[^] as the built-in game GUI framework, with the ability to use either DirectX (through SlimDX), or OpenGL (through OpenTK) with it. I am deciding on which Physics engine to use, but will likely use Jitter Physics[^].
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a
I'm a big fan of FarSeer Physics[^]
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
wout de zeeuw wrote:
Here's a little gotcha: it's obsolete
Says who? maybe you haven't noticed, but WPF is a key tool in Win 8. It's not obsolete and it's not going anywhere.
If it's not broken, fix it until it is
Kevin Marois wrote:
WPF is a key tool in Win 8
Really? Which apps those ship with Win 8 use WPF?
-
Kevin Marois wrote:
WPF is a key tool in Win 8
Really? Which apps those ship with Win 8 use WPF?
Desktop apps
If it's not broken, fix it until it is
-
Wout's wrong. WPF is not obsolete - the type of game you want to build will dictate whether or not WPF is a good choice. If it's something like Tetris, WPF is fine; if it's a FPS, then you don't want to use WPF.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
Pete O'Hanlon wrote:
If it's something like Tetris, WPF is fine; if it's a FPS, then you don't want to use WPF.
On the other hand HTML5 is good for both:). Ducks and runs.
-
Desktop apps
If it's not broken, fix it until it is
Yes. I get that but which desktop app which ships with Windows 8 is actually written in WPF?
-
Yes. I get that but which desktop app which ships with Windows 8 is actually written in WPF?
Hell if I know
If it's not broken, fix it until it is
-
Hell if I know
If it's not broken, fix it until it is
The right answer in none. The only one application which was written in WPF - Powershell IDE no longer ships in Windows 8. So to say WPF is a key tool in Windows 8 is not at all accurate. It is as much as a key tool as WTL.
-
The right answer in none. The only one application which was written in WPF - Powershell IDE no longer ships in Windows 8. So to say WPF is a key tool in Windows 8 is not at all accurate. It is as much as a key tool as WTL.
Um, sure. Whatever you say
If it's not broken, fix it until it is
-
Pete O'Hanlon wrote:
If it's something like Tetris, WPF is fine; if it's a FPS, then you don't want to use WPF.
On the other hand HTML5 is good for both:). Ducks and runs.
Why? It is good for both.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
Osbolete, huh? Then why was large chunks of the Visual Studio 2012 UI re-written with it??
A guide to posting questions on CodeProject[^]
Dave KreskowiakMS does a lot of things that are not rational.
Wout
-
I got it fine. You basically suggested Silverlight over WPF, and my point to you is that Silverlight won't be around, and WPF will be. Not sure where the disconnect is here.
If it's not broken, fix it until it is
Both Silverlight and WPF are in Windows 8. Any operating system that cannot handle Silverlight cannot handle WPF. That is, an operating system that can handle WPF will have a browser that supports Silverlight. In that way, they are tied together. So I reject the notion that one is going to disappear before the other, regardless of Microsoft's HTML 5 dreams. Given that I chose Silverlight for 3 reasons: 1: Forces asyncronous processing which is were the world is going anyways. 2: Best fit for preparation for porting to Window RT. 3: Ease of distribution (unless the game is going to be played only on local network). Thinking ahead that the library this guy builds may need to be ported to WindowsRT one day I suggested the technology (in my reading on the topic) that best supports that future state, eases distribution, and allows him to pick up asynchronous processing along the way. That and he may want to put his game on a Windows Phone. Those are very solid reasons which are something other than the FUD nonsense you posted. It isn't a Silverlight vs. WPF religious thing - it's a thinking ahead thing. Granted, now that Sinofsky's gone anything goes. We can only do the best with what we know.
-
I'm a big fan of FarSeer Physics[^]
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
That's 2D, Jitter is 3D. I will likely have a binding for Farseer though.
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a
-
Both Silverlight and WPF are in Windows 8. Any operating system that cannot handle Silverlight cannot handle WPF. That is, an operating system that can handle WPF will have a browser that supports Silverlight. In that way, they are tied together. So I reject the notion that one is going to disappear before the other, regardless of Microsoft's HTML 5 dreams. Given that I chose Silverlight for 3 reasons: 1: Forces asyncronous processing which is were the world is going anyways. 2: Best fit for preparation for porting to Window RT. 3: Ease of distribution (unless the game is going to be played only on local network). Thinking ahead that the library this guy builds may need to be ported to WindowsRT one day I suggested the technology (in my reading on the topic) that best supports that future state, eases distribution, and allows him to pick up asynchronous processing along the way. That and he may want to put his game on a Windows Phone. Those are very solid reasons which are something other than the FUD nonsense you posted. It isn't a Silverlight vs. WPF religious thing - it's a thinking ahead thing. Granted, now that Sinofsky's gone anything goes. We can only do the best with what we know.
MehGerbil wrote:
Given that I chose Silverlight for 3 reasons:
1: Forces asyncronous processing which is were the world is going anyways.
2: Best fit for preparation for porting to Window RT.
3: Ease of distribution (unless the game is going to be played only on local network).Errr...I think you missed the point. The user is NOT developing a game. They want to create an IDE.
-
MehGerbil wrote:
Given that I chose Silverlight for 3 reasons:
1: Forces asyncronous processing which is were the world is going anyways.
2: Best fit for preparation for porting to Window RT.
3: Ease of distribution (unless the game is going to be played only on local network).Errr...I think you missed the point. The user is NOT developing a game. They want to create an IDE.
-
MS does a lot of things that are not rational.
Wout
Irrational is very different from just plain stupid.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
I have been thinking of building a game development studio for some time, and have decided to bite the bullet and learn WPF for creating the UI. Anyone have any gotchas I need to look out for? (I am using VS2012 with .NET 4.5 and C#.) I am mostly basing the application off of SharpDevelop 4.2, so there will likely be several overlaps in the codebases. Edit: As several people seem to have read the above wrong, I am saying that I am building a Game Development Studio, not an actual Game.
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a
I guess it depends on, what kind of games should be designed using this studio software. If they should be cross platform, it could not be a good idea that the studio with its editors runs only on windows machines. What should be the key components of the studio? Should it be used as a kind of level designer or should it also be used as an ide for creating the games code? What kind of engine / framework will be running the games designed with the studio? I'm currently working a lot with WPF and I can say that sometimes I wish, I would have chosen winforms for the ui part of our application.
-
At this point I'd be a bit concerned about putting time into WPF. I say that as a Silverlight developer. Apparently those who've done comparisons have reached the conclusion that Silverlight more closely matches what we'll have available in WinRT - and given that Silverlight provides web distribution, enforces async processing, and may run out of browser with all the characteristics of a desktop application I think there is a strong case to be made to pick it over WPF.
I don't get that. WPF is a very stable tool and the default technology for desktop .NET development. Silverlight, on the other hand, is as good as dead. No new versions will come out and it's only a matter of time before it isn't supported any longer.