On Sat, Sep 17, 2011 at 10:04 PM, Ross Gardler <[email protected]> wrote: > On 17 September 2011 13:53, Steve Lee <[email protected]> wrote: >> It's great that there is a JQM template in the seed-widget ant target, >> and I understand it gets round some nasty problems. >> >> How ever it uses the minimised JQM and JQ libraries which makes >> debugging almost impossible. Therefore it is desirable to to be able >> to use the expanded JS libraries for development and then release >> using the minimised versions. >> >> Can this be done? Perhaps with a flag in the widget code or the ant >> widget targets? > > There is no automated mechanism to switch the JQM version at this > point. It seems strange that to debug a widget you need to drop into > the JQM code itself and thus we've not implemented such a feature. > Personally if I find some strange behaviour I write a spike to test > the specific behaviour so as to ensure there are no side effects from > other code.
When the problem only occurs in the dev code and not a spike you need to drop down. JQM is performs complex DOM manipulations and has a *lot* of strange behaviour and it's usually quicker to debug to figure out what it is really doing rather than endless trial and error or reading source (assuming you have the correct version). > However, if you really want to use the expanded libraries then you > need to change the following in "/features/jqmobile/feature.xml": ... thanks 2 other minor [potential] points with JQM being a wookie feature * loss of control of order of inclusion of files which docs indicate may be important and I had a CSS cascade issue. * version control of JQM for individual apps - may or may not want latest Steve
