[JsonMember]

Thanks Peter.

Guess I’m a bit discouraged to see that it is not a plan even in the works considering that things seem to be moving in this direction. I did not mention above but jquery even also offers this up as a feature. It particularly becomes helpful in situations where a library has grown in size and a team wishes to not include an entire widget library into the source revision control system. I’ve been there with dojo – in the days before it introduced the CDN feature – and we’ve had projects that contain a few hundred toolkit related files in their revision control repositories – which puts burdens on build processes, machine resources, IDEs, etc for the web application. I guess a project team could always host the widgets on a dedicated internal server (and in some ways that might actually be preferred), but never-the-less, still more curious to the reason for no CDN.

Related to this, what is the likelihood of jqWidgets introducing a light-weight loader – again similar to the asynchronous module loader concept that other widget systems like dojo utilize. It is very nice because you only have to have a single javascript page include (an include for just the light-weight loader) which in turn, loads in the modules/widgets needed by the page (that which is specified as part of a requires type declaration statement read in by the loader at page load time).

In my experience working with dojo this has been a very clean approach towards keeping the number of dependent javascript library includes to a minimum.

Just would like to see how jqWidgets plans to specifically address these concerns. We are evaluating whether to use jqWidgets both in the mobile and desktop web application space, hence a little more insight is much appreciated.

Regards,

Jason

[JsonMember]

Hi,

I am new to jqWidgets and was wondering the same exact thing. Specifically, along the lines of the CDN services. For example, the dojo toolkit utilizes the googleapis domain to centrally host its toolkit library, so developers can simply point to that source location for the needed javascript libraries. It makes it easier for people who just want to quickly build some test examples so that they don’t have to download and or carry-around the latest version of the sources. Any plans for this in the future ?

Liking more and more of jqWidgets every day – keep up the good work

Regards,

Jason

[Author]

Posts