Hi
Until the RunRev site has the libUrl documentation back up again, you can view it here:
<http://www.lacscentre.co.uk/liburl/>
You can also get an updater for the latest version (1.1.1 or 1.0.16) there as well. (Note that the previously announced betas of these versions introduced a bug that might affect POST commands to some http servers. So anyone using those betas should probably upgrade.)
The updater is semi-intelligent in that it will install the appropriate version for the engine you currently have installed. But if you later swap engines, and keep the same mctools.mc stack, you may end up with the wrong version. So it's probably best to keep the updater around, and run it again if you ever swap engines.
As discussed before, I was thinking about a more intelligent version that would keep two library stacks in custom properties, and load the appropriate one with a libraryStack handler. But I'm currently against the idea for two reasons;
1. It makes accessing/editing the script more difficult for developers, and I really want people to access the scripts and fix problems they find.
2. It's quite possible that future versions of libUrl will introduce more new syntax from newer engines, and therefore we'll need an even smarter (thus bug-prone) loading system.
But as always, I'm open to opinions.
Cheers Dave
PS I just made a late booking for EuroRevCon, so looking forward to meeting those of you who'll be there.
_______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
