Wouldn't the SDK just be XNA? Well, I guess technically you can only make games with XNA but if they modified it a bit for Zune, isn't that what they would use? I think Microsoft would be in the smarts to use XNA as its Game/Application SDK because its really easy to ease into. If you are reading Microsoft... :)
Technically, you can use XNA to make any kind of app, be it a game or a real application.
XNA is a software development platform with strong points leaning towards game development. XNA at some point will become the defacto standard for zune application development, probably (least i hope, gives me more incentive to learn C#)
When we used XNA last year in class, one group was working on a paint application for the Zune...They didn't finish it, but I believe that they ended up with something somewhat impressive, just not as much as they hoped, so I knew it was possible.
The thing with XNA is that its built to run off of a "game timer" which isn't very efficient for an app that doesn't have much going on. This is why I was wondering if they would do a proprietary version of XNA for Zune.
Bytheway, C# is spectacular, with a very low learning curve(If I were to teach CS, I would definitely start with C# because of its low bar), and its very powerful. On top of that, using XNA to code for Xbox 360, Windows, and Zune is a sinch...my group coded an awesome tower defense game for the 360 in a little under 3 weeks(like 45 minutes of full gameplay, not to mention its expandability that we built in to add more gameplay and maps). That's way more efficient than a lot of other platforms out there.
i think C++ is a good starting point for a CS degree. References are easier to understand if you already understand pointers (they aren't difficult at all to follow, but also having knowledge of pointers is very helpful). Plus the jump from C++ to C# is very minimal.
The Triumph proved to be one of the better looking and performing pre-paid handsets we'd had the pleasure of holding in our sweaty mitts, but we had one major hangup: the name.
The most commented posts on Engadget over the past 24 hours.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
Wouldn't the SDK just be XNA? Well, I guess technically you can only make games with XNA but if they modified it a bit for Zune, isn't that what they would use? I think Microsoft would be in the smarts to use XNA as its Game/Application SDK because its really easy to ease into. If you are reading Microsoft... :)
There's a calculator app that was written with XNA so it could still be using that.
Technically, you can use XNA to make any kind of app, be it a game or a real application.
XNA is a software development platform with strong points leaning towards game development. XNA at some point will become the defacto standard for zune application development, probably (least i hope, gives me more incentive to learn C#)
When we used XNA last year in class, one group was working on a paint application for the Zune...They didn't finish it, but I believe that they ended up with something somewhat impressive, just not as much as they hoped, so I knew it was possible.
The thing with XNA is that its built to run off of a "game timer" which isn't very efficient for an app that doesn't have much going on. This is why I was wondering if they would do a proprietary version of XNA for Zune.
Bytheway, C# is spectacular, with a very low learning curve(If I were to teach CS, I would definitely start with C# because of its low bar), and its very powerful. On top of that, using XNA to code for Xbox 360, Windows, and Zune is a sinch...my group coded an awesome tower defense game for the 360 in a little under 3 weeks(like 45 minutes of full gameplay, not to mention its expandability that we built in to add more gameplay and maps). That's way more efficient than a lot of other platforms out there.
i think C++ is a good starting point for a CS degree. References are easier to understand if you already understand pointers (they aren't difficult at all to follow, but also having knowledge of pointers is very helpful). Plus the jump from C++ to C# is very minimal.