On Wed, Feb 26, 2003 at 11:40:09AM -0800, Steven Fisher wrote:
> Add a second file extension that PilRC will recognize as a Palm resource 
> file.

Your later motivation for this -- "noone thought of this reason at the
time" -- seems good enough to me :-).  Of course, you'll have to use
the clunky work-around in the meantime.

> I think the easiest solution is to modify the PilRC core library to 
> parse a second extension as it does .rcp files now.
[...]
> I was thinking .rci; admittedly, .rip probably makes more sense, but I 
> expect we'd have too many collisions on that one.
[...]
> PilRC is already coded with behavior for 
> unrecognized file extensions -- it parses them as .h files. While this 
> might not make sense, changing the default behavior would probably break 
> at least some existing projects.

Probably, and it's good that you're thinking of such issues.

How's this for a compromise:  treat any extension whose first character
is "r" or "R" as a .rcp file; otherwise the existing behaviour.

This has the advantage that we get to punt on the decision of exactly
which other extension to commandeer ;-).

> And assuming it's a good change, how do I submit it? :)

Post a patch to the pilrc-developer mailing list that you'll find via
http://sourceforge.net/projects/pilrc/ .  Aaron will ignore it because
he is too busy to put together a new release :-), but others such as
Neil may well pick it up.

    John

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to