Tutorial search

All categories3DS MaxAccessAdobe AcrobatAdobe AuditionAdobe FlexAdobe PremiereAfter EffectsArchiCADArchitectural DesktopASPASP.NETAutoCADAutodeskBlender 3DBodyPaintBryce 3DBuzzsawC++CATIACinema 4DCivil 3DColdfusionCorel DrawCSSDelphiDreamweaverDWF ViewerExcelFireworksFlashFreehandFrontpageFruity LoopsGimpGoLiveHTMLIllustratorImage ReadyInDesignIntelliCADInventorJavaJavaScriptLand DesktopLightwave 3DLinuxMac OS XMapMaya 3DMechanical DesktopMicroStationMySQLOutlookPagemakerPaint ShopPainterPhotographyPhotoshopPHPPoserPowerPointPro/ENGINEERPythonRaster DesignRevitRhino 3DRuby on RailsSEOSolid EdgeSolidWorksSwift 3DSwish MaxTerragenValve EditorVectorWorksVisual BasicVIZWeb DesignWindowsWordXML

So named_scope is great. It's a quick and clear way to share common SQL fragments within your app by defining them in your models. But one aspect of scopes that might not be immediately apparent is how much logic you can strip from your controllers this way.

Keep your controllers clean and forms flexible by adding virtual attributes to your model. This very powerful technique allows you to create form fields which may not directly relate to the database.

Learn how to clean up your code through refactoring. This episode will show you how to move code from the view into the model to remove duplication and simplify the view.

If you want to change something in the layout on a per-template basis, content_for is your answer! This allows templates to specify view code that can be placed anywhere in a layout.

Move a find into the model to clean up the controllers and remove duplication. Also see how you can call these custom find methods through an association.