Closed AlyceBrady closed 10 years ago
This probably entails moving all the Ramp stuff under models to the library directory, renaming them along the way (from Application_Model_xxx to Ramp_Model_xxx). This approach cannot be extended to the controllers and views, however; the Ramp controllers will need to stay in the application/controllers directory. Smart controllers could probably be placed in application/controllers/smart (or, alternatively, maybe Ramp controllers could be placed in application/controllers/ramp).
One advantage of separating Ramp from Smart would be if customized screens, reports, or procedures start to fill up the controllers or models directories, making it harder to find what one is looking for.
Put Ramp and Smart in different modules? Other application controllers could go in their own modules?
May be worth delaying doing this, since no one is using Ramp without Smart yet (we're not yet at Ramp 1.0 nor even Ramp 0.8), Smart provides a better testing environment for Ramp than the simple Ramp demos we have, and we want the latest Ramp when working on Smart stuff. Keeping up with updates across two repositories would probably be more hassle than it's worth at this moment in time.
I'm labeling this a feature, since having Ramp as a separate, independent application could be considered a new feature at this point.