1. Apr 16, 2013
  2. Apr 02, 2013
    • Aurindam Jana's avatar
      Debugger: Accepts port range as arguments · f1559590
      Aurindam Jana authored
      
      Allow a port range to pass on command line, and try to listen on any of the
      ports in the range. (Re)using the ',' separator allows for backwards compatibility,
      that is, also Qt 4 will accept a -qmljsdebugger=port:1000,1010 argument, but
      will only try to listen on port 1000.
      
      Change-Id: Ic03fe20e4aee9ecdea86651f46f1df5cb19bd75c
      Reviewed-by: default avatarKai Koehne <kai.koehne@digia.com>
      f1559590
  3. Jan 10, 2013
  4. Sep 23, 2012
  5. May 14, 2012
  6. Apr 26, 2012
  7. Apr 25, 2012
  8. Apr 24, 2012
  9. Apr 10, 2012
  10. Mar 30, 2012
  11. Mar 19, 2012
  12. Mar 14, 2012
  13. Mar 13, 2012
  14. Mar 07, 2012
  15. Feb 24, 2012
  16. Feb 10, 2012
  17. Feb 09, 2012
  18. Jan 30, 2012
  19. Jan 23, 2012
  20. Jan 05, 2012
  21. Dec 21, 2011
  22. Dec 20, 2011
  23. Dec 16, 2011
  24. Nov 22, 2011
    • Kai Koehne's avatar
      Debugger: Move server into it's own thread · 43e20d57
      Kai Koehne authored
      
      So far the debugger infrastructure was running in the GUI thread,
      which required e.g. nested event loops to implement blocking behavior.
      The server and networking code are now running in their own thread,
      while the services are still running in the main thread.
      
      Because v8 isn't thread safe, we're adding two new JSEngines + isolates
      to qv8debugservice: One to decode JSON messages in the debugger thread,
      and one in the GUI thread.
      
      Change-Id: I746f5e203968f7bcc510fb66118c88ef0fd0cd14
      Reviewed-by: default avatarChristiaan Janssen <christiaan.janssen@nokia.com>
      43e20d57
  25. Nov 17, 2011
  26. Nov 01, 2011
  27. Oct 17, 2011
    • Kent Hansen's avatar
      Clean up declarative includes · 7fa3aa4d
      Kent Hansen authored
      
      (This commit is in preparation of moving several files
      to a separate library (QtQuick2).)
      
      Don't add all subfolders to the includepath (from the
      .pri files). There's no good reason to do that.
      
      For headers (both public and private) that are in the
      same folder as the file that includes them, prefer to use
      
       #include "foo.h"
       #include "bar_p.h"
      
      For public headers that are outside the current folder
      but have "unambiguous" names (e.g. qdeclarative prefix), use
      
       #include <foo.h>
      
      For private headers that are outside the current folder, use
      
       #include <private/baz_p.h>
      
      Also change
      
       #include <QtDeclarative/private/foo_p.h>
      
      to
      
       #include <private/foo_p.h>
      
      The header filenames already have a qdeclarative or qsg
      prefix; there's no need to prefix by module name to
      disambiguate.
      
      Finally,
      
       #include "private/foo_p.h"
      
      should be avoided. private/ is used for auto-generated
      (forwarding) headers, which never reside in the current
      (source) directory. Use angle brackets instead.
      
      Change-Id: I04f8477fdba043546064ee276475c09dc373f8f2
      Reviewed-by: default avatarJędrzej Nowacki <jedrzej.nowacki@nokia.com>
      7fa3aa4d
  28. Oct 04, 2011
  29. Sep 21, 2011
  30. Sep 20, 2011
  31. Sep 19, 2011
  32. Sep 02, 2011
  33. Sep 01, 2011
  34. Aug 24, 2011
  35. May 24, 2011