1. 03 8月, 2010 1 次提交
  2. 02 8月, 2010 2 次提交
  3. 30 7月, 2010 1 次提交
  4. 28 7月, 2010 2 次提交
    • W
      Fix middleware test · eff07495
      wycats 提交于
      eff07495
    • W
      Add a header that tells Internet Explorer (all versions) to use the best... · 123eb25f
      wycats 提交于
      Add a header that tells Internet Explorer (all versions) to use the best available standards support. This ensures that IE doesn't go into quirks mode because it has been blacklisted by too many users pressing the incompatible button. It also tells IE to use the ChromeFrame renderer, if the user has installed the plugin.
      
      This guarantees that the best available standards support will be used on the client.
      123eb25f
  5. 26 7月, 2010 2 次提交
  6. 21 7月, 2010 2 次提交
  7. 18 7月, 2010 1 次提交
  8. 17 7月, 2010 3 次提交
  9. 13 7月, 2010 1 次提交
  10. 07 7月, 2010 1 次提交
  11. 03 7月, 2010 1 次提交
  12. 02 7月, 2010 1 次提交
  13. 30 6月, 2010 2 次提交
    • W
      Create a deprecation behavior that triggers a notification for deprecation... · d4c7d3fd
      wycats 提交于
      Create a deprecation behavior that triggers a notification for deprecation notices, and make the behaviors independent of the environment names.
      
      * In Rails 2.3 apps being upgraded, you will need to add the deprecation
        configuration to each of your environments. Failing to do so will
        result in the same behavior as Rails 2.3, but with an outputted warning
        to provide information on how to set up the setting.
      * New Rails 3 applications generate the setting
      * The notification style will send deprecation notices using
        ActiveSupport::Notifications. Third-party tools can listen in to
        these notifications to provide a streamlined view of the
        deprecation notices occurring in your app.
      * The payload in the notification is the deprecation warning itself
        as well as the callstack from the point that triggered the
        notification.
      d4c7d3fd
    • J
      Push a failing test for issues [#4994] and [#5003]. · 67582f08
      José Valim 提交于
      67582f08
  14. 28 6月, 2010 1 次提交
    • J
      A few changes were done in this commit: · 9b19a6f1
      José Valim 提交于
      * Added :autoload to engines path API and redefine usage to be in sync with 6f83a503;
      * Do not autoload code in *lib* for applications (now you need to explicitly require them). This makes an application behave closer to an engine (code in lib is still autoloaded for plugins);
      * Always autoload code in app/ for engines and plugins. This makes engines behave closer to an application and should allow us to get rid of the unloadable hack required when controllers inside engines inherit from ApplicationController;
      9b19a6f1
  15. 25 6月, 2010 6 次提交
  16. 24 6月, 2010 5 次提交
  17. 23 6月, 2010 1 次提交
  18. 22 6月, 2010 1 次提交
  19. 21 6月, 2010 2 次提交
  20. 20 6月, 2010 3 次提交
  21. 19 6月, 2010 1 次提交