On Fri, Sep 30, 2011 at 9:34 AM, Ross Gardler <[email protected]> wrote: > On 30 September 2011 09:24, Scott Wilson <[email protected]> > wrote: >> On 29 Sep 2011, at 16:31, Steve Lee wrote: > > ... > >> One thing I noticed was that the JQuery and JQueryMobile imports are done >> statically in the HTML rather than via <feature> - is that because of a >> version incompatibility issue? > > That was the tiny contribution I made to the code (removing the > feature and adding static link). So I'll answer.
Thanks Ross > If we use the feature from within Wookie then the application must be > served by Wookie. If we use the static links then it works as a > standalone webapp. Since the client isn't currently running Wookie and > doesn't want to embed it in another application we saw no benefit to > the client in tethering to Wookie just for this feature. We could also use the CDN hosted files but going static removes another dependency (and it's appears safe to redistribute) > We also had a concern about the introduction of version > incompatibilities that were not under our control. Steve has already > raised a ticket about this. However, this was not something we > experienced, just something we didn't want to expose our clients to. > This can be resolved within Wookie though. I did hit a version problem with a JQM function - details in the ticket > Once the code is here we can optionally modify it to use features > again, but until we use some other Wookie specific feature I see no > benefit in it. +1 Steve
