Re: Shipping _syntax_ proposal (Was Re: UPS Shipping Returns $0.00 (Continue))

[mikeh@minivend.com]

Quoting Kyle Hayes (kyle540@quicknet.net):
> Here was where I was starting to head (totally unfinished):
> 
> shipping.cfg:
> 
> Database	Ground	Ground.csv	CSV
> Database	Zone	Zone.csv	CSV
> 
> ...
> LookUp	UPSGZone	DATABASE	Zone
> LookUp	UPSGZone	KEY		RANGE [value zip]
> LookUp	UPSGZone	COLUMN		Ground
> LookUp	UPSGZone	FAIL		'Unknown zip code [value zip]'
> 
> LookUp	UPSGTarif	DATABASE	Ground	
> LookUp	UPSGTarif	KEY	SUM weight
> LookUp	UPSGTarif	RANGE_MAX	150
> LookUp	UPSGTarif	RANGE_MIN	0
> LookUp	UPSGTarif	COLUMN	LOOKUP UPSGZone
> LookUp	UPSGTarif	FAIL	'UPS will only ship up to 150lbs.  Please contact us for bulk shipping information.'
> ...
> 
> Shipping upsg	NAME	UPS Ground
> Shipping upsg	VALUE	UPSGTarif

I am afraid I don't see where this helps the average user.
I believe the beauty of the MV scheme is this one:

expert_shipping	Shipping	[my-criteria]	0	99999999	f [my-shipping]

Now a usertag can implement anyone's scheme, while the ones that
many people use, the simple table-based ones, are covered.

Perhaps the focus should be a library of UserTags like:

	[dhl-shipping weight="@@TOTAL@@"].

As for add-on modules, they can be added at any time:

AddDirective YourLookUp lookups
GlobalSub  <<EOS
sub custom_shipping {
	use MyShippingModule;
	CODE: {
	}
	return $cost;
}
EOS

I encourage implementation of an alternate shipping setup. It doesn't
need me...I have done my best here. 8-)

-- 
Mike Heins                          http://www.minivend.com/  ___ 
                                    Internet Robotics        |_ _|____
                                    131 Willow Lane, Floor 2  | ||  _ \
It's a little-known fact            Oxford, OH  45056         | || |_) |
that the Y1K problem caused         <mikeh@minivend.com>     |___|  _ <
the Dark Ages. -- unknown           513.523.7621 FAX 7501        |_| \_\