Profile_bird

Hey there! Richard_Lord is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving Richard_Lord's tweets.

Already using Twitter
from your phone? Click here.

Richard_Lord

  1. @flashkiddy Thank you.
  2. I just uploaded an update to #Flint - new version 2.1.3. I will write the change list and blog post later, I have to get to work now.
  3. Adding new tween to shape action to #Flint.
  4. Rolling on the floor laughing. RT @bit101: lol http://bit.ly/5LuLj
  5. Fixed yet another bug caused by flex dispatching events twice when the trigger occurs only once.
  6. @jhooks I use the Logitech R-RB5 and like it a lot.
  7. @ashorten Best wishes, enjoy San Francisco.
  8. Note to self - performing modern dance in the kitchen at work is not advised. It scares the inmates.
  9. Thank you Tink for organising it, thanks to the audience for coming & for asking good questions & thanks to everyone that bought me a drink.
  10. Heading home after a great session at lfpug. My talk about frameworks went down well. A 1 hour talk became 2 hours with questions.
  11. Duck! @lowflyingrocks
  12. Obviously I don't yet know #Parsley & #Robotlegs as well as I know the others, but can put them into context. http://bit.ly/48btiy
  13. I'm speaking about Frameworks at LFPUG on Thursday, comparing #Cairngorm, #PureMVC, #Mate, #Swiz, #Parsley, #RobotLegs. http://bit.ly/48btiy
  14. Next up, #Robotlegs. I started playing with robotlegs yesterday but no example for you yet. There's lots to like about Robotlegs.
  15. Example flex project using #Parsley framework, with source. Matches those I posted previously using other frameworks. http://bit.ly/1V9VJs
  16. @say_hello_je The parsley example is up. http://bit.ly/1V9VJs
  17. Bah, did some work at the weekend but the work VPN is down so can't check-in to svn. Will have to take my macbook to work. :-(
  18. Enough verbal. Time to go to work.
  19. If DI container developers would agree a common metadata format, the lack of coupling to specific implementations would be clearer.
  20. @darscan Metadata indicates the purpose of a property or method but doesn't tie implementation of that purpose into a particular codebase.