Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Factory pattern
Message
From
08/04/2011 14:37:01
 
 
To
08/04/2011 14:27:16
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2008 Server
Database:
MySQL
Application:
Desktop
Miscellaneous
Thread ID:
01506688
Message ID:
01506696
Views:
59
I must confess that my brain is still partly in vacation mode. But I would consider having it all in one class, with properties for both the year and for the country. When these two properties are specified, the class should take care of everything else.

>There is a different VFP table (free table) per year and country and the table structure can change while the tables of the previous countries must stay intact for reproducing calculations is necessary.
>
>Therefore we want to encapsulate that completely in those classes where we keep the changing logic separate per country and year.
>
>I am also looking for a not so typical VFP solution, because we can re-use those strategies in future re-writes of the software.
>
>>I guess the difference from year to year, and from country to country, is relatively big? I mean, I guess that it's not possible to let it be data driven?
>>
>>>I'm struggling with a decision that I have to make:
>>>
>>>For every year I have a different taxtable, and that per country.
>>>
>>>For instance:
>>>Taxtable_Aru2010
>>>Taxtable_Cur2010
>>>Taxtable_Aru2011
>>>Taxtable_Cur2011
>>>
>>>I have a class for the countries, and a class for the different taxtables.
>>>
>>>Should I create a factory class which takes as parameter the country and year, and returns the correct object?
>>>
>>>LPARAMETERS toCountry, tcYear
>>>*
>>>LOCAL loTaxTable AS Taxtable OF Taxtables.vcx
>>>*
>>>DO CASE
>>>    CASE toCountry.Name = "Aruba"
>>>        loTaxTable = NEWOBJECT("Taxtable_Aru" + tcYear","Taxtables.vcx")
>>>    CASE toCountry.Name = "Curacao"
>>>        loTaxTable = NEWOBJECT("Taxtable_Cur" + tcYear","Taxtables.vcx")
>>>ENDCASE
>>>*
>>>RETURN loTaxTable
>>>
>>>
>>>Or should I have a factory method in the Country class that returns the correct object for the taxtable?
>>>
>>>LOCAL loTaxTable AS Taxtable OF Taxtables.vcx
>>>*-- Call the factory method in Country.
>>>loTaxTable = loCountry.GetTaxtable(tcYear)
>>>
>>>
>>>What is wisdom here, is there a "right" way of doing this, or is this just a preference what I like more?
>>>One thing I can imaging is that the latter solution violates the single responsibility principle, because the country class should not be made responsible for deciding which taxtable to use. But on the other hand, it is in the context of the country that the decision is done...
>>>
>>>I would like to collect a few cents worth of ideas to buy a factory pattern.
Previous
Reply
Map
View

Click here to load this message in the networking platform