Archive for the 'Uncategorized' Category

Hour a day

Published on September 1, 2010 in Uncategorized. 0 Comments

I’ve adjusted my day-job work schedule a bit as of late.  Now, I’m coming in and staying about an hour later Monday through Thursday.

Why?

Because my personal projects had stalled.  I’m using that 1 pre-work hour a day to work on Todo-Board

I’ve been at it for about two weeks, and in that 8 extra hours I’ve developed more of the site than what I accomplished in the previous several months!

I’m trying to complete one small logical piece every day and it’s amazing at what time-boxing your self for one hour a day can accomplish.   One day I made a new toolbar that hovers with the notes.  Another day I optimized the logic that decides when to save the project.  Yet another I implemented the ability to share your board through links on the site.

So many people say “If I only had the time, I could do X” and then never do it.  Why not find an hour a day and do it?

It also helps that this lets me miss some traffic.

Still time to teach your reps math Verizon.

Published on August 30, 2010 in Uncategorized. 1 Comment

I remember reading a story about a guy getting overcharged one hundred fold by verizon because the rep didn’t understand the difference betwee “Point zero zero two cents” and “Point zero zero two dollars”.  They’re still making the same mistake.

This rate was just quoted to me over the phone as “Point zero zero two cents”.

I asked to see it in writing and this is what I got:

They could fix it by quoting this in MB. Nobody is going to say $2/mb wrong.

GIT

Published on July 14, 2010 in Uncategorized. 4 Comments

I’ve been working with GIT more and more lately.  It seems like it’ll make complex projects with several simultaneous branches a lot easier to work on.  I just wish there were some really good easy to use graphical clients for non-engineers.  Something like Versions for SVN/OSX would be great.

If you’re looking for a book, go with the Pro Git one.  I originally bought the oreilly book and was disappointed.

A lesson on AIR certificate signing

Published on May 6, 2010 in Uncategorized. 4 Comments

Yesterday, I created a new version of one of my AIR apps. I tested it, it looked good, so I uploaded to my distribution site. One of the tests I always do after that is to use the auto-update feature to make sure the upgrade goes smoothly for my customers. It found the update, downloaded it as usual, began installing, and them BAMN

“Air cannot install this application because the installer is misconfigured.”

Odd I thought. So I dusted off a couple virtual machine images with different versions of AIR and my application installed, and they all behaved the same.

Then I tried to upgrade by manually double-clicking the .air package and got this error: “The application could not be installed because an application with that name already exists at the selected installation location. ”

It turns out that I hadn’t made a release since last I renewed my code signing certificate. Now, last year, around this time I didn’t have any problems. I just signed the new version with the new certificate and it all worked fine. But this year, something’s different.

After some digging around, I found out I may have to migrate from my old certificate to the new one. It’s a fairly trivial process. First you create your air package with your new certificate. Then you run adt and also sign it with your old certificate. A command like this works:

adt -migrate -storetype pkcs12 -keystore ../OLDAgileAgenda.p12 -storepass MYPASSWORD -keypass MYPASSWORD AgileAgendaBC_0070.air AgileAgendaBC_0070_migrated.air

BUT. When I ran that I received an error about my old certificate being expired and I can’t use it. Oh shit. You need to migrate certificates before they expire?

Some googling around and I found the answer. Apparently this was a common enough problem that AIR 1.5.3 changed this behavior slightly. Now, you can migrate from an expired certificate, but only for 180 days after the expiration. Luckily, I’m easily within that 180 day window, but I pitty large commercial applications that go out on CD and don’t get updated that often. (About that time I got spooked since I worked on one of those.  But that’s an enterprise-level problem to be solved in an enterprise-level way at an enterprise-later date and time.)

So to update my AIR sdk I downloaded from here and followed the instructions here.

Now, my adt migrate command worked perfectly.

So I tried installing the migrated air package, and the upgrade went through perfectly.  A shot at the auto-update, and that worked as well.

But I noticed something when I ran the app.  It had forgotten all my settings.  Unfortunately, that included the registration info.  If I released like this, I know I’d have dozens of angry emails the next day with customers who can’t find their license keys anymore.  So some more googling…

Turns out, the publisher ID changes when your certificate changes.  That publisher ID is the weird string in your local settings directory.  For instance, on OSX the local settings dir for my app was ~/Library/Preferences/com.agileagenda.AgileAgenda.F49A4D8DF78A1FEE7A3BE440DC11BAB18D922274.1

Now, there was an entirely new directory being created with a different publisher ID.

After some more searching, I found out that AIR 1.5.3 also solved this problem.  You can add a publisher id tag to your -app.xml file to specify one to use, such as:

<publisherID>F49A4D8DF78A1FEE7A3BE440DC11BAB18D922274.1</publisherID>

To use that, you’ll also have to update the XML namespace at the top of the file

<application xmlns=”http://ns.adobe.com/air/application/1.5.3″ >

(NOTE: For brand new applications, don’t specify a publisher id.  They’re being phased out.  Blank is better since your config directory name will be cleaner)

After doing that, I rebuild my air package, re-signed it with the migration certificate, re-performed all my tests.  And all was good.

Hopefully, this blog post will save someone else in the same situation a lot of frustration.

Scholastic / Tomsnyder hiring in Boston area (Watertown)

Published on April 22, 2010 in Uncategorized. Closed

My employer is hiring like mad.

I’d post the descriptions here, but that would be rather long, so here’s the craigslist ads for four of them:

http://boston.craigslist.org/bmw/sof/1704769566.html
http://boston.craigslist.org/bmw/sof/1704765818.html
http://boston.craigslist.org/bmw/sof/1704758792.html
http://boston.craigslist.org/bmw/sof/1704749682.html

Please use the email addresses in those posts, and do not contact me directly. I simply can not track this volume of requests outside those channels.

Alternative “skin” for ObjectHandles

Published on April 3, 2010 in Uncategorized. 1 Comment

Today, I worked a bit on getting an alternative look for ObjectHandles working.  See the blue border in the screen shot?  Clicking the left, right, or bottom edge resizes, and the top bar moves it around.  The corners resize as expected as well.  This is s a decent compromise for when you want to have text inside a moveable object, and you still want to be able to select the text with the mouse.

Here’s how I did it.

First, I created some custom handle classes. I had three other versions, one for the corners, one for the bottom bar, and one for the vertical ones. (They probably could have been a single class with a bit of smarts to it)

Here’s the one for the top horizontal bar.

  1.  
  2. <?xml version="1.0" encoding="utf-8"?>
  3. <s:Group xmlns:fx="http://ns.adobe.com/mxml/2009"
  4.                  xmlns:s="library://ns.adobe.com/flex/spark"
  5.                  xmlns:mx="library://ns.adobe.com/flex/mx"
  6.                  implements="com.roguedevelopment.objecthandles.IHandle"
  7.                  width="{model.width + 8}" height="12"
  8.                  
  9.                  >
  10.         <fx:Script>
  11.                 <![CDATA[
  12.                         import com.roguedevelopment.objecthandles.HandleDescription;
  13.                         import com.roguedevelopment.objecthandles.IHandle;
  14.                         import com.roguedevelopment.todoboard.model.BoardObject;
  15.                        
  16.                         [Bindable] protected var hd:HandleDescription;
  17.                         [Bindable] protected var model:BoardObject;
  18.  
  19.                         public function get handleDescriptor():HandleDescription
  20.                         {
  21.                                 return hd;
  22.                         }
  23.  
  24.                         public function set handleDescriptor(value:HandleDescription):void
  25.                         {
  26.                                 hd = value;
  27.                         }
  28.  
  29.                         public function redraw():void
  30.                         {
  31.                                 invalidateDisplayList();
  32.                         }
  33.  
  34.                         public function get targetModel():Object
  35.                         {                              
  36.                                 return model;
  37.                         }
  38.  
  39.                         public function set targetModel(value:Object):void
  40.                         {
  41.                                 model = value as BoardObject;
  42.                         }
  43.  
  44.                 ]]>
  45.         </fx:Script>
  46.         <fx:Declarations>
  47.                 <!– Place non-visual elements (e.g., services, value objects) here –>
  48.         </fx:Declarations>
  49.         <s:Rect x="{-width/2}" y="{-height/2}" width="100%" height="100%" topLeftRadiusX="3" topLeftRadiusY="3" topRightRadiusX="3" topRightRadiusY="3">
  50.                 <s:fill>
  51.                         <s:SolidColor color="#0A96CA" />                               
  52.                 </s:fill>
  53.                 <s:stroke>
  54.                         <s:SolidColorStroke color="#077BA7" />
  55.                 </s:stroke>
  56.         </s:Rect>
  57. </s:Group>
  58.  
  59.  

The big difference between this and the normal handles, is that the size of the handles is dependent on the width/height of the model object, something I hadn’t tried before.

Next, I created a custom handle configuration to position them around the edges.

  1.  
  2. oh = new ObjectHandles( sprite , selectionManager);
  3.  
  4. oh.defaultHandles = [];
  5.  
  6. // Top border
  7. oh.defaultHandles.push( new HandleDescription( HandleRoles.MOVE,
  8. new Point(50,0) ,
  9. new Point(0,-2) , new ClassFactory( TopHorizontalGrabberHandle )) );
  10.  
  11. // Bottom border
  12. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_DOWN,
  13. new Point(50,100) ,
  14. new Point(0,2) , new ClassFactory( HorizontalGrabberHandle )) );
  15.  
  16. // Left border
  17. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_LEFT,
  18. new Point(0,50) ,
  19. new Point(-2,0) , new ClassFactory( VerticalGrabberHandle )) );
  20.  
  21. // Right border
  22. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_RIGHT,
  23. new Point(100,50) ,
  24. new Point(2,0) , new ClassFactory( VerticalGrabberHandle )) );                 
  25.  
  26.  
  27. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_UP + HandleRoles.RESIZE_LEFT,
  28. zero ,
  29. new Point(-2,-2) ,
  30. new ClassFactory(CornerGrabberHandle)                  
  31. ) );
  32.  
  33.  
  34. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_UP + HandleRoles.RESIZE_RIGHT,
  35. new Point(100,0) ,
  36. new Point(2,-2) ,
  37. new ClassFactory(CornerGrabberHandle)) 
  38. );
  39.  
  40.  
  41.  
  42. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_DOWN + HandleRoles.RESIZE_RIGHT,
  43. new Point(100,100) ,
  44. new Point(2,2) ,
  45. new ClassFactory(CornerGrabberHandle)));
  46.  
  47.  
  48.  
  49. oh.defaultHandles.push( new HandleDescription( HandleRoles.RESIZE_DOWN + HandleRoles.RESIZE_LEFT,
  50. new Point(0,100) ,
  51. new Point(-2,2) ,
  52. new ClassFactory(CornerGrabberHandle)   ) );
  53.  
  54.  
  55. oh.defaultHandles.push( new HandleDescription( HandleRoles.ROTATE,
  56. new Point(100,50) ,
  57. new Point(15,0) ));
  58.  

And unfortunately, at this point I realized the ObjectHandles didn’t correctly rotate it’s handles, so everything went wacky when I rotated. So a bit of tinkering around in the core library and I got that fixed.

End results:

New version of ObjectHandles posted:

http://code.google.com/p/flex-object-handles/downloads/list

Besides the rotating handles change, I’ve also made the examples build under flex 3 again, and added a submitted patch that allows you to have an isLocked attribute on your model objects. When set that, you can’t drag or resize that object.

Todo-Board.com – another shot at project management

Published on March 24, 2010 in Uncategorized. 1 Comment

I’m always looking for new ways to manage projects.  Last time I searched high and low for a solution, I ended up writing AgileAgenda after having been disappointed in other offerings.  That’s a great tool, and I use it all the time.  But it’s a very specific type of tool for planning a large body of work before you start.

I’ve grown to love using task boards at work to help plan and track an immediate set of tasks.  I’m sure you’ve seen them before, those white-board like things with sticky notes all over them.

But they have one big problem, the next project I’m working on will be distributed across a few geographic locations.  That task board is a physical board in one room.  It doesn’t scale well.

Luckily, in the office, we’ve got these great interactive whiteboards in a few of the conference rooms.  If you haven’t seen one of these, they’re essentially a projector + touch screen.  A software version of a task board combined with that would rock.  So that’s been my latest pet project.

Lets take a look at why I like the task board.

  1. Everyone can understand it.  Engineers, QA, Project Managers, the random executive walking by my office.
  2. It helps to focus work on what’s most important.
  3. It helps you to chunk out work in manageable sizes.
  4. It’s a collaborative exercise to make and maintain the board.
  5. It’s flexible.

But as soon as we move from physical to digital, some of the key benefits of the task board go away.

  1. Turns from a “us doing this” to a person using a computer to do it.  Sure everyone can watch and comment, but giving everyone a stack of stickies, and a marker really adds something.
  2. It’s not ever-present in a room somewhere.
  3. Software like this can often be tedious to use.

Some things that my current physical task board can’t do that this one should

  1. Import things directly from other systems (We use Quality Center to track requirements, I’d like to hook up AgileAgenda, Basecamp,  Rally, Trac, and whatever other service I can)
  2. Automatically reconfigure the notes based on a series of views.  Sometimes you want to see that 4 column todo, doing, reviewing, done, but sometimes you want to organize by person, or tag, or search.
  3. Get this thing on my phone.  More and more people at work are getting Android powered phones (they outnumber iPhones at least 2 to 1 in the office).  I’d love to do some android development, so this looks like a prime candidate.

Some features I’m working on to try and keep the best parts of my task board:

#HashTags

One interesting feature I’m working on is the ability to tag tasks with #hashtags, and those tags can affect the appearance of the task.  You can make up tags on the fly as you type, and later go into the tag definitions and set what the tags should do.  They can apply a few canned effects, change the color of the note, or add an icon.

Click For Full Size

@Assignments

Just like #hash tags, you can assign tasks to people on the fly as you type.  You can even make up resources on the fly and later go in and edit the details about them.

Board Views

Looking at your tasks in the columns of “Todo”, “Doing”, “Reviewing”, and “Done” is great and what most people want to do a lot of the time.  But wouldn’t it be nice if you could reconfigure your board at will?  Without losing your current cofiguration?  Board Views do that for you.  You can create a new view, set up a new organizational scheme, and then jump back and forth between your views.  You can even define tags that are specific to a view.  So, for instance, you could swap between a view showing the state of tasks, to a view that shows assignments.

Click for full size.

Click for full size.

Collaboration

While you’re in a meeting organizing your board, other people in the meeting can be typing in new notes on their laptops or (eventually) on their cell phones.  Those notes then become available for you to drag onto your board, thus bringing the multi-user collaborative experience in.

Ubiquity

I want to make this so it can become ubiquitous in an organization.  Embed the board on your Intranet, throw it on your facebook, email a copy to someone, get reminder emails, set it up in Kiosk mode somewhere, subscribe to the the RSS feed, and follow your board’s tweets.

Todo-Board.com

And thus TodoBoard was born.  As of right now the basic tag and view functionality is all working.  Next is fleshing out some of the more auxiliary features, and it should be ready for some early testers.  I should be starting to give out beta accounts within the next two weeks, sign up now to get into that first batch of people.

Trying out Mercurial

Published on March 22, 2010 in Uncategorized. Closed

After reading the mercurial guide over at http://hginit.com/ last week, I decided to give it a shot.  The guys who host my version control system offer it as an option, so it was stupid easy for me to get started.

One thing I really like is being able to have a local change history that doesn’t get pushed up to the server.  I can commit often without worrying about breaking (albeit only theoretical in my case) other people’s environment.  This way I don’t accidentally lose any local changes and I can feel free to experiment a little more wildly.

So far, so good.  But this is just a 1-person project, so I’m not sure how in depth I can get.

An experiment in funding open source software

Published on February 16, 2010 in Uncategorized. Closed

In the past, I’ve blogged many times about my ObjectHandles library, and today I’m starting an experiment in generating some revenue for it.

There is now a new web page at http://object-handles-examples.appspot.com/ that has 7 example applications intended as either a training resource, or as a starting point for more complex applications.  I’m charging a fee for the source code to those examples.  The fee is whatever you decide to pay (with a $15 minimum)

The more revenue that this generates, the more motivation I’ll have to spend time working on the core library and additional examples.

The core library will continue to remain free and under the MIT license.  It can always be downloaded from http://code.google.com/p/flex-object-handles/

There were a few reasons for me to do this including:

  1. My motivation to work on the library has been very low lately.  I don’t have any current projects that are using it.
  2. The donations link that I have has received a total of 3 donations over 2 and a half years.
  3. By working on these examples, I was able to really exercise some of the core functionality.  While doing this I was able to
  • Completely revamp the constraints mechanism and implement things like an Aspect Ratio constraint
  • Find and fix a handful of bugs
  • Figure out the answers to some questions others have asked that I just didn’t know the answer to
  • Make several big performance improvements

P.S.  This gave me a chance to create a real site in Python/Django/Google App Engine for the first time, and I’m impressed.

Just say no to dell

Published on February 16, 2010 in Uncategorized. 1 Comment

I am so frustrated with the buying experience with Dell today that I’m giving up on them.  Their customer service is useless.  Their promises for delivery are repeatedly broken.  They have crazy restocking fees.

This is for an order placed 1/18, and I have no confidence that it would have actually gotten here on the 25th so I’m canceling that.  It wouldn’t be so bad if the people you have to talk to on the phone had some idea about what’s going on.  Something like “We just can’t get that video card” or “The wireless adapter is out of stock”.  I would have modified the order to get it sooner if possible.

But all I got was corporate-speak about how great dell was and how I’d just have to wait.

I’m buying a mac mini instead.  At least apple will screw me over with a smile.