Skip to main content

Malcolm McRoberts

Malcolm McRoberts's Public Library

  • WET solutions, which is commonly taken to stand for either “write everything twice” or “we enjoy typing

  • Use a capture variable for this when using the controllerAs syntax. Choose a consistent variable name such as vm, which stands for ViewModel.
    • Application Structure LIFT Principle



      [Style Y140]
      • Structure your app such that you can Locate your code quickly, Identify the code at a glance, keep the Flattest structure you can, and Try to stay DRY. The structure should follow these 4 basic guidelines.


        Why LIFT?: Provides a consistent structure that scales well, is modular, and makes it easier to increase developer efficiency by finding code quickly. Another way to check your app structure is to ask yourself: How quickly can you open and work in all of the related files for a feature?


        When I find my structure is not feeling comfortable, I go back and revisit these LIFT guidelines

        1. Locating our code is easy
        3. Identify code at a glance
        5. Flat structure as long as we can
        7. Try to stay DRY (Don’t Repeat Yourself) or T-DRY
Aug 19, 15

"iSirona becomes a part of NANTHEALTH"

  • iSirona becomes a part of NANTHEALTH

    • JIRA Portfolio Logo 

      Connect strategy to development reality


      JIRA Portfolio provides a single, accurate view for planning and managing initiatives across multiple teams and projects in JIRA.

  • I dont think it would be a simple process. You would need to change the structor, classes and ids of your HTML.


    For example if you wanted a dropdown menu you will have something like this.

    <div class="dropdown">   <a class="dropdown-toggle" data-toggle="dropdown" href="#">Dropdown trigger</a>   <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel">     ...   </ul> </div> 

    If you wanted to use Foundation you would need to change the HTML to something like this.

    <a href="#" data-dropdown="drop1">Has Dropdown</a> <ul id="drop1" class="f-dropdown" data-dropdown-content>   <li><a href="#">This is a link</a></li>   <li><a href="#">This is another</a></li>   <li><a href="#">Yet another</a></li> </ul>

    Obviously the CSS would be different but I imagine you expect that from migrating.  One other thing I can think of is that foundation uses Sass and not less like bootstrap so if you have written any less that will need to changed to Sass.

  • app.use(express.static('public'));
  • pp.use(express.static('public')); app.use(express.static('files'));
  • app.use('/static', express.static('public'));

  • Add

    process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

    in code, before calling https.request()

  • var express = require('express'); var things = []; var app = express(); var admin_app = express(); var port = 8080;  var admin_port = 8081;'/factory/', function(req, res) {  //Create a thing and add it to the thing array });  //Assume more functions to do to things here....'/killallthings/', function(req, res) {  //Destroy all the things in the array });'/listallthings/', function(req, res) {  // Return a list of all the things });'/killserver/', function(req,res){  //Kills the server after killing the things and doing clean up });  //Assume https options properly setup.  var server = require('https').createServer(options, app);  server.listen(port, function() {  logger.writeLog('Listening on port ' + port); });  var admin_server = require('https').createServer(options, admin_app);  admin_server.listen(admin_port, function() {  logger.writeLog('Listening on admin port ' + admin_port); });

  • Introduction

    This tutorial is meant as a quick-start guide to using NANTHealth's UI framework, Plato.

    Plato is the successor to ndoXdm. It is based on AngularJS, and uses Twitter Bootstrap components and CSS classes for the front-end.

  • Switching from Bootstrap to Zurb Foundation

      <!-- <br /> -->   

    I’ve just updated my site’s HTML/CSS and moved from Twitter Bootstrap to  Zurb Foundation. This post captures my subjective notes on the  migration

  • because I’d kept most of my custom CSS in a separate  file, it was literally a case of swapping out one framework for another and  bug-fixing from there onwards
  • Customising the styles was another area of concern but I was pleasantly  surprised to find I needed less customisation than with Bootstrap. This  is likely because I didn’t have to override as many defaults (and probably  because I’ve learned more about CSS since then). The one thing I seemed to  be missing was a way to deal with code sections, so I just took what  Bootstrap had and copied it in. At some point I should revisit this.

3 more annotations...

    • 3. 12-column grid system
       When it comes to frameworks, a grid system is what gives you the power to lay out your website or app.


      Both frameworks have:

      • Rows and columns
      • Ability to nest columns in rows, and vice versa
    • 4. Stylized CSS components
       Bootstrap and Foundation both come with pre-styled, ready-to-go components.


      A few of these include:

        • Navigation bar
        • Buttons
        • Pagination
        • Labels
        • Progress bar
        • And more
  • Browser support Chrome (Mac, Windows, iOS, and Android)Safari (Mac and iOS only)Firefox (Mac and Windows)Opera (Mac and Windows)IE8+ Chrome (Mac, Windows, iOS, and Android)Safari (Mac and iOS only)Firefox (Mac and Windows)Opera (Mac and Windows)IE9+

1 more annotation...

  • This rubygem does not have a description or summary.

1 - 20 of 1980 Next › Last »
20 items/page

Diigo is about better ways to research, share and collaborate on information. Learn more »

Join Diigo