[Erp5-dev] tutorial
Kevin Deldycke
kevin at nexedi.com
Mon Apr 25 19:39:29 CEST 2005
Le Mercredi 20 Avril 2005 12:39, Yoshinori Okuji a écrit :
> On Wednesday 20 April 2005 02:29 pm, Kevin Deldycke wrote:
> > So the PaySheetTransaction is a subclass of the Folder Class. That's a
> > fact. When I have build the payroll system, I used Accouting Transaction
> > module as a model. And at this moment, Folder was a parent of
> > AccountingTansaction (and it's always the case). If you think that this
> > class relationship is not correct, please tell me.
> >
> > In my paragraph I try to explain why PaySheetTansaction is not a subClass
> > of any of the 5 basic class : because PaySheetTansaction is a place where
> > paysheet-related objects are stored. Folder is just a utility class to
> > classify and regroup objects. If you have a better way to explain this, I
> > will be happy.
> >
> > "objets de type PaySheetTransaction vont nous servir à regrouper au même
> > endroit les objets relatifs à une feuille de paie" -> We will use
> > PaySheetTransaction objects to store every paysheet-related sub-objects
> > (like PaySheetLine and PaySheetTransactionLine).
>
> Thank you for your help. I now understand what you meant.
>
> But this suggests that ERP5 actually has 5+1... This is a bad sign.
No no no. The 5 basic classes are designed to represent any businness in any
company. The "+1" class has no connection with the Universal Business Model.
It's just a convenient way to classify documents and it doesn't change the
fundamental model. The rules and statements that drive the UBM are not
invalidated by removing the "+1".
So IMO it's not a bad sign.
More information about the Erp5-dev
mailing list