23 Jan
2010
23 Jan
'10
1:59 a.m.
On 01/22/2010 11:47 PM, Caleb James DeLisle wrote:
I prefer something like resources/uicomponents/widgets/validation/
We have other small "tools" that don't have a community and advanced
stuff like version control, tracker and mailing lists. IMO, this is
normal, and acceptable. Such a tool usually has less than 1k likes of
code, so there's not much to maintain. If there are bugs or
compatibility issues, a mail to the author with either a bugfix request
or a patch should be enough.
But yes, the bug management question is a very good one, and one we
usually consider for larger libraries/tools.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Flavius Olaru wrote:
I second Caleb, this is a functionality used by other applications and
even platform elements, so it should also be in the platform.
Hi devs, Hi Caleb
Why not create a LiveValidation Application before adding it to the core?
There is
an application here:
http://incubator.myxwiki.org/xwiki/bin/view/XWiki/LiveValidation
The idea of a template (registerinline.vm) calling an application seems
backward to me. Also there are
some leftovers in resources like YUI at an obsolete
version...
It was my mistake proposing it go in the yui folder, It doesn't
depend on yui
so it should be in it's own folder. and one more
thing, i found nothing about their(LiveValidation)
bugs management.
You make a very good point. I think it's also important to
note that the
code is under 900 lines fully documented, it contains 1200 lines of unit
tests, it will only be used on pages which call it via jsfx.use and
it is not intended for security as nefarious users may simply turn off
javascript. Maybe we
should think about this, and if the LiveValidation
Application with this javascript library becomes mature/tested and has an
maintainer could go into XWiki Core.
Thanks, this is my view on this.
Flavius Olaru
I appreciate your input.
Caleb