Me too, the Annotations for Service Discovery was enlightening. I like it now. Measuring Simplicity is something I have long cared about; especially API simplicity. I do hope "cool" will not subvert simplicity at the UI level either, as we continue to refine Squeak's UI..
On Fri, Apr 30, 2010 at 4:00 AM, Hannes Hirzel hannes.hirzel@gmail.com wrote:
On 4/30/10, Squeak List squeaklist@yahoo.com wrote:
very cool,
or, if "cool" is the "wrong" word, how about something like: "thank you"?
http://squeakingalong.wordpress.com/
thanx,
ken
Yes, I'd like to join saying thank you to Andreas for taking the energy for the two design criteria write-ups this week which elaborate on and summarize the discussions we had
- Annotations for Service Discovery
April 27, 2010 by andreasraab
There has been an interesting discussion going on in squeak-dev about “annotations for service discovery”. Stated simply, the problem is how a third party package can safely extend system-level services in the face of rapid evolution of the underlying system. In Squeak, this mostly affects the following three areas:
* Preferences. Packages often want to show preferences in the standard preferences tools. * File services. Packages that provide services to operate on files, need to register these. * Menu items. Packages providing UI elements want to register these with the proper menus.
- Measuring Simplicity
April 30, 2010 by andreasraab
* Conceptual Simplicity, measuring how many entities we need to understand what the software does, * Interface Simplicity, measuring how many entities we need to understand how to use the software, and * Implementation Simplicity, measuring how many entities we need to understand how the software does it.
-- HJH