Part pkg Mixin Refactor - Revision history

Ivan: reverting spam

2009-07-25T23:55:57Z

reverting spam

RaclaLielp at 22:35, 19 July 2009

2009-07-19T22:35:08Z

RaclaLielp at 17:32, 8 July 2009

2009-07-08T17:32:26Z

RaclaLielp at 17:32, 8 July 2009

2009-07-08T17:32:09Z

Ivan: Reverted edits by VitrcNavar (Talk); changed back to last version by Supaplex

2009-04-29T18:56:14Z

Reverted edits by VitrcNavar (Talk); changed back to last version by Supaplex

VitrcNavar at 10:27, 20 April 2009

2009-04-20T10:27:26Z

Supaplex: Reverted edits by TatapAselc (Talk); changed back to last version by Ivan

2008-02-07T15:57:13Z

Reverted edits by TatapAselc (Talk); changed back to last version by Ivan

TatapAselc: siterricdo

2008-02-07T08:29:23Z

siterricdo

Ivan: /* Description */

2007-10-22T22:01:46Z

‎Description

Jayce at 00:11, 3 April 2007

2007-04-03T00:11:51Z

New page

=Description=
I'm looking at refactoring parts of the part_pkg architecture. The previous refactor was great, in that it made it easy to create new plan types, based on perl modules. The current problem that I see is there is only a linear inheritance. What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done. This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not copied and pasted into new sets.

← Older revision		Revision as of 22:01, 22 October 2007
Line 1:		Line 1:
	=Description=		=Description=
	I'm looking at refactoring parts of the part_pkg architecture. The previous refactor was great, in that it made it easy to create new plan types, based on perl modules. The current problem that I see is there is only a linear inheritance. What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done. This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not copied and pasted into new sets.		I'm looking at refactoring parts of the part_pkg architecture. The previous refactor was great, in that it made it easy to create new plan types, based on perl modules. The current problem that I see is there is only a linear inheritance. What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done. This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not copied and pasted into new sets.
		+
		+	''I agree we need more flexibility with price plans and the ability to "mix-and-match" pieces, doing something with Mixins sounds useful.'' --[[User:Ivan\|Ivan]] 15:01, 22 October 2007 (PDT)

@@ Line 1: / Line 1: @@
 =Description=
 I'm looking at refactoring parts of the part_pkg architecture.  The previous refactor was great, in that it made it easy to create new plan types, based on perl modules.  The current problem that I see is there is only a linear inheritance.  What I propose is to move to a Mixin style architecture, as many of the other parts of Freeside have done.  This would allow us to create basic code for concepts such as 'Introrate' or 'Referrals' which could quickly be added to any package type, not  copied and pasted into new sets.
 ''I agree we need more flexibility with price plans and the ability to "mix-and-match" pieces, doing something with Mixins sounds useful.'' --[[User:Ivan|Ivan]] 15:01, 22 October 2007 (PDT)