| 00:19.48 | *** join/#uphpu wps (n=wps@70.98.110.105) |
| 00:19.48 | *** mode/#UPHPU [+o wps] by ChanServ |
| 02:38.11 | *** join/#uphpu jsmith (n=jsmith@smithfam.dsl.xmission.com) |
| 02:38.29 | wps | so when do you actually move, jsmith ? |
| 02:38.36 | jsmith | Tuesday |
| 02:38.47 | wps | oh, that soon? |
| 02:38.49 | wps | wow |
| 02:38.54 | wps | you ready to go? |
| 02:38.55 | jsmith | Yeah... |
| 02:38.59 | jsmith | No... still more packing to do. |
| 02:39.03 | jsmith | But I'm getting close |
| 02:39.06 | wps | your place sold? |
| 02:39.10 | jsmith | Yeah |
| 02:39.11 | wps | wow |
| 02:39.31 | wps | moving is a bear |
| 02:39.40 | jsmith | Sure is. |
| 02:52.56 | wps | you driving a truck yourself or paying someone to do it? |
| 02:56.41 | jsmith | Paying someone else |
| 02:57.00 | jsmith | Paying someone else to load the truck, paying someone else to drive the truck... |
| 02:57.11 | jsmith | ... all I have to do is box up everything and put it in the front room |
| 02:57.17 | wps | good plan… going that far |
| 02:57.38 | *** topic/#UPHPU by wps -> Utah PHP Users Group | uphpu.org |
| 02:57.47 | jsmith | Yeah... plus it'll save the backs of all my friendly neighbors |
| 02:57.53 | wps | indeed |
| 04:28.45 | *** join/#uphpu wps (n=wps@70.98.110.105) |
| 04:28.45 | *** mode/#UPHPU [+o wps] by ChanServ |
| 04:36.33 | jsmith | wps: Question for you to think about, in your spare cycles... |
| 04:36.50 | jsmith | (since you're a visually creative person) |
| 04:40.23 | wps | yes? |
| 04:42.06 | jsmith | How would you make it easy to visualize the number of callers in a call queue, and the wait time of each caller, along with the average wait time? |
| 04:42.16 | jsmith | How's that for a loaded question? |
| 04:43.00 | wps | is this for an interface for some type of an application? |
| 04:43.10 | wps | do you actually see a list of the callers? |
| 04:43.42 | wps | do you want something quantitative or abstract (simply a graphic representation) of the number? |
| 04:45.44 | jsmith | It's not an interface, just an information display |
| 04:46.17 | jsmith | You don't have to see the list of callers (there's nothing interesting besides the amount of time they've been waiting. |
| 04:46.34 | wps | what type of display? |
| 04:46.35 | wps | LCD? |
| 04:46.36 | jsmith | You could represent it graphically... |
| 04:46.41 | wps | on a phone? |
| 04:46.42 | jsmith | Projected on a wall... |
| 04:47.00 | wps | like for a call center? |
| 04:47.05 | jsmith | Yeah... |
| 04:47.20 | jsmith | I told you it was a loaded question... |
| 04:48.48 | wps | well, my first thoughts are that something more than simply a number (count) would be good, as to communicate the "weight" of how many are waiting |
| 04:49.02 | jsmith | Yup... |
| 04:50.12 | jsmith | I'd also somehow like to incorporate the change in average wait time over say the past 5 minutes... are people now waiting longer than those who called in 10 minutes ago, or waiting less... in other words, is the queue filling up faster than it's being emptied, or being emptied faster than it's being filled up. |
| 04:51.02 | jsmith | Anyway, just curious if you had any ideas... I've been scratching my head trying to come up with something simple and elegant, but I'm not visually creative... |
| 04:51.11 | wps | I'm thinking of an atom… with bodies orbiting around it… giving you two variables: the amount of bodies orbiting and the speed at which they orbit |
| 04:52.20 | jsmith | Hmmmmn... I was thinking about a spiral... almost a seashell shape... the next call to be answered has obviously been waiting the longest, so he get's the tallest wedge... maybe the wedges change color depending on how long they've been in the queue |
| 04:52.56 | jsmith | orbiting speed (in the atom example) doesn't really equate with wait time in my mind |
| 04:54.10 | wps | I was simply thinking that the orbits would slow as the system "bogs down" (ie: wait times become longer) |
| 04:55.02 | wps | one big challenge with either is how to you communicate comparison… there might be more calls now with longer wait times, but compared to what? |
| 04:56.23 | wps | perhaps you would have to have a "standard" next to it that is an average of days in the past or something so that the current graphical element (whatever it is) can be compared against it |
| 04:58.10 | wps | current speed test: 6349 / 1058 (down/up) |
| 04:59.16 | jsmith | Not bad... |
| 04:59.38 | wps | i've gotten 8000 before |
| 05:00.32 | wps | latency is a little worse than my last ISP, but the download increase is nice |
| 05:02.58 | wps | the only time that I notice the latency though is when I am mounting a volume on my home computer on my work computer and navigating the file tree across the net |
| 05:21.35 | jsmith | wps: I may have just found something... |
| 05:22.02 | jsmith | Maybe I'll work something up over the weekend, and then let you tell me what you think... |
| 13:22.20 | *** join/#uphpu RyanE (i=Piadas@rberick.dsl.xmission.com) |
| 13:37.49 | *** join/#uphpu RyanE_ (i=Piadas@rberick.dsl.xmission.com) |
| 15:06.48 | *** join/#uphpu jsmith (n=jsmith@smithfam.dsl.xmission.com) |
| 15:52.45 | macnewbold | wade and j smith, when you get back: regarding your call queue visualization problem, to me a color coding scheme was the first that came to mind |
| 15:53.03 | macnewbold | a colored bar or something, that gets longer and shorter with number of waiters, |
| 15:53.31 | macnewbold | and the color of each chunk (representing one caller) gets "hotter" the longer they've been waiting |
| 15:54.05 | macnewbold | everyone starts out pale blue maybe, then increases through greens, yellows, and then turns red as they've been waiting longer and longer |
| 15:54.25 | macnewbold | then you can see how much of your bar is red vs yellow vs green at a glance |
| 15:54.48 | macnewbold | and the length of the bar shows how many callers there are at once |
| 15:54.55 | macnewbold | and whether it is growing or shrinking |
| 15:55.28 | macnewbold | if you had a way for it to scroll off the screen, you could keep new data at the top, and push historical data down the page, |
| 15:55.37 | macnewbold | so you can see if the red zone is shrinking or growing, etc. |
| 15:55.47 | macnewbold | just a thought |
| 16:12.22 | wps | good thoughts |
| 16:12.27 | wps | hard to say without knowing more about his project |
| 16:13.00 | wps | I at first thought he was looking for something fairly abstract, but it I think now that he is looking for something more detailed |
| 16:13.41 | *** join/#uphpu jsmith_ (n=jsmith@smithfam.dsl.xmission.com) |
| 19:10.59 | *** join/#uphpu ChanServ (ChanServ@services.) |
| 19:10.59 | *** mode/#UPHPU [+o ChanServ] by irc.freenode.net |
| 22:29.46 | *** join/#uphpu bigdog_ut (n=bigdog@207.135.132.13) |
| 22:29.46 | *** mode/#UPHPU [+o bigdog_ut] by ChanServ |
| 22:42.43 | *** join/#uphpu bigdog_ut (n=bigdog@207.135.132.13) |
| 22:42.43 | *** mode/#UPHPU [+o bigdog_ut] by ChanServ |