anutron / clientcide

see: http://code.google.com/p/cnetjavascript/issues/detail?id=43

see: http://code.google.com/p/cnetjavascript/issues/detail?id=60

see: http://code.google.com/p/cnetjavascript/issues/detail?id=79

see: http://code.google.com/p/cnetjavascript/issues/detail?id=100

see: http://code.google.com/p/cnetjavascript/issues/detail?id=102

see: http://code.google.com/p/cnetjavascript/issues/detail?id=103

see: http://code.google.com/p/cnetjavascript/issues/detail?id=104

see: http://code.google.com/p/cnetjavascript/issues/detail?id=108

see: http://code.google.com/p/cnetjavascript/issues/detail?id=110

see: http://code.google.com/p/cnetjavascript/issues/detail?id=113

see: http://code.google.com/p/cnetjavascript/issues/detail?id=115

http://skitch.com/peterpunk/bp7ty/clientcide-datepicker-issue-with-march-09

Happens with ff3 and not Ie.

sample code:

    this.date = new DatePicker(this.input, {
      'onHide': this.calendarHide.bind(this),
      'format': "%m/%d/%Y"
    });

    this.date = new DatePicker(this.input, {
      'onHide': this.calendarHide.bind(this)
    });

I noted something odd going on in the validateField method in the FormValidator.Tips class.

Test case: create a multi text field form. Introduce multiple validations on some of the fields, and have at least 2 that have no "required" validations. My example had the following 5 text field validations:

• required validate-integer
• required minLength:10
• validate-url
• validate-url
• validate-url

I used all the default options on the instantiations of FormValidator.Tips and Fupdate.Prompt, specifying the minimum necessary arguments.

I noticed when I setup a Fupdate.Prompt with this form (after initializing the FormValidator.Tips ) that if I failed the first field (enter alpha chars) and the second field (enter too few chars) then corrected the first field I could post the form even though the second field still was invalid. Another behavior was that if I had a correct integer entry in field one, a too short entry in field 2, then clicked around in fields 3 through 5 I could make the error tip go away on field 2, and post.

I found the following changes to FormValidator.Tips in the validateField method solved this behavior...but it is likely not the most elegant. It also removed a JS error I saw in console from the msgs.getChildren().hide() line in this same method.

Here's my sloppy but working changes:

    validateField: function(field, force){
        
        var advice = this.getAdvice(field);
        var anyVis = this.advices.some(function(a){ return a.visible; });       
        if (anyVis && this.options.serial) {
            if (advice && advice.visible) {
                var passed = this.parent(field, force);
                if (!field.hasClass('validation-failed')) advice.hide(); 
            }
            return passed;
        }
        var msgs = field.retrieve('validationMsgs');
        if (msgs) {
            var msgChildren = msgs.getChildren();
            msgChildren.each(function (item,index) { item.hide(); });
            
        }
        if (field.hasClass('validation-failed') || field.hasClass('warning')) if (advice) advice.show();
            
        var passed = this.parent(field, force);

        if (this.options.serial && !passed) {
            var fields = this.element.getElements('.validation-failed, .warning');
            if (fields.length) {
                fields.each(function(f, i) {
                    var adv = this.getAdvice(f);
                    if (adv) adv.hide();
                }, this);
                passed = this.parent(field, force);
            }
        }

        return passed;
    },

Hi there,

As mentionned here http://github.com/anutron/clientcide/issuesearch?state=open&q=datepicker#issue/15 and here http://github.com/anutron/clientcide/issuesearch?state=open&q=datepicker#issue/26 some dates break the DatePicker.

I'm sure that's an issue, as you can reproduce the bug in the tutorial/demo section here :
http://www.clientcide.com/wiki/cnet-libraries/09-forms/02-datepicker

Try to type any november date prior to 2009, like 2007-11-07, and all calendar's cases will be filled by the same number (28 for this example). Works the same way on FF or IE.

As the previous issues were posted several months ago, is there a chance to get an answer, or even an hint to fix the problem ourselves ?

StickyWin (2.2.0) modalOptions: {hideOnClick: false} not working

the title says it all.

Datepicker works bad for sure... even on http://www.clientcide.com/wiki/cnet-libraries/09-forms/02-datepicker the third datepicker is faulty: when you enter soem date in the field (e.g. 1/1/2010) and the open the datepicker and press "next month" to reach October 2010 the last row contains seven days of "31st"...
clicking "next month" then brings you to a "correct" October 2010...
why calculating dates through 1000ths of seconds?
and Cleintcide in complete: pitty nobody seems to read this comments and react to them :-(

Form.Validator.Tips doesn't remove the PointyTip graphic of the error dialog for a field, once that field has been selected.

Here is a sample HTML page that has a Form.Validator.Tips associated with a form with 2 text inputs, both set as required. Error msgs can be triggered correctly, but are not removed after entering a legal value.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

    
        
        
        
        Sample
        div.DefaultStickyWin {font-family:verdana; font-size:11px; line-height: 13px;position: relative;}div.DefaultStickyWin div.top{-moz-user-select: none;-khtml-user-select: none;}div.DefaultStickyWin div.top_ul{background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/full.png) top left no-repeat; height:30px; width:15px; float:left}div.DefaultStickyWin div.top_ur{position:relative; left:0px !important; left:-4px; background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/full.png) top right !important; height:30px; margin:0px 0px 0px 15px !important; margin-right:-4px; padding:0px}div.DefaultStickyWin h1.caption{clear: none !important; margin:0px !important; overflow: hidden; padding:0 !important; font-weight:bold; color:#555; font-size:14px !important; position:relative; top:8px !important; left:5px !important; float: left; height: 22px !important;}div.DefaultStickyWin div.middle, div.DefaultStickyWin div.closeBody {background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/body.png) top left repeat-y; margin:0px 20px 0px 0px !important;   margin-bottom: -3px; position: relative;    top: 0px !important; top: -3px;}div.DefaultStickyWin div.body{background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/body.png) top right repeat-y; padding:8px 23px 8px 0px !important; margin-left:5px !important; position:relative; right:-20px !important; z-index: 1;}div.DefaultStickyWin div.bottom{clear:both;}div.DefaultStickyWin div.bottom_ll{background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/full.png) bottom left no-repeat; width:15px; height:15px; float:left}div.DefaultStickyWin div.bottom_lr{background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/full.png) bottom right; position:relative; left:0px !important; left:-4px; margin:0px 0px 0px 15px !important; margin-right:-4px; height:15px}div.DefaultStickyWin div.closeButtons{text-align: center; background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/body.png) top right repeat-y; padding: 4px 30px 8px 0px; margin-left:5px; position:relative; right:-20px}div.DefaultStickyWin a.button:hover{background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/big_button_over.gif) repeat-x}div.DefaultStickyWin a.button {background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/big_button.gif) repeat-x; margin: 2px 8px 2px 8px; padding: 2px 12px; cursor:pointer; border: 1px solid #999 !important; text-decoration:none; color: #0 !important;}div.DefaultStickyWin div.closeButton{width:13px; height:13px; background:url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/closebtn.gif) no-repeat; position: absolute; right: 0px; margin:10px 15px 0px 0px !important; cursor:pointer;top:0px}div.DefaultStickyWin div.dragHandle {  width: 11px;    height: 25px;   position: relative; top: 5px;   left: -3px; cursor: move;   background: url(http://github.com/anutron/clientcide/raw/master/Assets/stickyWinHTML/drag_corner.gif); float: left;}

    






        

            
            
            
                

                    

                        Customer Name
                    
                
                

                    
First name
                    

                
                

                    
Last name
                    

                
            
        
 

Here is a solution used...

Form.Validator.Tips.AFix = new Class({
    Extends: Form.Validator.Tips,
    validateField: function(field, force){

        var advice = this.getAdvice(field);
        var wasFailed = field.hasClass('validation-failed'); 
        var wasWarning = field.hasClass('warning'); 
        var isPassed = this.parent(field, force);
        if (!this.options.serial) {
            if ((wasFailed || wasWarning) && advice)  {
                if (isPassed)
                    advice.hide();
                else
                    advice.show();
            }
        }
        
        return isPassed;
    }
});

In the Lightbox:nextEffect function, the URI is run through JS escape(), which means that the colon in http:// becomes %3A. The URI thus doesn't work when set as a background image. Probably wants encodeURI().

Demo: http://mooshell.net/6cFmm/5/

I came across some issues in the datepicker:

1. Fields should not be filled automatically with date of today (or option to set it off)
   
2. Userinput should be checked without using issue above (1)
   
3. Field can be checked/formatted on load/init

I created a fork: http://github.com/storeman/clientcide/blob/7d91b663ef9c2cf79d1d72b1e665c19005555296/Source/Forms/DatePicker.js

Removed the option 'updateOnBlur' and added those options:
fillOnBlur [defaults to true]
checkOnBlur [defaults to true]
checkOnInit [defaults to false]

With those defaults the current usage isn't broken

Just downloaded 2.2.0 and noticed the build version is no getting added in?

 var Clientcide = {
version: '%build%',
assetLocation: "http://github.com/anutron/clientcide/raw/master/Assets",

Should be an easy one :)

Making use of the FormValidator.Tips extension to use error tips
instead of the default FormValidator messages.

I'm calling validatorInstance.reset(); to clear the validation results
on my form.

Problem is that calling reset() doesn't clear the pointy tip display.
Is there an easy way to either:

A) Clear All Pointy Tips ?

or

B) Make reset() clear a validator instances pointy tip ?

I'm using the standard display one error tip at a time best practice.

Heres the mooshell:
http://mootools.net/shell/Dt4uQ/

To reproduce:

Click form 1 email field, tab out to trigger validation tip.

Click form 2 email field. Triggers click handler to call to activationValidator.reset()

Note the css class validation-failed is removed, but the pointy tip remains.