2010/1/10 Arthur Gunn <[email protected]>: > Renaming your app's user model would seem like a very clean and easy > way of doing things. > > I don't see any way of doing things without renaming your app's user > model. The only alternative would be to drop it and patch radiant's > user model with your changes. That's likely to be more trouble than > it's worth, and the only potential advantage it brings you is that > radiant editors can automatically become app editors and vice versa. > > Just call your apps user model Person.
And then go and rename it in every single location, from models to controllers, specs and selenium tests.. I was hoping for another way, as that is going to take a long, long time, and be potentially very fiddly and error-prone. Shouldn't Radiant be using its own namespace for everything? I suppose I could say the same thing about my app, why didn't I use my own namespace? I think I will just host the two apps separately, and use ActiveResource or something to make them communicate when I have to, and get my app to 'download' the layout from Radiant or vice versa. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
