Porting ExpressionEngine to CI |
[eluser]Derek Allard[/eluser]
Zawk. Without more details I can't say, but my "knee jerk" reaction is that if you intend on "copying" EE, you should not look at its source code, for the same reason that programmers working on the Linux codebase can't look at MS code. You don't want to "contaminate" yourself, even accidently. My secondary thought is that EE is already a great, mature product, that serves the same niche you want to serve, and is produced by a company that you (presumably) like and have goodwill for. Why would you want to do this? I'm going to stop short of saying "no", because I truthfully don't know without more details, but I plainly agree that copying the db structure of another app with the intention of mimicking its functionality is just plain wrong. You could try contacting EllisLab sales if you wanted a formal opinion on it - [email protected]. Although I'm employed by EllisLab, this is not a company statement. My personal stance on it would be to discourage such a thing. |
Messages In This Thread |
Porting ExpressionEngine to CI - by El Forum - 08-23-2007, 07:37 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 01:13 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 01:23 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 02:12 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 02:28 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 04:37 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 07:34 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 10:54 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 11:16 AM
Porting ExpressionEngine to CI - by El Forum - 08-24-2007, 12:10 PM
|