Forum OpenACS Development: Re: Re: Re: Re: Re: xoWiki and images
I do admit it's not pretty at this point but we just needed something real quick that deviates from the default implementation. It just attempts to do more on the resolver but the code is backwards compatible with current implementation such that everything can still be passed by URL and folder ids are still supported. The package ids are not required to be specified as parameter but just an option that I check precedence-wise.
We also have several clients who use .lrn and .folio and we needed to support both with a single patch that's why the resolver looks complex. The only actual hard code on the resolver in the strict sense is the check on a mounted /xowiki which is already being mounted on install.
If you have implementations that achieve similar functionality lying around feel free to commit and we're sure to pull it.