| public class Widget | |
| { | |
| public int Id { get; set; } | |
| public string Name { get; set; } | |
| public string Description { get; set; } | |
| } |
| # .gitignore for ASP.NET MVC / Windows Azure development | |
| # Original file: https://gist.github.com/3318347 by @codingoutloud | |
| ## Github doc on ignoring files: https://help.github.com/articles/ignoring-files | |
| ## The man page for .gitignore (referenced by github): http://man.cx/gitignore | |
| ## Of possible interest (can be complex): https://github.com/github/gitignore | |
| # Troubleshooting | |
| # 1. If you add a .gitignore file to an existing repo (or significantly change one), you may want | |
| # to force it to act as though the new/updated .gitignore was in force the whole time. | |
| ## http://stackoverflow.com/questions/1139762/gitignore-file-not-ignoring |
| namespace YourNamespace | |
| { | |
| /// <summary> | |
| /// Uses the Name value of the <see cref="ColumnAttribute"/> specified to determine | |
| /// the association between the name of the column in the query results and the member to | |
| /// which it will be extracted. If no column mapping is present all members are mapped as | |
| /// usual. | |
| /// </summary> | |
| /// <typeparam name="T">The type of the object that this association between the mapper applies to.</typeparam> | |
| public class ColumnAttributeTypeMapper<T> : FallbackTypeMapper |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="keywords" lang="de" content="Zeitleiste, Zeitlinie, Zeitkarte, Geschichte, Chronologie"> | |
| <meta name="keywords" lang="en" content="Timeline, Timemap, History, Chronology"> | |
| <title>Timeline - Proof-of-concept</title> | |
| <!-- That's my local d3 path. When working locally, use your local path. --> |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| Versioning is an anti-pattern | |
| ============================= | |
| We often say "use the right tool for the job", but when managing change | |
| in software systems, we always use versioning. Hypermedia APIs are | |
| actually hindered by introducing versioning and manage change in a | |
| different way. With that in mind, there are also a lot of options for | |
| managing change in a Hypermedia API. We'd like to change our service and | |
| break as few clients as possible. Versioning is only one way to manage | |
| change, though... and my contention is that it's not appropriate for |
D3.js visualization of the famous polar area diagram from Florence Nightingale's "A contribution to the sanitary history of the British army during the late war with Russia".
Two works served as the inspiration for this implementation:
A few comments. Bostock's implmentation, while visually similar to Nightingale's visualization, is wrong. First, the data is not correct. You can verify this in Nightingale's original work. Second, Bostock directly maps the wedge radius to deaths. This mistake is common. Instead, Nightingale represents deaths in terms of area, thus requiring the radius for each
| 1033edge.com | |
| 11mail.com | |
| 123.com | |
| 123box.net | |
| 123india.com | |
| 123mail.cl | |
| 123qwe.co.uk | |
| 126.com | |
| 150ml.com | |
| 15meg4free.com |
| DELETE o FROM `wp_posts` o | |
| LEFT OUTER JOIN `wp_posts` r | |
| ON o.post_parent = r.ID | |
| WHERE r.id IS null AND o.post_type = 'product_variation' |
| // Move Yoast to bottom | |
| function yoasttobottom() { | |
| return 'low'; | |
| } | |
| add_filter( 'wpseo_metabox_prio', 'yoasttobottom'); |
