1. 08 Sep, 2011 1 commit
  2. 07 Sep, 2011 2 commits
  3. 06 Sep, 2011 1 commit
  4. 08 Aug, 2011 3 commits
  5. 05 Jul, 2011 1 commit
  6. 24 Jun, 2011 1 commit
  7. 23 Jun, 2011 1 commit
  8. 07 Jun, 2011 1 commit
  9. 20 May, 2011 1 commit
  10. 12 May, 2011 1 commit
  11. 06 May, 2011 2 commits
  12. 04 May, 2011 1 commit
  13. 21 Apr, 2011 1 commit
  14. 13 Apr, 2011 1 commit
  15. 01 Mar, 2011 2 commits
  16. 21 Feb, 2011 1 commit
    • Christian Kamm's avatar
      QmlJS: Remove the strict separation of types and attached types. · 1d4cd9b7
      Christian Kamm authored
      The problem was that several lookup calls suddenly failed because
      the actual QML types were no longer in the default scope chain. However,
      the QML documentation says the type names are in the scope.
      
      Also, 'MyComponent.' in a JS-expression context only showed the attached
      properties of MyComponent and missed the enums.
      
      With this change completion now may offers too many options, but that's
      better than missing some.
      
      This reverts parts of 490f2797
      
      Reviewed-by: Leandro Melo
      1d4cd9b7
  17. 10 Feb, 2011 1 commit
  18. 09 Feb, 2011 1 commit
  19. 12 Jan, 2011 2 commits
  20. 17 Dec, 2010 1 commit
  21. 13 Dec, 2010 2 commits
  22. 07 Dec, 2010 1 commit
  23. 06 Dec, 2010 2 commits
  24. 29 Nov, 2010 4 commits
  25. 25 Nov, 2010 3 commits
  26. 24 Sep, 2010 1 commit
  27. 16 Sep, 2010 1 commit
    • Christian Kamm's avatar
      QmlJS: Speed up Link significantly, provide more info on imports. · c7b3e3c8
      Christian Kamm authored
      Link now caches imports. That means importing the same library (say, Qt)
      from more than one file no longer creates an importing namespace for
      each one. Instead, a single one is created for the instance of Link.
      
      To make this work, the type environment in ScopeChain has been given its
      own type: Interpreter::TypeEnvironment. That has the added benefit of
      being able to carry meta-information about imports. You can use
      TypeEnvironment::importInfo(qmlComponentName) to get information about
      the import node that caused the import of the component.
      c7b3e3c8