Re: configuration files and Framework Dependency

[David E Jones]

-David


On Nov 3, 2007, at 11:28 PM, BJ Freeman wrote:

The CustomTimePeriod entity is not accounting specific. The fiscal period is only one possible type of custom time period. So, yes, this is more general than just the application of it in the accounting component and the entity definition is where it belongs.

I guess missed why timeperiods, a accounting feature, is not in accouning.

Unless you consider Workeffort an overriding component to timeperiods.

specific.
Maybe I misundertood.



David E Jones sent the following on 11/3/2007 9:45 AM:

did you not mention about puttting things in common that are application

What is the broken dependency here? The CustomTimePeriod entity is
defined in the framework/common component, which is one that the
webtools component depends on.


and we should have some sort of accounting-specific time period setup
screen (or screens) in the accounting manager.

-David


On Nov 3, 2007, at 7:14 AM, BJ Freeman wrote:

These definitely need to be modernized to use the form widget and such,

Ok got these Configuration files pulled from the applications in my web

tools.
Was going to put them in SVN till it dawned on me that there is not
suppose to be any dependency.

it has it own page in Webtools.
Since this effects a application, does this not break the dependency
rule?


there is only one pages to maintain or make seperate pages like
timeperiods in Webtools?

The Setup would mostly be a controller that includes all the apps
controllers and a menu for selecting the setup pages throughout the
applications.
and example of a setup page is the Emails for productstores.

now I notice the setting the Timeperiods for Fiscal is in Webtools and So do we want to have another app in the applications that does Setup so

smime.p7s
Description: S/MIME cryptographic signature