Version upgrades - JQuery 1.3, JQuery UI, messaging

[Justin]

Hello,

I have spent most of the day testing the JQuery and JQuery UI upgrade.

For the most part it seems like everything is working as it should.

I have filed  4 jiras, which all seem to be relatively minor.

	FLUID-2186:
	Progress Test 4.5 fails
	http://issues.fluidproject.org/browse/FLUID-2186

	FLUID-2187:
	Avatar for portlets with permissions does not remain under pointer  
while dragging
	http://issues.fluidproject.org/browse/FLUID-2187

	FLUID-2188:
	jquery ui tabs don't display as tabs
	http://issues.fluidproject.org/browse/FLUID-2188

	FLUID-2189:
	Server version of Uploader still points to jQuery 1.2.6
	http://issues.fluidproject.org/browse/FLUID-2189



Additionally, I have been able to close a few older issues.

	FLUID-894:
	Avatar moves offscreen and away from pointer, at screen edges; using IE
	http://issues.fluidproject.org/browse/FLUID-894

	FLUID-952:
	Avatar not under pointer if element is picked up while partly off  
screen, using IE
	http://issues.fluidproject.org/browse/FLUID-952

	FLUID-954:
	Page won't scroll during DnD, using Opera
	http://issues.fluidproject.org/browse/FLUID-954

- Justin

On 2-Feb-09, at 5:19 PM, Antranig Basman wrote:

> 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 - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work