Call for standards: EPROM/cal editing

[Programmer]

I agree Terry,
There are those that have put a lot of effort forth, and should be
able to protect their work. Makes sense to me...I know how many
hours I've put into ECU files--takes a lot of trial and error.
Lyndon.
-----Original Message-----
From: TK <terryk at foothill.net>
To: gmecm at diy-efi.org <gmecm at diy-efi.org>
Date: November 2, 2000 11:37 PM
Subject: Re: Call for standards: EPROM/cal editing


>The format for GMEPro's EPE files is readily available but few people have
>taken advantage of that. They just want me to keep cranking out EPE files.
>That's fine by me.  The sharing of home-brewed EPE files is fine by me, but
>I don't want the one's I supplied floating around any more than they are.
>
>During the program's early development, I released the format of GMEPro's
>EPE files and noticed it found it's way into at least one other program.
>That's cool too.
>
>I don't think any of us relish the idea of rewriting the files so the other
>editors can read them. It's a fair amount of work and I'm sure each of us
>have little differences that would make them incompatible (or we'd argue
>until the next coming of Christ on what to do).
>
>Frankly, for the non-shareware programmers, it is MP3 in the making. No
>doubt, if I opened up the EPE files, it would further the "knowledge base
of
>the DIY community." But for me, I sell the EPE files rather than the
>program. That's where the real work is located.
>
>I hope that makes sense without sounding too dick-headed.
>
>Terry
>
>
>>
>> That's one of the goals, yes. Another of the primary
>> desired outcomes would be the ability of the average
>> Joe who's working out the table locations in a yet
>> unknown cal to add them to a TDF as he finds them.
>>
>> He could use any editor he liked to use, and not be
>> restricted to whichever one happened to have a TDF
>> for his application. (Or maybe none, if no one yet
>> supported it)
>>
>> Ultimately, it'll be up to the editor authors such
>> as yourself whether or not you'll support the standard
>> format. That's what really makes a standard a
>> *standard*,
>> adoption by the programming/software community.
>>
>> The ultimate intent is to make a definition file
>> that's freely available (even if the Editor isn't)
>> so that the tuner can use his choice of editor and
>> maybe further the knowledge base of the DIY community.
>> That's the hope, anyway. :)
>>
>>
>> Later,
>>
>> Dig
>
>
>---------------------------------------------------------------------------
-
>To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
>in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>
>

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org