Let's take advantage of our Pluralsight benefits and study the course over a few weeks, then gather for beer and fellowship and open discussion on what we've learned.
Course Viewing Sessions at VersionOne (Alpharetta):
Parking: Ample parking is behind the building. Just look for signs after you park.
Pre-Event Code Showcase: Have you built something with SPA-style techniques? share your link on this page or come over a few minutes earlier with your device of choice to show others!
6:05: View lessons 1 and 2 back-to-back. Latecomer? No prob, just grab a beer, find a chair, and enjoy yourself.
7ish: 10 minute break before 3rd lesson: intros, brief discussions
7:45: Finish & clean up
GoToMeeting Remote Viewing Info: check this page around 6 pm the day of for a GoToMeeting link to watch / listen remotely.
Viewing Sessions Schedule (Alpharetta):
Thu Oct 4: (This session)
Surfacing JSON Data with ASP.NET Web API
Optimizing the Single Page
SPA Basics: Separating the Ravioli
Thu Oct 11:
Loading Views with MVVM and Knockout
Data Services on the Client
Navigation, Transitions, Storage, and Messaging (Half)
Thu Oct 18:
Navigation, Transitions, Storage, and Messaging
Saving, Change Tracking and Validation
Mobility and Responsive Design with CSS and LESS
Thursday Nov 1:
Social gathering at Manuel's Tavern in Eagle's Nest Room (far left corner up the stairs)
Learn More About Single Page Applications:
Here's an excerpt from John's blog post introducing the course:
What is a SPA?
In short, there is a great wikipedia page that explains what a SPA is, some ways to create a SPA (there is not just one cut and dry way), and some pros and cons. Definitely check it out. My cliff notes, that I include in the course, are that a SPA is a web app that fits on a single web page that provides a fluid user experience. A SPA is fully (or close) loaded on the initial page load, it’s key resources are preloaded, and progressively downloads features as required. A SPA may also persist and maintain important state on the client while also handling navigation, history and deep linking. A great examples of a SPA is gmail.
What’s the point?
The user experience is key. If you can speed up the perception of page loads and navigation for the user, you win. A SPA preloads what the user may most oft use, so when they navigate they are not making network trips and page reloads on those oft used features. Thus the result is a snappy app and a happy user.
"We are a group of .NET developers who are passionate about improving the way we develop software. We recognize there is no single solution, but instead there are multitudes of alternatives that can be applied to different situations. Our community is a place for sharing these alternatives, so that together we can learn, teach, and encourage new ideas.
- You're a developer who uses what works while keeping an eye out for a better way.
- You reach outside the mainstream to adopt the best of any community: Open Source, Agile, Java, Ruby, etc.
- You're not content with the status quo. Things can always be better expressed, more elegant and simple, more mutable, higher quality, etc.
- You know tools are great, but they only take you so far. It's the principles and knowledge that really matter. The best tools are those that embed the knowledge and encourage the principles."