Using DataTable with Editable plugin - Getting the data source via ajax request HomeWiki Preamble DataTable Editable plugin works with DataTables that dinamically read cells that should be displayed via ajax call. In this example, cells are not placed in the source of the page - they is loaded from the server-side via JSON request. Live example Processing... Showing 1 to 10 of 57 entries Initialization code In the initialization code you will need to pass URL of the data source that contains data that will be loaded. Additional HTML code Html code is same as in the other cases, however you will need to add one change into the "Add" form. <! Other examples
Don’t design like a programmer, part 2 « User Experience Design Training & Consulting–UX Design Edge In my original Don’t design like a programmer post, I explored a common UI design trap that programmers often fall into, where you have a data structure, map that directly to a UI, and expect the results to be a good user experience. Sometimes that approach works just fine, but often it does not. The original post explains the potential usability problems in detail. This is an easy trap to fall into if you are thinking about the code instead of your users. As a developer myself, I’m very sympathetic here. Someone named pankratiev put a link to that post on Y Combinator Hacker News and my site traffic just exploded—so much that my web host couldn’t handle it. I will start that challenge with this post. First, the original designs Here’s the first UI in the post: Actually, I didn’t say this was a bad design—rather I showed how this UI is a direct mapping of this data structure: struct UserOptions { bool Option1; bool Option2; String Option3: String Option4: struct RetrevalOptions { bool NoClobber;
Chapter 21, The Basics of Composition For centuries there has been a link between art and mathematics. For centuries there has been a link between art and mathematics, but how can you quantify beauty? How can you create a formula for aesthetic appeal? Philosophers, mathematicians, architects and artists have tried to answer these questions for thousands of years. During art college I was subjected to a lecture on the Golden Section, (who remembers that lecture, come on hands up?) The Golden Section Many theories on aesthetic measurement have their basis in numerical patterns that occur naturally such as the proportions of the human body, for example the distance between your elbow and the tip of your fingers compared to the distance between your elbow and your wrist. The Golden Section, Golden Ratio, and the grandiose Divine Proportion are all names for the same thing; a ratio of 1.618. Throughout art school I was taught to ‘feel’ my way round composition. The Rule of Thirds Looking Room Think back to last night. Basic Framing
Butterick’s Practical Typography This is a bold claim, but I stand behind it: if you learn and follow these five typography rules, you will be a better typographer than 95% of professional writers and 70% of professional designers. (The rest of this book will raise you to the 99th percentile in both categories.) All it takes is ten minutes—five minutes to read these rules once, then five minutes to read them again. Ready? Go. The typographic quality of your document is determined largely by how the body text looks. That’s it. Then, if you’re ready for a little more, try the summary of key rules. If you’re ready for a lot more, start at the foreword and keep reading.
Mobile First With Bootstrap 3 Ok so a couple of weeks now, on it's very own two year anniversary Mark Otto and the rest of the guys responsible for the develop and maintenance of Bootstrap announced the official release of the framework's third version, and it came on steroids, let's see what we're getting. What's New? First off, the most important changes you're going to find in the new Bootstrap release is the support for responsive websites, as a matter of fact the responsive module has been removed. Now, from its core, Bootstrap is responsive, more than that, this new version comes with the approach of "Mobile First", meaning that almost everything has been redesigned to start from a lower screen size and scale up (more on that in a bit). Nearly everything has been redesigned and rebuilt to start from your handheld devices and scale up. In the look and feel you'll see a lot of changes too, prominently the fact that the whole style has gone flat, and there's an optional theme for a 2.0-er look. Grid System Forms
Dependency Injection Inversion - Clean Coder Dependency Injection is all the rage. There are several frameworks that will help you inject dependencies into your system. Some use XML (God help us) to specify those dependencies. Others use simple statements in code. In either case, the goal of these frameworks is to help you create instances without having to resort to new or Factories. I think these frameworks are great tools. Consider, for example, this simple example using Google’s Guice framework. public class BillingApplication { public static void main(String[] args) { Injector injector = Guice.createInjector(new BillingModule()); BillingService billingService = injector.getInstance(BillingService.class); billingService.processCharge(2034, "Bob"); } } My goal is to create an instance of BillingService. Oh ho! And here’s the magic module that tells Guice how to create the arguments for the BillingService Clever these Google-folk! Isn’t that cool! Well, yes it’s cool. Why is this worse? I don’t want to write a Guice application.
SOLID: Liskov Substitution Principle • SoftwareYoga This is the third in the series of posts on SOLID Software Principles. We previously covered the Single Responsibility Principle and the Open-Close Principle. In this post, I will take you through the L in SOLID, the Liskov Substitution Principle. The primary idea behind the Open-Closed principle is achieved using inheritance i.e. introduce new classes for new functionality and keep the classes related to existing functionality untouched. The Liskov Substitution Principle is a simple yet effective way to improve the code. Originally written by Barbara Liskov, It states: If for each object o1 of type S there is an object o2 of type T such that for all programs P defined in terms of T, the behavior of P is unchanged when o1 is substituted for o2 then S is a subtype of T More simpler definitions have arisen since the original paper and they go as: That sounds simple enough, but there is more than meets the eye. Signatures requirements Contravariance of method arguments in the subtype Example
oop - HAS-A, IS-A terminology in object oriented language