![]() A copy of the presentation is available in PDF format. I'd like to thank those in attendance for their patience, apologize for my forgetfulness, and hope that at least a little information was conveyed. Thankfully a fellow attendee loaned me his computer and using the USB drive I did have on me, I managed to gave a modified version of the talk sans running demo code. However, it wasn't until after sprinting back to the meeting and futzing with projectors for 15 minutes that I realized this issue. Alas in my rush to borrow an adapter (only being able to find a mini display port to HDMI) I ran afoul of the old Mac VGA/HDMI mechanical virus issue. ![]() The meeting was only a few blocks away from the Allurent offices so I ran (more like a sprint) back to find suitable replacements. Alas the talk didn't go as planned since I forgot my bag of video output adapters at home and didn't notice until I was setting up. Tonight I spoke at the Boston Flex User Group about AIR 2.0 with a focus on the new Native Process API and Networking APIs. As time permits I hope to add additional visualizations to the tool now that the overall framework is in place. ![]() For those that don't have a Zeo I've included a sample of my own data to get an idea of what it tracks. This includes a pure AS3 library for parsing the data and a sample Flex application for visualizing it. All of the source code is available on bitbucket at Zeo Data Explorer. Along with the generic parsing library I've started exploring different ways to visual my sleep, beyond what you can do on myZeo, in an application called the Zeo Data Display. To that end I put together a generic library for parsing the CSV file you can export from the myZeo site. For anyone that uses a Zeo to track their sleep, I've been playing with different ways to visual my sleep data, which some of you may have heard me talk about at BarCamp Boston 5. I'm pleased to announce the first release of Zeo Data Explorer. Be warned there aren't answers to these problems, despite what the introduction alludes to. As the introduction emphasizes, to really get the most put of the book, you will want to work through the exercises at the end of each day, as that is the best way to get a feel for each language. The writing is uneven between the chapters and some concepts (like monads and monitors) could use much better code examples. None of the topics are covered in great detail but for those curious what Ruby, Io, Prolog, Scala, Erlang, Clojure, and Haskell are all about, this book does a reasonable job of introducing and demonstrating each language. This book offers an exploration of various programming paradigms (object oriented, prototype, constraint-logic, and functional), concurrency models (actors, futures, and transactional memory), and programming constructs (list compression, monads, and matching). Seven Languages in Seven Weeks by Bruce A.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |