Welcome back, NOFers. Last time, I examined how NakedObjects handles collections, which provide the ability to associate a number of objects with one another (msdn.com/magazine/mt833439). As I went through that piece, however, I introduced the concept of an "action" into the code without really explaining it in any detail. Because actions are the "code" pairing to properties' "data," it makes sense to go over actions in a bit more detail-and in particular, note the places where actions can live and how they appear in the UI. Ready to act naked?
展开▼
