So we were creating an AngularJS app as the front-end for a Salesforce community. We used VisualForce remoting to get the data while in Salesforce. But we didn’t want to muck around having to constantly deploy assets into Salesforce during development. So, we came up with a pretty effective way of allowing front-end designers/dev’s to work outside of salesforce without having to modify the app when it was plugged into salesforce. Here’s how… Continue reading “Effectively working with AngularJS in and out of Salesforce” »
Here’s something about how to create a filter plugin for the jquery datatables plugin and then test it using qunit.
So, the last post talked about the hubspot set up. This part talks about how we used grunt to automate certain aspects of the build process.
Recently, we’ve started using Hubspot, which is a service that helps companies with their inbound marketing. It provides a content management system (which they call a ‘content optimization system’ :p) that can be hooked in to fairly easily. For me, its syntax is very similar to twig, a popular php templating language. It provides control structures, filters, functions etc. There’s some nice bits and some truly flakey bits – here’s what I’ve learnt so far…
I recently had to do some work with a flat html site that, previously, required loads of copying and pasting identical bits of html (headers, navs, footers). This quickly became tiresome so I turned to good-ol grunt.
I’m trying to follow john papa’s excellent angular design principles article. One aspect to this is setting up routes that resolve service calls that can immediately be called by controllers using the ‘controllerAs’ syntax. However, the question arises of how to test these? After trawling round loads of different articles, I’ve cobbled together a solution that works (for better or worse).
This post is a continuation of this one about setting up FOSRestBundle. The issue is that by default, the REST API that is created is accessible to anyone. For my angularjs app though, I only want the app to be able to access the API, no one else. Otherwise, external sites could hi-jack my API to get data from providers like Amazon. Since these usually have some kind of throttle on them, the API needs securing.
This post is about getting to grips with foundation, a responsive framework based on SASS. I’m trying to build in mixins that will allow a default desktop stylesheet to be generated for IE7,8, and a mixin to accommodate IE7’s lack of support for box-sizing.