General
Archiver
Posts: 46,084
Group -
Ryan just brought something back to mind, that I've been meaning pose
for quite some time. Ryan requested coding help on a sophisticated device,
something that he probably knew one of us had used. I hadn't used it, but I
remembered who had. Luckily I keep my own Stamp List archives (although
they're
in a bit of mess at the moment).
The coding was authored by Tracy, and to date, I've only seen Tracy share
code on
this list that he considered non-proprietary. Call it "public domain" if
you will.
If that is indeed the case, then might I propose that some, if not all, of
the
various routines for interfacing unusual or sophisticated devices be
submitted to
L.O.S.A as a central repository for such routines.
Many lists such as this have a voluntary archivist, who does just that.
He/she will
extract "important" or "unusual" routines from the message traffic, and
place them
in a central spot for all to access as needed in the future. In many ways
we had
that facility before - with the original Stamp List archives, but now there
is no
such facility (to my knowledge).
Might I suggest that one or the other (L.O.S.A or Stamp List Archive) ought
to be implemented as a ... standard practice here.
All constructive contributions are elicited.
Thanks to all.
Bruce
Ryan just brought something back to mind, that I've been meaning pose
for quite some time. Ryan requested coding help on a sophisticated device,
something that he probably knew one of us had used. I hadn't used it, but I
remembered who had. Luckily I keep my own Stamp List archives (although
they're
in a bit of mess at the moment).
The coding was authored by Tracy, and to date, I've only seen Tracy share
code on
this list that he considered non-proprietary. Call it "public domain" if
you will.
If that is indeed the case, then might I propose that some, if not all, of
the
various routines for interfacing unusual or sophisticated devices be
submitted to
L.O.S.A as a central repository for such routines.
Many lists such as this have a voluntary archivist, who does just that.
He/she will
extract "important" or "unusual" routines from the message traffic, and
place them
in a central spot for all to access as needed in the future. In many ways
we had
that facility before - with the original Stamp List archives, but now there
is no
such facility (to my knowledge).
Might I suggest that one or the other (L.O.S.A or Stamp List Archive) ought
to be implemented as a ... standard practice here.
All constructive contributions are elicited.
Thanks to all.
Bruce
Comments
The Stamp FAQ has a small library of contributed code like this. However, I
don't post anything on the FAQ without the author's permission. Sometimes I
e-mail the author and ask for something, but usually I wait until someone
sends me something.
For those that don't know the FAQ is at:
http://www.al-williams.com/wd5gnr/stampfaq.htm
Topic 3.11 has code for the following:
74HC595
ADC0831
DAC8800
MAX395
MAX528
MAX541
LTC2400
MAX7219
Contributors to this have been Kyle Schmidt, John Barrowman, and Ed Ward.
The article credits the authors. I don't test the code or change it.
I encourage everyone to do 3 things:
1) Send me your device code for inclusion.
2) Send me your FAQ articles (they are published with credit).
3) Read the FAQ. Many of the questions here can be resolved by reading the
FAQ.
I have often thought about changing the structure of the FAQ. Multiple pages
are nice in a way (faster loading), but they are more work. A single page is
easy to save or print. If anyone has thoughts on the FAQ's format, etc.,
tell me. It is there as a public service and you are the public.
I have also thought about using DHTML to make the FAQ outline collapsible --
this wouldn't affect non-DHTML browsers, but would be a nicety for those who
do use one.
Regards,
Al Williams
AWC
* 8 channels of PWM. http://www.al-williams.com/awce/pak5.htm
once it's done you are certainly welcome to the Archery Tournament Timer, lock
stock and barrel. (BS2 and schematic and parts list)
Just not quite there yet. [noparse]:)[/noparse]
Al Williams wrote:
> Hi Bruce and list.
>
> The Stamp FAQ has a small library of contributed code like this. However, I
> don't post anything on the FAQ without the author's permission. Sometimes I
> e-mail the author and ask for something, but usually I wait until someone
> sends me something.
>
> For those that don't know the FAQ is at:
> http://www.al-williams.com/wd5gnr/stampfaq.htm
>
> Topic 3.11 has code for the following:
> 74HC595
> ADC0831
> DAC8800
> MAX395
> MAX528
> MAX541
> LTC2400
> MAX7219
>
> Contributors to this have been Kyle Schmidt, John Barrowman, and Ed Ward.
> The article credits the authors. I don't test the code or change it.
>
> I encourage everyone to do 3 things:
> 1) Send me your device code for inclusion.
> 2) Send me your FAQ articles (they are published with credit).
> 3) Read the FAQ. Many of the questions here can be resolved by reading the
> FAQ.
>
> I have often thought about changing the structure of the FAQ. Multiple pages
> are nice in a way (faster loading), but they are more work. A single page is
> easy to save or print. If anyone has thoughts on the FAQ's format, etc.,
> tell me. It is there as a public service and you are the public.
>
> I have also thought about using DHTML to make the FAQ outline collapsible --
> this wouldn't affect non-DHTML browsers, but would be a nicety for those who
> do use one.
>
> Regards,
>
> Al Williams
> AWC
> * 8 channels of PWM. http://www.al-williams.com/awce/pak5.htm
--
ARC in Lago Vista, TX
Did you know that dolphins are so intelligent that within only a few weeks of
captivity, they can train Americans to stand at the very edge of the pool and
throw them fish.
tried to do in the FAQ is collect code for communicating with common devices
like A/D, D/A, memory, etc.
The LOSA, on the other hand catalogs projects. You still have to provide a
"home" for them. There are lots of places to do that now for free, and you
can list the project with the LOSA.
Regards,
Al Williams
AWC
* Expand your Stamp I/O with a PAK-III or -IV:
http://www.al-williams.com/awce/pak3.htm
>
Original Message
> From: A.Ron Carmichael [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=JZZ_wVTAf2b9zo_P64CLwUKAIvLAc72IButp8PCulTn-sLtiN4Mqadb31cGVYlD6qOFFOEGXcinsyCE]arc@i...[/url
> Sent: Wednesday, April 19, 2000 4:39 PM
> To: basicstamps@egroups.com
> Subject: Re: [noparse][[/noparse]basicstamps] General "basicstamps" Question
>
>
> Hi, Al:
> once it's done you are certainly welcome to the Archery
> Tournament Timer, lock
> stock and barrel. (BS2 and schematic and parts list)
>
> Just not quite there yet. [noparse]:)[/noparse]
>
> Al Williams wrote:
>
> > Hi Bruce and list.
> >
> > The Stamp FAQ has a small library of contributed code like
> this. However, I
> > don't post anything on the FAQ without the author's permission.
> Sometimes I
> > e-mail the author and ask for something, but usually I wait
> until someone
> > sends me something.
> >
> > For those that don't know the FAQ is at:
> > http://www.al-williams.com/wd5gnr/stampfaq.htm
> >
> > Topic 3.11 has code for the following:
> > 74HC595
> > ADC0831
> > DAC8800
> > MAX395
> > MAX528
> > MAX541
> > LTC2400
> > MAX7219
> >
> > Contributors to this have been Kyle Schmidt, John Barrowman,
> and Ed Ward.
> > The article credits the authors. I don't test the code or change it.
> >
> > I encourage everyone to do 3 things:
> > 1) Send me your device code for inclusion.
> > 2) Send me your FAQ articles (they are published with credit).
> > 3) Read the FAQ. Many of the questions here can be resolved by
> reading the
> > FAQ.
> >
> > I have often thought about changing the structure of the FAQ.
> Multiple pages
> > are nice in a way (faster loading), but they are more work. A
> single page is
> > easy to save or print. If anyone has thoughts on the FAQ's format, etc.,
> > tell me. It is there as a public service and you are the public.
> >
> > I have also thought about using DHTML to make the FAQ outline
> collapsible --
> > this wouldn't affect non-DHTML browsers, but would be a nicety
> for those who
> > do use one.
> >
> > Regards,
> >
> > Al Williams
> > AWC
> > * 8 channels of PWM. http://www.al-williams.com/awce/pak5.htm
>
> --
> ARC in Lago Vista, TX
>
> Did you know that dolphins are so intelligent that within only a
> few weeks of
> captivity, they can train Americans to stand at the very edge of
> the pool and
> throw them fish.
>
>
>
>
> He/she will extract "important" or "unusual" routines from the message
> traffic, and place them in a central spot for all to access as needed
> in the future. In many ways we had that facility before - with the
> original Stamp List archives, but now there is no such facility (to
> my knowledge).
Hi Bruce,
Egroups has a nice archive. For example, the following command will sort
out all that has been said about ATMEL in the past two months:
http://www.egroups.com/messagesearch/basicstamps?query=Atmel
I don't think there is any boolean search, though. Anybody know otherwise?
Here is how to get to the entry screen for the archive. The archive is
public.
http://www.egroups.com/messages/basicstamps
And here is the entry screen for the group, showing how many members are
currently signed up (~1145), and other subscription information.
http://www.egroups.com/group/basicstamps
The link to the message archive is on the left side of the screen. You can
also see how many messages have been posted by month, and click on a month
to bring up a list of messages starting on that date.
Lake many of us here, I came in to egroups on the Parallax bandwagon and
receive the messages by email. I don't know if I can post messages through
the web site. You are supposed to have a password to do that, but I don't
know if I have one already, or do I have to sign up again there to get one?
Anybody know? Do I want one?
Now about the question of "extract "important" or "unusual" routines"....
I have my own big text file containing all sorts of useful information that
I have cut out of messages over the past couple of years as I learned about
the stamp and all sorts of interesting things. Thanks, one and all.
> Ryan requested coding help on a sophisticated device, something
> that he probably knew one of us had used. I hadn't used it, but
> I remembered who had. Luckily I keep my own Stamp List archives
> (although they're in a bit of mess at the moment).
> The coding was authored by Tracy, and to date, I've only seen
> Tracy share code on this list that he considered non-proprietary.
> Call it "public domain" if you will. If that is indeed the case, ...
Well, I did stick a copyright on the top of it. I have have no problems
with anyone modifying the code for their own purposes. Indeed, it is just a
demo of the basic functions and takes a lot of work to make it do something
really useful. However, I'd not like to see the demo code appear verbatim
in a book or online without the credit attached to it, because that first
hurdle, understanding the data sheet and the a-b-c's of making it work,
takes a lot of thought and frustration. That comment can be taken in
general. That said, I would be happy to see it posted in the FAQ, and here
in the archive. Or I wouldn't have posted it in the first place. That is
what makes this list worthwhile. All the give and take.
-- Tracy Allen
Electronically Monitored Ecosystems
http://www.emesystems.com
>> Many lists such as this have a voluntary archivist, who does just that.
>> He/she will extract "important" or "unusual" routines from the message
>> traffic, and place them in a central spot for all to access as needed
>> in the future. In many ways we had that facility before - with the
>> original Stamp List archives, but now there is no such facility (to
>> my knowledge).
>
>Hi Bruce,
>
>Egroups has a nice archive. For example, the following command will sort
>out all that has been said about ATMEL in the past two months:
>
> http://www.egroups.com/messagesearch/basicstamps?query=Atmel
>
>I don't think there is any boolean search, though. Anybody know otherwise?
>
>
>Here is how to get to the entry screen for the archive. The archive is
>public.
>
> http://www.egroups.com/messages/basicstamps
>
>And here is the entry screen for the group, showing how many members are
>currently signed up (~1145), and other subscription information.
>
> http://www.egroups.com/group/basicstamps
>
>The link to the message archive is on the left side of the screen. You can
>also see how many messages have been posted by month, and click on a month
>to bring up a list of messages starting on that date.
>
>Lake many of us here, I came in to egroups on the Parallax bandwagon and
>receive the messages by email. I don't know if I can post messages through
>the web site. You are supposed to have a password to do that, but I don't
>know if I have one already, or do I have to sign up again there to get one?
> Anybody know? Do I want one?
Nope - you can assign YOUR OWN. Once you do that,the entire profle opens up
to you.
I used it while switching around my mail-list routing. I've placed
"important"
lists on one ISP, and "less important" with another. One ISP I often can't log
onto, since it's inexpensive and gets bogged down when the kids are home
from school
(like SOON - Friday), and the other is more expensive, but has ample capacity.
Regardless of where any list is destined, I can re-route it from my end now.
What a BOON to productivity !
>
>Now about the question of "extract "important" or "unusual" routines"....
>I have my own big text file containing all sorts of useful information that
>I have cut out of messages over the past couple of years as I learned about
>the stamp and all sorts of interesting things. Thanks, one and all.
>
>> Ryan requested coding help on a sophisticated device, something
>> that he probably knew one of us had used. I hadn't used it, but
>> I remembered who had. Luckily I keep my own Stamp List archives
>> (although they're in a bit of mess at the moment).
>> The coding was authored by Tracy, and to date, I've only seen
>> Tracy share code on this list that he considered non-proprietary.
>> Call it "public domain" if you will. If that is indeed the case, ...
>
>Well, I did stick a copyright on the top of it. I have have no problems
>with anyone modifying the code for their own purposes. Indeed, it is just a
>demo of the basic functions and takes a lot of work to make it do something
>really useful. However, I'd not like to see the demo code appear verbatim
>in a book or online without the credit attached to it, because that first
>hurdle, understanding the data sheet and the a-b-c's of making it work,
>takes a lot of thought and frustration. That comment can be taken in
>general. That said, I would be happy to see it posted in the FAQ, and here
>in the archive. Or I wouldn't have posted it in the first place. That is
>what makes this list worthwhile. All the give and take.
Indeed it does work, and well.
Exactly why I put the public domain in quotes - I wasn't sure your intent.
Sometimes the intent is for the larger program to be protected, but a given
routine is not. To be honest, I didn't even look at the program, I just
grabbed
it verbatim and in toto from my archive. I HAD to be safe then <smile>.
Thanks for the clarifications, and I'm sure we should all work within those
minimal confines. I would suggest that all such similar contributions be
treated in a the manner as you have outlined; certainly easy enough to do.
Forward - the Stamp Brigade !
Regards,
Bruce
>
> -- Tracy Allen
> Electronically Monitored Ecosystems
> http://www.emesystems.com
>
>
>
>