I think the bane of development planning can be those conversations where you personify your framework and start debating about what a service should "know", whose "job" a particular operation is, or what the handler should "care" about. This is one of those sort of questions, but I'll keep it brief since I'm more interested in your opinions than my ramblings.
This Wednesday Adobe's Kevin Hoyt spoke in Kansas City to a captive audience of about 75 people including ColdFusion programmers, HTML/CSS builders, and designers. The meeting was great. It also included Jack Stack BBQ and shwag from Uhlig, Emfluence, and Tek Systems to name a few. Kevin didn't drop any bombs I hadn't heard about yet, but there were definitely a few things I learned about Adobe's up-and-coming products. Here's a quick overview of my notes:
After a couple very long airport delays I have arrived in San Francisco and can't wait for the first workshops tomorrow. I have a laptop in tow and hope to blog what I can providing there is wireless available.
I was just staring a a piece of ActionScript code trying to figure out why the two date objects I was comparing were not coming up equal. I'm ashamed to say I didn't notice the problem at first because I had mistakenly typed
Two equals signs ("==") work a little better than one since the single operator obviously changes the value of the former operand. :) Once I fixed that, I found my real problem.
In case you are wondering, "Axes" is the plural form of "Axis" and it is pronounced "Axees" with a long e as in "see". Perhaps you have never pondered that one, but it's been driving me crazy. In this post I wanted to demonstrate a little experiment I did tonight to try and not duplicate as much formatting when it came to my charting data tips. I can already think of a few problems with it, but I wanted to try anyway.
Well, once again this is a pretty basic post of information readily available on the Internet. It took me seemingly forever to piece it all together, so I am blogging it to cement it in my mind and hopefully help someone else down the road. This week I have conquered the formatting of my X and Y axis labels for my charts. As usual, the hoops are a little bulky to jump through when you just want to add a very simple bit of formatting, but the flexibility is awesome.
I feel dumb saying this, but I am having a heck of a time finding consistent information about Flex 3 classes. I am just starting in Flex and it isn't TOO hard to find an example out there that is close to what you are doing, but often times examples don't cover all the bases, and I'll need to look up a method to get its exact signature. (How many arguments, what type, etc) Generally, I'll turn to the livedocs for this, but I have been wasting a lot of time Googling and I don't think it should be this hard.
If you have been programming in Flex for a while, I have nothing earth-shattering to say here. Nevertheless, having just figured it out I wish to write it down as much for my sake as anyone else. My latest task, simple as it was, involved formatting the numbers in several of my Data Grids as dollars and cents.
I have been enjoying my dip into Flex so far. Sometimes you don't notice habits until you have to change them. One rut I've gotten into over the years is the procedural way web-based apps have gotten be thinking about programming.