This way all the functionality you wish to export via services is  
regrouped in a service provider, rather than scattered in class  
methods as it was in the previous design.

Each service provider implements methods returning the ServiceAction  
objects it wishes to define, and also act as a placeholder for the  
preferences that are set through the UI.

Then the framework has only to search in subclasses of  
ServiceProvider to find all the services defined in the system.

	Romain

Il giorno Sep 15, 2006, alle ore 5:50 PM, stephane ducasse ha scritto:

> romain
>
> why do we need to create a class
>
>> Services will create for you a FooServiceProvider class, a method  
>> category named 'services' in it, and compile the following method  
>> for you:
>>
>>
>
> stef
>
>>
>
>

--
Romain Robbes
http://romain.robb.es



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20060915/2f313977/attachment.htm