This is for anyone who has to build an AngularJS application that needs to support IE9 and below.
Today we launched a new productivity app for Mac OS called Filedart (filedart.com). Filedart allows users to share files and screenshots in seconds. Drag a file or take a screenshot and your file is on the cloud. A URL is instantly in your clipboard, ready to be pasted into chat windows, emails, or sharing tools. On the receiving end, users click on the URL link to access the file or image in their browser. No sign in or registration is required.
This isn’t a new concept, but we think we’ve done it better. We intentionally kept the feature set minimal, focusing on design and usability. As we developed the tool, we made frequent use of Filedart for collaboration. We darted screenshots of the product page, various iterations, of the logo, nightly builds, and marketing strategies. It quickly became apparent that we were settling into a new way of working. After a few tosses, using Filedart becomes as intuitive and natural as Copy/Paste. While you don’t need Copy/Paste to work on a Mac, most of us would hate to go without. Filedart starts to feel the same way.
In terms of privacy, we don’t request user data and promise not to peek at your files. We don’t know who you are, and we are not interested in snooping. Ultimately we hope that the tool we created is useful, reliable, and secure.
We would love to hear your feedback on how to make Filedart better – just email us at email@example.com. Happy darting!
Web users never like to wait for a website to load. As a software company, a long wait time can result in losing potential clients. One of the tricks that can speed up the loading of your website is the optimization of your images. There are several free tools that you can use for this. Here are five that I recommend.
Recently, I had the opportunity to work on an exciting in-house project for Grio called Filedart. This service, which will launch in the near future, affords the denizens of the web the ability to effortlessly upload content to the cloud by dragging photos or files to a small icon in their taskbar. After the file is uploaded by the client, the service automatically copies a mini-fied URL to the client’s clipboard. This URL leads to a brand-new, public web hosting wrapper for that file that they can easily distribute to their friends of colleagues to share. The service is free, and users don’t even have to log-in to use it.
Here at Grio we strive to constantly improve the quality of our software. But what exactly does that mean? Is there a way to measure software quality? What are the metrics? What are the tools needed for this endeavor?
By now, my post on unit tests influenced you so much that now you have 100% unit test coverage. But yet, some functional bugs still creep in and you still get the dreaded “It’s a bug because you didn’t build what I wanted” bug.
So let’s take a look at acceptance tests and how they can you help you improve your external quality and your compliance with product requirements.
A few weeks ago I had to deal with setting up a cron job that periodically updated some db tables of a Ruby on Rails application running on Heroku. Here’s a brief step-by-step tutorial to make your life easier in case you were approaching the same task.
Over the years, I’ve used a variety of editions of Eclipse with a variety of plugins. These days I try and minimize all of that and ask Eclipse to do as little as possible as infrequently as plausible. The below is a diary of sorts of the events that led to that choice.
A selection of ways Eclipse has failed me:
- It lies about custom key bindings being set, doesn’t actually set them despite indicating it has, and stores the bindings in the robust and never problematic Java-properties+XML standard format resulting in configuration files that look like this:
org.eclipse.ui.commands=<?xml version\="1.0" encoding\="UTF-8"?>\n<org.eclipse.ui.commands>\n<activeKeyConfiguration keyConfigurationId\="org.eclipse.ui.emacsAcceleratorConfiguration"/>\n<keyBinding commandId\="org.eclipse.jdt.ui.edit.text.java.search.references.in.project" contextId\="org.eclipse.ui.contexts.window" keyConfigurationId\="org.eclipse.ui.emacsAcceleratorConfiguration" keySequence\="COMMAND+SHIFT+V"/>\n<keyBinding commandId\="org.eclipse.ui.window.previousPerspective" contextId\="org.eclipse.ui.contexts.window" keyConfigurationId\="org.eclipse.ui.emacsAcceleratorConfiguration" keySequence\="ALT+COMMAND+CTRL+ARROW_LEFT"/>\n</org.eclipse.ui.commands>
Normally I could care less what format software stores its config files in, but despite the braindead format I’ve still had better luck editing this file by hand than trying to get Eclipse to handle it correctly. If your config file format is too error-prone for your software to handle, maybe it’s time for a change.
Recently I started work on an iOS game. I decided not to use the Core Animations framework provided by Apple and instead experiment with some third party game engines. I chose Cocos2D as it is an all in one package. It gives you the ability to add and control sprites, add cool graphics and animations, access to a sound engine and also 2 physics libraries.