Submitted by ken on Sat, 2016-03-05 12:00
A Drupal Taxonomy is a very neat concept. They are handy for categorizing content. Combined with the Autocomplete Term widget, Taxonomies allow content creators to easily find an existing term or create a new term to associate with their content. I use a single taxonomy "Tags" to categorize content on this site. This post is tagged with Drupal and Taxonomy (look below at the "Tags" section).
Submitted by ken on Sat, 2016-02-27 12:30
Next step was to produce a (more) polished product. We started to feed real data into our prototype code and quickly spotted some obvious visual issues:
Submitted by ken on Sat, 2016-02-20 01:30
We needed to produce a Business Quadrant chart and had decided to use the graphael graphing engine to do it.
The first step was to create a skeleton module based upon Drupal Charts design that would allow us to specify and supply the chart data via a View. The initial version only provided the (x,y) data points by selecting a series of nodes.
Submitted by ken on Sat, 2016-02-13 12:30
We came to the conclusion that we needed to roll our own Business Quadrant Charts and started the search for a suitable open source graphing engine that we could easily incorporate into Drupal.
We separated the problem into two distinct architectural areas:
Submitted by ken on Sat, 2016-02-06 12:30
At this point we were a little confused. We did not think our ask was special. All we wanted was to create a simple business graph. Why was it not easy?
Further investigation of the Google Scatter charts revealed they were perfectly suitable for a scientific scatter plot, but highly unsuited for a business quadrant chart. Why was this? A review of requirements revealed that they were fundamentally different animals, they just looked similar on the surface.
A Scientific Scatter Plot has the following attributes:
Submitted by ken on Sat, 2016-01-30 12:00
I was recently involved in a situation where we needed a simple graph to depict the likelihood of an event versus the impact of that event. All we needed was a simple 5 x 5 grid showing a bunch of data points. Both the X axis and the Y axis would have labels like Very Low, Low, Medium, High, Very High. We needed a Scatter Chart. I have seen lots of them. Nothing special. We just needed to add a graph to a Drupal system and generate dynamic graphs based upon data in the system. This should be simple.
Submitted by ken on Sat, 2016-01-16 12:00
My test rig and YS50 mule strobe were all working fine. It was now time to get serious and start to hook it up to real equipment.
At first I thought I should tackle jamming the Arduino into the Sea & Sea TTL converter housing. But I decided that I needed 100% confidence in my setup before I started to solder wires to the Arduino. Soldering was a final commitment.
So the next step was to include a real camera into the setup. This required more brain power than I anticipated.
Submitted by ken on Sat, 2016-01-09 12:00
The next step was to hook my Arduino Quench program to a real power level control switch. Seems easy, but once again I hit some interesting potholes along the way.
The Sea & Sea TTL converter housing came with 3 rotating controls:
Submitted by ken on Sat, 2016-01-02 12:30
The next step was to be able to control the power output of the strobe. The Nikonos TTL wired interface provides a Q (quench) signal line. This is used to instruct the strobe to stop firing. If the Q line is unused the strobe will fire a full dump each time it is triggered. If the Q line is dragged low after the X line then the strobe will stop firing. The longer you wait to assert low on Q the longer the strobe dump is. If you wait too long to assert low on Q then the strobe will perform a full dump. This all works when the strobe is in TTL mode.
Submitted by ken on Sat, 2015-12-26 12:30
Now that I had determined how to properly structure my real-time code for the Arduino, it was time to start controlling my strobe.