Hey,
> Before we approach this from scratch
Well, since Validator already exists (and IMO has proven very well how
useful it is in some of my extensions), it's only building the second half
of the bridge, not staring from scratch.
> Would it make sense for SMW to use Validator?
I'd not be suggesting it if I did not think this was the case :) The only
real pain is the b/c (all extensions with query printers will have to be
modified to work with such a new SMW) and the introduced dependency.
Although I've not heard anyone complain about the later for any of my
extensions (for over a year), as you can simply bundle Validator with any
extension that required it in releases.
> Could this also simplify our code?
The biggest win in simplification of existing code would probably be in the
query printers. Also, making the query printers and non-ask parser hooks use
Validator would add a bunch of stuff such as the earlier mentioned
auto-documentation and error feedback for users basically for free, without
adding any complexity to SMW whatsoever (as SMW will just define what the
parameters are, and Validator can figure out for itself how to do things
with them).
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
