2 typos, your grammar
source | link

The question is a bigbit vague (e.g. what exactly do you mean by a third party?), but to try and answer anyway:

I think you're looking for the Observer pattern. The intent of the pattern is to allow entities to be notified when the state of some object changes, while decoupling the two sides. I.e., the observers don't know anything about the subject except that it is observable, and the subject knows nothing about the observers except that they can be notified.

You can register all the modifiers as observers to your app (whatever part of it makes the most sense and is relevant to your situation: the GUI, the Model facade if you have one, etc...), and then you can send them a notification whenever the app's state changes, while keeping all of them decoupled and keeping things flexible.

Edit: If you're using the MVC pattern, thanthen the Model class (more accurately the facade class to the backend system) is probably you'reyour Subject that the observers will listeblisten to, because it stores the state of the app and can notify the observers when anything changes.

The question is a big vague (e.g. what exactly do you mean by a third party?), but to try and answer anyway:

I think you're looking for the Observer pattern. The intent of the pattern is to allow entities to be notified when the state of some object changes, while decoupling the two sides. I.e. the observers don't know anything about the subject except that it is observable, and the subject knows nothing about the observers except that they can be notified.

You can register all the modifiers as observers to your app (whatever part of it makes the most sense and is relevant to your situation: the GUI, the Model facade if you have one, etc...), and then you can send them a notification whenever the app's state changes, while keeping all of them decoupled and keeping things flexible.

Edit: If you're using the MVC pattern, than the Model class (more accurately the facade class to the backend system) is probably you're Subject that the observers will listeb to, because it stores the state of the app and can notify the observers when anything changes.

The question is a bit vague (e.g. what exactly do you mean by a third party?), but to try and answer anyway:

I think you're looking for the Observer pattern. The intent of the pattern is to allow entities to be notified when the state of some object changes, while decoupling the two sides. I.e., the observers don't know anything about the subject except that it is observable, and the subject knows nothing about the observers except that they can be notified.

You can register all the modifiers as observers to your app (whatever part of it makes the most sense and is relevant to your situation: the GUI, the Model facade if you have one, etc...), and then you can send them a notification whenever the app's state changes, while keeping all of them decoupled and keeping things flexible.

Edit: If you're using the MVC pattern, then the Model class (more accurately the facade class to the backend system) is probably your Subject that the observers will listen to, because it stores the state of the app and can notify the observers when anything changes.

1
source | link

The question is a big vague (e.g. what exactly do you mean by a third party?), but to try and answer anyway:

I think you're looking for the Observer pattern. The intent of the pattern is to allow entities to be notified when the state of some object changes, while decoupling the two sides. I.e. the observers don't know anything about the subject except that it is observable, and the subject knows nothing about the observers except that they can be notified.

You can register all the modifiers as observers to your app (whatever part of it makes the most sense and is relevant to your situation: the GUI, the Model facade if you have one, etc...), and then you can send them a notification whenever the app's state changes, while keeping all of them decoupled and keeping things flexible.

Edit: If you're using the MVC pattern, than the Model class (more accurately the facade class to the backend system) is probably you're Subject that the observers will listeb to, because it stores the state of the app and can notify the observers when anything changes.