In chatting to Colin, he pointed out that a feature I was thinking of integrating into our DOM binder (back-tracks for selectors) is already in JQuery 1.3 - this only adds to the pressure to get these version upgrades tried out as soon as we can. Unfortunately I read the following version note today:
stable release, jQuery UI 1.5.3 is only compatible with jQuery 1.2.6 preview release, jQuery UI 1.6rc6 is only compatible with jQuery 1.3+ This implies that we would also upgrade trunk to this preview release of jQuery UI - this would only make sense if we were sure that the final would be available before our own 0.8 release. Since it was implied to be released last Saturday, I think this seems a good bet. So, let us try to bash through this tomorrow (or I might try the raw file upgrades tonight and try and pick up a few pieces). The "upstream goal" was that I was trying to improve diagnostics from the framework - I am working on the Pager, and had managed to configure it without a PagerBar, and the resulting failure was pretty opaque - an empty JQuery was handed to the fluid.container() method which had been evaluated several levels further up the stack in the DOM binder of the overall pager. We need to make sure that meaningful diagnostics are emitted by the framework in all reasonable cases, in particular ones which sensibly guide the user to resolution of the problem. In the short term this will cause some file bloat of the framework files, but we should work towards a properly decoupled messaging system (perhaps even with I18N) for the 1.0 release to mitigate this. Boz. _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
