E
Eric Cathell
I am planning on writing an application that has some base
functionality...for instance a basic PIM. But I want to be able to add
functionality to this PIM in the future...but I want to do so in the form of
pluggable modules. This way I can increase core functionality, or implement
different functionality within the new module(this could be for different
locations or different clients). I am thinking the provider pattern is the
way to go with this, and i have looked over the examples but none of them
really go in the direction I think I need to go.
So for instance client A wants a PIM that tracks XYZ information, but client
B wants to track WXYZ information. This would entail a database change to
include W information. however because the plugins are unique...the change
in the database does not affect them. Then if client b wants even different
funtionality it can be added for them at a later time, by working on their
plugin. At a later time client a wants to add POS to the application, they
would receive a new module which is plugged in(obviously this is a common
occurence). This would help to separate the program into various modules and
(in my mind) provide for better maintenance down the road.
So am I right to think that I need to start with the providerbase? Where
could I find examples of what I am trying to do? I have looked at the
quickstarts for the various providerbases...but they are super
specific...any tips?
Eric
functionality...for instance a basic PIM. But I want to be able to add
functionality to this PIM in the future...but I want to do so in the form of
pluggable modules. This way I can increase core functionality, or implement
different functionality within the new module(this could be for different
locations or different clients). I am thinking the provider pattern is the
way to go with this, and i have looked over the examples but none of them
really go in the direction I think I need to go.
So for instance client A wants a PIM that tracks XYZ information, but client
B wants to track WXYZ information. This would entail a database change to
include W information. however because the plugins are unique...the change
in the database does not affect them. Then if client b wants even different
funtionality it can be added for them at a later time, by working on their
plugin. At a later time client a wants to add POS to the application, they
would receive a new module which is plugged in(obviously this is a common
occurence). This would help to separate the program into various modules and
(in my mind) provide for better maintenance down the road.
So am I right to think that I need to start with the providerbase? Where
could I find examples of what I am trying to do? I have looked at the
quickstarts for the various providerbases...but they are super
specific...any tips?
Eric