Merci, jean-françois Là par contre, je pige pas tout, il propose de lancer version "boucher" et d'y aller à la machette en fonction des injures^Wwarnings qui apparaîssent.
Y'a pas une ptite liste des depreciations ? ---------------- Deprecation Since Rails 1.0 we've kept a stable, backward-compatible API, so your apps can move to new releases without much work. Some of that API now feels like our freshman 15 so we're going on a diet to trim the fat. Rails 1.2 deprecates a handful of features which now have superior alternatives or are better suited as plugins. Deprecation isn't a threat, it's a promise! These features will be entirely gone in Rails 2.0. You can keep using them in 1.2, but you'll get a wag of the finger every time: look for unsightly deprecation warnings in your test results and in your log files. Treat your 1.0-era code to some modern style. To get started, just run your tests and tend to the warnings. ----------------- _______________________________________________ Railsfrance mailing list [email protected] http://lists.rubyonrails.fr/mailman/listinfo/railsfrance
