Greasemonkey/JavaScript: How to get the source code after AJAX change?

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Greasemonkey/JavaScript: How to get the source code after AJAX change?

      For example, when I'm at the resources page and click on Metal Mine, I get the costs and stuff but these are not displayed in the initial source code. So how do I "refresh" the source code in order to get these information?

      I'm not sure if that's the right place I'm posted in. If not, please move :)

      Anyway thanks in advance.

      //edit: Alright I did some research and think I have to work with addEventListener. So I tried this one on the resorces page:

      Source Code

      1. function insertText() {
      2. document.getElementById('costswrapper').innerHTML += 'Hello World';
      3. }
      5. document.getElementById('inhalt').addEventListener('DOMNodeInserted', insertText, false);

      But when I click on let's say Metal Mine the text gets inserted a million (or so) times. I guess that's because by clicking on Metal Mine there are lots of nodes inserted and thus the function insertText is called lots of times.

      What can I do against that?

    • You can do it with something like that :

      Source Code

      1. var First = true;
      2. function insertText()
      3. {
      4. if(document.getElementById('costswrapper') && First)
      5. {
      6. document.getElementById('costswrapper').innerHTML += 'Hello World';
      7. First = false;
      8. }
      9. }
      11. setInterval( insertText,500); // run the function every 500ms
      13. document.getElementById('inhalt').addEventListener("click", function(event)
      14. {
      15. First = true;
      16. },true) ;
      Display All



      I don't think it's the best solution, but ... ^^


      ** OgameTech **

    • Would you mind explaining that a bit benneb? It's just that I started to learn JavaScript 2 days ago by looking through scripts like Antigame and trying to write some easy scripts.

      So why is it working when you set a time out of 0 ms?

      //edit: I tried it without the setTimeOut but only with "if (e.target.id != 'content') return;" and it works. So what exactly is the time out for?

    • Also another question: How do I realize onClick functions in userscripts? For example I have a link and when you click on it a function HelloWorld() gets called?

      I know I can do this with addEventListener again, but I think there's another solution since Antigame for example doesn't use addEventListener for its calculator on the fleet page as far as I could see.

    • RiV- wrote:

      So what exactly is the time out for?


      This "senseless" makes the included function independent from the eventhandler itself.


      Add a html attribute to this object, like <a onclick="functionname(); return false;"

      "return false" avoid the default action ( for <a : follow the href link)

    • I have this:

      Source Code

      1. function hallowelt() {
      2. alert('hallo welt');
      3. }
      5. function insertText(e) {
      6. if(e.target.id != 'content') return;
      8. document.getElementById('costs').innerHTML += '<br><a href="#" onclick="hallowelt(); return false;">test</a>';
      9. }
      11. document.getElementById('planet').addEventListener('DOMNodeInserted', insertText, false);
      Display All


      But that doesn't work for me. The log says that hallowelt is not defined :/

    • don't hesitate googling ;)

      You can't use onclick="..." syntax here due to the different execution context. Your handler "hallowelt(); return false;" is resolved in the main page context, which doesn't know about the hallowelt() function defined in the userscript in the Greasemonkey sandbox.

      Use addEventListener instead.
      In general try avoid things like 'onclick = "some handler"' as it has a few restrictions in comparison with 'addEventListener' model.

    • No, it is reliable.

      The production (it is the JS variable defined in OGame, which is used here) is always greater than 0 on a planet, no matter if storages are full or not or if you are in vaction mode or not.