Traits

Summary: New stable implementation of Traits
Author: Adrian Lienhard, Nathanael Schärli
Owner: Adrian Lienhard (al)
Co-maintainers: <None>
Categories:

SqueakL - The original license of Squeak from Apple. Obsolete since Squeak 4.0 (which only accepts MIT contributions). SqueakL is not recommended to be used for new projects.
Squeak3.7 - Released 15 Sept 2004.
Beta - Useable but still not stable, probably has bugs.
Non official package - Just a package for Squeak, no community guarantees. :)
Squeak - The official distribution of Squeak.

Homepage: http://www.iam.unibe.ch/~scg/Research/Traits
PackageInfo name: <Not entered>
RSS feed:

Description:

* Prerequisite packages: Monticello *

Please find more information and papers about Traits at:
http://www.iam.unibe.ch/~scg/Research/Traits

Our implementation consists of the following parts:

The Kernel: In contrast to the traits prototype, the new traits implementation features a clean, efficient and stable kernel, which is an extension of the traditional Smalltalk-80 kernel of Squeak.

The User Interface: We've started implementing a new traits browser with OmniBrowser. It supports composing and browsing classes and traits and let you "dive" into the composition structure of traits. In addition, the old browser has been modified to show a flat view for programmers who like to view and work with Squeak as it was before.

Monticello: We've made Monticello traits aware, letting you save and load traits (even to SqueakSource). Note, that code which is saved with this modified version of Monticello can not be loaded with a normal Monticello (even if it does not include traits). This implementation should be considered as a prototype and should be refactored.

As an alternative you can also use the normal fileOut mechanism which supports traits as well.

UI Limitations

There are still many features missing that are absolutely essential for getting the real "traits experience", but these are mainly related to the UI and IDE. For example:

- There are no virtual categories that present the conflicts and glue methods of a composite class/trait.
- There is no automatic computation of requirements
- There is no information that shows which traits/classes provide or require the currently selected methods
- There is no support for turning classes into trait
- etc.

The current UI is just a "minimal placeholder" that allows one to start using/playing with traits.

Releases

1-beta1 - Release beta1
2-beta1.1 - Release beta1.1
3-beta2 - Release beta2
4-beta2.1 - Release beta2.1

Back