FLUID-4568: Separate dependence of core framework on jQuery

Metadata

Source
FLUID-4568
Type
Improvement
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Antranig Basman
Reporter
Antranig Basman
Created
2011-12-13T01:51:57.775-0500
Updated
2012-01-20T16:50:11.235-0500
Versions
N/A
Fixed Versions
  1. 1.5
Component
  1. Framework

Description

A number of use cases have emerged over time where it would be better to have a looser coupling between the core framework and jQuery utilities. The most immediate is the use of Infusion as part of the server-side within node.js for Cloud4All. Whilst we have historically maintained a "fake DOM" approach to allowing jQuery to boot up to support the core framework, this is becoming increasingly expensive as the relevant libraries (jsdom, etc.) are quite unstable and every upgrade seems to cause an expensive maintenance cycle.
Also, there are other use cases where the expense of loading jQuery when no DOM-dependent operations are required might be avoided, as well as perhaps cases whether other frameworks' core functions might become desirable (e.g. upcoming YUI version).

The idea suggested today was to create a "standalone jQuery" implementation which just "mocks up" (or rather, "implements") the few features of jQuery (inArray, extends) which are required by the non view-dependent parts of the core framework. On the serverside, this mock can extended with features supporting node-based I/O in place of jQuery AJAX functions.

Comments