X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from imo-d22.mx.aol.com ([205.188.144.208] verified) by logan.com (CommuniGate Pro SMTP 5.1c.2) with ESMTP id 1221698 for flyrotary@lancaironline.net; Sun, 02 Jul 2006 23:01:14 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.188.144.208; envelope-from=ARGOLDMAN@aol.com Received: from ARGOLDMAN@aol.com by imo-d22.mx.aol.com (mail_out_v38_r7.5.) id q.525.2628a8c (65097) for ; Sun, 2 Jul 2006 23:00:24 -0400 (EDT) From: ARGOLDMAN@aol.com Message-ID: <525.2628a8c.31d9e248@aol.com> Date: Sun, 2 Jul 2006 23:00:24 EDT Subject: Re: [FlyRotary] Re: So many questions, so little time To: flyrotary@lancaironline.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1151895624" X-Mailer: 9.0 SE for Windows sub 5026 X-Spam-Flag: NO -------------------------------1151895624 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 7/2/2006 9:32:00 AM Central Standard Time, dale.r@cox.net writes: Huh? What's secret about it? If the link is part of one's sig-line, everyone who gets your message will see the URL. I was referring to the past, not the proposed. The above makes sense to me. You are looking at the "whole" list. I only had two builder's data to work with, at the moment. Scroll up or down from whichever one you started with to see everyone else's. Pardon my relative web-niavity. I finally got it. (I think) That's a little more difficult. Letting folks add their own information requires allowing them "edit" privileges to the site. The only _practical_ way I know of doing that is something like the Wiki. I'll defer to our Wikipedia expert as to whether this is a suitable format for a Wiki page. Understood, but that doesn't make it undesirable. My intention was to compile the data from submissions and manually update as necessary (shouldn't be too often, I'd guess) the same way the Rotary Roster is currently maintainedL According to what I now see the list looks really good. I guess my problem was not really being hit between the eyes that such a list was in existence. According to some of the other posts, I was not alone. _http://members.aol.com/_ht_a/rotaryroster/index.html_ (http://members.aol.com/_ht_a/rotaryroster/index.html) . Recognize that this level of detail is entirely dependent on the discipline of the builder to provide it. I can lay out a "form" - Ed's is a good start - but, if the Rotary Roster is any indication, not everyone will "fill in" all the blocks. Understood. That is a loss for all of us. Rich, it's only _data_. I think you have too high hope for what a simple list can do. What discloses the problems is the individual reports we get from the builders - *way* too much data to put in a simple table. So let's put our collective heads together and with the probable computer knowledge available from this group, find a way. (Didn't they say that man would never fly?) Rich (really appreciative of what you have done, Dale, looking for possible expansion) -------------------------------1151895624 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

In a message dated 7/2/2006 9:32:00 AM Central Standard Time,=20 dale.r@cox.net writes:

<= BR>Huh? What's secret about it? If the lin= k is=20 part of one's sig-line, everyone who gets your message will see the=20 URL.

I was referring to the past, not the proposed. The above makes sense to= =20 me.

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size= =3D2>

=
=20
You are looking at the "whole" list.  I on=
ly had two builder's data to work 
with, at the moment.  Scroll up o=
r down from whichever one you started 
with to see everyone else's.<=
/FONT>

Pardon my relative web-niavity. I finally got it. (I think)

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2>
That's a little more difficult. Let= ting=20 folks add their own information requires allowing them "edit" privileg= es=20 to the site. The only _practical_ way I know of doing that is=20 something like the Wiki. I'll defer to our Wikipedia expert as t= o=20 whether this is a suitable format for a Wiki=20 page.

Understood, but that doesn't make it undesirable.

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2>My intention was to compile the data from=20 submissions and manually update as necessary (shouldn't be too often,=20= I'd=20 guess) the same way the Rotary Roster is currently=20 maintainedL

According to what I now see the list looks really good. I guess my prob= lem=20 was not really being hit between the eyes that such a list was in existence.= =20 According to some of the other posts, I was not alone.

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2>

http://membe= rs.aol.com/_ht_a/rotaryroster/index.html

=
 .

Recognize that this level of detail is entirely depend= ent on=20 the discipline of the builder to provide it. I can lay out a "fo= rm"=20 - Ed's is a good start - but, if the Rotary Roster is any indication,=20= not=20 everyone will "fill in" all the=20 blocks.

Understood. That is a loss for all of us.

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2>

Rich, it's only _data_. I think y= ou have=20 too high hope for what a simple list can do. What discloses th= e=20 problems is the individual reports we get from the builders - *way*=20= too=20 much data to put in a simple=20 table.

So let's put our collective heads together and with the probable comput= er=20 knowledge available from this group, find a way. (Didn't they say that man w= ould=20 never fly?)

Rich (really appreciative of what you have done, Dale, looki= ng=20 for possible expansion)

-------------------------------1151895624--