10 Pines Blog
Patagonia is a conference registration web based system written in Pharo using Seaside, whose main purpose is to fulfill the ESUG conference registration needs. It was developed at 10Pines under the sponsorship of ESUG. It has been develop using some design principles that were “grown” developing other two systems, being Patagonia the latest version of them. These design principle’s objective is the development of “robust” software, that is, software that can easily change in a safe fashion, being at the same time self defensive when used incorrectly and self “teachable” to new programmers of the system.
2 Oct 2010
OOSCM (Object Oriented Software Configuration Management) is a tool we are developing to better support traits that are unique to object oriented development. Current SCM tools (CVS,SVN,GIT,Monticello, etc) are file based solutions, the file is the minimum versionable element, but when developing with objects files are not the elements we manage, we manage and version classes, methods, packages, etc. OOSCM will keep the history of changes of these elements (from basic changes like modifying a method to composite one like renaming a class) providing at the same time means to treat products, baselines, projects, etc. as first class versionable elements with the objective of helping team development in all its steps (programming, integration, etc). The talk provides a description of the tool’s objective, architecture and current development state.
2 Oct 2010
Nowadays, more applications are RIA oriented solutions. RIA (Rich Internet Applications) is a new kind of application with more advantages than traditional applications. It emerges as a combination of features offered by web applications and desktop applications. Even multimedia capabilities are covered because these environments have internal players.
24 Sep 2009
testing smalltalk esug-2009 esug
During the 70s, mutation testing emerged as a technique to assess the fault-finding effectiveness of a test suite. It works mutating objects behavior and looking for tests to “kill” those mutants. The surviving mutants are the starting point to write better tests. Thus, this technique is an interesting alternative to code coverage regarding test quality.
18 Sep 2009