Touch - JavaScript Mobile Framework for Building HTML5 Web Apps DHTMLX Touch is a free open source JavaScript library for building HTML5-based mobile web apps. It's not just a set of UI widgets, but a complete framework that allows you to create eye-catching, robust web applications that run on iOS, Android, and other mobile platforms. Syntax DHTMLX Touch framework offers intuitive object inheritance. You can define an object with properties, some of which are objects or arrays of objects, and some are simple strings or numbers. Extendable Functionality DHTMLX Touch provides an elegant and simple solution to extend and customize the existing functionality of the library and to add new UI components. Data Storage on the Client Side Global data storage is an advanced and useful feature that allows keeping relations between data elements (e.g. list of employees and employee details form) on the client side. This feature provides automatical update of data across UI elements without user intersection. Server-Side Support Development Tools Compatibility Support
The top 9+7 things every programmer or architect should know I recently finished 97 Things every programmer should know. Well to be completely honest I did skim over a couple of the 97, but all and all this was a very nice compilation of thoughts and topics about software development from very experienced authors. Well worth a read. A couple of the “97 Things” discussed, stood out more than the others, the following would be the ones I rank as my top 9. 1. The Boy Scout Rule – Robert C. To be honest this is not something I have followed throughout my career, and although I certainly try improve code where I can, I never did it per check-in. I work in a corporate environment were applications often last for 4-10 years. 2. Over the years this has become particularly important to me. 3. 4. 5. 6. “If you are trying to be focused and “productive” for more than 30 hours a week, you are probably working too hard.” I couldn’t agree more with Olve Maudal. 7. 8. 9. Previously I commented on the 97 Things every programmer should know. 1. 2. 3. 4. 5. 6. 7.
GitHub - teamcapybara/capybara: Acceptance test framework for web applications LimeJS HTML5 Game Framework Agile Software Development: 10 Key Principles of Agile Software Development Agile is one of the big buzzwords of the IT development industry. But exactly what agile development? Put simply, agile development is a different way of managing IT development teams and projects. The use of the word agile in this context derives from the agile manifesto . Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.” Ever since then, the use of methods that support these values has become increasingly popular. From my use of various agile methods, I have written about 10 key principles of agile. 1. 2. 3. 4. 5. 6. 7. each feature before moving on to the next 8. 9. 10. There are various methodologies that are collectively known as agile, as they promote the values of the agile manifesto and they are consistent with the above principles. Kelly. See also:
CruiseControl Home AmplifyJS - A Component Library for jQuery The New Methodology In the past few years there's been a blossoming of a new style of software methodology - referred to as agile methods. Alternatively characterized as an antidote to bureaucracy or a license to hack they've stirred up interest all over the software landscape. In this essay I explore the reasons for agile methods, focusing not so much on their weight but on their adaptive nature and their people-first orientation. Probably the most noticeable change to software process thinking in the last few years has been the appearance of the word 'agile'. This new movement grew out of the efforts of various people who dealt with software process in the 1990s, found them wanting, and looked for a new approach to software process. This essay was originally part of this movement. My conclusion then, which I still believe now, is that there were some fundamental principles that united these methodologies, and these principles were a notable contrast from the assumptions of the established methodologies.