Programmatically Run Lint
While most people prefer to run SmallLint (Smalltalk Code Critics) from within OmniBrowser, the question arises from time to time on how to do the same from within a workspace script:
While most people prefer to run SmallLint (Smalltalk Code Critics) from within OmniBrowser, the question arises from time to time on how to do the same from within a workspace script:
The code critics tool of the Refactoring Browser points out all kinds of code smells. However, correct spelling of entities in source code is an often neglected smell and remains unchecked by the traditional rules.
A less well known feature of my recent changes and improvements to the Refactoring Browser, and especially the integrated Code Critic tools (including Slime, the Seaside consultant in a box) is the possibility to ignore certain rules on annotated methods. Simply add a pragma to the method you want a certain rule to ignore:
In this screencast I present 3 tools from the refactoring engine and how they are integrated into the OmniBrowser framework.
In this screencast I present 3 new refactorings that were are not part of the original refactoring browser. I use these refactorings on a daily bases and I think that they are a huge time saver.
Over the past couple of months I've been integrating some more refactoring tools with the OmniBrowser framework. This was mostly done as a side-track of different projects: Whenever I needed another feature I added it to my preferred browser framework.
SmallLint is a famous code critics tool for Smalltalk that checks for over 60 common types of code smell and possible bugs. I've added a couple of rules that are targeted at Seaside applications: