In Part One of this AngularJS Nuts and Bolts series, I discussed the concept of Form Controllers, and showed how they can be used effectively for Form Validation. This post will continue the discussion, focusing on an add-on module for AngularJS called ngMessages.
Typically, when someone gets started with AngularJS, there’s always the simple example that they are presented with showing a text box of some sort, and then a span tag somewhere below that are both bound to the same underlying ng-model. But this only scratches the surface of a very rich architecture underneath! In a series of articles, starting with this one, I’m going to cover some aspects of AngularJS that any newcomer should make themselves aware of if you are going to build real-world applications beyond “Hello World”.
We will start with Form Controllers.
If you’ve used the designer view while editing XAML files and you prefer the dark theme for Visual Studio 2012 / 2013, you’ve probably run into this problem:
In the default dark color scheme, the design window is too dark to see anything without modifying your code to add an unnecessary background. No need to modify your code.
Bring up “Extensions and Updates” under the TOOLS menu, click on the “Online” section, and search for “theme editor”. Install Visual Studio 2013 Color Theme Editor.
After a restart, you’ll see a “Color Themes” tab. Click on the icon in the top right of the Dark theme to make a copy of the theme. Name it however you wish and use the pencil icon to edit the theme.
In the top right, search for “artboard”. Set the colour of the Cider -> ArtboardBackground to FFFFFFFF and set ArtboardSecondaryBackground to FFEEEEEE. You’ll get a nice white checkerboard pattern from now on after you save the theme and apply it (click on the theme in “Color Themes”).
Based on the first comment by yAak on this post about using a style in your solution to force a white background in the designer.
Anyone who works in the IT industry will tell you that nothing is ever static. One has to keep up their skills and stay abreast of the newest developments and changes to the tools we use to get the job done. Every 18 months, things change. There is always something that I like to call “The New Shiny”.
So two questions arise:
- Where do I start?
- How do I learn the ins and outs of “The New Shiny”?
While I do not claim to be a guru, I have been called “a learning machine”. Read on to see how I tackle the challenge of learning new things in my personal development process.
I bought a Surface Pro 3 Core i7 512GB and returned it within a week. This is a device I wanted to love. Read on to hear about the the pros and cons of the device, why I returned it, and whether I think you should buy one.
By Daniel H. Pink
Original Source: The RSA Animate: ‘DRIVE – The Surprising Truth About What Motivates Us’
Arrogance is not inspiring. But why is arrogance common on I.T. project teams? Why do self-proclaimed experts abound, even though we know this is poisonous on a high-knowledge project? Jeffrey Way has an explanation …
Read More »
If you’ve ever been in a management or leadership role on a project (and yes, there is a distinction between management and leadership), I’m sure this list will resonate with you. This is a compilation of published Lessons Learned by Derry Simmel, a North Carolina project manager.
These are the 10 most common Lessons Learned by enterprise project teams, as reported and published by their PM Offices.
1. The people we had were great; there just weren’t enough of them.
2. We left management and planning unattended for too long.
3. Unclear roles and responsibilities led to confusion and loss of precious time.
4. We had the most success when we were all informed.