I didn't really like the first one. The middle one's metaphor was sort of weak - playing the piano can be considered "play."
The last one is awesome, though. ![]()
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
I didn't really like the first one. The middle one's metaphor was sort of weak - playing the piano can be considered "play."
The last one is awesome, though. ![]()
57 seconds ago, PopeDai wrote
Personally I'd have preferred it if Nokia had a nomenclature like "Lumia 920 CDMA" or "Lumia 820 for T-Mobile".
AFAIK, Verizon had a crappier Nokia WP while AT&T got the shiny 920. The 928 could be just be for making Verizon users feel like that they got the latest and greatest rather than a late phone model.
15 minutes ago, Srikanth_t wrote
Lumia 928....really ? really ?
Yes. Did you think they'd make only one phone a year?
The rest of your post has to do with the software, which doesn't need to change for every hardware release, and thus, isn't really relevant.
However,
Missing custom fields
what exactly do you mean by this?
I think Windows 8 works just fine for general app development questions. WinRT tends to bring up stuff related specifically to the API.
11 hours ago, Charles wrote
but it will be interesting to see how long it does live...
Do Operating Systems ever die? When you power a machine off, you don't SEE the OS, but for all we know, it could be having a party behind your monitor. ![]()
@spivonious: I'd assume you could just ignore the multiple resolutions and keep the current snapped view/non-snapped views for backwards compatibility. While there might be a way to subscribe to the resolution changes, I don't think it will be front and center. They might want devs to think in as few different modes as possible (like snapped, half, full) so it doesn't become a mess with too many layout changes.
2 minutes ago, Sven Groot wrote
And how do you do static pages with Razor? I want them to be able to use the global layout, so I do plan to convert the static pages to .cshtml. But it seems you can't just serve static .cshtml files without a controller serving them up as views.
Well, if you tried to render a view without a controller, you'd be breaking out of MVC. Not sure how you'd use the global layout outside of MVC...seems like a lot of internal plumbing that you would have to manually execute somehow.
I don't think you could do much with the codebehind pages w/o modifications...the only way to serve them up properly so that they still work would be through an iframe. But then, you'd still have to modify those pages to strip out the menus and surrounding chrome.
My suggestion for the static pages still stands...you could just use jquery to load in something like the #contentInner section div into your MVC view (just have one view based on id). You wouldn't have to modify each static page in that case.
You could leave the pages as they are, but then have a /Software/{id} view, in addition to ketch's /Software/index view. Have the details view showing a lot of info about the software and have a link pointing to that software's static page.
Your "hackish" suggestion would work too...I actually did something similar in a project recently. Instead of showing details, you just have a div on the page and javascript somewhere that does $("div").load("", "mysoftwarelink"); MVC will set mysoftwarelink based on the {id} parameter, and the client browser will pull the relevant pages on load.
@felix9: Yeah, that's what I was referring to. Sweet. I think all that's left in terms of the start screen is discoverability of corner actions and swipes.
Looks awesome! Very clean, too. I love Knockout, even though you haven't really used it on that main page. I'll hav to take a look at Foundation...I've been mostly doing responsive layouts by hand pulling in and out CSS.
Just out of curiosity, have you looked at WPF lately (the current state of desktop development)? I picked it up again after a few years and I'm just amazed at just how nice and simple (albeit, after a slight learning curve) it is to create a good user experience. Module injection through Prism is just wonderful. Trying WPF now gave me that same feeling I had when I recently dabbled with the modern web frameworks/paradigms. You really get that sense of "I can focus on the user experience independently from the logic"