If you're attending Philly ETE this week, be sure to check out our mobile apps.
Monday, April 9, 2012
Sunday, April 1, 2012
Notes from the Phorum -- Cloud means something a little different to everyone
Enterprise
Enterprise users get dinged for cloud-washing: buying VMware and saying they're running a cloud. But many of them do want to offer a "private cloud". Some of the differences? Automation, standard cloud "machine" configurations, self-service provisioning, a single cloud for all business units, calculating runtime costs and charging projects for them. Some of the obstacles? Lack of automation in existing processes, trying to bring complex legacy applications on board, trying to migrate existing staff and tools "to the cloud". A key recommendation was when building a private cloud, start it as a totally separate effort that offers capabilities to the business, and strive to reach the point where they will go to you instead of a third-party cloud.But why run a private cloud? The number one reason the business prefers the cloud is that it facilitates speed and agility -- effectively taking much of the budgeting and procurement out of a project. And if you try a project and it doesn't work, you shut down the cloud instances and wash your hands with much less regret. As for IT, a well-implemented private cloud can further increase the utilization of hardware over virtualization alone, and the automation allows fewer administrators for the same quantity of hardware. Plus you're offering the business capabilities, instead of hurdles.
Along those lines, there was significant discussion of the changing role of IT as a business moves more toward the cloud. Instead of the detailed management of servers, virtualization consoles, and execution environments, it becomes managing multiple sets of capabilities -- one-off hardware required for legacy applications, virtual machines, private cloud, public cloud, etc. While you might promote the cloud for mainstream projects, there will always be some with special requirements that place it somewhere else along that spectrum, and the goal is more to shepherd each project to the right home.
With all that said, there was a lot of enthusiasm for public cloud offerings. While the security of a public cloud service is still the number one concern, even among businesses that are using the cloud, there were many arguments made that such concerns are no longer insurmountable. Cloud vendors have fewer hardware and software platforms to maintain, and more motivation to do it right (given the cost of a failure). Plus there's no guarantee that internal employees are less likely to make security mistakes. "Do you truly believe your company manages their machines better than the next company? How about, better than a vendor whose business is the cloud?"
Startups
On the other hand, one attendee quipped, "the only thing Enterprise is to me is a rental car company." The advice to startups came from a totally different direction. Use the cloud in every possible way -- only be smart about it.On Software as a Service: Why buy a box of software and a machine to run it, when you can use a lower-cost online service that you don't have to manage and gives you regular feature updates automatically?
On Infrastructure as a Service: No VC will fund you if your business plan shows boxes instead of Amazon.
On Platform as a Service: You could come up with specific requirements, build the perfect software, find the ways to customize it just like you need, and integrate it with other systems. But we've done that already and poof! this great platform emerged. Why not just take advantage of that instead? (Granted, this was SalesForce.com talking.)
In fact, one of the challenges quoted was that there are so many good-looking services that are easy to adopt, you may find yourselves three months down the road before you realize it's not really what you want after all. So the pearl of wisdom was to define your requirements well in advance, and then find the right combination of services to support them. Another was to think carefully before you start custom-integrating all these services. You're better off changing your process to fit the service than spending truckloads of time on custom integration. Plus there are companies out there who do that already.
Developers
Of course you can build applications for the cloud. But one point was to realize that's what you're doing going in. You won't necessarily have multiple machines on the same network segment (or even with multicast capability at all!), different "identical" machines may perform differently, machines or resources may go down at any time, common services like e-mail might not be available, you may be limited in what database it's convenient to use, and so on.And the cloud isn't automatically cheaper -- in many cases you have to be careful about shutting machines down whenever they're not really in use in order to realize the potential cost savings. (As an aside, one blog breathlessly proclaims that Amazon has reduced the EC2 price-per-compute-unit by 15% over the course of six years. Conveniently overlooked: Moore's Law suggests that you should receive 1600% more hardware power per dollar over the same period of time.) In other cases, the time and cost savings comes from adopting a runtime platform instead of cloud infrastructure (a VM).
Final Thoughts
Overall though, the message was largely the same for everyone -- there are benefits to be reaped from the cloud, but you have to be wise about it. Plan first, don't just meander toward the cloud and assume you'll get to the right place in time. you may, but it may be a lot more time than you're counting on.Monday, March 26, 2012
Breaking: Android Philly ETE Application Released
Wednesday, March 14, 2012
What is Chariot Day?
Some of the things that make Chariot Day a big success are:
Content -- The sessions range from highly polished, conference-ready presentations to less polished, more impromptu "stunt coding", but the one thing that is common is the high quality of the content. The reason the content is so good is that it is very evident that the developers are passionate about the technologies they are talking about. I get excited about things at Chariot Day because the presenters are so excited. This year's topics were:
- Building Real-Time Web Applications
- Real world Hadoop
- Programming Environments Designed for Children
- jQuery Mobile + Backbone.js
- Griffon - Making Java Desktop Development Groovy
- Scala
- Sencha Touch
- Tech Radar
- ByteBuffers and Off Heap Memory
- One month with Arduino
- NoSQL: Cool vs. Real
- Andriod 101 (lab)
- Partitioning & Scaling Batch Processing to the Cloud
- CPU Caches
- Introducing KIF
Participation -- We had 38 attendees and 15 presentations. We ran 3 concurrent tracks of presentations all day. That represents about 90% of the consultants attending and a little less than half presenting. It is exciting that that many people came and were willing to present. It is really valuable to get up in front of your peers and tell them about technologies you think are important.
Fun Factor -- There was breakfast, lunch, and snacks served and the food was quite good. We have a special "limited edition" Chariot Day t-shirt designed and printed each year. This year's shirt was really cool. There is a book buy where you can order any technical book you want and pick it up on Chariot Day. There is always some kind of interesting mad scientist project demonstrated; this year's Arduino talk featured a fully automatic Nerf gun that could be controlled via a web browser. We have a crazy Quizzo game at the end of the day with questions about topics discussed during the day. In short, it is a lot of fun.
Friday, March 2, 2012
Android 101: A Crash Course
I'm planning a dive into Android and teaching concepts along the way. At the end of my session, students will away with a simple Doctor Who app and learn about these foundation topics:
- XML layouts
- Themes, styles, drawables, & strings
- Click/event handling
- Starting a new activity
- Specifying an icon for the app
- Fragments & tablet version (if time)
Wednesday, February 22, 2012
Using jQueryMobile and Backbone.js for handling forms
Introduction
In this post, I continue the development of my basic "exercise app" that I started (and enhanced) in these posts:
- Intro to Backbone with jQuery Mobile
- Sorting Collections with Backbone.js and jQuery Mobile
- From a List to a Details View using jQuery Mobile and Backbone.js
Adding a new activity
Just like in the previous post, the first thing we need is a jQueryMobile page to hold the form content. Add the following to index.html:
Save
New Activity
In the code above, we see the typical jQueryMobile page. The main things of interest here are with respect to the anchor tag in the header div:
- Specify data-rel="back" to navigate to the previous page once the save is complete. This way whether we enter the form page from "Add" or "Edit", navigation will be handled.
- The class="ui-btn-right" moves the button to the right side of the header bar.
- The data-theme="b" causes the save button to use the blue theme.
Notice that we are using the HTML 5 input types for some of the fields. Browser support for these will vary, but worst case they will deprecate to a text input type. For example, on iOS, the date will present a native date picker, whereas on Android (or Chrome, etc.) the field will behave as a standard text input.
Now we need to navigate to the form page. This requires modifying the "Add" button on the list page.
Activities
Add
In order to transition to the form page, the href attribute on the anchor tag (i.e. button) needs to be changed to the id of the form page, as shown in line 4 above. The final step in presenting the form page to support adding exercise activities is modifying the add button click handler.
$('#add-button').live('click', function(){
var activity = new exercise.Activity(),
activityForm = $('#activity-form-form'),
activityFormView;
activityFormView = new exercise.ActivityFormView({model: activity, viewContainer: activityForm});
activityFormView.render();
});
Here we create an empty model, grab the form node, create a new exercise.ActivityFormView with these objects, and render the form. Testing at this point reveals a problem. The screen shot below doesn't look right ;)
Investigating the browsers console reveals an error: Uncaught ReferenceError: distance is not defined. This is due to the underscore template trying to access an undefined attribute of the model. The issue is described here with some work arounds. I found the easiest workaround is to provide defaults for the model, as shown below.
exercise.Activity = Backbone.Model.extend({
defaults: {
date: '',
type: '',
distance: '',
comments: '',
minutes: ''
}
});
Now the form renders properly. With the help of some CSS, we can tighten things up a little and end up with the version on the right (the CSS is part of the source code, see the links at the end of this post).
Editing an existing activity
With the template and the view already implemented, adding edit functionality is pretty straightforward. The first step is to update the href attribute of the edit button on the activity-details page.
Edit
Activity Details
As we did with the add button, this should reference the activity-form page. Now we need to add the click event handler for the edit button.
$('#edit-activity-button').live('click', function() {
var activityId = $('#activity-details').jqmData('activityId'),
activityModel = exercise.activities.get(activityId),
activityForm = $('#activity-form-form'),
activityFormView;
activityFormView = new exercise.ActivityFormView({model: activityModel, viewContainer: activityForm});
activityFormView.render();
});
If you recall, the activityId is passed to the details page view the list item click event handler. We reuse that fact here to retrieve the activity from the collection.
Time to test. Selecting an activity renders the detail page. Clicking the edit button renders the form, pre-filled with the activity details. Everything looks great.
But wait.....that screenshot was from the browser on which I am testing. We should always test on devices as well. Earlier I mentioned that we are using some of the HTML 5 input types (i.e. date). The nice thing is that iOS 5 will render a nice date picker for date types. The challenge is that the date needs to be in a specific format for that to work. The image below shows what the form page looks like on an iOS device.
Fixing the Date
No date value is showing up on our iOS device. This is a known issue. So, for iOS we need the date format as yyyy-mm-dd, while for other platforms, I prefer the date to be shown as mm/dd/yyyy. I do realize that date formats should be localized, but for the purpose of this example I would like to keep it straightforward and specify mm/dd/yyyy as the display date format. There are many options that could be pursued here, but to demonstrate some more capabilities of Backbone.js, we will modify our model to help meet our date requirements.
First, the date attribute in our JSON feed is a string. Lets convert this to a date when the data is retrieved from the server, then when we need the date, we can just manipulate it as needed. This can be accomplished several ways.
- Implement a parse method on the collection that converts the String to a Date as the data is being fetched from the server.
- Implement a method on the model that converts the date String to a Date and sets it on the model. This would then require the calling code to know to call this method depending upon the circumstance.
- Override the set method on the model, look for the date attribute, then convert it to a date as needed.
set: function(attributes, options) {
var aDate;
if (attributes.date){
//TODO future version - make sure date is valid format during input
aDate = new Date(attributes.date);
if ( Object.prototype.toString.call(aDate) === "[object Date]" && !isNaN(aDate.getTime()) ){
attributes.date = aDate;
}
}
Backbone.Model.prototype.set.call(this, attributes, options);
}
Also, update the defaults so that the date attribute is now a Date instead of a String.
defaults: {
date: new Date(),
type: '',
distance: '',
comments: '',
minutes: ''
},
While this clearly isn't the most robust date handling, it is fine for now. In a future version, this should be improved.
Next, add attributes to our model that will format the date in the ways we need it (i.e. mm/dd/yyyy and yyyy-mm-dd).
dateInputType: function(){
return exercise.formatDate(this.get('date'), "yyyy-mm-dd"); //https://github.com/jquery/jquery-mobile/issues/2755
},
displayDate: function(){
return exercise.formatDate(this.get('date'), "mm/dd/yyyy");
}
The formatDate function is a simple date formatter to meet our specific needs and can be found in the source code that accompanied this post (see link at the bottom of the post).
Now, how do we use these new methods in our view. The first thing to realize is that we pass the template JSON. The default implementation of the toJSON method of a Backbone.js model will not include these functions. Therefore, we need to override the toJSON method.
toJSON: function(){
var json = Backbone.Model.prototype.toJSON.call(this);
return _.extend(json, {dateInputType : this.dateInputType(), displayDate: this.displayDate()});
}
Here, we are using the Underscore.js extend to add our attributes to the standard Backbone JSON. Now, we need to modify our view templates to use the appropriate JSON attributes.
Notice that lines 16-21 include some conditional logic. This is a very basic device detection check to determine which date format to use. There are plug-ins,etc. that provide more robust alternatives, but to keep things clear, this will serve our needs. The screen shots below show the desktop browser and the iOS versions of the form with the appropriate date handling.
Saving
The final step is to implement the save functionality.
$('#save-activity-button').live('click', function(){
var activityId = $('#activity-details').jqmData('activityId'),
activity,
dateComponents,
formJSON = $('#activity-form-form').formParams();
//if we are on iOS and we have a date...convert it from yyyy-mm-dd back to mm/dd/yyyy
//TODO future version - for non-iOS, we would need to validate the date is in the expected format (mm/dd/yyyy)
if (formJSON.date && ((navigator.userAgent.indexOf('iPhone') >= 0 || navigator.userAgent.indexOf('iPad') >= 0)) ){
dateComponents = formJSON.date.split("-");
formJSON.date = dateComponents[1] + "/" + dateComponents[2] + "/" + dateComponents[0];
}
if (activityId){
//editing
activity = exercise.activities.get(activityId);
activity.set(formJSON); //not calling save since we have no REST backend...save in memory
}else{
//new (since we have no REST backend, create a new model and add to collection to prevent Backbone making REST calls)
activity = new exercise.Activity(formJSON);
activity.set({'id': new Date().getTime()}); //create some identifier
exercise.activities.add(activity);
}
});
I used the JavascriptMVC formParams jQuery plugin (found here) to convert my HTML form into a JSON object. Then, the date is converted into the appropriate format. One thing to note here is that since we have no real back end server for Backbone to interface with, we don't call save on the model or create on the collection. These methods would cause the appropriate REST calls to the server.
Since the click event on the list view passes the activityId to the details page, we can use this to determine if we are adding or editing. One thing to consider here is that the user may click an existing activity, then go back to the list, then click add. In this case, the activityId from the previously selected activity is still attached to the activity-details view. This will cause our save implementation to think we are editing. To prevent this, we should remove the activityId from the activity-details page when adding a new activity. This can be accomplished by adding the highlighted line below to the add handler.
$('#add-button').live('click', function(){
var activity = new exercise.Activity(),
activityForm = $('#activity-form-form'),
activityFormView;
//clear any existing id attribute from the form page
$('#activity-details').jqmRemoveData('activityId');
activityFormView = new exercise.ActivityFormView({model: activity, viewContainer: activityForm});
activityFormView.render();
});
The final step is to make sure our views are updated accordingly when we add or modify activities. Since the details view retrieves the activity before the page loads, no change is required here. But our list view only renders during the initial page load. This is where we can take advantage of Backbone event binding. A few small additions to the ActivityListView and things will be handled.
initialize: function() {
this.collection.bind('add', this.render, this);
this.collection.bind('change', this.changeItem, this);
this.collection.bind('reset', this.render, this);
this.template = _.template($('#activity-list-item-template').html());
},
...
changeItem: function(item){
this.collection.sort();
}
The change event will bubble up from the model and fires as a result of the set being called. In the changeItem method, we sort the collection to handle any changes in the date attribute. The sort method call will cause the reset event to fire, which then results in the render method invocation, causing the list to be re-rendered. This keeps everything in the correct order. The add event will be fired when we add a new activity to the collection. Since we implemented the comparator method on the collection, models added to the collection will be added in the appropriate order.
We can now add and edit activities. Start exercising :)
The source code for this post can be found here
Wednesday, February 15, 2012
Sencha Touch 2 - NavigationView, Templates and Forms
This post will build on the example application from the Introduction to Sencha Touch post. We will look at sorting, templates, navigation and forms.
Sorting
In the existing code new items appear at the bottom of the list. I’d prefer to see the newest items first. After a Sorter is added to the Store, Sencha displays records in the proper order.var store = Ext.create('Ext.data.Store', {
storeId: "activityStore",
model: "Activity",
proxy: {
type: 'ajax',
url: 'exercise.json'
},
sorters: [
{
property: 'date',
direction: 'DESC'
}
],
autoLoad: true
});
Detail View
The user should able to drill into an Activity on the list to see the details.Template
We will create an XTemplate that will be populated with the data from the Model. Templates can be created in Javascript or externalized. I prefer to put more complex templates in HTML rather than inline Javascript. Sencha recommends external templates are defined in a hidden textarea.<textarea id="detail-template" style="display:none">
<div>
Date: {date:date("m/d/Y")} <br/>
Type: {type} <br/>
Distance: {distance} <br/>
Time: {minutes} minutes <br/>
Notes: {comments} <br/>
</div>
</textarea>
The template is created once in code.var template = Ext.XTemplate.from(Ext.get('detail-template'));
List item disclosure
Sencha displays a disclosure icon for each row when a function is assigned to the onItemDisclosure property of the list. Clicking on this icon allows the user to drill into the details for a row.The onItemDisclosure function
- receives the selected record as an argument
- populates the template with the model’s data
- creates a new panel
- pushes the panel onto the navigation view
{
xtype: 'list',
title: 'Activities',
itemTpl: '{date:date("m/d/Y")} - {type}',
store: store,
onItemDisclosure: function (record, btn, index) {
view.push({
xtype: 'panel',
title: 'Activity',
html: template.apply(record.data),
styleHtmlContent: true
});
}
}
Pushing the panel onto the NavigationView handles a lot of stuff. The view becomes visible, the navigation bar title is set, a back button is displayed, navigation is handled automatically. This is a nice new feature in Sencha Touch 2.0.
Showing and hiding buttons
When the user is viewing the details, the Add button should disappear. We can manually hide the button in the onItemDisclosure before pushing the view.onItemDisclosure: function (record, btn, index) {
view.down('#addButton').hide();
view.push({
// ...
The Add button needs to be shown again when the user navigates from the detail back to the main screen. Since the NavigationView handles the navigation automatically, we listen for the pop event and make the Add button is visible.var onNavigationPop = function(v, item) {
v.down('#addButton').show();
};
var view = Ext.create("Ext.NavigationView", {
fullscreen: true,
items: [
// ...
],
listeners: {
pop: onNavigationPop
}
});
Similarly, we can add onNavigationPush to hide the Add button whenever we push a new view on the stack. This is better than hiding the button in onItemDisclosure.var onNavigationPush = function(v, item) {
v.down('#addButton').hide();
};
var view = Ext.create("Ext.NavigationView", {
fullscreen: true,
items: [
// ...
],
listeners: {
pop: onNavigationPop,
push: onNavigationPush
}
});
view.getNavigationBar().add([
{
xtype: 'button',
id: 'addButton',
align: 'right',
ui: 'action',
iconCls: 'compose',
iconMask: true,
handler: addNewRow
}
]);
Adding new records with a form
The current implementation puts a fake row into the store when the Add button is pressed. We want to display a form to collect the user input.We are going to change the implementation of addNewRow to create a FormPanel and push it onto the view. The NavigationView destroys components as they are popped, so we recreate the form every time. Alternately we could set autoDestroy to false on the NavigationView.
var addNewRow = function() {
view.push(Ext.create('Ext.form.Panel', formBase));
};
The formBase object contains the form fields.var formBase = {
title: "Activity",
itemId: "form",
items: [
{
xtype: 'datepickerfield',
name: 'date',
label: 'Date',
value: new Date()
},
{
xtype: 'selectfield',
name: 'type',
label: 'Type',
options: [
{ text: "" },
{ text: "Run", value: "Run" },
{ text: "Bike", value: "Bike" },
{ text: "Swim", value: "Swim" },
{ text: "Walk", value: "Walk" }
]
},
{
xtype: 'textfield',
name: 'distance',
label: 'Distance'
},
{
xtype: 'numberfield',
name: 'minutes',
label: 'Minutes'
},
{
xtype: 'textfield',
name: 'comments',
label: 'Notes'
}
]
};
Saving data
The navigation bar needs a save button. Initially this button will be hidden.{
xtype: 'button',
id: 'saveButton',
text: 'Save',
align: 'right',
ui: 'action',
handler: save,
hidden: true
}
The addNewRow function makes the save button visible.var addNewRow = function() {
view.push(Ext.create('Ext.form.Panel', formBase));
view.down('#saveButton').show();
};
The save button is hidden in onNavigationPop.var onNavigationPop = function(v, item) {
v.down('#addButton').show();
v.down('#saveButton').hide();
};
The save function- gets the form using the item id
- creates an new Activity model from the form data
- adds the new model to the store
- navigates back to the list view
var save = function() {
var form = view.down('#form');
var record = Ext.create('Activity', form.getValues());
store.add(record);
// TODO validation and error handling
view.pop();
};
Note that Sencha automatically displays the new data in the list without any effort on our part.
Additional enhancements to improve this example could include things like validating form data, editing existing rows, sending data back to the server, converting to MVC.











