Skip navigation
Currently Being Moderated

when create jquery mobile site (local) code i think of libraries is old, what to do

Feb 8, 2013 9:52 AM

Tags: #version #jquery_mobile

 

 

I bought dw cs6 but after 6mos i get creative cloud cs6, but not reinstalled it... i think prior 1mo linked to my  creative cloud this dw ver but not reinstalled as well, when click update dw appear the  creative cloud update but no updates for dw... when create jquery mobile site (local) code i think of libraries is old, what to do???

 
Replies
  • Currently Being Moderated
    Feb 8, 2013 10:53 AM   in reply to lsepolis123

    Not sure if I'm understanding your correctly but as for getting and using the latest stable version of the jQuery Mobile, visit http://jquerymobile.com/ and download it and integrate the updated files into your project.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 5:20 AM   in reply to lsepolis123

    With the stand-alone Dreamweaver CS6 (not cloud version) you will have to manually download and manually integrate the updated jQuery Mobile files.

     

    I don't know about the cloud version - presumably Adobe could include the latest version of jQuery Mobile with the cloud version a lot more easily.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 10:18 AM   in reply to lsepolis123

    Before you get all excited here…

     

    It has been my experience that newer versions of jQuery can "break" older code. So you would have to update both. I regularly use some JavaScript code that requires jQuery 1.4.2. I installed the latest version of jQuery (currently 1.9.1) and it breaks what I'm doing completely.

     

    So, if you're installing a newer version of the minified jQuery in your website (which you can get here), and you're using older code, you may find that it simply does not work.

     

    Now, presumably, if you are using a jQuery widget that is being provided by Adobe, they'll have it in sync with the right version of jQuery. But I don't upgrade just to upgrade.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 12:06 PM   in reply to lsepolis123

    I wouldn't uninstall the stand-alone Dreamweaver. Just download the jQuery mobile files you need from the jQuery mobile site and replace the old versions in your site. But as mhollis55 notes, please test as newer versions of jQuery may break older jQuery plug-ins.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 12:13 PM   in reply to mhollis55

    jQuery's latest 1.9.x.min.js is breaking almost all my widgets too.  Don't know why.  So I stepped back to 1.8.1 without any problems.

     

     

    Nancy O.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 12:47 PM   in reply to Nancy O.

    They're dropping support for some old browser behaviors and nmaking major optimizations. jQuery provides another download for a migration plugin that will help old plugins work with the latest jQuery 1.9.1. See here: http://jquery.com/download/ (under jQuery Migrate plugin).

     

    The roadmap for version 2 of jQuery will drop even more support for older browsers (and all support for IE6). This will provide jQuery more room to grow in the future and help reduce the size of the script.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 1:08 PM   in reply to bemdesign

    I'm all for progress and dropping support for IE6's obsolete browser.  But latest jQuery shouldn't break all my plugins at once.  They're not that old.

     

     

    Nancy O.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 1:24 PM   in reply to bemdesign

    Hmm.

     

    I'm with Nancy—but I understand the eagerness to leave old Internet Exploder browsers in the dust. Heck, they should end support for IE 7 and 8, for that matter. Maybe perhaps 9.

     

    But I wonder how I would adapt my code…

     

    Is there a toolkit for jQuery scripts that have been broken?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 1:28 PM   in reply to Nancy O.

    We've been trying to help people avoid those problems for a few years

    now, Nancy They will continue and they will likely get worse.

     

    JQuery Best Practice: The Definitive Guide:

    1. Use jQuery only if you write your own plugins and are prepared to

    keep everything updated.

    2. See #1.

     

    That's it.

     

    The open source movement is a double-edged sword. It can produce great

    tools. The jQuery library is a great tool. But it is only a great tool

    for JavaScript authors. The downside is that the movement, by nature,

    has zero accountability beyond the core tool.

     

    I've said this numerous times, but for those with an open and logical

    mind, it could have value and it could save you grief:

     

    PVII has been making client-side commercial extensions longer than

    anyone else. In fact, we invented the genre. We do not enjoy writing

    thousands of lines of script from scratch. We would love to be able to

    use someone else's core library, but...

     

    There is not one in existence that has the level of quality and

    flexibility that we would need and so we write our own scripts.

     

    The same can be said for Adobe's dearly departed Spry libraries. We

    would have blessed Adobe for eternity if Spry was good enough to use as

    a basis for writing extensions. It wasn't even close. We were honest

    about its flaws, and Dreamweaver's former product manager banned us from

    all internal Adobe groups and committees unless we were willing to paint

    Spry in a more positive light. Well, the product manager is gone and

    Spry is gone.

     

    Please, do yourself a big favor and stay away from jQuery plugins unless

    you write them yourself.

     

    Wanna do a fun test? Enable script error notifications in IE9 or IE10

    and browse the Web for a few days. On many very high profile sites that

    deploy jQuery, you will get constant error messages. The errors are not

    due to bugs in IE9 or IE10, they are due to seriously flawed script.

     

     

    --

    Al Sparber - PVII

    http://www.projectseven.com

    The Finest Dreamweaver Menus | Galleries | Widgets

    Since 1998

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 1:43 PM   in reply to Al Sparber

    That's it, I'm having Al write everything from now on.

     

    Really good caveats, Al. Now, I'm going to have to adapt some scripts. I note that the jQuery folks have admitted to many of the issues Al brings up with a migrate tool.And I have spoken with people who write code at a much higher level than I probably ever will who have told me that jQuery is too confining and has problems.

     

    I do have to disagree with Al with respect to his Internet Exploiter testing. I do not trust anything Microsoft says "is an error." There is a similar reporting feature in Firebug for Firefox and, I believe Chrome may have something as well. Microsoft recently came out with a whine about how nobody was supporting Surface—this two weeks after the API for it was announced. They were saying, in effect, "you're supporting Apple's Mobile Safari, so you should support our mobile browser, too."

     

    While it would not surprise me if Surface became the new Zune, a bare two weeks after releasing the API is a little bit presumptuous. After all, Microsoft is the only browser maker that has disavowed its own work—without providing a free, automated upgrade.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 1:48 PM   in reply to Al Sparber

    Al,

    I know you've been preaching this for years.  And I agree with you to the extent that's it's possible & profitable for freelancers like me to write & re-write plugins while staying on top of other duties.  JQ is convenient.  Simple to deploy.  And I get a lot of bang for my buck using it.  Until it breaks of course. Fortunately, I don't use jQuery for really vital stuff.   Believe it or not, Al, I do pay attention to what you say.

     

     

    Nancy O.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 2:39 PM   in reply to mhollis55

    Your political feelings about Microsoft are irrelevant. An error is an

    error and Firebug checks Firefox - not Explorer. I don't think you

    understood that particular point. When you are that far off the point it

    is sometimes better to drop it or to seek a more direct venue for

    discussing it.

     

    --

    Al Sparber - PVII

    http://www.projectseven.com

    The Finest Dreamweaver Menus | Galleries | Widgets

    Since 1998

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 4:28 PM   in reply to bemdesign

    @bemdesign,

    Just tested  jQ latest with jQ Migrate and it does work nicely.

     

    <script src="http://code.jquery.com/jquery-1.9.0.min.js"></script>
    <script src="http://code.jquery.com/jquery-migrate-1.1.0.min.js"></script>

     

    Thanks for the tip!  Much appreciated.

     

     

    Nancy O.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 5:30 PM   in reply to Al Sparber

    Al, until Microsoft makes a browser that runs in OS X they have no right to demand I cater to their new platform.

     

    I do check out my sites using virtualization, but only as I am about to launch and only to determine whether or not HTML5 will degrade nicely.

     

    Everyone else makes a browser I can use, everyone. And, since I like getting my work done without needing to do computer maintenance all the time, I don't use Windows as my primary OS.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 5:33 PM   in reply to Nancy O.

    Nancy, I am very pleased that I could offer you a tip. I never thought that day would come.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 12, 2013 6:02 PM   in reply to mhollis55

    Actually, Mark, I have no idea what you are talking about The fact

    is, you don't understand what I said about the script errors, which have

    nothing to do with what you think they do - not even remotely. I'm

    thoroughly lost on your Apple kick. I could care less, actually, what

    Apple or Microsoft do or do not do. But that's not relevant to this

    discussion either

     

    --

    Al Sparber - PVII

    http://www.projectseven.com

    The Finest Dreamweaver Menus | Galleries | Widgets

    Since 1998

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 14, 2013 8:07 AM   in reply to lsepolis123

    From jQuery's Content Distrubution Network (CDN). 

    http://code.jquery.com/   The latest stable release of jQuery mobile is 1.2.0.

     

     

    Nancy O.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 14, 2013 12:27 PM   in reply to lsepolis123

    I said 1.2.0 is the latest stable release. 

     

    Nancy O.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points