Skip to content
Snippets Groups Projects
  1. Sep 08, 2011
  2. Sep 07, 2011
  3. Sep 06, 2011
  4. Aug 08, 2011
  5. Jul 05, 2011
  6. Jun 24, 2011
  7. Jun 23, 2011
  8. Jun 07, 2011
  9. May 20, 2011
  10. May 12, 2011
  11. May 06, 2011
  12. May 04, 2011
  13. Apr 21, 2011
  14. Apr 13, 2011
  15. Mar 01, 2011
  16. Feb 21, 2011
    • 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. Feb 10, 2011
  18. Feb 09, 2011
  19. Jan 12, 2011
  20. Dec 17, 2010
  21. Dec 13, 2010
  22. Dec 07, 2010
  23. Dec 06, 2010
  24. Nov 29, 2010
  25. Nov 25, 2010
  26. Sep 24, 2010
  27. Sep 16, 2010
    • 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
Loading